Omniscio

Re-run from here (edit a message & re-run in a new session)

Pick any message in a conversation and re-run the chat from that point in a brand-new session: reword one of your own messages and resend it, or write a fresh next message from an AI reply. Omniscio forks a session that shows the whole conversation up to the point you picked, and never changes the original.

On this page

What it is

Pick any message in a conversation and re-run the chat from that point in a brand-new session. You can reword one of your own messages and resend it, or — if you anchor on one of the AI's replies — write a fresh next message. Either way Omniscio forks a new session that shows the whole conversation up to the point you picked (so it reads like the same chat continued, not a blank new session), runs your message there, and drops you into the new chat. The original conversation is never changed — re-running always forks; it never edits in place or rewinds the session you started from.

This is the answer to "can I edit a message I already sent?" — you can't change a sent message in place (the agent already saw it, and the transcript is the real context the CLI resumes from), but you can edit it and re-run from there into a clean fork. The fork runs on the same engine the conversation was already on — a Codex conversation continues on Codex, a Gemini one on Gemini — and carries that session's engine, model and thinking level, so you get the same assistant with your correction applied rather than a different one.

Where to find it

How to use it

  1. Hover the message you want to re-run from and open its actions:
    • On one of your messages, choose "Edit & re-run from here" (the ⋯ menu). A box opens pre-filled with that message so you can reword it.
    • On an AI reply, choose "Re-run from here" (the ⋯ menu). The box opens empty — type the next message you want to send.
  2. Edit or type your message, then press Ctrl+Enter (or click "Re-run in new session").
  3. Omniscio opens a new session that shows the earlier conversation (cloned into it) with your edited message in place, and runs it. You land in the new chat. A clickable "Spawned by …" note at the top links back to the original, which is left exactly as it was.

What carries over: everything in the conversation up to the message you picked — for your own message, everything before it (your edited text replaces it); for an AI reply, everything up to and including that reply (you continue after it). The new session shows that earlier conversation — a visible clone of your and the AI's turns — so it reads like the same chat, with your edited message in its place. If the history is too large for the model's memory, Omniscio keeps the most recent part that fits for the AI and shows a small note that the assistant only remembers the recent part (you still see all of it above). Attachments in the earlier turns show a light "[attachment]" marker rather than the original file (v1), and the new session continues on the same engine and model the source session was running — unless that session's model cannot run on its own engine (an old row), in which case the fork still lands on the right engine using that engine's default model.

How it behaves

Not over the CLI

There is no agent version. POST /session/:id/rerun-from-message is retired and answers every caller 410 GONE: its body carried the new chat's first message, so an agent could start a copy of your session with your words rewritten, and that message would read as yours. Only you re-run from a message, from the message's menu in the app.

Bringing the fork's work back

When the fork finds what you were after, open the fork's ⋯ menu and choose Bring back to <the original session>. Its new messages (never the copied earlier chat) go into the original session's message box as one removable chip, and nothing is sent until you send. See Bring a fork back.

  • edit-a-user-message.md — the broader "can I change a sent message?" question (in-place edit still isn't possible; re-run-from-here is the fork-based answer)
  • session-provenance.md — the "Spawned by" link back to the original
  • asides.md — the other fork mechanism (a one-off side question against the same session)
  • start-a-new-session.md — a fully fresh session with no carried context
  • bring-a-fork-back.md — carry the fork's new messages back into the original

Last verified 2026-10-26