some things mention are outdated - particularly the tool call pruning feature. this has been disabled by default for a while specifically because of complaints like this

when we looked through our data it's not so clear cut that it's net negative https://x.com/thdxr/status/2048268697790300343

also i'm pretty excited about our new system prompt approach - can define each component in a way that avoids busting the cache when they change. eg that midnight issue: https://x.com/thdxr/status/2070721003924103651

providers (anthropic is the first) are supporting this as a native concept

Comments URL: https://news.ycombinator.com/item?id=48914805

Points: 3

# Comments: 0

it will use whatever small model there is in your provider

we had a fallback where we provided free small models if your provider did not have one (gpt nano)

some configs fell back to this unexpectedly which upset people so we removed it

the issue that was reported was fixed as soon as we heard about it - going through the process of learning about the CVE process, etc now and setting everything up correctly. we get 100s of issues reported to us daily across various mediums and we're figuring out how to manage this

i can't really say much beyond this is my own inexperience showing

we've done a poor job handling these security reports, usage has grown rapidly and we're overwhelmed with issues

we're meeting with some people this week to advise us on how to handle this better, get a bug bounty program funded and have some audits done

Comments URL: https://news.ycombinator.com/item?id=44867374

Points: 251

# Comments: 42

and nothing expires out from the session until you get near the context window max - at which point we do a compaction process

we're a little over a month into development and have a lot on our roadmap

the cli is client/server model - the TUI is our initial focus but the goal is to build alternative frontends, mobile, web, desktop, etc

we think of our task as building a very good code review tool - you'll see more of that side in the following weeks

can answer any questions here

but we're going to make all this very configurable next week

we're very focused on UX and less so on LLM performance. we use all the same system prompts/config as claude code

that said people do observe better performance because of out of the box LSP support - edit tools return errors and the LLM immediately fixes them

You might be familiar with Claude Code but OpenCode runs a full TUI rather than the typical scrolling CLI output.

This allows for better UX and can be used with any LLM. We're also working on support for using multiple LLMs together.

It has built in support for LSP servers so it can pick up errors from your codebase. We've found this greatly reduces the bad errors.

Some other features - Session Management: Save and manage multiple conversation sessions - Tool Integration: AI can execute commands, search files, and modify code - Persistent Storage: SQLite database for storing conversations and sessions - LSP Integration: Language Server Protocol support for code intelligence - File Change Tracking: Track and visualize file changes during sessions - External Editor Support: Open your preferred editor for composing messages

Comments URL: https://news.ycombinator.com/item?id=43988566

Points: 3

# Comments: 0

even if the models do not get better there is so much demand even just b2b

we have all these problems we can fix but we are totally limited by availability

cloud providers are overwhelmed by the demand - you can see this in how stingy they are with rate limits and how they don't even talk to you unless you've already spent a lot with them