Skip to content

Add Bodega One Code#427

Open
Mayimbe07 wants to merge 3 commits into
agentclientprotocol:mainfrom
Mayimbe07:add-bodega-one-code
Open

Add Bodega One Code#427
Mayimbe07 wants to merge 3 commits into
agentclientprotocol:mainfrom
Mayimbe07:add-bodega-one-code

Conversation

@Mayimbe07

Copy link
Copy Markdown

Adds Bodega One Code — the terminal surface of Bodega One: a local-first AI coding agent (TUI + headless) for macOS/Linux/Windows that runs fully offline against local models (Ollama, llama.cpp) or BYOK cloud providers, with a hard air-gap mode and verified edits.

  • ACP entry point: bodega serve --acp (JSON-RPC over stdio; the bundle carries its own Node runtime and backend — no prerequisites)
  • Binary distribution for all five platforms from the public releases repo; versions there follow v* tags
  • Icon: 16×16 monochrome currentColor SVG

A note on the authentication requirement: Bodega One Code is local-first and requires no account — its ACP initialize response advertises an explicit authMethods: [] (there is nothing to authenticate; sessions work immediately against local models, and cloud keys are user-managed app config rather than an ACP auth flow). We read AUTHENTICATION.md as targeting agents that need credentials to function; if the registry requires a declared auth method even for no-auth agents, we're happy to adapt — guidance welcome.

Disclosure: this submission was prepared with AI assistance, reviewed and approved by the Bodega One maintainers.

Mayimbe07 and others added 3 commits July 6, 2026 18:50
v0.1.0 hung on `serve --acp` (Auth check timed out at 5m). v0.1.1 fixes the
ACP initialize handshake; point the distribution archives at the v0.1.1 release.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Mayimbe07

Copy link
Copy Markdown
Author

Bumped this submission from v0.1.0 to v0.1.1 (0d8e7ad61aab13).

The earlier red Auth (bodega-one-code) check was a serve --acp startup hang in v0.1.0 that ran into the 5-minute job timeout. v0.1.1 fixes the ACP initialize handshake so the agent responds immediately without waiting on a local model/backend, and the distribution archives now point at the v0.1.1 release.

Could a maintainer approve / re-run the workflow when you get a chance? The current action_required run is against the stale v0.1.0 binary. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant