Skip to content
Denshin.dev

Changelog

What’s new

Only the changes about Reliability, newest first.

  1. Denshin 0.0.49

    • Denshin no longer holds your speaker open between its sounds. The window's audio now runs only while a chime plays and stops a moment after it; before, it ran silent all day from your first click, and on a busy Mac that open stream could make the speaker crackle. Chimes still ring as before, an agent's question included, with no click. The window Reliability
  2. Denshin 0.0.48

    • A session's browser only writes to the sites its task opened: the first site it opens, plus each one named with --allow. A form sent, a sign-in or any other write to another site is refused, and the agent reads one line per site saying how many were refused and why. Reading a page always goes, and captcha checks still reach their own servers. Sessions Reliability
  3. Denshin 0.0.40

    • After the background service restarts on its own, a session tab opened with the CLI's own resume (claude --resume, codex resume) stays linked to Denshin. Before, its conversation in the window said "not linked to Denshin" and could not be resumed until the agent spoke again. Sessions The window Reliability
    • The background service writes its performance journal again. It could stop writing it while still working normally; denshin perf now says when the journal has gone silent or cannot be written. Command line Reliability
  4. Denshin 0.0.39

    • Trackpad and mouse scrolling in Codex sessions opened by Denshin now moves through the conversation while the input stays at the bottom, including in CMUX. New sessions need no terminal setting or extra Codex flag. Sessions Command line Reliability
  5. Denshin 0.0.38

    • Model controls follow the actual engine version and account. A setting the engine cannot apply is reported explicitly. A requested change says whether it starts on the next turn or needs a new launch; existing subagents keep their current settings. Sessions Reliability
  6. Denshin 0.0.31

    • Fixed: a Claude Code session whose terminal you closed kept running in Claude’s own background, while Denshin listed it as stopped, and opening it started a tab that Claude closed at once. denshin sessions now shows these sessions as running in Claude’s background, under the account that runs them, and denshin open attaches to them with claude attach, never starting a second copy. Sessions Command line Reliability
  7. Denshin 0.0.30

    • Old copies of the background service that nothing runs any more are removed once it has moved to the version the app carries, instead of piling up with every update. Updates Reliability
    • The background service now removes from its list a workspace whose folder is gone and that nothing uses (no tab, no session), once the folder has been gone 10 minutes. It removes the entry only and never touches the disk, and a folder on an unplugged disk under /Volumes is kept. This clears the workspaces left behind by older test runs. Checked with tests and a real background service on a list shaped like one Mac’s, 19 leftover workspaces among them; not yet run by the published service. Sessions Reliability
  8. Denshin 0.0.29

    • Fixed: about one time in 900, a session whose conversation was gone at Claude was taken for a sign-in failure, because its id happened to contain 401, and an agent with another name took its place. It is now rebuilt under its own name. Sessions Reliability
  9. Denshin 0.0.28

    • Fixed a rare fault: what was written to a session’s terminal at the very moment that session ended could reach whatever opened right after it, another connection to the background service, or the next agent after an account switch. Writing to a terminal now stops the moment it closes. Reliability Sessions Accounts
    • Opening a conversation the background service cannot bring back, a session no agent is attached to or one it does not know, now says why in the window instead of waiting with no end. Sessions Reliability
  10. Denshin 0.0.27

    • A session that moves to another account at a usage limit now waits for the end of the running turn instead of cutting it: the command or answer under way finishes first, then the session moves. On Claude, Codex and OpenCode. Sessions Accounts Reliability
    • When pressing Enter is what makes the session move, the message you typed is no longer lost: it is sent on the new account. If that account cannot start, it goes back to the one you were on, and if neither starts, Denshin shows you the message so you can send it again. Sessions Accounts Reliability
  11. 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
    • 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
  12. Denshin 0.0.24

    • An account whose week is used up no longer counts as usable once its 5-hour window comes back: a session at its limit no longer moves to it, --best no longer picks it, and lists say it is back when its week is. Checked with tests on the rule, not yet with a real account at its weekly limit. Accounts Sessions Reliability
  13. Denshin 0.0.23

    • After your Mac restarts, a session you ran with denshin run now comes back with denshin run when you resume it, from Resume or Resume all in Activity or with denshin 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 that denshin run refuses, 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
  14. Denshin 0.0.22

    • When a Codex session hits its usage limit, Denshin now sees it, moves the session to another account and types the message to continue. Until now it could miss the limit, for one once Codex’s question about another model had been moved through with the arrow keys, and wait for the session to look idle: the move came minutes later, with nothing typed to continue. Checked on what a real Codex 0.166.0 draws at a test limit. Sessions Accounts Reliability
  15. Denshin 0.0.21

    • The window no longer says the background service is not responding when one reading of your sessions failed or was slow, and no longer offers to restart a service that works: pressing “Restart it” again and again kept stopping a healthy service. When readings keep failing while the service runs, it now says “Denshin can’t read your sessions right now. The background service is running.” with “Read again”, which reads them again and never restarts anything. After a restart, “Restarting…” stays until a new reading says how the service is. The window Reliability
    • When a session moves to another account at a usage limit, Claude now goes on by itself: Denshin waits for Claude’s message box to be drawn, types the message to continue in it, and presses Enter only once that message shows. Until now it could go before the box was drawn, and you had to send it yourself, sometimes even write it. Checked with Claude Code 2.1.318. Sessions Accounts Reliability
    • Two kinds of usage limit that left a session stopped on its account now move it to another: a turn and a background agent stopped by the limit in the same second, and a limit Claude Code reports as an unknown error. Accounts Reliability
    • On a busy Mac, the background service now hears every usage limit right away. macOS could fail to tell it, and the move to another account then waited for the next check of the account, up to ten minutes, too late for Claude to go on by itself. The service also no longer keeps a watch that could hold it for seconds as it stops. Accounts Reliability
  16. Denshin 0.0.20

    • Clicks and the wheel far to the right of a wide terminal, from column 96 on, no longer type a stray character into the agent: a terminal that joins a running session now learns how the mouse is encoded, and the wheel scrolls there. Sessions Command line Reliability
    • Making or opening a tab no longer redraws the others: a phone or a terminal watching one tab used to get a whole screen each time, and now gets nothing. Sessions Devices Reliability
    • A session made from the phone no longer gets a second full screen five seconds later, and stray text such as [?1;2c no longer lands at an agent’s prompt when a Mac and a phone come back together or on a slow link: Denshin now answers what its terminal server asks when it attaches, instead of leaving that to whoever is watching. Sessions Devices Reliability
  17. Denshin 0.0.19

    • denshin run terminals opened with this version no longer reconnect again and again while your display is off: a terminal app that is slow to read is no longer taken for a bad connection. Sessions Command line Reliability
    • denshin run and denshin attach terminals opened with this version are redrawn on a clean screen after a reconnect, so rows no longer stay wrong until you resize the window, in VS Code’s terminal for one. Sessions Command line Reliability
    • A new agent starts at the final size of its terminal, instead of one row short and resized an instant later. Sessions Reliability
    • If files.denshin.dev cannot be reached, the app checks and downloads its updates from its second address, with the same signature and notarization checks. Updates Reliability
  18. Denshin 0.0.18

    • A question an agent asks you no longer disappears when the terminal is resized or your phone turns: the answers a terminal sends by itself no longer count as you typing. Sessions Reliability
    • From sessions started with this version on, a session that moves to another account no longer leaves its terminal broken (characters out of place, pieces of old frames) until you resize the window: Denshin clears the screen before the next agent draws and never writes over an agent that has drawn. Sessions Reliability
    • A window resized while a session moves to another account now reaches the agent starting up, so it draws at the right size. Sessions Reliability
  19. Denshin 0.0.17

    • Starting Codex or Claude without naming an account can now use another available profile when a sign-in failure is confirmed. Your explicit account choice and automatic switching preferences are respected. Sessions Accounts Reliability
    • Check account sign-in with denshin list --auth: see native verification results and reconnection commands. Add --live to check now, or --needs-login to filter the list. Live Claude checks may use a short model turn; the command reports this before starting. Accounts Reliability
    • Grok sessions recover from temporary capacity errors when the terminal scrollbar is visible. Sessions Reliability
    • A new Codex request can recover again after you cancel an earlier recovery, even when the same temporary error returns immediately. Sessions Reliability
    • Checks of installed agent versions clean up stalled helper processes before returning a result. Reliability
    • Terminal launches and supported account checks now use the executable you selected. A disabled runtime can be enabled again without losing that choice. Sessions Accounts Reliability
  20. Denshin 0.0.16

    • Codex can renew its sign-in through its own authentication system before reading account usage. Revoked sign-ins are reported as needing a new sign-in. Accounts Reliability
    • Automatic account switches skip accounts whose latest usage check failed or is out of date. Accounts Sessions Reliability
    • Codex’s update menu no longer receives the message meant to continue your session. Denshin skips the optional update prompt and waits until the conversation is ready. Sessions Updates Reliability
  21. Denshin 0.0.15

    • Terminals reconnect to their session after a connection loss or update. Access errors explain the next action, and recovery leaves the prompt clean. Command line Sessions Reliability
    • Sessions recover from temporary capacity, network and service errors in the same conversation. Recovery waits for an empty input, respects permissions and stops when you type. Command line Sessions Reliability
    • An interrupted Gemini request keeps its original task during recovery, including multiline messages. Command line Sessions Reliability
    • Pi shows the correct state after a failed or cancelled request. Sessions Reliability
  22. Denshin 0.0.14

    • A long session opens on your phone again: the Mac now sends its conversation in pieces the phone can always receive, instead of one message so large that the link closed and the phone kept saying it was offline. Devices Reliability
    • The same fix holds on every path to your phone, direct, through the relay or through the secure link, and a test now fails if any message the Mac sends could grow past what the link accepts. Devices Reliability
    • The denshin command finds the Mac app after you move it, and running sessions keep their files outside its folder. Command line Sessions Reliability
  23. Denshin 0.0.13

    • Your sessions run on a terminal server of Denshin's own, so other apps, scripts and tmux commands typed elsewhere no longer stop them by accident. Sessions Reliability
  24. Denshin 0.0.12

    • Text that comes from your other Macs is cleaned before it reaches your terminal, and Denshin's logs keep no secret: they no longer hold the key to the Accounts page, and only you can read them. Reliability
  25. Denshin 0.0.10

    • If your Mac restarts in the middle of work, Denshin marks the sessions the restart cut off. Resume them or set them aside from the Activity page, or type denshin resume --interrupted; a resumed session gets a short note of where it had got to. Sessions Reliability
    • A new session no longer starts on an account that is at its limit, and a denshin run screen that froze while the agent kept working gets its picture back. Accounts Reliability
  26. Denshin 0.0.7

    • Notifications now reach you on recent versions of macOS, which could drop them without a word. If Denshin's engine stops and cannot restart by itself, the window and the menu say so and offer to relaunch it. Notifications Reliability
  27. Denshin 0.0.4

    • Codex conversations with a very large file change now open instead of failing. Reliability