Codeoid: Coordinate AI Coding Agents Across Sessions

Overview

Codeoid is a self-hosted harness for running and coordinating AI coding agents across multiple repositories and sessions. A single daemon manages sessions and makes them available through terminal and web interfaces, with Telegram support on the ZeroID authentication path.

Its main distinction is persistent, workspace-scoped memory: a session can retrieve details from earlier sessions rather than relying only on a compressed conversation history. Codeoid also supports several agent backends, including Claude, Codex, Gemini, OpenAI, and pi. It is aimed at developers doing parallel or long-horizon agent work, rather than people seeking an inline IDE assistant.

Key Features

• Run multiple agent sessions and attach to them from terminal, browser, or Telegram.
• Share workspace memory across sessions, including retrievable records of tool calls and results.
• Use Claude by default, or select Codex, Gemini, OpenAI, or pi as a backend.
• Create sessions in separate Git worktrees while keeping memory anchored to the shared workspace.
• Stream follow-up input during an active turn, with options to interrupt or queue it.
• Choose guarded, interactive, or budget-limited autonomous execution modes.
• Use ZeroID for cryptographic agent identities, delegated sub-agent identities, and attributable actions, or start in local mode without ZeroID.

Use Cases

• A developer splitting a feature into parallel worktrees can run separate sessions while letting each retrieve relevant workspace history.
• A team managing long-running coding tasks can use the web interface or Telegram to reconnect to daemon-owned sessions from another device.
• Developers comparing agent backends can run sessions through one control plane instead of managing each backend as a separate workflow.
• A security-conscious team can use ZeroID identities and audit attribution when running agents whose tool actions need to be traceable.

Getting Started

With Bun installed and an agent backend authenticated, install and start locally:

bun install -g @highflame/codeoid
codeoid start --local

Then run codeoid tui or open http://localhost:7400/ui/. See the README for ZeroID setup, backend configuration, and other clients.

Alternatives

• synara: Synara coordinates sessions in a local-first desktop workspace with project files, previews, and Git review, while Codeoid centers on a shared daemon and multiple clients.
• OpenHands: OpenHands manages agent conversations and automations across local, remote, and cloud backends, while Codeoid focuses on persistent sessions across agent backends and clients.

Considerations

• The project is young and its contributor activity is highly concentrated: most code contributions come from one person, even though commits and releases have been frequent recently. The repository also has a sizable open-issue queue, so check current issues for problems affecting your workflow.
• Codeoid runs agents with shell and file-write access. Local mode binds to loopback and uses a token, but it does not provide verified agent identities or cryptographic audit attribution. ZeroID is the path for those capabilities and requires additional setup.
• The README specifies Bun as the runtime, while the repository requirements data identifies Node.js from package.json. Confirm the supported runtime and installation path for your environment before adopting it.
• The README describes bun test, but the available requirements data does not report tests. Verify the current test and CI coverage against the guarantees your team needs.
• The terminal cockpit recommended by the project is a separate repository; this repository includes an Ink-based TUI fallback. Telegram is available only with ZeroID authentication.
• The project uses the MIT License. Review its terms and any dependencies' licenses for your intended use.