A sent message can only be copied — no way to edit or delete it #91

Activity

1. hussain

   added

   enhancementNew feature or requestNew feature or request

   on Oct 8, 2026
2. hussain commented on Oct 11, 2026

   

   hussain

   on Oct 11, 2026

   Member

   More actions

   Thanks for the report. Here is where this stands, as of 2026-10-11.

   Why patchbay can't do it on its own. The conversation belongs to the agent: it is what the agent replays when a session reloads, and what it builds its next turn on. Hiding a message only in patchbay would leave it in the agent's history, so it would still shape the next answer and come back on reload. Resending a trimmed copy into a new session would cost real model turns and still couldn't undo tool calls that already ran. Edit and Delete need the agent to change its own history, and that requires a protocol (ACP) method.

   What ACP offers today: nothing yet.

   • ACP v1 has no edit or delete. session/fork exists (still marked unstable), but it copies the whole session, unwanted message included.
   • The ACP v2 draft gives every message a stable id, which these features need, but it doesn't define edit or delete yet.

   The two proposals in flight:

   Proposal	What it does	Status
   Session Rewind, RFD #1321 (v2)	session/rewind cuts history at a message. session/edit_prompt replaces a sent prompt and runs again from there. Behind a session.rewind capability.	Open; last activity 2026-05-31
   Session cursors, RFD #2114	The agent hands out markers at points in the conversation, and session/fork can start a new session from one.	Open; last activity 2026-09-07

   Rewind is the direct match: Edit is edit_prompt, and Delete is rewinding to just before the message. Cursors give a branch instead: a new session that starts before the message, while the original stays as it was.

   What's available now:

   • Stop while the turn is still running catches most accidental sends.
   • Copy prompt, then resend the corrected text. Earlier prompts can't be reached — not to reuse one in the composer, not to jump to one in the transcript #59 tracks making that reuse quicker.

   What would trigger the work. Patchbay will build this once two things are true:

   1. One of these methods lands in a published ACP schema.
   2. An agent declares support for it.

   Then Edit and Delete appear on a sent message, for agents that declare the capability. Until then, this stays open as the record.
3. hussain commented on Nov 2, 2026

   

   hussain

   on Nov 2, 2026

   Member

   More actions

   Thank you for the careful report. I'm closing this as not planned for now. Here is why, and what would bring it back.

   Nothing has changed on the protocol side since my last comment. Neither Session Rewind (RFD #1321) nor session cursors (RFD #2114) has landed in a published ACP schema. Until one does, an agent has no way to change its own history, and patchbay won't fake it with a copy that the agent would still build on and replay.

   What patchbay does today, wherever the agent declares support:

   • Fork (⋯ menu) opens a new session that carries the history, and leaves the original as it was.
   • Delete… removes a whole session from the agent's history.
   • Stop, while the turn is still running, catches most accidental sends. Copy prompt lets you resend corrected text.

   To be clear, none of these reaches a single message. A fork still contains the message you wanted gone. They're the closest options available, not what this issue asks for.

   I'll reopen this when one of those methods lands in a published ACP schema and an agent declares support for it. At that point Edit and Delete will appear on sent messages for every agent that offers them.
4. hussain

   closed this as not plannedon Nov 2, 2026