Obliviate: Recover a Spoiled AI Agent Session Without Starting Over

You are coordinating two agent tasks. One session is focused on Task A, while another agent is handling Task B. Then you paste Task B's request into the Task A session by accident.

You correct yourself in the next message, but the incorrect request is still part of the history. The agent can keep treating it as relevant context, bringing the wrong domain, constraints, or implementation direction back into a task that was otherwise on track.

What Obliviate Changes

Obliviate treats session history as an editable artifact. Instead of abandoning a useful conversation because one request was sent to the wrong agent, you can remove that turn or redo it with the correct instruction.

The edit is deliberately designed to be safe:

• The source or live session is never modified.
• Every edit happens on a fork of the session.
• Deletion requires explicit confirmation of the complete affected set.
• Structural IDs and references are preserved and validated; every mutation keeps a backup.

Install Obliviate

Claude Code

Add the marketplace, then install the plugin:

Verify that obliviate appears in /plugin. Restart Claude Code if it asks you to do so.

OpenCode

Install the OpenCode skill and editor agent into the current project:

Add -- --global to make it available to all projects:

For a project install, confirm that .opencode/skills/obliviate/SKILL.md and .opencode/agents/obliviate-editor.md exist. For a global install, confirm the same paths under ~/.config/opencode/. Restart OpenCode after installation because skills and agents are not hot-reloaded.

Recover the Session

1. Identify the accidental request. Locate the turn containing the request intended for the Task B agent.
2. Ask Obliviate to remove or redo it. Use a clear request such as "remove the request I sent to the wrong agent" or "redo my earlier request with the Task A instructions."
3. Review the forked session. Obliviate shows the affected turns before making the history change.
4. Confirm the affected set. Verify that the selected turns are the accidental cross-task instructions, then approve the edit.
5. Continue with corrected context. Work in the forked session, where the mistaken Task B request no longer distracts the Task A conversation.

When This Is Useful

• A prompt for another agent task was sent into the active session.
• An earlier prompt was based on an assumption that proved false.
• A dead-end approach is repeatedly influencing later answers even after it was corrected.

Keep the Useful Context

Restarting a session is expensive when most of its context is still valuable. If one cross-task request spoiled an otherwise productive conversation, Obliviate lets you correct the history instead of throwing the whole session away.