I’m not an expert in this problem but could we just fork the current chat from a given point?
Then I would be able to choose a prompt I sent maybe 2-3 prompts ago that I know is a good state to continue the work from.
Or could we have an option here to reduce the current context window by some method like filtering / summarization / replacement of parts (automatically)?
Are there any plans for this?
We have plans to introduce automatic compactation, see the roadmap: Tidewave Public Roadmap · GitHub
if you are using the new Claude Code or Codex support, they already compact for you.
I used Tidewave last night to solve some longstanding UI nits on my app. Not having to manually fight CSS / Tailwind for hours to get the UI I want is well worth a little iterating with the agent! Very nice!!
Quick question… I used my existing Anthropic API Key (Sonnet 4.5) and the small changes burned through credits pretty quickly compared to my normal agent workflow inside Zed using the same model. I’m assuming it’s all of the JS testing code which of course Zed agent is not generating that is the difference. It wasn’t too bad just a few dollars but they were pretty small changes and if I were using it all day it would quickly add up!
So I noticed Claude Code integration was recently released as an alternative to using the Anthropic API keys and looking at the documentation it appears to be the recommended path (since it’s listed first in the guides and “Bring your own keys” is introduced as “You can also use…”). I was wondering is the benefit of using Sonnet 4.5 through Claude Code from Tidewave so we can use our Pro/Max subscriptions and save money or are there some other context/response quality improvements doing it that way versus just using our API keys?
If you want to save money then you can use openrouter and just go with a free model, they are good actually.
For ex. grok 4.1 fast is free now.
Correct and the preferred method forward is through Claude Code / Codex for those with Anthropic / OpenAI subscriptions!
