Skip to content

Kujo OpenCode v0.2.0

Choose a tag to compare

View all tags
@robertdevore robertdevore released this 17 Oct 23:46
· 19 commits to codex/opencode-ability-integration since this release
v0.2.0
587401b

Kujo OpenCode brings Kujo's local tools into OpenCode 2, with native controls, scoped specialists, request-bound approvals and receipts for tool results.

Highlights

  • Use Understand, Build, Review, Browser, Workflow and Ship specialists for focused tasks.
  • Inspect, preview, run and test Kujo source through the canonical tools.
  • Review changes, create starters, query project knowledge and verify browser workflows.
  • Operate Dispatch workflows with explicit checkpoint decisions and recovery after a lost response.
  • Inspect receipts in OpenCode and opt into RunLedger tracking and metadata-only Watchdog delivery.
  • Install, update, repair and uninstall with project and version isolation.

Install

You need Node.js 20+, npm, Git and OpenCode 2, version 2.0.31 or newer.

npm install --global @kujolang/kujo-opencode@0.2.0
cd /path/to/your/project
kujo-opencode setup
kujo-opencode doctor
kujo-opencode demo
opencode

Setup downloads the pinned Kujo sources and runtime. In OpenCode, open /kujo to select a profile, enable capabilities, choose a specialist or inspect evidence. Connect your model through OpenCode's provider settings.

Compatibility and evidence

Native and rendered host checks cover Linux, macOS and Windows on OpenCode 2.0.31 and 2.0.32. Live specialist and lifecycle evidence uses macOS x64, OpenCode 2.0.32 and an authorized ChatGPT connection with openai/gpt-5.6-sol. These are distinct test scopes. The free GLM/DeepSeek specialist route is not verified.

The attached archive is the npm payload. Checksums, the dependency and source inventories, and the acceptance report identify the exact tested release. Registry provenance links publication to its GitHub workflow.

User guide · Walkthrough and demo source

Registry installation, upgrade, signatures and provenance passed in the consumer verification run. The original publication run accepted the package but encountered registry propagation and a consumer-test working-directory issue; the separate verification run completes those checks without republishing.

Assets 12
Loading