Agent Hive (oc-arkive)

OpenCode workflow plugin for plan-first development with isolated workers, durable .hive/ state, and explicit human approval gates.

After installation, ask Hive for a feature in plain language. The first feature loop is below. Ad-hoc work, independent review commands, and the public agent seats are in the Operator Guide.

Demo

Older walkthrough of the plan-first loop. Package names and UI have changed since this was recorded.

Untitled.video.-.Made.with.Clipchamp.mp4

Requirements

• OpenCode >= 1.14.48 (peer dependency of oc-arkive)
• A project whose work resolves to one or more git repositories. Single-repo projects need no manifest; multi-repo topology is optional. When a multi-repo root needs explicit topology, ask Hive to inspect, discover, and update it; do not hand-create <project>/.hive/repositories.json.
• Optional: VS Code for sidebar plan review via vscode-arkive

Quick start

1. Append oc-arkive@latest to the existing plugin array in your OpenCode config (opencode.json or opencode.jsonc). Keep your existing plugin entries, preserve unrelated settings, and retain the surrounding config. This JSONC fragment uses placeholders:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "existing-plugin@version", // placeholder: retain your current plugin entry
    "oc-arkive@latest"
  ],
  "model": "provider/model" // placeholder: retain your existing setting
}

For a brand-new config, a plugin array containing only "oc-arkive@latest" is sufficient.

2. Restart OpenCode so it loads the plugin.

First feature loop

1. Open the project and ask for a feature in plain language, or use /hive-plan.
2. The primary agent discusses the scope and writes a plan. Review it in chat or VS Code, add comments, and request changes until the plan is clear.
3. Approve the plan with /approve-sync-plan or ask the agent to approve and sync it. Hive creates the executable task records.
4. Start execution with /start-execution. Workers perform task-level, best-effort checks in isolated git worktrees while implementing tasks. The primary agent tracks dependencies and progress.
5. The operator/orchestrator inspects completed worker output.
6. Merge completed task branches after inspection.
7. Run fresh build/test verification against the merged result.
8. Mark the feature complete only after that merged-result verification passes.

What you can run

Workflow	When	How you start
/grill	Explicit alignment on any context, without assuming implementation or a next command	/grill <context>
/interview	Clarify an idea toward a reliable implementation-brief handoff	/interview <idea>
Feature	Plan review, task dependencies, isolated task worktrees, or a durable audit trail	Ask in plain language, or /hive-plan
Ad-hoc (hive-builder)	Bounded non-feature work that should not create feature or task records	Talk to hive-builder (dedicated mode) or hive-master (unified)
/dash-review	Read-only Git, process/concept, or local-artifact review in one frozen workspace	/dash-review [intent] [--artifact <file>]
/vuln-review	Authorized bounded static security review of one frozen snapshot	/vuln-review [intent] [flags]

By default (dedicated mode), architect-planner and swarm-orchestrator handle feature work and hive-builder handles ad-hoc work. Set "agentMode": "unified" for one hybrid hive-master that can coordinate both. /dash-review and /vuln-review always bind to separate review primaries.

Agents at a glance

Dedicated mode registers architect-planner and swarm-orchestrator. Unified mode registers hive-master instead. hive-builder and the subagents below are in both modes.

Seat	Role
architect-planner	Writes feature plans. Does not implement. Default in dedicated mode.
swarm-orchestrator	Executes approved feature work. Dedicated-mode execution seat.
hive-master	Hybrid planner and orchestrator. Unified-mode default.
hive-builder	Ad-hoc orchestrator. No feature or task DAG.
scout-researcher	Retrieves bounded source evidence; does not own diagnosis, tradeoffs, or solution selection.
forager-worker	Implements in isolated worktrees; diagnosis-only assignments are report-only. Never delegates.
plan-reviewer	Checks whether a plan is worker-executable.
code-reviewer	Checks an implementation against the task or plan.
simplicity-reviewer	Deletion-biased cleanup of a completed diff.
approach-advisor	Read-only architecture and tradeoff advice.
vulnerability-reviewer	Read-only attacker-to-impact review.

Why each seat exists, how it behaves, and the full ad-hoc / dash-review / vuln-review loops are in the Operator Guide.

Runtime configuration is global only: ~/.config/opencode/agent_hive.json. Project-local agent_hive.json and agent-hive.json files are ignored. Dedicated mode is the default; set "agentMode": "unified" for a single hive-master seat (see the plugin README agent mode section). For existing-config compatibility, see the plugin README.

Packages

Package	Distribution	Role
oc-arkive	npm	OpenCode plugin: agents, tools, skills, MCPs, commands
vscode-arkive	GitHub Release VSIX	Sidebar, plan/overview review, background job viewer

Documentation

Doc	Audience
Operator Guide	Agents, feature / ad-hoc / dash-review / vuln-review workflows
Plugin README	Slash-command flags, tool contracts, helper recovery, and config
Philosophy	Why the workflow is shaped this way
Design	Internal architecture and source-of-truth rules
Hive Tools	Full tool inventory and contracts
Data Model	.hive/ layout and task status fields
VS Code extension	Companion install and scope
Releasing	Maintainers: publish and recovery

License

MIT with Commons Clause. See LICENSE.