2 ms·
Actually, the ability to retain the current version when jumping back in conversation history is extremely useful for one reason: trimming context. For example
by d4rkp4ttern 1y ago
Actually, the ability to retain the current version when jumping back in conversation history is extremely useful for one reason: trimming context. For example I could work on adding a feature X, which will add some context. Then I rewind and add feature Y, etc. This helps delay compaction.
- Wowfunhappy 1y agoYes, as I said there needs to be a way to jump back without rolling back the code as well!
- adastra22 1y agoYou can. There is a slash command to move back to a prior point in the conversation. On mobile rn, but I know the is command exists as I’ve used it before.