Agentic Orchestrator

Integrate Intutic governance with DoorDash's Agentic Orchestrator (agentico) — a public, open-source (Apache-2.0) desktop app + CLI that turns a feature prompt into a multi-phase AI coding workflow.

Live-verified, not just README-read

Unlike several recent harness integrations (Muse Code, Grok Build, Xirp), this one's core facts were confirmed by actually downloading and running the real released binary (agentico v0.152.0, darwin_arm64) during this integration's research — agentico --version, agentico --help, and agentico server --help all matched what's documented below. The one real gap this research surfaced — the OpenCode backend had no Intutic gate to delegate to — has since been closed (see below).

What Agentic Orchestrator is (and is not)

Agentic Orchestrator is not itself an AI agent. It is a desktop app (with a companion CLI, agentico) that turns a high-level feature prompt into a checkpointed engineering workflow — knowledge-base build, inquiry, research, design, roadmap planning, phase implementation, review, and PR publish — supervised from one workspace. The actual model-driving work is delegated to already-installed CLI backends: Claude Code, Codex, and OpenCode (confirmed via agentico server --help's --providers flag: Available: claude, codex, opencode). Each feature runs in its own git worktree under ~/.agentic-orchestrator/worktrees/ (confirmed via the project's own README), so several features can proceed concurrently without colliding in the main checkout.

This is the same "wraps other already-gated CLI harnesses" shape as Xirp — but cross-platform (macOS and Linux, via Homebrew, a prebuilt binary, or go install) rather than Xirp's macOS-only beta, and with a real, confirmed default config path rather than a guessed one.

Why this integration is detection-only

1. Detection. intutic status/intutic init recognise an Agentic-Orchestrator-managed workspace, so it shows up in reporting.
2. Worktrees. Each feature runs in its own git worktree under ~/.agentic-orchestrator/worktrees/. intutic gates install writes project-tier files only into the checkout it runs in, so a feature worktree is governed by each backend's user-level registration: the PreToolUse hooks in ~/.claude/settings.json (Claude Code) and ~/.codex/hooks.json (Codex). OpenCode's plugin is project-level (.opencode/plugins/), so OpenCode sessions in a feature worktree are not gated unless you copy the plugin there. See Worktree Coverage.

There is no config format of Agentic Orchestrator's own for Intutic to write. config.yaml's defaults.models.* keys select which model each workflow phase uses — they are not an LLM base-URL / API-routing surface. Routing is each wrapped backend's own concern, exactly as it already is when that backend runs standalone.

Governance model

Agentic Orchestrator is registered as a NO_GATE harness with a 'delegated' gate kind (see packages/shared-types/src/gateKind.ts) — the same classification Xirp introduced, reused rather than reinvented. A tool call made inside an Agentic-Orchestrator-managed session is governed by whichever wrapped backend's own gate is already running (claude-code-check.js, codex-check.js) — the same gate this product already lists under that backend's own row, not a second one credited to Agentic Orchestrator.

OpenCode is gated too

All three wrapped backends are Intutic harnesses of their own: Claude Code and Codex through their hook files, and OpenCode through the plugin intutic gates install writes into .opencode/plugins/. In feature worktrees, Claude Code and Codex are covered by their user-level hooks; OpenCode's plugin is project-level (see above).

Setup

1. Agentic Orchestrator detection

Detection checks (in order), cross-platform:

• ~/.agentic-orchestrator (confirmed default home directory — holds config.yaml, the features/ state dir, and worktrees/)
• the agentico binary found in your PATH
• (macOS only) /Applications/Agentico.app, the desktop app bundle

No environment-variable override for either the config or state-dir path is documented anywhere in the binary's own --help output (only the explicit --config/--state-dir flags) — unlike Xirp's guessed $XIRP_HOME, this was directly confirmed by running the real binary, not assumed.

2. Initialize Intutic

Run intutic init and intutic gates install as normal, against the main checkout of the repository Agentic Orchestrator will manage, with its backends recorded. No extra step is needed for Agentic Orchestrator: there is no config for Intutic to write for Agentic Orchestrator itself; governing the backends you use (Claude Code, Codex, OpenCode) is what matters.

3. What gets written

• For Agentic Orchestrator itself: nothing. tools/cli/src/harness/agenticOrchestrator.ts's writeConfig is a no-op by design, matching Xirp's exact pattern. Agentic Orchestrator has no instructions file; the backends it runs read their own (Where rule sets go).
• For each wrapped backend: what that backend's own adapter writes. User-level hook registrations (Claude Code, Codex) govern every feature worktree; project-level files, including OpenCode's plugin, exist only in the main checkout.

Config details

Property	Value
Harness type	agentic-orchestrator
Config file	none (delegates entirely to the wrapped backend)
Gate kind	delegated — see gateKind.ts
Detection	~/.agentic-orchestrator, agentico on PATH, or (macOS only) /Applications/Agentico.app
Wrapped backends	Claude Code, Codex, OpenCode — each gated by its own adapter
Worktree coverage	through each backend's user-level hooks — see Worktree Coverage

Source

• Project: doordash-oss/agentic-orchestrator (Go, Apache-2.0)
• Binary: agentico — confirmed real by downloading and running the actual GitHub release artifact (v0.152.0, darwin_arm64) during this integration's research