Repository navigation
Bloks 2.2: Rewind, and a backup engine
Two ways to stop losing work: take a conversation back, and keep going when an engine runs out.
Rewind to here
Hover any message you sent and press the clock. That message and everything after it are taken back, the agent starts a fresh session that has heard only what is left, and every file it changed since is put back, newest turn first. Any file you edited yourself since is left alone and named. Your message returns to the box, to send again or change first, and what was rewound folds into one line you can open. How it works
A backup engine
Pick one in an agent's settings. When a turn fails because the agent's engine is out (a usage limit, a rate limit, no credit, an outage, signed out), the backup picks up the same message with the conversation so far, and the chat says what happened. The engine that ran out rests until it said it would be usable again, for every agent on it, and each agent goes back to its own engine by itself after that. Failures about the work itself, like a failing test, still fail as before. How it works
Also
- Claude Code's own error text (for example its usage limit message) now shows as the reason a turn stopped, in routine runs too.
- Rewinds are written to the tamper-evident record.