Go back to an earlier point, on a new branch
Moves back to an earlier entry and continues from there — the conversation, the files, or both. Rewinding ALWAYS branches and never deletes: the timeline walked away from stays in the tree with its own tip, navigable and continuable, so going back is a way to stop adding to something rather than a way to lose it. Undoing a rewind is continuing the abandoned branch again, not a second mechanism. The same is true of the files. Before anything is restored, the working tree AS IT IS becomes its own restore point, so the state the rewind moved away from can be put back byte for byte. Nothing in the person’s own git history sees any of it; the restore points live in narya’s shadow repository beside the checkout. scope has no default, and a request omitting it is refused. The two axes fail in opposite directions — rewinding the conversation without the code leaves the agent arguing with a working tree it cannot see, rewinding the code without the conversation throws away work the transcript still claims exists — so this operation never guesses. A scope that moves files is refused with 409 while a turn is in flight anywhere in this checkout, which includes another session standing in it: several sessions share one working tree and one set of restore points, and restoring under a live tool would destroy whatever it is part-way through writing. The refusal names the session that is working, and scope=conversation is unaffected because it touches no file.
Path Parameters
The session's id.
Body
Where to go back to, and what to take back. Both fields are required: there is no default scope, and a request without one is refused rather than guessed at.
The transcript entry to go back to. For a conversation rewind the new branch continues from this point. For a code rewind the files return to the restore point standing at this entry, or to the nearest one before it.
Required in every request, and IGNORED in exactly one: a code rewind that sets partEntryId takes its restore point from that step instead, because a step already says which moment it undoes. It stays required rather than becoming conditional so that one field always names the moment a rewind is about, whatever else narrows it.
What the rewind takes back. code restores the working tree and leaves the conversation exactly where it is, in this same session. conversation branches at the entry and leaves every file untouched. both does the two together, so the new branch continues against the restored tree. Deliberately without a default: guessing wrong in either direction breaks something the other direction would have preserved.
code, conversation, both Optional title for the new branch. Meaningless for scope=code, which creates no session.
512Narrows the restore to exactly these files and leaves every other one alone: reverting a whole step is often too much, because the agent got four files right and one wrong. Absolute paths inside the session's repository; one that resolves outside it is refused and nothing is written. Each path names a FILE: one naming a directory is refused too, because restoring a directory would put back everything under it and remove whatever this session added there while reporting the one path that was sent. Name the files inside it, or revert the whole step with partEntryId instead. Meaningful only with scope=code — any other scope with this set is refused, because there is no honest reading of "branch the conversation, but only these files". A whole-tree restore point is still taken first, so the undo of a one-file revert is the same mechanism as the undo of everything else. An EMPTY list is a 400, never a whole-tree restore: leave the field out to revert everything, because a selection that filtered to nothing must not overwrite the files on disk.
1 - 512 elements4096Reverts one transcript entry's worth of file effects as a unit: the files that entry wrote, edited or deleted go back to how they stood immediately before it, and nothing else moves. A file the entry only READ is not touched — reverting a read would put back a file the agent merely looked at. Meaningful only with scope=code, and never together with paths, which would be two answers to one question.
Response
The files were restored and this session continues. Answered for scope=code, whose whole point is that the conversation does not move.
A durable conversation container. Survives the process that created it; archiving hides it from active lists but its transcript remains queryable and exportable forever.
The session's id.
Absolute path of the repository the session works in.
4096Lifecycle: running while a turn executes or normal follow-ups chain; waiting after interrupt when admitted steering or follow-up inputs remain queued; idle only when neither execution nor queued input exists; archived accepts no new work.
idle, running, waiting, archived Which kind of client opened this session, recorded when it was created and never rewritten. Always present: unknown for a session created before this host recorded the datum, which is the honest answer rather than a guessed frontend.
inline, tui, oneshot, api, unknown Human-readable title.
512The model provider currently in use.
The model currently in use.
The preset of request options this session's turns run under — the name, not the options it stands for, since what a name means is the catalogue's answer and can change while the session's own choice cannot. Absent on a session that never chose one, which is every session running its model at the model's own defaults.
The named response style this session's answers are shaped by — the name, not the prompt it appends, since what a name means is configuration's answer and changes when somebody edits that file while the session's own choice does not. Absent on a session that never chose one, which is every session answering in narya's own voice. Unlike variant it survives a model switch: a style is a fact about how the conversation reads rather than about the model answering it. A client renders this and derives nothing — the names that exist are the host's answer (setSessionStyle refuses the rest).
64One sentence stating what a client could not otherwise know about the model this session opened on or was just moved to, present on the responses to createSession and setSessionModel. Two facts earn it. The first is a model narya chose itself rather than being told to use: no default_model configured and no model previously chosen, so the first provider holding a usable credential answered — or a named model the catalogue no longer carries, for which the provider default was substituted. It names the alternatives that also qualified and how to choose another, because a choice nobody made has to be stated to be a choice at all rather than something that merely happened. The second is a level this session will run without: a model reference may carry one (see the variant field), and an endpoint that does not take the field runs at its own default instead — so a level named at creation or at a switch, or configured beside default_model, is said here rather than quoted in a picker while every request drops it. A client that renders the live event stream rather than the session's transcript has no other road to it. Otherwise absent, including for a model that was simply configured, chosen or named; absent on getSession and listSessions, which report state rather than how it came about.
1024What this session has consumed and cost across every turn it has run — a running total, not the last turn's figure. Carried by getSession and by every row of listSessions, so a client drawing a list of sessions can say what each one has cost without asking per row. Absent on a session that has never completed a turn, and its costUsd is absent whenever any one of that session's turns could not be priced: the sum over only the priced turns is smaller than what the session actually cost, and a figure that quietly understates money is worse than an admitted unknown.
What the newest round of this session's own conversation sent and produced — the LAST turn's figure, not the running total above. Carried by getSession only. It exists because the two are not interchangeable for the one question a reader reopening a long conversation asks: how much room is left before this compacts. That answer is the size of the prompt last sent, and usage above is a sum over every turn the session ever ran, which is a larger number growing without bound and means nothing as a fraction of a context window. The live event stream carries this figure on turn-finished, so a client watching a session has always had it; a client that READ the session had no source for it at all and drew no context figure until it spent a turn of its own. Restoring a recorded reading rather than deriving one is the whole of it — nothing here is computed from the transcript. The newest round of the MAIN lane: a delegation's rounds are another conversation's prompts, and the figure is about the reader's. Absent on a session that has never completed a round, and on one whose rounds all ran on delegates. Its costUsd is that one round's price, absent when the round could not be priced.
Pending steering and follow-up references in durable operation order. Content is intentionally absent; fetch the transcript by entryId.
When the session was branched, the session it branched from.
What a model said this conversation tried and concluded. Absent until somebody asks for it (summarizeSession) — nothing summarises a branch because a rewind moved away from it. A model that answers past this length is trimmed to it, with a marker saying so rather than a sentence that just stops.
4096When the summary was taken. Read against updatedAt it answers whether the summary predates the last thing that happened here.
Whether somebody is there to answer a permission prompt raised here. Absent on a session nobody ever said either way about, which reads as attended — the posture is only ever recorded because somebody stated it (setSessionPosture), never inferred from whether a client happens to be connected.
attended, detached Whether this session pays to keep its provider cache alive while nobody is using it, and the most it may ever spend doing so. Absent on a session nobody ever turned it on for, which is every session until somebody does — warming is off unless somebody asked (setSessionWarming).
When a reader last had this session in front of them (acknowledgeSessionViewed). Read against updatedAt it answers whether anything has happened here since somebody looked, which is what lets a client mark a background conversation as carrying news — and, because the fact is held here rather than in a window, what makes two clients agree about it and makes the answer survive a relaunch. ABSENT on a session nobody has ever viewed, which is not the same as viewed long ago: one has nothing to report, the other has everything that ever happened in it.
How the last turn here ended. It is what lets a client that was not running at the time tell a conversation that finished from one that failed. Absent on a session that has never run a turn. An interrupt is not among the values: somebody was there and stopped it themselves, so it is not news to bring back to them.
finished, failed What this session's provider prompt cache has cost it, from both sides: what letting it expire cost, and what keeping it alive cost. Present only on getSession, and only once one of the two has happened — a session that has never paid for either carries nothing here rather than a pair of zeros.
The agent's own task list for this session — every item it has written, in the order it wrote them, whatever is in the store right now.
It is here rather than behind a listing of its own because the list is a stored row and every client already reads the session when it attaches, so one optional field costs no round trip and no second operation. A change to the list is announced as task-list, which carries the same whole list for the same reason; this is where a client that was not attached at the time gets it.
Present on getSession only, like lastTurnUsage and cacheSpend and for their reason: a listing that carried it would read every row's tasks to draw a page nobody asked for.
ABSENT MEANS EMPTY, and it cannot mean anything narrower: the store holds rows, so a list nobody ever wrote and a list somebody cleared are the same read. The live stream is where those two differ — a clearing write announces task-list carrying an empty array — and a read that returned [] would be claiming to know which of the two it was looking at.