Denshin 0.0.23
- After your Mac restarts, a session you ran with
denshin runnow comes back withdenshin runwhen you resume it, from Resume or Resume all in Activity or withdenshin resume --interrupted: on its account, in its folder, on the version installed then, and it moves to another account at a usage limit and goes on by itself again. Until now it came back as the bare agent, with none of that. The list says “held by denshin run”; a session whose account Denshin no longer knows, or thatdenshin runrefuses, comes back as before, and Denshin says why. Checked with a real background service and stand-in agents, not yet across a real restart. Sessions Activity Command line Reliability - When the account a session is moved to at a usage limit refuses it, the session goes back to its own account as before, and now the next move still types the message to continue, if it comes within 15 minutes of the limit. Until now that next move typed nothing. A Codex session also makes that next move as soon as its screen is still, instead of waiting for it to look idle. Checked with stand-in agents, not yet with a real Claude or Codex. Sessions Accounts Reliability
- Denshin now also reads a Codex usage limit in the record Codex keeps of each session. A limit the screen no longer shows, after a relaunch that does not draw it again or under a question drawn over it, now moves the session to another account without waiting for it to look idle, and the message to continue follows. Checked on the shape of real Codex records, not yet read from a live session. Sessions Accounts Reliability
- To get them: the return after a restart comes with the background service, which follows the app by itself at a quiet moment, within about three hours with automatic updates on;
denshin restartdoes it right away. Running sessions keep running, their terminals reconnect, and what is typed in a terminal while it reconnects is lost. The return also holds fordenshin runsessions already running, as long as the service has this version before the Mac restarts. The two fixes at a usage limit need a session started withdenshin runafter the update; a session started with 0.0.22 moves onto this version at its next account switch once the service runs it, a move not yet seen between two published versions. Updates Sessions