Given that Claude Code is a scriptable CLI tool with an SDK, why can't OpenCode just call Claude instead of reusing its auth tokens?

▲

ehsanu1 4 hours ago | parent | next [-]

You can't control it to the level of individual LLM requests and orchestration of those. And that is very valuable, practically required, to build a tool like this. Otherwise, you just have a wrapper over another big program and can barely do anything interesting/useful to make it actually work better.

▲

Wowfunhappy 4 hours ago | parent [-]

What can't you do exactly? You can send Claude arbitrary user prompts—with arbitrary custom system prompts—and get text back. You can then put those text responses into whatever larger system you want.

▲

handfuloflight 4 hours ago | parent [-]

May as well just use Claude Code then.

	▲	Wowfunhappy 4 hours ago \| parent [-]
		Well, I do use Claude Code myself, but I'd thought the point of OpenCode was that it could combine the responses of multiple LLMs.

▲

localhost 4 hours ago | parent | prev [-]

This is what ACP and https://github.com/zed-industries/claude-code-acp enables. ACP controls agents - there is native support in Copilot CLI and Gemini and adapters for claude code and codex.

▲

Imustaskforhelp 4 hours ago | parent [-]

wow. ACP is used within zed so I guess zed is safe with ACP using claude code

I wonder if Opencode could use ACP protocol as well. ACP seems to be a good abstraction, I should probably learn more about it. Any TLDR's on how it works?

▲

threecheese 3 hours ago | parent | next [-]

According to Opus, ACP is designed specifically for IDE clients (with coding agent “servers”), and there’s some impedance mismatch here that would need to be resolved for one agent cli to operate as a client. I havent validated this though.

—-

1. ACP Servers Expect IDE-like Clients The ACP server interface in Claude Code is designed for: ∙ Receiving file context from an IDE ∙ Sending back edits, diagnostics, suggestions ∙ Managing a workspace-scoped session It’s not designed for another autonomous agent to connect and say “go solve this problem for me.”

2. No Delegation/Orchestration Semantics in ACP ACP (at least the current spec) handles: ∙ Code completions ∙ Chat interactions scoped to a workspace ∙ Tool invocations It doesn’t have primitives for: ∙ “Here’s a task, go figure it out autonomously” ∙ Spawning sub-agents ∙ Returning when a multi-step task completes

3. Session & Context Ownership Both tools assume they own the agentic loop. If OpenCode connects to Claude Code via ACP, who’s driving? You’d have two agents both trying to: ∙ Decide what tool to call next ∙ Maintain conversation state ∙ Handle user approval flows

▲

ikidd 2 hours ago | parent | prev | next [-]

opencode acp -- start ACP (Agent Client Protocol) server

▲

threecheese 3 hours ago | parent | prev [-]

[flagged]

	▲	Imustaskforhelp 3 hours ago \| parent [-]
		WHAT?? Edit: I may have been rude previously but I was feeling beyond angry because I have tried to be a part of the community and I don't even know what to say I genuinely am speechless. I think its so sad to see HN community be unable to trust and how you accuse me man which is so sad to see. I genuinely just don't know what to say? I hope you are (jokng or something?) but what sort ofjoke is this?