OrgBots

Your AI agents, working together.

Coordinate specialist agents around one project, keep their changes in separate workspaces, and review what reaches your source tree.

Install OrgBots See the verification record
OrgBots room usage view showing room status and per-provider token accounting. The values are seeded fixture data, not live usage.
Product screen from a seeded fixture. Values shown are examples, not a real provider run.
Now available: OrgBots 2.0.0 for Ubuntu 24.04 amd64 through a signed APT repository.

Keep each agent’s work reviewable.

Agents use isolated project copies. OrgBots compares each copy with the project before integration and surfaces conflicts and deletions for owner review.

When an agent changes the same file as the owner, integration stops and shows the conflict. Replacing or removing an existing file requires a writable ext4 drive mounted at /mnt/hdd; originals go to /mnt/hdd/OrgBots Trash.

  • Separate copies preserve the project while agents work.
  • Conflict review keeps overlapping edits out of the integration step.
  • Deletion approval names the exact files before they move to Trash.

Read the workspace safety guide

OrgBots approval dialog listing the exact deleted project file that will be moved to the owner's Trash drive before applying changes.
A synthetic fixture shows the exact deletion awaiting owner approval.

Follow the work and its usage.

Rooms preserve the work session. Usage records separate input, output, cache reads, and cache writes by provider and agent.

OrgBots usage report listing room and agent token categories, with API-backed spend and subscription API-equivalent cost separated.
Seeded provider report. API spend and subscription equivalents are labeled separately.

Use the room history to pick up work, answer an agent’s question, and inspect what each provider contributed. When the provider returns enough data, OrgBots records token categories and API cost estimates.

  • Subscription usage stays distinct from actual API charges.
  • Missing usage or pricing remains unknown.
  • Local CLI subscriptions and provider API keys are managed separately.

Read what has and has not been measured

Keep a team session in one place.

Rooms carry questions, notifications, attachments, previews, and background work alongside each project. Bring your installed tools and review each permission request.

The specialist preset uses Astra for code and security coordination and review, and Julian (Opus) for design and architecture coordination. Choose the available models and roles for each room. Codex, Claude, and Grok CLI use their installed Linux accounts. API providers and an Ollama endpoint can be configured separately.

  • Project context: work with files, Git, MCP tools, and skills available through installed tools, subject to their permissions.
  • Continuity: return to the room history, open questions, notifications, and ongoing work.
  • Portable backups: private backups are unencrypted and capped at 64 MiB.

See the release scope and verification record

OrgBots synthetic fixture showing an agent change with a conflicting project path.
Synthetic fixture data. See the evidence page for the full test limits.

Start with your existing provider setup.

OrgBots uses the Codex, Claude, and Grok command-line accounts already installed on Linux, or DeepSeek API keys or a configured Ollama endpoint.

Install the package

Ubuntu 24.04 amd64 is the currently supported Linux target. The installer pins the APT signing-key fingerprint.

Connect your providers

Your CLI subscriptions and API accounts remain with their providers. Their billing and terms still apply.

Review each integration

Agents prepare changes in private working copies. You review conflicts and protected removals before they apply.

Read installation instructions and prerequisites

Make the next coding session easier to follow.

Install for Ubuntu