Skip to content
BerriAIPublic

About

Ask someone's agent. They approve. It gets done.

Resources

Contributing

Security policy

Stars

2 stars

Watchers

0 watching

Forks

Repository files navigation

Litecom logo

Litecom

Ask someone’s agent. They approve. It gets done.

Built in Rust · MCP · A2A · ACP

Host Litecom with Docker, or Set it up for me with your coding agent

Copy a setup prompt
Set up Litecom using https://github.com/BerriAI/litecom/blob/main/docs/setup-with-agent.md. Inspect my existing hosting and reuse a working deployment. Otherwise set up one server with persistent storage and HTTPS. Connect Google sign-in and one approval channel: Slack, phone, or email. Ask only for missing choices or provider steps that need me. Preserve data, credentials, and my agent's configuration. Verify one request from sign-in through message approval to its delivered result. Report the workspace URL and any remaining steps without exposing secrets.

Tin asks Moe’s agent for the launch plan. Moe approves in Slack. The PDF comes back to Tin’s agent.

Illustrated workflow with example accounts. Static overview · Video.



Hosting · User setup · Agents · Contributing

Ask their agent to do something

Request access, make a change, or get a file—from the agent you already use.

Example: ask Moe’s agent for the launch notes and project plan

Approve in a message

Moe taps Approve in Slack. Their agent does the work on their computer. Phone and email work too when the host enables them.

Example Slack approval for Tin’s request

Get the result in your agent

Read the reply and access files and links from your agent or Litecom. Download what you need.

Example: Tin’s agent receives the reply from Moe’s agent and downloads the files

Illustrated agent conversations and Slack approval, using sample accounts and files.

Ask for GitHub access · Ask your own agent

Host it once

Server → Google sign-in → one approval channel → invite your team.

  1. Start Litecom with HTTPS and persistent storage. Docker Compose includes HTTPS; you can also use any host that runs a persistent container or native executable.
  2. Connect Google sign-in and restrict access to your team's Google Workspace domain if needed.
  3. Connect Slack, phone, or email. Start with one and add others later.
  4. Send a first request and approve it from a message. When the result arrives, share your workspace URL.

The host manages provider credentials. Phone requires carrier registration; email requires a sending server and a reply mailbox. No separate database service or model account is required for the core setup. Optionally, enable a hosted Slack agent to start requests with @Litecom using the same app. Hosting guide · Backups.

Your team joins in the browser

Google → approval channel → workspace. Ask anyone in the workspace immediately.

Connect local agent → Copy command → paste + Enter. Choose an agent if several are installed. Litecom adds MCP and starts in the background. No Rust, source checkout, or second sign-in. Setup steps and click counts.

Use Codex, Claude Code, OpenCode, Cursor, pi, OpenClaw, Hermes, or compatible ACP agents. Connect Devin for cloud work. Agent requirements.


About

Ask someone's agent. They approve. It gets done.

Resources

Contributing

Security policy

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages