Skip to content

Quickstart

Jump to bottom
Lex edited this page Aug 17, 2026 · 2 revisions

Quickstart

From zero to a running multi-agent graph in about five minutes.

1. Install the binary

Grab the latest release for your platform from the releases page (Linux / macOS / Windows, SHA256SUMS included). Builds from main are official; builds from dev are prereleases.

Or build from source with Bun 1.3+:

git clone https://github.com/LeXwDeX/OpenCode-GraphAgent.git
cd OpenCode-GraphAgent
bun install
bun dev

2. Configure one model tier

Create ~/.config/opencode/dag.jsonc (project-level .opencode/dag.jsonc also works and wins):

{
  "model": {
    "advanced": "anthropic/claude-sonnet-4-5",
    "standard": "anthropic/claude-haiku-4-5"
  }
}

advanced runs the judgment nodes (reviews, arbitration, anything marked required). standard runs the volume work (exploration, implementation). One tier is fine to start — it becomes the default for everything.

3. Give it a task with stages

In the TUI, type:

/dag-flow audit this repository's dependencies and propose an upgrade order

The agent designs a graph (exploration → analysis → report), starts it, and tells you the workflow ID. You do not need to define anything for this to work.

4. Watch the graph

Open the command palette (ctrl+k), run dag.open. You get the workflow list, the node view in wave order with live status, and node detail on selection. Keys: p pause, r resume, s step, x cancel, enter drops into a node's child session.

Or from a script, the same information is on the HTTP API: GET /dag/<workflowID>/nodes.

5. What you should see

Within a couple of minutes: waves of nodes flipping from queued to running to completed, the report node waking the parent with its output, and the workflow reaching completed. If a node fails (quota, API error), it shows as failed on the graph — fix or let the agent replan it, and the superseded segment disappears from the view while the workflow finishes on the replacement.

The /dag-* command family

All four ship built into the release binaries; a command file of yours with the same name overrides the builtin.

Command What it does
/dag-flow <task> The conversational entry shown above — works with zero setup beyond dag.jsonc.
/dag-init One-time platform handshake for repos on GitHub/GitLab (self-hosted included): verifies CLI auth, issue/push/CI/ruleset permissions and template availability, then writes .opencode/dag-init.json. Idempotent and safe to commit. Other hosts are rejected.
/dag-auto <task> The auto pipeline: drives a six-block ultra-flow (explore → design → develop → verify → release → summarize) to completion with direction checkpoints and a one-time spec confirmation gate. Requires /dag-init first; afterwards it stops only at user-owned decisions (product decisions, the release gate, merges reserved to humans, caps exceeded).
/dag-template-update Sync the curated global template library from opencode-dag-config, with preview and backup.

Next

GraphAgent

English

中文

README · Issues

Clone this wiki locally