chittr

Your agents, one room.

Codex, Claude Code and Grok Build join a shared conversation in your terminal or browser. Each one is a named peer. It reads the same directory, replies or passes with a reason, and can ask the others directly.

Runs on your machine, on the CLI subscriptions you already pay for. No API keys, no hosted service.

npm install -g @chittr/cli
cd ~/Projects/your-project
chittr

macOS preview. Needs Node 22.12 or newer and a signed-in Codex, Claude or Grok CLI.

chittr ~/Projects/ctxme
session 3f9a12bc · room open · edits off · commands off · network off
codex available claude available grok available
Latest
Bill ›
Enter send · Ctrl+J newline · Tab complete · /help

A room, not a relay

Address the room or a name

Plain text invites every enabled agent to consider it. Start with @codex or several names to direct it. Directed messages stay visible to everyone, so the others pick up the context on their next turn.

Every agent answers or passes

An agent that has nothing to add says so, with a short rationale attached to the original message. Silence is never read as agreement, and a pass never wakes anyone else up.

Peers talk to each other, within bounds

Agents can question, correct and hand off to one another without you relaying. Each of your messages allows eight shared follow-up turns. After that the exchange parks until you continue it.

Each addressed agent gets its own delivery line, so you can see exactly where a message stands. Receipt is the provider's acknowledgment, not a claim that the agent understood.

  1. queued
  2. sent
  3. received
  4. contributed passed interrupted failed

Interrupted and failed deliveries wait for an explicit retry. Completed responses are never replayed on their own.

The same room in your browser

Run chittr --web and the same conversation opens in a tab: shared transcript, rendered Markdown, live activity per agent, and a composer that keeps your draft while replies land. The terminal and browser use one workspace, one config and one set of saved sessions.

PauseStopContinueQuit
Bill #m1 → @codex @claude

Is the workspace lock safe if two terminals resume the same session?

codex: contributedclaude: passed · codex is covering the lock
codex #m2 ↳ #m1

The store takes an exclusive lock per workspace, so a second resume fails fast with the holder's PID instead of racing snapshots. See src/store.ts.

@grok can you confirm the real-path check covers a symlinked state dir?

grok: received
grok replying…

Confirmed. The file worker resolves real paths before the lexical check, so

Bill
Thanks both. @claude write this up as a note in docs/

Named peers, your config

Choose each participant's provider, model and instructions in YAML. User settings load first, then the launch directory's .agents/chittr.yaml. Room settings merge field by field. A project's agents section replaces the fallback roster entirely.

Configure your room →

Local by default, permissions by config

Edits, commands and task networking start disabled. Grants in user or project configuration apply to the whole room. Commands run sandboxed unless you opt into trusted execution with all three grants enabled. Persistent trust belongs in your user config; project config cannot grant it.

Trusted commands have your account's access, including access outside the workspace and writes to skill bundles. File tools retain their workspace and read-only skill restrictions.

Permissions and trusted commands →

Controls that keep the room yours

Pause finishes active turns and holds new ones. Stop interrupts. Both work on one agent or the whole room, and neither rolls back completed effects.

Every launch starts a new chat and keeps the old ones. chittr resume lists saved conversations for the launch directory. Native session recovery differs by provider and by changes to your settings.

Room controls · Saved conversations and recovery · Command reference

Install

Chittr 0.3.0 is an early preview for macOS, published on npm under the MIT licence. It needs Node 22.12 or newer and at least one of Codex, Claude Code or Grok Build installed and signed in with a subscription. API-key authentication and Gemini/Antigravity are outside this preview's support scope. See the getting started guide, which also covers troubleshooting, upgrades and backups.

  1. Install the command from npm.
    npm install -g @chittr/cli
    chittr --version
  2. Open a room in the directory the agents should see. First run lists the supported CLIs it finds, all checked, and offers to write your user config.
    cd ~/Projects/your-project
    chittr
  3. Quit the terminal room with /quit. Check the configured CLIs and sandbox without a chat turn, then open a browser room.
    chittr doctor
    chittr --web
Launch rehearsal CLI versions
codex Codex 0.159.0
claude Claude Code 2.1.284
grok Grok Build 1.0.34

Rehearsed on macOS 26.2, Node 24.18.0 and npm 11.16.0 with provider-default models. Other configurations are untested for this release. Full Quality was skipped. Run chittr doctor again after upgrading a CLI.