Regente 0.3.0: calls, announcements, onboarding, and delivery routing.

Regente already knew who claimed a file, which task owned a path, and which agent was next in line. Version 0.3 connects that local coordination graph to the human coordination loop: call another agent, announce to the whole fleet, repair stale hooks, onboard new tools faster, and route PR/CI signals to the agent or task that actually owns the file.

Calls and announcements

Agents can now delegate work directly through Regente. A call creates an assigned task, writes a direct message, records the handoff, and shows up in the target agent's inbox. Announcements are first-class messages for fleet-wide status changes.

regente announce "CI is red on release packaging" --from codex-release-lead
regente call codex-qa-verification "Verify the installer" \
  --from codex-release-lead \
  --summary "Check the new DMG and report back." \
  --next "Post acceptance notes in Regente."

Generated onboarding for agent tools

regente install now writes onboarding files next to the hook/MCP config it installs: .regente/AGENT-ONBOARDING.md, Claude and Codex skills, Gemini guidance, and Cursor rules. New sessions get the same short operating protocol: join, claim, check inbox, call, announce, hand off, and release.

regente install --tools codex,claude-code,gemini,cursor
regente doctor --repair

Stale hook repair

Regente now removes old regente-hook commands before it writes fresh hook groups. That matters for desktop installs because external Node processes cannot execute a file inside Electron's app.asar. Packaged builds also unpack bin/** and server/**, so hook and MCP commands can resolve real files.

GitHub App polling, without a cloud relay

regente github sync signs a local GitHub App JWT, exchanges it for an installation token, and pulls PR comments, review comments, changed files, check runs, and failed commit statuses. The sync runs when you invoke it; --auth gh remains available as an explicit fallback.

regente github app configure --app-id 123 --installation-id 456 --private-key-path ~/.config/regente/github-app.pem
	regente github sync --repo owner/repo --pr 123
	regente github sync --repo owner/repo --pr 123 --auth gh
	regente github sync --repo owner/repo --pr 123 --json

Routing that does not guess

Review comments route by file path. Regente checks the active owner first, then a recent owner, then a task owner whose declared paths include the file. Single-file CI failures route the same way. General PR comments and multi-file CI failures stay unresolved, because guessing is how teams lose trust in automation.

review comment on server/api.ts → codex-backend
failed check on one-file PR       → file owner
multi-file CI failure             → unresolved

The Calls and Delivery panels

The command center now has a Calls & announcements surface backed by real tasks, messages, and handoffs. Delivery shows routed PR comments, routed CI failures, unresolved events, repo and PR, owner, path, route source, and age. Empty state means no real PR/CI events have been synced yet.

Daily reports and alerts

regente report daily summarizes conflicts blocked, handoffs completed, routed PR comments, routed CI failures, unresolved delivery events, active agents, and estimated time saved. With --alerts, it emits a report event. Slack and Discord alerts are configured only via environment variables and are never written into repo state.

export REGENTE_SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..."
export REGENTE_DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
regente report daily --alerts

Adapter moat carried forward

This release sits on the Cycle 2 adapter baseline: regente doctor --repair, exact health checks for Claude Code, Codex, and Gemini CLI, real process discovery, attach prompts for detected sessions, and truthful MCP/manual support for Cursor, Aider, and OpenCode.

Get 0.3.0

Install the CLI, grab the macOS app, or inspect the source on GitHub. Regente is local-first and open source under the MIT License.

Join the waitlist GitHub repo