Integrate OpenCode as an agent provider for NanoCrew deployments.
npx skills add https://github.com/CjLogic/nanocrew --skill add-opencode
Please help me install this Agent Skill. Skill: add-opencode Source: https://github.com/CjLogic/nanocrew/tree/main/.codex/skills/add-opencode Command: npx skills add https://github.com/CjLogic/nanocrew --skill add-opencode
Integrates OpenCode as an agent provider for NanoCrew deployments, enabling per-session and per-group provider usage and seamless host/container configuration.
Execute this skill to fetch the OpenCode provider, wire it into your host and container, and prepare OpenCode-based agent provisioning.
High-intent search queries and answers about installing and using this skill.
To integrate OpenCode as an agent provider for NanoCrew, you need to copy the provider files from the providers branch, wire them into host and container barrels, install dependencies, and rebuild the image.
Yes, the OpenCode provider integration supports per-session and per-group provider configuration, allowing you to apply specific overlays for OpenCode-based agent execution across your NanoCrew deployments.
The best way to set up host and container integration for an OpenCode agent provider is to copy the provider files into your environment and update the host and container barrels before rebuilding the image.
Yes, you need access to the providers branch to fetch the necessary OpenCode provider files, copy them into your environment, and wire the provider modules into your host and container barrels.
If your OpenCode agent provider is not working, ensure you have updated the host and container barrels, installed all required dependencies, and rebuilt the NanoCrew image after copying the provider files.
llama-farmStage changes, create conventional commits, push to origin, and open a PR via gh CLI.
BartunekEnable the OpenCode provider in NanoClaw with host and container wiring.
BartunekInstall Codex provider per group with vault-based authentication.
thmtzEnable the OpenCode agent provider in NanoClaw Fleet with dependency installation and image rebuilds.
