Comment by thdxr
7 days ago
hey one of the authors here
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
Like it a lot so far!
After a brief play last night, the biggest feature of aider I miss is more control over the context window -- saying "/clear" to re-start the conversation from scratch, or specifying files to add or remove as they become relevant or irrelevant. Not clear how much or how long files stay in the context window.
The other question I have is whether you use Anthropic's "prompt caching" [1] to reduce the cost of the long conversation?
[1] https://docs.anthropic.com/en/docs/build-with-claude/prompt-...
There’s some discussion in GitHub that suggests they are not using prompt caching, but recognize the need and are looking at it: https://github.com/sst/opencode/issues/254
we actually do heavily use prompt caching now
curious why /clear instead of making a new session?
and nothing expires out from the session until you get near the context window max - at which point we do a compaction process
I don't think I realized how the sessions worked; It looks like /new would get pretty close. One of the things /clear does in aider is clear the chat history but not the files you've added (which are always done manually).
Again the theme of the difference is control over the context: partly for cost management, partly because the quality tends to degrade with the length of the context.
But it may be that the main thing needed is just a change of workflow. So far I am finding opencode's ability to find things out for itself quite refreshing.
1 reply →
Would be cool if it could be an alternative frontend for gemini-cli, claude code, acli and the other tui's