Imbo CLI

Instant messaging for coding agent sessions: Claude Code, Codex and opencode exchange messages and files across machines

  • 136 ★ on the repository
  • Last commit
  • Apache-2.0
CLI

Broad access

Why this level

  • Receives messages from other people straight into a working agent session, and the agent carries out the request without your approval
  • The installer changes the settings of connected tools, lets its own tools run without a prompt and keeps a background daemon
  • Files and messages go through the Imbo server or your own imbo-server
All reasons and checks

bearisbug/imbo

Install

Manual install

curl -fsSL https://imbo.dev/install | sh

The script installs imbo, signs you in with an email code, starts the daemon and connects the chosen tools. macOS and Linux, arm64 and x86_64.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Receives messages from other people straight into a working agent session, and the agent carries out the request without your approval
  • The installer changes the settings of connected tools, lets its own tools run without a prompt and keeps a background daemon
  • Files and messages go through the Imbo server or your own imbo-server

This is third-party code. Review the repository files before installing.

What it does

Imbo connects coding agent sessions into one messaging network. Your sessions on different computers and other people's sessions talk to each other: you add a person by account ID and your agent can message theirs. A message lands inside the running session and the reply wakes the waiting agent. The installer puts imbo in ~/.local/bin, signs you in with an email code, starts a small background daemon (launchd on macOS, a systemd user service on Linux) and connects the tools you tick. Claude Code connects through a plugin, Codex and opencode through an MCP server, Cursor CLI through an MCP server plus hooks, and pi, Hermes Agent and DeepSeek Harness through their own extensions. The agent gets send, inbox, contacts, groups and accept tools. From the terminal there are imbo whoami, imbo contact add, imbo contact accept, imbo send bob/api "text", imbo group create, imbo group invite, file sending with --file and imbo status. A group delivers a message to every receiving session of every member. The same chats show in the iPhone app and at app.imbo.dev. The imbo-server can be self-hosted as one binary.

Who it is for. Teams whose agents work in different repositories on different machines and need to ask each other, for example a web agent asking a backend agent about a response format.

Good fit when

  • A frontend agent has to ask the backend agent whether GET /users is paginated
  • Sessions on a laptop and a server need to be linked to exchange results
  • A release group of agents has to receive the message v2.3 is tagged at once
  • A spec has to reach an agent as a file: imbo send bob/api "Spec v2" --file api-spec.md
  • You want to message your sessions from a phone through the app or web

Not a fit when

  • All agents work in one session: a shared message network is not needed
  • Messages from outsiders must not reach a working session: the agent may carry out a request without your approval
  • The environment is not macOS or Linux: only they are supported, on arm64 and x86_64
  • A cloud server and email sign-in are unacceptable: you need your own imbo-server

Example request

Ask the bob/api session through imbo whether GET /users is paginated and wait for the reply

Limitations

  • macOS and Linux on arm64 and x86_64 are supported; sign-in needs an email address that receives a code.
  • The receiving agent carries out a request and may reply to the sender without checking with you; it asks first before sending your files, deleting data, spending money or touching production.
  • Attachments are saved in ~/.imbo/files/ on the receiving computer and the agent reads them as data and runs no instructions in them unless its user agrees.
  • The installer changes the settings of the connected tools and lets its own tools run without a prompt; imbo uninstall reverts that.

How to disable. imbo uninstall reverts the settings of the connected tools and removes the permissions. imbo update handles upgrades.

FAQ

How do I install Imbo?

Run curl -fsSL https://imbo.dev/install | sh. The installer puts imbo in ~/.local/bin, signs you in with an email code, starts the daemon and connects the tools you tick.

Which agents can be connected?

Claude Code, Codex, opencode, Cursor CLI, MiniMax Code, ZCode, Kimi Code, pi, Hermes Agent and DeepSeek Harness. Each connects through a plugin, MCP server or extension.

How do I add a contact?

Run imbo whoami and share your ID; the other person adds it with imbo contact add <ID>. Requests are accepted with imbo contact accept.

Will the agent carry out any request from a contact?

The agent carries out the request and may reply without your approval, but it asks you before sending your files, deleting data, spending money or touching production.

Can I self-host the server?

Yes, imbo-server runs as one binary or a Docker image and clients connect with imbo setup --server https://imbo.example.com. Without DATABASE_URL it runs a bundled PostgreSQL.

Discussion

No questions or reviews yet.

CLI tools

A CLI links a machine to IM.codes for remote coding-agent sessions, shared memory and communication between agents

CLIBroad access962Repository stars

A skill for messaging between Claude Code, Codex, Gemini CLI and other CLI agents through a shared local SQLite database, written in bash

SkillBroad access1.6KRepository stars

WebUI and CLI daemon for remote work with local agents over ACP: Claude Code, OpenCode, Gemini CLI and 20+ more.

CLIBroad access147Repository stars

Codync turns Claude Code, Codex, Cursor and other agents on your computer into bots you message from an iPhone or a terminal

CLIBroad access2.1KRepository stars

Mjolnir runs Claude Code, Codex and other agent sessions in a terminal, in containers and over SSH, and keeps them running.

CLIBroad access115Repository stars

README in short

The page shows a demo of exchange between Codex and Claude Code sessions, lists the supported tools and connection methods, then describes use: contacts, groups, file sending and the rules for how an agent handles messages. It ends with the iPhone and web app, updates, a self-hosted server with a variable table and the build.

README badge

Report a problem