we implemented a similar idea some time back and it has proven quite useful: https://blog.codesolvent.com/2025/01/applying-forkjoin-model...

In Solvent, the main utility is allowing forked-off use of the same session without context pollution.

For instance a coding assistant session can be used to generate a checklist as a fork and then followed by the core task of writing code. This allows the human user to see the related flows (checklist gen,requirements gen,coding...etc) in chronological order without context pollution.

▲

jborland 12 days ago | parent [-]

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?

	▲	Edmond 12 days ago \| parent [-]
		Feel to "borrow" the term "context pollution" :) Yes it has proven quite a useful feature. Primarily for the reason stated above, allowing users to get a full log of what's going on in the same session that the core task is taking place. We also use it extensively to facilitate back-and-forth conversation with the agents, for instance a lot of our human-in-loop capabilities rely on the forking functionality...the scope of its utility has been frankly surprising :)