Skip to content
Denshin.dev

Changelog

What’s new in Denshin 0.0.26

Denshin 0.0.26

  • New: denshin incidents lists every time an agent stopped without you wanting it over the last seven days, counted by day: a usage limit the session did not go on from, a move to another account that failed, an agent that ended on an error or was killed, a session cut by a restart and never brought back, an error the session gave up on, and background work lost at a limit. Each comes with its session, account, how long it stayed stopped and the line of Denshin’s own record that says it; a message to continue that was never typed is told from one typed and never taken. Waiting for a reset when no other account could take the session, and the stops you wanted (a line you typed, a quit), are said apart. --since, --until, --top and --json choose what to read. It only reads what Denshin already writes, and sees only sessions run with denshin run. Checked with tests, with a real background service and a stand-in Claude, and on a copy of one Mac’s week; not yet run by the published app. Sessions Command line Reliability
  • When a session moves to another account at a usage limit and Claude asks a question as it starts again, the keys you press now reach that question: Enter, the arrows and Esc answer it, and Denshin types the message to continue once Claude’s message box is drawn. Until now Denshin held those keys while it waited for the box, so the session stayed at its question and Denshin gave up after three minutes with nothing typed. A word or Ctrl-C typed meanwhile is still yours and goes instead of the message, and so is Ctrl-D now; keys typed meanwhile keep their order. Checked with a stand-in agent on a real terminal, not yet with a real Claude at a real limit. Sessions Accounts Reliability
  • That message to continue now asks to resume each sub-agent that was running by sending it a message, since its conversation is kept, rather than starting it over, and to run again only the background commands whose result is still needed, after reading what they left. Until now it said to restart them, which started sub-agents from scratch. A sub-agent’s turn cut by the limit, and what a command held in memory, cannot come back. The message shows whole in a real Claude Code 2.1.318, in English and in French; whether Claude then resumes its sub-agents rather than starts them over is not yet seen. Sessions Accounts
  • A session that waited at its limit for another account to have room now still gets the message to continue: Denshin types it if the move comes within 15 minutes of the moment another account could take the session, no longer of the limit. On November 4, four sessions on one Mac waited half an hour that way and got nothing typed. Checked with tests, not yet at a real limit. Sessions Accounts Reliability
  • To get them: denshin incidents comes with the app. The three changes at a usage limit need a session started with denshin run after the update; a session started with 0.0.22 or later moves onto this version at its next account switch once the background service runs it, a move not yet seen between two published versions. The service follows the app by itself at a quiet moment, within about three hours with automatic updates on; denshin restart does it right away. Running sessions keep running, their terminals reconnect, and what is typed in a terminal while it reconnects is lost. Updates Sessions

All versions