ADR: Harness support for opencode

Open
  • Is something wrong?
#137 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@savitharaghunathan is already working on this.

Since Aug 12, 2026.

Assessment

This issue has not been assessed yet.

Description

Context

The harness today is coupled to goose in three places:

  1. Lifecycle — internal/goose/lifecycle.go starts goose serve, translates
    LLM credentials to goose-specific env vars (GOOSE_PROVIDER, GOOSE_MODEL,
    ANTHROPIC_API_KEY, etc.), and manages the process.

  2. Skill discovery — PR #136
    symlinks .agents/skills → /opt/skills so
    goose's native skill platform finds mounted SkillCards. This path
    (.agents/skills) is goose-specific. opencode uses a different convention.

  3. ACP protocol — internal/acp/ implements the ACP WebSocket protocol
    (JSON-RPC over WS). goose implements ACP natively. opencode does not — it
    would need an adapter or a different integration path.

ADR 0001 already anticipates multiple runtimes (layer 1.5 runtime images:
agent-base-goose, agent-base-opencode) and states that subagent delegation
is a runtime concern. But the harness has no abstraction for swapping runtimes.

Questions to resolve

  • Lifecycle interface: What does the harness need from a runtime? Start,
    health check, stop, port. Should this be a Go interface the harness calls, or
    a process convention (binary name, env vars, exit codes)?

  • Skill delivery: goose scans $HOME/.agents/skills and <cwd>/.agents/skills.
    What does opencode scan? Do we need per-runtime symlink targets, or is there a
    shared convention (e.g., Agent Skills spec directories)?

  • ACP compatibility: Does opencode support ACP? If not, what's the
    integration path — ACP adapter sidecar, stdin/stdout, HTTP API? The harness
    tee (ADR 0008) assumes ACP for live viewer streaming and HITL.

  • Prompt assembly: The harness builds a single prompt from context layers
    and sends it via ACP. If a runtime doesn't support ACP, how does the prompt
    reach the agent?

  • Rules (from #135): type: rule SkillCards need to be always-loaded in the
    prompt regardless of runtime. The mechanism (env var like KONVEYOR_RULES,
    .goosehints, or runtime-agnostic config file) should work across runtimes.

  • Provider credentials: providerEnv() maps KONVEYOR_LLM_* to
    goose-specific env vars. opencode likely expects different var names. Should
    this mapping live in the harness or in the runtime image?

Goose-specific surface area

Area Goose coupling opencode equivalent
goose serve Binary + CLI flags ?
GOOSE_PROVIDER / GOOSE_MODEL Env vars ?
ACP WebSocket Native support ?
.agents/skills/ Native skill discovery ?
.goose/ state dir gitignore'd ?
--with-builtin developer CLI flag ?
.goosehints Runtime-specific config ?

Expected output

An ADR documenting:

  • The runtime abstraction boundary (what the harness expects vs. what the runtime provides)
  • How skill delivery works across runtimes
  • How ACP or an alternative protocol handles observability and HITL
  • Whether provider credential mapping belongs in the harness or the image
Dominant language
Go
Stars
5
Forks
13
Avg merge
3d 3h
Merged PRs (30d)
45

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from konveyor/agentic-controller

All issues in konveyor/agentic-controller

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.