Show HN: Gigacode – Use OpenCode's UI with Claude Code/Codex/Amp

One slick control panel for code bots; fans cheer while standards nerds debate

TLDR: Gigacode lets you use the OpenCode interface to control Claude Code, Codex, and Amp via Sandbox Agent SDK. Commenters praise the “harness” idea, debate standardizing with ACP, and cheer hopes for interchangeable backends and UIs—while Windows users grumble about WSL—making this playful tool feel unexpectedly important.

Gigacode dropped with a bold promise: use the familiar OpenCode interface to steer code-writing bots like Claude Code, Codex, and Amp, all patched together by the Sandbox Agent SDK. It’s experimental, “not a fork,” and yes, Windows folks, you’ll need WSL. The crowd reaction? Loud. The top vibe is that harnesses matter as much as the brainy models themselves, with vercantez co-signing what many devs have felt: the wrapper and tools can make or break the experience.

But not everyone is here just to vibe. phromo rolls in with the “make it a standard” energy, pointing to agentclientprotocol.com and asking if pushing ACP (Agent Client Protocol) over HTTPS basically equals this Sandbox magic. Cue a mini skirmish: protocols vs pragmatism. Meanwhile, solarkraft is all joy—“this was made for me”—dreaming of an ecosystem where backends and UIs are swap-friendly, not just for coding. Jokes and memes flew: “One UI to rule them all,” “WSL or bust,” and the line “not a fork (and never will be)” got meme-ified as a badge of honor. Verdict: a playful hack that could spark a serious standards conversation. And somewhere in the threads, a dozen devs quietly asked for Windows support, then shrugged and installed WSL.

Key Points

  • Gigacode connects OpenCode’s UI to external coding agents (Claude Code, Codex, Amp) via the Sandbox Agent SDK.
  • It is not a fork of OpenCode; it uses a universal HTTP API and an OpenCode‑compatible endpoint provided by Sandbox Agent SDK.
  • Gigacode runs agents using their native harnesses, differing from OpenCode’s direct model/tool loop approach.
  • Users gain agent‑specific capabilities (e.g., Read/Write/Bash, sandboxed execution, permission rules) instead of a single tool loop.
  • Installation supports macOS, Linux, and WSL, with commands via curl, npm, bun, npx, and bunx; Windows is unsupported.

Hottest takes

"Harnesses matter almost as much as the models in 2026" — vercantez
"if you shuffle acp over https is it then similar" — phromo
"I feel like this was made for me" — solarkraft
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.