One thing I notice across all these coding agents is that none of them have a trust or reputation layer. If an agent generates code, merges a PR, or deploys something — there is no cross-tool way to verify whether that agent has a track record of reliable output. We treat every agent invocation as equally trustworthy. In a world where agents are increasingly calling other agents' tools via MCP, that seems like a gap. The agent running your code review has no way to know if the agent that wrote the code has ever produced working code before.
OpenCode – Open source AI coding agent
661–670 of 700 posts
Re: OpenCode – Open source AI coding agent
#662Re: OpenCode – Open source AI coding agent
#663[flagged]
I built a product solving this problem about a year ago, basically a serverless, container-based, NATed VScode where you can eg "run Claude Code" (or this) in your browser on a remote container. There's a reason I basically stopped marketing it, Cursor took off so much then, and now people are running Claude/Codex locally. First, this is something people only actually start to care about once they've been bitten by i…
[dead]
Re: OpenCode – Open source AI coding agent
#664OpenCode was the first open source agent I used, and my main workhorse after experimenting briefly with Claude Code and realizing the potential of agentic coding. Due to that, and because it's a popular an open source alternative, I want to be able to recommend it and be enthusiastic about it. The problem for me is that the development practices of the people that are working on it are suboptimal at best; they're con…
I also want to recommend it, but only to those who enjoy figuring out why their installation is broken after what was a harmless minor or even patch release.
The amount of configuration updates, broken plugins… on top of what was already a difficult product to customise; it’s simply too much.
Why isn’t `opencode-workspace` the default, given that the base product is barely usable? Bah. I just reinstalled AGY and Mistral’s Vibe and got on with the work.
I’m old. It’s an open-source, gratis thing. I’m grateful for projects like OpenCode, but it was infuriating to configure a good set of plugins and prompts for spec-driven development, only to have it all stop working a few times because of something hard to debug.
Re: OpenCode – Open source AI coding agent
#665Earlier 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.
[deleted]
Re: OpenCode – Open source AI coding agent
#666Can someone explain how Claude Code can instantly determine what file I have open and what lines I have selected in VS Code even if it's just running in a VS Code terminal instance, yet I cannot for the life of me get OpenCode to come anywhere close to that same experience? The OpenCode docs suggest its possible, but it only works with their extension (not in an already open VS Code terminal) with a very specific key…
The claude code application installs a VSCode extension on first run that handles this communication. Seems like OpenCode is lacking this integration.
Re: OpenCode – Open source AI coding agent
#667[flagged]
With OpenCode, I've found that I can do this by defining agents, assigning each agent a specifically model to use. Then K manually flip to that agent when I want it or define some might rules in my global AGENTS.nd file to gives some direction and OpenCode will automatically subtask out to the agent, which then forces the use of the defined model.
[flagged]
Re: OpenCode – Open source AI coding agent
#668Re: OpenCode – Open source AI coding agent
#669Earlier quoted context omitted.
I have the impression that most vibe coders don't read code. I guess they would probably use something accessible to them, just in case.
[flagged]
LLMs should know that, for maybe a CRUD app, there should be taken care of security at various layers, i.e. input validation in controllers. Knowledge from popular frameworks that communicate security boundaries should be transferable for them, even if everything is custom code. Very confusing to me how they manage to completely ignore so much of it. I guess they are too good following suit of a productivity minded vibe coder.
Re: OpenCode – Open source AI coding agent
#670Earlier quoted context omitted.
I had to double check this. Here is summary: The model selection for title generation works as follows (prompt.ts:1956-1960): 1. If the title agent has an explicit model configured — that model is used. 2. Otherwise, it tries Provider.getSmallModel(providerID) — which picks a "small" model from the same provider as the current session, using this priority list (provider.ts:1396-1402): - claude-haiku-4-5 / claude-haik…
When I did this, I used a single local llama.cpp server instance as my main model without setting a small model and it did not use it for chat titles while I used it for prompts. Chat titles would work even when the local llama.cpp server hadn't started, and it was never in the the llama.cpp logs, it used an external model I hadn't set up and had not intended to use. It was only when I set `small_model` that I was ab…
Maybe it was for older version?