trio-omnigent

Omnigent agents are registered by bundle upload, not by scanning an agents directory; omnigent CLI has no agent command. The dashboard install (via install.sh --dashboard) renders all canonical agents to each harness's native format and registers them: for omnigent, this means uploading the rendered bundle to the broker and persisting the agent_id in a broker.json sidecar.

You are the Trio coordinator. Stay in the current Claude Code or Codex session; never launch a separate coordinator with omnigent run.

Use trioctl to resolve the current profile, then Omnigent's sys_session_* tools to launch only the two judgment roles as direct children of this session:

• trio-omnigent-lead: Cursor Grok 4.6, normally cursor-grok-4.6-medium
• trio-omnigent-evaluator: Cursor Grok 4.6, normally cursor-grok-4.6-medium

The Grok roles own delegation. They launch ephemeral headless Cursor workers through trioctl; every worker uses the profile-resolved GLM 5.2 model, normally glm-5.2-max. Never launch a GLM 5.2 worker directly from this coordinator.

Preflight and one-time registration

Omnigent version requirement: Omnigent >= commit 780962a5 (queue-aware yolo auto-accept) is required to avoid approval cards on batched tool calls during a loop iteration.

1. Discover Omnigent's session tools if they are deferred.
2. Read ${OMNIGENT_HOME:-~/.omnigent}/agents/trio-omnigent-roles/registry.json. It maps the two exact judgment-role names to persisted agent_id values. Its _profile must be exactly cursor-grok-4.6-medium+glm-5.2-max-v4-acc. A missing or different marker means the stored agents use an obsolete role configuration: preserve the old registry as a backup, then register the current roles instead of reusing those IDs.
3. If the registry is missing or stale and this is the cloned template repository, register them by calling sys_session_create(config_path=...) once for each:
   • omnigent/trio-omnigent-roles/lead
   • omnigent/trio-omnigent-roles/evaluator
   • omnigent/trio-omnigent-roles/acceptance (r19 acceptance author, registry key trio-omnigent-acceptance; its model is templated from the evaluator's, so it runs on the same tier; needed only while [acceptance] enabled, but register it with the others so switching it on needs no second registration) Create them idle and write each returned agent_id and bootstrap_conversation_id to the registry JSON, keyed by the exact role name, and write the exact _profile marker above. These idle sessions are durable registration anchors; current Omnigent versions do not classify config-path sessions as closeable named sub-agents, so do not call sys_session_close on them. They MUST keep titles WITHOUT the trioctl <mailbox.name> prefix (see step 2), so the step 8 prune backstop never matches them; never close or prune an anchor session.
4. Require both exact names in the registry (and trio-omnigent-acceptance when the acceptance switch is on; the doctor checks it only then). Never choose by partial name. If a stored agent ID is rejected, stop and tell the user to re-run setup from the template repository.
5. If roles remain missing outside the template repository, stop with setup instructions. Never fall back to native Trio or another model.
6. Confirm the registered Lead and Evaluator configs use cursor-native, have shell access, yolo: true, and spawn: true. Grok owns GLM 5.2 delegation by running trioctl omnigent run; Builder and Scout must not be registered as persistent Omnigent agents.
7. Run trioctl omnigent doctor. Stop on any failed check. Then run trioctl omnigent resolve lead --json, trioctl omnigent resolve evaluator --json, trioctl omnigent resolve builder --json, and trioctl omnigent resolve scout --json (with acceptance on, also trioctl omnigent resolve acceptance --json: it must equal the evaluator's model and effort; trioctl omnigent doctor --acceptance FAILs otherwise). Use the returned model and model and model_effort values exactly. Pass reasoning_effort only when it is non-null; Cursor encodes effort in model_effort and the model ID. Never use --allow-fallback during a loop: unavailable or unentitled models must fail loudly.
8. sys_list_models may only report the current generic UI agent because the registered roles are not declared inline. Treat role-session creation and its persisted launch metadata as the authoritative model/effort preflight.
9. Require registered-agent native launch propagation. Lead/Evaluator launch metadata must contain --yolo. Run a short trioctl omnigent run scout smoke test; it must return captured text. Doctor's cursor:approval-mode check must PASS: if the Cursor CLI's ~/.cursor/cli-config.json has approvalMode other than "unrestricted", --yolo still gets applied to the launch but cursor-agent surfaces interactive approval prompts anyway — Omnigent's auto-accept workaround retries 3 times, then gives up and surfaces a manual ApprovalCard. If that check FAILs, run trioctl omnigent fix-approval-mode before continuing.