opencode-controller — Claude Code skill: session and agent management
opencode-controller — a skill to manage Opencode through slash commands. Selects AI models, switches between planning and development agents, handles project sessions.
no license 167 installs ★ 675 updated 2026-03-07
npx skills add sundial-org/awesome-openclaw-skills --skill opencode-controller -a claude-codeWhat opencode-controller does
opencode-controller orchestrates work in Opencode: launches project sessions via /sessions, picks an AI provider through /models, toggles agents via /agents. The workflow is two-phase — Plan agent analyzes the task and drafts a step-by-step plan, then Build agent implements it. The skill itself does not generate code; all development happens inside Opencode.
Before starting, it asks which AI provider to use and how to authenticate. If the provider needs login, it sends the authentication link from Opencode. Switching between Plan and Build is explicit: Plan allows only questions and plan refinement, Build does not answer questions — you go back to Plan, clarify, then return to Build. The cycle repeats until requirements are met.
Requires Opencode installed. User approval is needed before creating a new project session.
What it helps with
- toggle between planning and coding in one interface
- manage AI model selection across different providers
- persist and restore project sessions without losing context
- coordinate multi-step work through plan-build-verify cycles
Example prompts for the agent
- Start the Plan agent and help me design the API structure
- Switch to Build and implement the approved plan
- Open a session for my project and select Claude as the provider
How to install opencode-controller
1Skills CLI (Vercel)
npx skills add sundial-org/awesome-openclaw-skills --skill opencode-controller -a claude-code2Manually: put the files in place
~/.claude/skills/opencode-controller/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/opencode-controller/
1Skills CLI (Vercel)
npx skills add sundial-org/awesome-openclaw-skills --skill opencode-controller -a codex2Manually: put the files in place
.agents/skills/opencode-controller/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sundial-org/awesome-openclaw-skills --skill opencode-controller -a cursor2Manually: put the files in place
.cursor/skills/opencode-controller/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sundial-org/awesome-openclaw-skills skills/opencode-controller2Manually: put the files in place
.github/skills/opencode-controller/SKILL.md1Skills CLI (Vercel)
npx skills add sundial-org/awesome-openclaw-skills --skill opencode-controller -a gemini-cli2Platform CLI
gemini skills install https://github.com/sundial-org/awesome-openclaw-skills --path skills/opencode-controllerManually: put the files in place
.devin/skills/opencode-controller/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sundial-org/awesome-openclaw-skills --skill opencode-controller -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about opencode-controller
How do I install opencode-controller in Claude Code?
Run npx skills add sundial-org/awesome-openclaw-skills --skill opencode-controller -a claude-code, then open ~/.claude/skills/opencode-controller/SKILL.md.
What does opencode-controller do?
Manages Opencode via commands: selects the AI provider, switches agents between planning (Plan) and implementation (Build), handles project sessions. Code is written in Opencode itself; the skill coordinates the workflow.
Why does the Plan → Build order matter?
Plan agent validates logic and clarifies requirements; Build agent executes the agreed plan. If a question arises in Build, return to Plan, address it, then go back to Build. This prevents rework and errors.