[FEATURE] opencode compatibility

[thoroc]

Problem Statement

Ability to use Han in opencode instead of Claude Code

Proposed Solution

• Investigate Opencode difference with Claude Code
• Adapt the project to accommodate Opencode

How It Embodies Bushido

• Righteousness (義) - Does the right thing
• Courage (勇) - Makes a bold improvement
• Compassion (仁) - Helps users or contributors
• Respect (礼) - Honors existing conventions
• Honesty (誠) - Transparent about trade-offs
• Honor (名誉) - Maintains quality standards
• Loyalty (忠義) - Long-term maintainability

Alternatives Considered

This is a new 'feature'

Additional Context

https://opencode.ai/

[jwaldrip]

@thoroc give it a try! https://han.guru/blog/han-meets-opencode

[thoroc]

@jwaldrip Thank you; I'll do that at first opportunity

[jmaver]

install seems to only install into claude-code.
open code fails with:
{
"name": "BunInstallFailedError",
"data": {
"pkg": "opencode-plugin-han",
"version": "latest"
}
}

[jwaldrip]

@jmaver I pushed some updates and I will be testing locally today. Tell me if you have any luck with the new version

[thoroc]

I am getting the following:

Installing to project scope (.claude/settings.json)

Installing to .claude/settings.json...

Scanning codebase for marker files...

No plugins detected via file markers.

Starting AI analysis for additional recommendations...


🤖 Han Plugin Installer

⠦ Analyzing codebase...


Error during plugin installation: Claude Code process exited with code 1

This is my attempt to test it in a bun/typescript/nx project.

[jwaldrip]

Status check on this thread — the bridge plugin itself is in plugins/bridges/opencode/ and the docs at han.guru/docs/installation/opencode tell users to add "plugin": ["opencode-plugin-han"] to opencode.json.

The reason `@jmaver` saw `BunInstallFailedError` is that `opencode-plugin-han` is not published to npm yet — `https://registry.npmjs.org/opencode-plugin-han\` returns 404. Bun resolves the entry literally from npm and 404s.

To unblock this issue we need either:

1. Publish the package to npm — add an npm publish step for plugins/bridges/opencode to the existing release workflow (the npm token is already configured for the han binary packages). Requires updating package.json (main currently points at src/index.ts; should point at dist/index.js since dist/ is already built and shipped) and gating the publish on plugin version changes.
2. Document a non-npm install path — opencode plugins can be loaded from a local file path or a git ref; if we point users at a git URL the install error goes away but they lose automatic updates.

@thoroc's "Claude Code process exited with code 1" is a different failure — that's the AI analysis step inside han plugin install --auto failing, unrelated to the opencode bridge itself.

Leaving this open until we wire up the publish step. Mostly flagging so the next time someone picks this up they don't go in circles on the install error.