opencode adapter

[dazmc]

It would be good if opencode was supported

[hanool]

There is opencode adaptor written in doc, but when I do:
npx @open-gitagent/gitagent@latest run -r https://github.com/shreyas-lyzr/architect -a opencode

fails with:

✗ Unknown adapter: opencode
i Supported adapters: claude, openai, crewai, openclaw, nanobot, lyzr, github, git, prompt

[dazmc]

ths is what i found - the github repo mentions it but the website gitagent.sh makes no mention of it. In addition the version shown in the github repo is 0.1.7 but the npm install version appears to be 0.1.0 - all very confusing.

[dazmc]

@hanool if you follow the steps in the CONTRIBUTING.md you can build gitagent locally with opencode and copilot etc...

$ gitagent export -f copilot --help
Usage: gitagent export [options]

Export agent to other formats

Options:
  -f, --format <format>  Export format (system-prompt, claude-code, openai, crewai, openclaw, nanobot, lyzr, github, copilot,
                         opencode)
  -d, --dir <dir>        Agent directory (default: ".")
  -o, --output <output>  Output file path
  -h, --help             display help for command

$ gitagent export -f opencode -o test1

Exporting agent
i Format: opencode
✓ Exported to test1

$gitagent export -f copilot -o test2

Exporting agent
i Format: copilot
✓ Exported to test2

[dazmc]

this is what i did @hanool

  gh repo clone XXXXX/gitagent
  cd gitagent/
  npm install
  npm run build
  # see available commands
  more dis/index.js
  # test available commands
  node dist/index.js init
  node dist/index.js info
  node dist/index.js export --help
  # export using opencode adapter
  node dist/index.js export -f opencode -o test
  # overwrite my npm installed gitagent with my compiled one in /usr/local/bin
  sudo npm link --force
  # now my gitagent works for opencode, copilot etc...
  gitagent export -f opencode -o test1
  gitagent export -f copilot -o test2

[hanool]

@dazmc Thanks! It seems there's a gap between repository's README and website gitagent.sh.
I'll try local build!

[Keesan12]

Fastest way out is to separate documented adapters from shipped adapters in CI and release notes.

If opencode is named in docs, CI should assert it appears in the supported adapter list in the release build. Otherwise the docs should fail. I’d also lock a tiny adapter contract up front: transport, file attachment shape, resume/cancel behavior, and expected audit fields. That’s usually where these integrations drift. We took the same approach in MartinLoop because loop governance only stays portable if the adapter boundary is explicit.