5 ms·

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

by thdxr 1y 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

cchance 1y ago
Would be cool if it could be an alternative frontend for gemini-cli, claude code, acli and the other tui's
gwd 1y ago
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-caching https://docs.anthropic.com/en/docs/build-with-claude/prompt-...
- threecheese 1y ago
  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 https://github.com/sst/opencode/issues/254
  - thdxr 1y ago
    we actually do heavily use prompt caching now
- thdxr 1y ago
  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
  - gwd 1y ago
    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.
    - gwd 1y ago
      > partly because the quality tends to degrade with the length of the context. And as if to emphasize this, I was using opencode this morning with Sonnet; but once the context window got up close to 100k, only about 30% through implementing a new feature (which doesn't seem that large to me), it repeatedly failed with "Error: oldString not found in content or was found multiple times", which I take to mean that it wasn't generating patches in the right format. This isn't the first time this has happened to me. Maybe my code is just more complicated than other people's, so it gets confused more easily. But having tools to manage the complexity the LLM is exposed to has been critical to making it useful.

by thdxr 1y ago

cchance 1y ago

Would be cool if it could be an alternative frontend for gemini-cli, claude code, acli and the other tui's

gwd 1y ago

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-caching https://docs.anthropic.com/en/docs/build-with-claude/prompt-...

threecheese 1y ago
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 https://github.com/sst/opencode/issues/254
- thdxr 1y ago
  we actually do heavily use prompt caching now
thdxr 1y ago
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
- gwd 1y ago
  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.
  - gwd 1y ago
    > partly because the quality tends to degrade with the length of the context. And as if to emphasize this, I was using opencode this morning with Sonnet; but once the context window got up close to 100k, only about 30% through implementing a new feature (which doesn't seem that large to me), it repeatedly failed with "Error: oldString not found in content or was found multiple times", which I take to mean that it wasn't generating patches in the right format. This isn't the first time this has happened to me. Maybe my code is just more complicated than other people's, so it gets confused more easily. But having tools to manage the complexity the LLM is exposed to has been critical to making it useful.