3 ms·

The /tree feature is incredible for context management. It's really surprising the other harnesses haven't slurped it up yet. It lets you rewind back to any pre

by timwis 2mo ago

The /tree feature is incredible for context management. It's really surprising the other harnesses haven't slurped it up yet. It lets you rewind back to any previous message and fork the conversation from there, removing your 'side quest' (e.g. where you dig into something the agent said) from the context. Some other harnesses have a 'rewind' feature, but this lets you maintain the previous conversation history in a separate thread, and even jump between them.

anon7000 2mo ago
I think cursor has this where you can fork a thread from a previous message
- newtwilly 2mo ago
  Yes, pi's works a bit better since it exposes the whole tree to you, but in the simple case of forking to a new conversation it is about the same as Cursor and probably other coding agents. One thing you can do in pi that you can't in Cursor: Have a 5-prompt conversation, jump back to prompt 3 and have a new conversation [call this convo2], then jump back to the original point 5, then jump back to convo2. So fork is really only needed for when you need to interact with the conversation tree in two separate processes.
paldepind2 2mo ago
You can do that in Copilot in VSCode. There’s a fork icon before every message that creates a new session from that point. The relationships are not maintained in a tree though (not sure if Pi does that).
- wongarsu 2mo ago
  Claude code in the cli also has /fork to clone the current session state. But if you use it more than once or twice that quickly becomes hard to manage. Actual tracking in a tree sounds like an awesome feature (and one that I love in conversational UIs like openwebui as well)
veber-alex 2mo ago
You can fork a conversation in Claude as well.
- timwis 2mo ago
  Only at the current point in the conversation though, right? You can't rewind and then fork from a previous message, as far as I know
baby 2mo ago
Double escape in other coding agents
catlover76 2mo ago
[dead]

by timwis 2mo ago

anon7000 2mo ago

I think cursor has this where you can fork a thread from a previous message

newtwilly 2mo ago
Yes, pi's works a bit better since it exposes the whole tree to you, but in the simple case of forking to a new conversation it is about the same as Cursor and probably other coding agents. One thing you can do in pi that you can't in Cursor: Have a 5-prompt conversation, jump back to prompt 3 and have a new conversation [call this convo2], then jump back to the original point 5, then jump back to convo2. So fork is really only needed for when you need to interact with the conversation tree in two separate processes.

paldepind2 2mo ago

You can do that in Copilot in VSCode. There’s a fork icon before every message that creates a new session from that point. The relationships are not maintained in a tree though (not sure if Pi does that).

wongarsu 2mo ago
Claude code in the cli also has /fork to clone the current session state. But if you use it more than once or twice that quickly becomes hard to manage. Actual tracking in a tree sounds like an awesome feature (and one that I love in conversational UIs like openwebui as well)

veber-alex 2mo ago

You can fork a conversation in Claude as well.

timwis 2mo ago
Only at the current point in the conversation though, right? You can't rewind and then fork from a previous message, as far as I know

baby 2mo ago

Double escape in other coding agents

catlover76 2mo ago

[dead]