Custode 0.1.0

Custode 0.1.0

Custode 0.1.0 is a private, source-installed, single-operator local alpha. It proves one complete operating loop: configure a Claude or Codex agent with its own checkout, give it bounded repository work through the dashboard or MCP, handle questions and approvals, inspect the result, and recover durable context after a restart.

Highlights

• One operator surface across the LiveView dashboard, mix custode CLI, and authenticated MCP endpoint.
• Guided empty-fleet setup with caretaker, backlog worker, steward, specialist, tutor, and bespoke agent shapes.
• Claude and Codex routines through released oban_claude and oban_codex packages.
• Custode-managed repository clones so agents do not share the checkout running Custode.
• Durable activity, conversation arcs, gates, notebook state, handoff context, and operator messages.
• Human approval for repository writes, with gate class and risk recorded for review.
• Generated reference documentation for the complete MCP tool, prompt, and resource surface.
• A standing custode-dev maintenance routine completed the 0.1.0 quickstart work through an owned checkout and merged PR #659.

Start with guides/demo.md for the complete fresh-home path.

Release proof

• Tested tag commit: 68c4b120bc21d1b0ff0a90567ca55e8279b2d3d7.
• A fresh GitHub checkout and fresh CUSTODE_HOME applied all 42 migrations, passed mix custode doctor, and booted an empty fleet.
• The browser setup created a Codex specialist with a managed clone and a weekly schedule without editing TOML or cron.
• The real worker turn reported the exact checkout commit and verified guides/demo.md; both checkouts remained clean.
• After a process restart, the roster, managed checkout, provider-session state, conversation, and result were reconstructed in the dashboard.
• Formatting, warning-free compilation, strict Credo, 1,751 tests, and Dialyzer all pass on the tagged commit.
• GitHub Actions could not execute because the account spending limit was exhausted. The release result comes from the complete local gates above.

Known limitations

• This release supports one local operator and one Custode instance. The dashboard and MCP server listen on localhost; remote access is operator-managed.
• Installation is from source. The pinned mcp_ex dependency remains private and requires repository access or a local path override.
• Scheduled queues currently depend on the Claude boot diagnostic even on a Codex-only host. Direct dashboard and MCP messages to Codex routines still work; the demo guide documents the preflight.
• Scheduled beats start fresh provider sessions. Operator conversations can retain a resumable provider session, while portable context lives in Custode's durable records.
• General automatic routing, missions, Git-backed research subjects, generated MCP tools, hosted authentication, and a native desktop shell remain roadmap work.