add-opencode

Enable the OpenCode agent provider in NanoClaw Fleet with dependency installation and image rebuilds.

5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/thmtz/nanoclaw-fleet --skill add-opencode-thmtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-opencode
Source: https://github.com/thmtz/nanoclaw-fleet/tree/main/.claude/skills/add-opencode
Command: npx skills add https://github.com/thmtz/nanoclaw-fleet --skill add-opencode-thmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NanoClaw Fleet ships with Claude provider by default; this skill enables OpenCode as an agent provider by copying OpenCode provider files, wiring them into host and container barrels, installing dependencies, and rebuilding the agent image to support per-session and per-group provider selection.

Core Features & Use Cases

  • Integrates the OpenCode provider into the fleet by adding provider files and wiring them into host/container.
  • Ensures version pinning and Dockerfile adjustments to align CLI/SDK versions.
  • Supports per-group or per-session OpenCode provider selection via AGENT_PROVIDER and host environment variables (OPENCODE_*).

Quick Start

Run the add-opencode skill to copy the OpenCode provider, install dependencies, and rebuild the agent image for your fleet.

Frequently Asked Questions about add-opencode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable OpenCode as an agent provider in NanoClaw Fleet?

To enable OpenCode as an agent provider, this Skill copies provider files, wires them into host and container barrels, installs dependencies, and rebuilds the agent image for per-session or per-group selection.

Can I use OpenCode for per-group agent provider selection?

Yes, OpenCode provider selection is supported on a per-group or per-session basis by configuring the AGENT_PROVIDER and host environment variables with the OPENCODE_ prefix.

What is the best way to switch from the default Claude provider to OpenCode?

Switching from the default Claude provider to OpenCode requires copying provider files from the providers branch, respecting version pins, adjusting the Dockerfile, and rebuilding the agent container.

Do I need to rebuild the Docker image when adding the OpenCode provider?

Yes, rebuilding the agent Docker image is required to apply the OpenCode configuration, ensure CLI and SDK version pins are respected, and integrate the host and container barrels.

How does version pinning work when integrating the OpenCode agent provider?

Version pinning ensures CLI and SDK versions align across the OpenCode provider integration by adjusting the Dockerfile and respecting version pins during the host and container barrel wiring process.