Live data from Hacker News

OpenCode – Open source AI coding agent

opencode.ai

601–610 of 700 posts

Re: OpenCode – Open source AI coding agent

#601
post #409
post #374

Earlier quoted context omitted.

> and (partly as a result) it's fairly resource inefficient (often uses 1GB of RAM or more. For a TUI). That's (one of the reasons) why I'm favoring Codex over Claude Code. Claude Code is an... Electron app (for a TUI? WTH?) and Codex is Rust. The difference is tangible: the former feels sluggish and does some odd redrawing when the terminal size changes, while the latter definitely feels more snappy to me (leaving a…

I think you’re confusing capital c Claude Code, the desktop Electron app, and lowercase c `claude`, the command line tool with an interactive TUI. They’re both TypeScript under the hood, but the latter is React + Ink rendered into the terminal. The redraw glitches you’re referring to are actually signs of what I consider to be a pretty major feature, a reason to use `claude` instead of `codex` or `opencode`: `claude`…

Codex is using its app server protocol to build a nice client/server separation that I enjoy on top of the predictable Rust performance.

You can run a codex instance on machine A and connect the TUI to it from machine B. The same open source core and protocol is shared between the Codex app, VS Code and Xcode.

Re: OpenCode – Open source AI coding agent

#602
post #7

Earlier quoted context omitted.

do you care about harness benchmarks or no?

Just a data point, I would need to use it for my workflows. I do have a monorepo with a root level claude.md, and project level claude.md files for backend/frontend.

thats not at all the question i asked

Re: OpenCode – Open source AI coding agent

#603
post #355

Earlier quoted context omitted.

RCE is exactly the feature of coding agents. I'm happy with it that I don't need to launch OpenCode with --dangerously-skip every time.

No, it is still configurable. You can specify in your opencode.json config that it should be able to run everything. I think they just argued that it shouldn't be the default. Which I agree with.

No, the problem is that when logging in, the provider's website can provide an authentication shell command that OpenCode will send to the shell sight unseen, even if it is "rm -rf /home". This "feature" is completely unnecessary for the agent to function as an agent, or even for authentication. It's not about it being the default, it's about it being there at all and being designed that way.

Re: OpenCode – Open source AI coding agent

#605
I do like OpenCode, and have been using it in and off since last July. But I feel like they’re trying to stuff too much GUI into a TUI? Due to this I find myself using Codex and Pi more often. But am still glad OpenCode and their Zen product exist.

Re: OpenCode – Open source AI coding agent

#606
post #409

Earlier quoted context omitted.

I think you’re confusing capital c Claude Code, the desktop Electron app, and lowercase c `claude`, the command line tool with an interactive TUI. They’re both TypeScript under the hood, but the latter is React + Ink rendered into the terminal. The redraw glitches you’re referring to are actually signs of what I consider to be a pretty major feature, a reason to use `claude` instead of `codex` or `opencode`: `claude`…

Codex is using its app server protocol to build a nice client/server separation that I enjoy on top of the predictable Rust performance. You can run a codex instance on machine A and connect the TUI to it from machine B. The same open source core and protocol is shared between the Codex app, VS Code and Xcode.

OpenCode works this way too
Post reply on HN