jborland

Great thanks. We are working on this.

Wondering why they necessarily have to be on the same git branch?

Take your refactoring example. Start with base branch ‘A’, then for each of the 3 related components, create a new git branch from branch ‘A’.

If we built this on the Twigg interface, would this be useful?

Nice! Excited to see what you come up with. Best of luck

Thanks! We can hope ;)

Not currently, sorry. But you can sign up and use it for free, with paid options for higher rate limits and better models.

Yes! That's top on our priority list - will update when we have added it.

Thanks! We've been working on this since July - we found it takes quite a while to get something from idea stage to an actual production version.

Regarding data agreements, we have the standard 'enterprise' agreement with the providers, which is that none of your data will be used for training purposes, and will be deleted after a standard specified time window (30 days).

Great to hear others are thinking along similar lines!

Context pollution is a serious problem - I love that you use that term as well.

Have you had good feedback for your fork-off implementation?

That's great to hear! Best of luck with it, let me know how it goes.

I definitely think that there is a lot of work to do with context management UX. For us, we use react flow for our graph, and we manage the context and its tree structure ourselves so it's completely model agnostic. The same goes for our RAG system, so we can plug and play with any model! Is that similar for you?

Thanks for the feedback. We will add in CLI integration soon!

Could you please explain what you mean by "within branch" context switches?

The way Twigg works is you can choose exactly what prompt/output pairs (we call them nodes) are sent to the model. You can move 'nodes' from one branch to another. For example, if you do a bug fix in one branch, you can add the corrected solution as context to another branch by moving the node, whilst ignoring the irrelevant context spent trying to fix the bug.

This way you can specify exactly what context is in each branch.

Thanks! I totally agree, we want to add CLI agent integration! I often use Gemini CLI (as it's free), and it's so frustrating not being able to easily explore different tangents.

Would you prefer a terminal Claude-Code style integration, or would browser based CLI integration work too?

Yes, you can switch models any time for different chat nodes. So you can have different LLM review each others work, as an example. We currently have support for all the major models from ChatGPT, Gemini, Claude and Grok. Hope this helps