On this page
Active used repeatedly Started May 2026

Agent Rally Point

Coordinate coding agents across models with shared claims, decisions, handoffs, and receipts.

Product overview Demo Source Code
Rust Python SQLite tmux cmux ptyd

Rally gives agents a shared account of the work

When several coding agents share a project, each needs to know who owns a file, what another agent changed, and whether a requested review reached its recipient. Agent Rally Point records those facts in one local ledger. Codex, Claude Code, Cursor, and other hosts can use the same CLI protocol because coordination does not depend on a model provider.

The shared record reduces the status work an operator has to reconstruct across separate conversations. It also gives each agent a place to check before acting and a durable way to report the result.

Agents claim work, report results, and acknowledge handoffs

  1. An agent joins with its own identity and reads the current room, lead, mission, and claims.
  2. Before editing, it claims the file or other resource it needs. Rally refuses an overlapping exclusive claim and names its holder.
  3. The agent performs the work, records an artifact or blocker, and releases its claim.
  4. A receiving agent writes a receipt for a handoff. The sender can then distinguish delivery from acknowledgement and completed work.

Configured host hooks can check file claims before edits. That edit-time check warns by default; strict mode can stop a conflicting edit when the host honors the result. Rally does not lock files against arbitrary writes, so agents still need separate worktrees and disciplined ownership for concurrent changes.

The ledger keeps history separate from the current view

Rally appends typed facts to a local JSONL log. It derives current claims, blockers, decisions, and next actions in a rebuildable SQLite view. Losing the cache does not erase the history. The CLI works without a central server or a model call; Git or another file transport can move facts between machines.

Managed terminal panes can deliver a recorded handoff immediately. Delivery alone does not prove that the recipient read or accepted it. Rally waits for a receiver-authored receipt, and a completed task needs its own result and verification evidence.

The protocol stays smaller than the work it coordinates

Rally records ownership, decisions, and evidence; the coding host still edits files and runs checks. Its default boundary checks are advisory, and it does not make simultaneous edits safe. The public installation guide explains the CLI baseline and the separate host-specific hook setup.