You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v0.22.0 — any agent in any role, with measured orchestrator capability
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Any agent can be offered for any role. The registry's roles array no longer gates the pickers. Every detected agent appears for orchestrator, coder, reviewer, scout and integrator; roles is kept and documented as informational so existing readers keep working.
Orchestrator capability is MEASURED, not declared. og now probes Omnigent's own harness capabilities (capabilities[<harness>].subagents) to decide whether an agent can actually dispatch sub-agents, caching the result and falling back to the registry relay flag when Omnigent is not importable from the installer's interpreter. Every message says which source answered. An acp:<slug> harness resolves through the shared acp key first.
The capability list is visible../install.sh --check prints an orchestrator-capability block, and --questions carries a structured per-agent dispatch map ({can, source}) on the orchestrator question alongside the existing human-readable note — so an AI installer never has to parse prose to learn whether an agent can orchestrate.
Delegated worker tabs carry the vendor glyph. In og herdr, a worker's tab read coder_cmdcode:fix-stale-comments, repeating the agent name already drawn as a mark in og agents. It now reads ⌘ fix-stale-comments, resolved through the same chain the pane uses so a tab and its row can never disagree about a worker's brand.
Fixed
Six registry rows claimed a dispatch capability they do not have.agy, cursor, gemini, goose, hermes and grok were all marked relay: true while their harness reports subagents=False. grok was additionally offered as an orchestrator, so the installer would happily have built a brain that could never delegate — and nothing would have said so until the first real dispatch.
devin pointed at a harness id that has no capability entry at all (devin rather than devin-native), so the preflight map would have dropped the worker. Repointed; devin-native measures subagents=True, and the row stays flagged unverified_roles: ["orchestrator"] until a real run proves it.
A refusal now names the fix in the same sentence as the fault: cmdcode cannot be the orchestrator: omnigent reports harness 'acp:command-code' (via shared key 'acp') cannot dispatch sub-agents, so it could never delegate. Orchestrator-capable agents here: claude, opencode, codex, devin.
Changed
Former hard refusals for non-orchestrator roles are now warnings. An unverified row or an unknownprompt_delivery warns and proceeds — the first real dispatch is the proof, so neither may block an otherwise-legal install.
Docs
AGENTS.md and the registry header now describe roles as informational and relay as a fallback used only when the measured probe is unavailable.