OpenUltraCode adds UltraCode-style workflow discipline to opencode. It keeps the model you already selected, then adds prompt assets, role agents, slash commands, verification tools, and a small plugin for state, degradation notices, and request hints.
It uses no proxy. It does not replace the selected model, create synthetic model IDs, or route provider traffic. If you change models, use opencode's normal model selection.
- Install the latest release with
curl -fsSL https://raw.githubusercontent.com/norandom/OpenUltraCode/main/install.sh | sh. - If you already have a checkout and want the development path, run
./install-dev.shfrom the repo root. - The release installer pulls the latest GitHub release asset, copies the skill, slash commands, and agents into
~/.config/opencode/, asks which fusion model IDs to set, and registers the plugin path in~/.config/opencode/opencode.json. - Quit and restart opencode so the global plugin, commands, skills, and agents are loaded.
The restart matters because opencode loads plugins, commands, skills, agents, and config at startup. If /ultracode does not appear, confirm you restarted opencode after running install.sh or install-dev.sh.
Release installs do not run Dagger or pnpm run check on the user's machine. The GitHub Actions release workflow runs build, ESLint, tests, and asset validation, then publishes open-ultracode-release.tar.gz as the GitHub release asset consumed by install.sh.
Development installs use pnpm with a 3-day release-age cooldown (minimumReleaseAge: 4320 in pnpm-workspace.yaml). That keeps brand-new package releases out of the install path. pnpm-workspace.yaml allows the esbuild install script because the TypeScript test runner needs it. install-dev.sh also configures the repository pre-commit hook to run Dagger-backed ESLint through pnpm run lint.
Slash commands are what you type in opencode:
/ultracodefor comprehensive build/review/verify work./ultracode-debugfor reproduce/root-cause/fix loops./ultracode-spec-auditfor incomplete or contradictory specs./ultracode-researchfor adversarial research against a plan or claim./ultracode-verifyfor evidence-based completion checks./ultracode-fusionfor explicit two-model fusion rounds with a selected decider./ultrathinkfor grounded, non-coding problem solving./ultrathink-fusionfor grounded, non-coding two-panel fusion problem solving.
The skill is named open-ultracode. It is not a slash command. The slash commands above tell opencode to use that skill, and opencode exposes skills to agents through its skill system rather than as /open-ultracode.
Supporting assets:
- Role agents for coordinator, planner, implementer, adversary, reconciler, verifier, and researcher workflows.
- Fusion agents for panel and arbiter roles. These are intentionally separate from the normal workflow agents.
- Plugin tools for workflow status, verification evidence, blocked checks, and completion reports.
Comprehensive task execution:
/ultracode "Implement the approved registration-flow task, run the relevant tests, reconcile adversarial findings, and report completion evidence."
Debugging:
/ultracode-debug "The docs asset test fails after adding a new command. Reproduce the failure, find the root cause, fix the smallest boundary, and verify the regression."
Spec audit:
/ultracode-spec-audit "Review this checkout spec for missing actors, permissions, error states, and verification criteria before implementation."
Adversarial research:
/ultracode-research "Attack this implementation plan and identify assumptions, edge cases, unsafe defaults, and evidence gaps before we build it."
Fusion workflow:
/ultracode-fusion --panel ultracode-fusion-panel-a --panel ultracode-fusion-panel-b --decider selected-model "Compare the two proposed API designs and produce one implementation recommendation."
Fusion with an arbiter agent:
/ultracode-fusion --panel ultracode-fusion-panel-a --panel ultracode-fusion-panel-b --decider ultracode-fusion-arbiter "Review this migration plan and resolve disagreements with cited evidence."
Grounded problem solving without coding:
/ultrathink "Decide whether we should keep the release installer shell-only or introduce a compiled helper. Use only the supplied constraints and call out unknowns."
Grounded fusion problem solving:
/ultrathink-fusion --panel ultracode-fusion-panel-a --panel ultracode-fusion-panel-b --decider selected-model "Evaluate the product tradeoff using grounded evidence, not loose recall."
/ultrathink and /ultrathink-fusion are not coding commands. They separate supplied facts, verified evidence, assumptions, hypotheses, and recommendations. If the problem depends on facts that are not supplied, they should ask for context or mark the point as unknown instead of drifting into loose recall.
/ultracode-fusion is explicit opt-in fusion, not transparent routing for every prompt. A run has three model-bearing roles:
- The selected opencode model remains the coordinator. It gathers context, validates arguments, dispatches rounds, and reports the final trace.
- Exactly two panel agents produce and critique candidate answers. Pass them with repeated
--panel <agent-name>flags. - The decider is either
selected-modelor a configured fusion arbiter agent passed with--decider <agent-name>.
The default fusion concept is critique-revise-vote: each panel generates an answer from the same bounded context package, critiques the other panel's answer, revises its own answer, ranks the alternatives against the rubric, and then the decider arbitrates the final response.
The bundled placeholders are:
ultracode-fusion-panel-awithmodel: provider/model-a.ultracode-fusion-panel-bwithmodel: provider/model-b.ultracode-fusion-arbiterwithmodel: provider/arbiter-model.
The release installer replaces those placeholders for you. It reads the current model from ~/.config/opencode/opencode.json, then lets you choose each fusion role with a small terminal menu using the up and down arrows. The default for panel A, panel B, and arbiter is openai/gpt-5; you can pick the current opencode model if it differs, or enter a custom provider/model-id. In non-interactive shells, the installer uses openai/gpt-5 for all three fusion roles.
You can also edit the installed agent files manually and replace those placeholder model IDs with opencode model IDs that exist in your configured providers, such as openai/gpt-5, another GPT-5-family model, DeepSeek, or a local/provider-specific model. The command rejects runs that do not provide exactly two fusion panel agents or that name a decider outside selected-model or a fusion arbiter agent.
One-shot independent answers are reported as panel-consult, not strong fusion. Strong fusion requires the critique, revision, vote, and arbitration loop.
OpenUltraCode inherits the active selected model from opencode. Normal bundled workflow agents do not set model: frontmatter, and the plugin does not install provider routes or model aliases.
Fusion agents are the deliberate exception: they use explicit model: frontmatter so /ultracode-fusion can compare two configured opencode models while the selected model remains the coordinator. This still uses opencode's native agent model selection. It is not a proxy, synthetic model ID, provider route, hidden model switch, or replacement for the selected model.
The package can add high-effort request hints only when a provider parameter already exists in the outgoing request. If the provider does not expose a compatible field, OpenUltraCode records a visible degradation notice instead of pretending the behavior is available.
- If commands, agents, or skills do not appear, restart opencode.
- If high-effort behavior is unsupported, check workflow status for a degradation notice.
- If a permission is denied, OpenUltraCode records the workflow as blocked and reports the safe next step.
- If completion is partial or blocked, run
/ultracode-verifyand collect fresh evidence before claiming completion.
See docs/CONCEPTS.md, docs/LIMITS.md, and docs/CONFIGURATION.md for workflow details.