Long sessions keep their context — and their price
Reconnects, /compact and /resume no longer rebuild your conversation from scratch — a session comes back exactly as it was, and costs a fraction of what it used to. Plus faster web lookups and a cleaner terminal.
Improved
- Session context survives everything — a dropped connection, a sleeping laptop or a server update no longer costs you your context. The session comes back with everything it had, and the model keeps working from the same understanding instead of quietly losing part of it.
- Near-free reconnects — rejoining used to be billed as if the whole conversation were new. It now reuses the cached context almost entirely, which on a long session is the difference between cents per message and fractions of a cent.
- Cheaper
/compact— summarising a long conversation no longer re-processes it from scratch, so compacting is both faster and dramatically cheaper. - Faithful
/resumeand rewind — the conversation is restored exactly as it was rather than rebuilt approximately, and keeps the same pricing benefit. - Parallel web lookups — when the assistant looks several things up at once, the requests now go out together instead of one after another, so a batch takes about as long as the slowest one rather than the sum of all of them.
- Lookups no longer block the turn — files read in the same step appear straight away instead of waiting behind the network. Anything you still have to approve is untouched and runs in order, exactly as before.
- Clearer fetches — fetching a page now shows the address instead of the long instruction that goes with it, and reports how much was actually downloaded and how the site answered.
- Dashboard — cached usage is now shown as a percentage, and the usage chart's tooltip includes what you spent that day.
Fixed
- Resuming a session immediately after launching the CLI could leave the assistant with none of your history — the terminal showed the conversation while the assistant had nothing. This was worst right after a
/compact, where the summary is the entire conversation. The history is now held and delivered as soon as the connection is up. /resumeno longer offers conversations whose transcript is gone — those opened as a blank session with no explanation. The list now shows only what can actually be restored, and cleans itself up.- A session now appears in the list from its very first message. Starting a conversation and closing the terminal within a few seconds could previously leave it off the list entirely, even though it was saved.
- Resuming a conversation no longer shrinks it in the list: it keeps its real message count and its original first line instead of being relabelled after your next message.
/rewindnow lists only your own messages — internal bookkeeping entries no longer appear as things you can roll back to, and the restore-code marker lands on the right message.