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?

▲

confusus 6 days ago | parent | next [-]

Definitely terminal! Browser might work but honestly I would just not use it

▲

captainkrtek 12 days ago | parent | prev [-]

Imo I’d prefer terminal for this as well. Ie; if I could keep context specific to a branch, or even within a branch switch contexts.

▲

jborland 12 days ago | parent [-]

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.

▲

captainkrtek 11 days ago | parent [-]

Sure, currently I’m performing a big refactor. As I do this, I find myself switching between refactoring perhaps 2-3 related (but still separate) components in my code. I find claude struggles to separate them if I’m working on one then need to switch tracks. Being able to contain the work on each part (all within the same git branch) but in separate contexts, may be helpful to prevent misinterpretation.

	▲	jborland 10 days ago \| parent [-]
		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?