Changelog
What’s new
Only the changes about Sessions, newest first.
Denshin 0.0.50Latest
- Agents can now work in your own Chrome, with your sign-ins, in tabs of their own. Run
denshin browser chrome installonce, then load the Denshin extension in Chrome with the one step it shows (Developer mode, then Load unpacked);denshin browser chrome statussays when it is ready, and an agent adds--chrometo itsdenshin browsercommands. It never touches your own tabs, each session's tabs close with it, and its writes go through the same checks as its own browser. Its commands are logged too, with their time and session:denshin browser tracereads them. Updates keep it working with nothing to install again; when the extension itself changes,statusasks you to reload it in chrome://extensions. Sessions Command line
- Agents can now work in your own Chrome, with your sign-ins, in tabs of their own. Run
Denshin 0.0.49
- Every command an agent gives its browser is now logged on your Mac, with the time, its session, its agent and what it did on the page:
denshin browser tracelists the latest session's,--whyadds what the agent was doing from its own transcript,--session,--taband--sincepick others. Typed values, passwords and tokens are masked, and the log keeps 14 days at most.denshin browser guidealso tells an agent that a script it keeps checks its own result before saying it succeeded. Sessions Command line
- Every command an agent gives its browser is now logged on your Mac, with the time, its session, its agent and what it did on the page:
Denshin 0.0.48
- Agents now have a browser of their own: in a session started from Denshin,
denshin browser openfollowed by an address opens a page, thensnapshot,click,filland the other browsing commands read and use it. It runs headless and never shows on your screen. Each session has its own, with its own cookies, and it closes with the session, withdenshin browser close, or past its memory cap (3 GB unless the agent sets another).denshin browser statussays whether it runs and what it uses, anddenshin browser guideprints what an agent needs to know to drive it. Sessions Command line - 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
- Agents now have a browser of their own: in a session started from Denshin,
Denshin 0.0.47
- Sessions nobody used for a day now close by themselves: every hour, Denshin closes a session whose last exchange is more than 24 hours old. Its conversation stays, and
denshin openpicks it up where it stopped. A session is never closed while it works, waits for you, runs something under it (a build, a server, tests) or has uncommitted changes in its folder, and waking a session to move it to another account does not count as using it. Sessions - From 12 hours without an exchange,
denshin sessionsanddenshin topmark a session « to close », so you can close it first or pick it up again.denshin tidy --dry-runsays what would close and why,denshin tidy --loglists what closed, anddenshin tidy offturns it off (denshin tidy on --after 36hsets another delay). Sessions Command line
- Sessions nobody used for a day now close by themselves: every hour, Denshin closes a session whose last exchange is more than 24 hours old. Its conversation stays, and
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
- After the background service restarts on its own, a session tab opened with the CLI's own resume (
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
Denshin 0.0.38
- Model profiles for Claude and Codex let you choose the main model, the default for new subagents and supported role exceptions from Denshin. Profiles can be shared across launches, scoped to a project or selected for a session. The Mac and phone use the same settings as
denshin models. Sessions Command line - 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
- Profiles travel with session copies and account changes. Account selection checks the requested models and their reported quotas, and concurrent profile edits are protected by revisions. Sessions Accounts
- Model profiles for Claude and Codex let you choose the main model, the default for new subagents and supported role exceptions from Denshin. Profiles can be shared across launches, scoped to a project or selected for a session. The Mac and phone use the same settings as
Denshin 0.0.36
- A key you type in a session’s terminal in the window now shows about three times sooner: 13 ms instead of 42 ms in the usual case. The background service and the window each held what came back for a full frame, 16 ms, even a single key after a pause; they now pass it on at once, and still send at most one frame every 16 ms when a lot of output comes at once. The phone’s terminal gets the background service’s half. Measured key by key, 200 keys with none lost or out of order, on a test background service with the window’s page in a browser; in a test build of the app the measure varies more than the gain, and on a real screen it is not measured. Sessions The window
- Opening a session’s terminal in the window now shows that session’s own screen, at the window’s size. Before, when the session was last drawn at another size, its old screen showed first, squeezed into the new one, then jumped by up to 256 px when the session redrew, and the pane could stay empty for 400 ms or flash blank. The background service now waits for the session to redraw at the new size before it sends the first screen, the pane says
Opening the session…until that screen is drawn, and a reset clears in the same frame as the screen that follows. Checked on 172 opens of a test build of the app, out of sight: no empty pane, no flash, no jump; not yet with the published app on a real screen. The window Sessions
Denshin 0.0.35
- A Claude session Denshin runs now says in its status line, under the prompt, which account it is on and what that account has left, for example
maman@gwendall.dev · 5h 94% · week 91% left. It follows the session when it moves to another account at its limit, so an old limit message in the conversation no longer looks like the current one. Your own status line stays, after Denshin’s words, and your settings files are never written. Sessions Accounts - Codex in yolo (
--yolo, ordenshin yolo on) now starts without asking whether to trust the folder, for the folder it opens only, so a Codex started in a tab nobody watches gets to work. Without yolo, Codex still asks. Command line Sessions
- A Claude session Denshin runs now says in its status line, under the prompt, which account it is on and what that account has left, for example
Denshin 0.0.34
denshin openon a Claude session running in Claude Code’s background now takes it back: when it is idle, Denshin stops the background job and resumes the same conversation in a Denshin tab, so it switches accounts at its limit and carries its context like any session Denshin started. A session at work is never cut: Denshin says so and you open it again once it is idle. An older tab that only attached to it is closed first, so there is never a second copy. Sessions Accounts- One verb to go back to a session:
denshin open.denshin run claude --resume 2f6c1a0b,-r 2f6c1a0banddenshin run codex resume 01a1b942still work and now take the same path, with their own options kept;denshin runis for new sessions. Sessions Command line - One
--yolofor every agent:denshin run claude --yolo,denshin run codex --yolo,denshin open claude/2f6c1a0b --yolo, andclaude --yoloin a shell with Denshin’s functions. Denshin hands each one its own words (Claude’s long permissions flag, Codex’s bypass, Gemini’s and OpenCode’s), and refuses it for an agent that has none. A session keeps its mode when it is opened again or moves to another account at its limit.denshin yolo onmakes it the default for new sessions; it is off unless you turn it on, and--no-yoloopts out once. Command line Sessions
Denshin 0.0.33
- The session list behind
claude -r,codex resume,/sessionsand$sessionsnow fits one screen: 20 sessions per page, this folder first and the ones at work before the rest,nandpto turn pages, and any text you type filters by title, folder or id (/clears it). Each row gives a short id, the state, how long ago, the one account that runs or last ran the session, the title and the folder, on one line even at 80 columns. Sessions Command line denshin sessions-commandtakes a word to filter by and stops at the same first 20 sessions, so an agent reading it no longer gets 900 lines, and with no terminal to fit, its rows keep whole titles.--allstill lists everything. Sessions Command linedenshin view --jsonlnow reaches every tab Denshin holds, by its tab id, its title, its run or its session id, short or full. A message sent to a Codex tab arrives whether Codex is idle or working, through Codex’s own queue, and the view says it was queued. A message that cannot be delivered is reported, never dropped, and a session no tab holds says so, with where it runs. Sessions Command line
- The session list behind
Denshin 0.0.32
- New: with Denshin’s shell functions installed (
denshin shell claude codex --install --yes),claude -r,claude -c,codex resumeandcodex resume --lastopen Denshin’s list of your sessions from every account and every CLI, this folder first, instead of the CLI’s own list, which only shows the account signed in. A number attaches the session,dand a number opens it in the background,qquits. An id given explicitly opens throughdenshin open. Sessions Command line Setup - New:
denshin sessions-command install claudeadds a/sessionscommand to Claude Code, anddenshin sessions-command install codexa$sessionsskill to Codex. From inside a session, they list every session of every account and open the one you pick in a tab of the background service. Sessions Command line Setup denshin sessions --alllists every session with no cap on the number of rows, and a session that old can now be opened too. Sessions Command line
- New: with Denshin’s shell functions installed (
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 sessionsnow shows these sessions as running in Claude’s background, under the account that runs them, anddenshin openattaches to them withclaude attach, never starting a second copy. Sessions Command line Reliability - Opening a stopped session whose account is at its limit now starts it on the account with the most room that can work now and reads its history, and says so in one line, the way the rotation already moves running sessions. Before, it started on the account at its limit. When no other account can work, it says the limit before starting. Sessions Accounts
- New:
denshin open claude/2f6c1a0b --detachopens any session in a tab of the background service with no terminal attached, and--jsonnames the tab, so an agent or a script can reopen a session for you. Without--detach,denshin openstill attaches your terminal. Sessions Command line - To get them: they come 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. Updates Sessions
- 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 0.0.30
- 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
/Volumesis 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 - To get them: the new reset text in the window and the menu bar comes with the app. The account switch lines, the cleanup of gone workspaces and of old copies come 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. Updates Sessions
- 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
Denshin 0.0.29
denshin sessionsnow lists your work, not every conversation: a session’s continuations after a compaction, its relaunches and its sub-agents fold under one row with one title, and the runs of one automated prompt fold into one “Automated” row per project. On one Mac’s sessions, 811 rows became 70.denshin wherereads the same model, and the newdenshin modelshows it: what needs you first, by one rule (a question or a permission, then a stop only you can restart, then a result you have not seen), then each project with its sessions at work and quiet;--jsongives all of it. The background service works it out once and keeps it current; at rest it costs about 0.1% of one core. A session you run withdenshin runkeeps its own row, socloseandswitchstill act on it, anddenshin sessions --jsonkeeps its shape. The window and the phone do not read the model yet. Checked with tests, a real background service and a copy of one Mac’s sessions; not yet run by the published app. Sessions Command line- New:
denshin perfsays how fast your sessions open. Each session opened in the Mac’s window or on the phone is timed where it opens, from the click until it is readable, and this Mac’s background service keeps those timings for 30 days in~/.denshin/perf: durations and ids only, never what a session says. They stay on this Mac (the phone sends its own to your Mac); the only thing that leaves it is a notification to your devices, at most once a day for each surface and mode, when an open is still not readable after 5 seconds or the day’s slow opens run over budget.denshin perfshows the median and the slowest opens by surface and mode (conversation or terminal), today and over 7 days, the worst opens and those over budget;--days,--topand--jsonchoose what to read. The phone reports its opens once the phone app has its next update. Checked with tests and a real background service, with a stand-in window and phone; not yet in the published app’s window or on an iPhone. Sessions Command line Devices - 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
- To get them:
denshin model,denshin perfand the timing in the window come with the app. The model thatdenshin sessions,whereandmodelread, and the record of opens, come 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. Until thendenshin sessionslists one row per conversation, as before. Running sessions keep running, their terminals reconnect, and what is typed in a terminal while it reconnects is lost. Updates Sessions
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
- To get it: the background service follows the app by itself at a quiet moment, within about three hours with automatic updates on;
denshin restartdoes it right away. A session started withdenshin rungets it when it starts after the update, or at its next account switch once the service runs this version. Updates Sessions
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
- After the move, the session goes on by itself, on Claude, Codex and OpenCode: no message to type again, no session to start over. Sessions Accounts
- A new session now starts on an account that still has quota, never on one set aside at its usage limit. Sessions Accounts
- To get them: the changes need a session started with
denshin runafter 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. The service 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. Updates Sessions
Denshin 0.0.26
- New:
denshin incidentslists 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,--topand--jsonchoose what to read. It only reads what Denshin already writes, and sees only sessions run withdenshin 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-Ctyped meanwhile is still yours and goes instead of the message, and so isCtrl-Dnow; 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 incidentscomes with the app. The three changes at a usage limit need a session started withdenshin runafter 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 restartdoes it right away. Running sessions keep running, their terminals reconnect, and what is typed in a terminal while it reconnects is lost. Updates Sessions
- New:
Denshin 0.0.24
- New:
denshin wheresays where each project stands, on this Mac and, with--fleet, on your linked Macs: each session’s agent, Mac, account and state, what it waits for, your last ask and its last message (cut short, with home folders and keys masked), its branch, uncommitted changes, commits ahead and, through your owngh, its pull request and CI. What waits for you comes first, a question before a finished turn.--waitingkeeps only those,--pathnames the other sessions in the same repository, worktrees included, and--jsongives the whole reading. It reads facts only and asks no model. A linked Mac that does not answer is said silent, and one on an older version too old. A first reading may not place every session in its project yet; later readings do. Measured at 3 to 5 seconds on a real Mac’s sessions, up to half a minute under heavy load;--fleetwas checked between two test Macs, not yet across real ones. Sessions Command line Devices - 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,
--bestno 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 - To get them:
denshin where, the order of the lists and--bestcome with the app. A session no longer moving to an account whose week is used up 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.denshin where --fleetreads a linked Mac once that Mac’s background service has this version too. Updates Sessions
- New:
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
- After your Mac restarts, a session you ran with
Denshin 0.0.22
- From this version on, a
denshin runsession moves onto each new version of Denshin at its next account switch, without closing its tab: the same terminal, the agent picks up its conversation on the new account, and the terminal says once which version takes over. Even aCtrl-Ctyped during the move goes to the session instead of closing the tab. A session moves only once the background service runs the new version, and one that never switches keeps its version. It starts with sessions opened after this update: those running now keep theirs until their tab closes. To keep sessions where they are, create the file~/.denshin/run-swap-off, or start a session withDENSHIN_RUN_SWAP_OFF=1to keep just that one. Sessions Command line Updates - The window, the menu bar and the phone get your sessions faster. One reading in ten took over 400 ms, while the background service looked through every project folder for a session with no conversation yet, or waited for git; none now takes more than 50 ms. With 20 tabs open, a usual reading takes 6 ms instead of 21, since a session’s agents are read again only when they change. Measured on a test service with a real Mac’s sessions. Sessions The window Devices
- Text a program copies in a tab now reaches the terminal where you run
denshin runordenshin attach, cmux or Ghostty for one, which can put it in your clipboard. Until now Denshin’s terminal server dropped such a copy, unless the program wrapped it for tmux as Claude Code does. Reading stays closed: a tab cannot read what another tab copied. Checked with real tmux, not yet in cmux or with the Mac’s clipboard itself. Sessions Command line - 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
- To get them: the faster readings and the copy come with the background service, for tabs already open too. It 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 Codex fix, and moving onto later versions at a switch, need a session started withdenshin runafter the update. Updates Sessions
- From this version on, a
Denshin 0.0.21
- A Claude session’s agents at work are now all there, as Claude Code lists them: one launched long before, or one back at work after it seemed done, no longer goes missing or reads as ended, and its time counts from its current run. On one session where Claude Code listed nine at work, Denshin showed one running and two ended. Sessions The window
- Clicking an agent above the message box now opens its own conversation, even while it is still at work. Until now it opened empty. Sessions The window
- Codex in a terminal tab now shows its agents too: above the message box, in the session list, where the session says it waits on them, and in
denshin sessions --lineage, each with its task, what it is doing, for how long and its tokens, and each opens like a Claude agent. Checked against real Codex records, not yet in the window itself. Sessions The window Command line - 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
- To get them: the window’s fix comes with the app. The agents and the limits heard on a busy Mac come 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. Claude going on by itself after a move, and the two kinds of limit above, need a session started withdenshin runafter the update. Updates Sessions
Denshin 0.0.20
- In native terminals such as cmux,
denshin runanddenshin attachnow show a session’s real 24-bit colours, curly underlines, strikethrough and overlines from its first draw. Until now most sessions got 256 colours and none of those styles. The phone gets the real colours too. Checked with real tmux and a stand-in for these terminals, not yet in cmux itself. Sessions Command line - 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;2cno 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 - Leaving with
Ctrl-]gives your terminal back: in a terminal opened after this update, you return to your shell’s own screen with its scrollback, and clicks and the wheel no longer type at the prompt. The window title is not restored. Checked with a stand-in terminal, not yet in Terminal.app, Ghostty or cmux. Sessions Command line - To get them: nothing to do for the colours, the mouse, the redraws and the stray text. They come with the background service, which follows the app by itself at a quiet moment, within about three hours with automatic updates on. Running sessions keep running, their terminals reconnect, and what is typed in a terminal while it reconnects is lost.
denshin restartdoes it right away. Only theCtrl-]fix needs a terminal opened after the update. Updates Sessions - Terminal.app,
screenand terminals over SSH keep their 256 colours when opened after this update. One opened before it can show wrong colours, blinking or hidden text once the service has moved (an older Terminal.app at least), until you close it and open it again.COLORTERM=256color denshin attachasks for 256 colours in any terminal. Sessions Command line
- In native terminals such as cmux,
Denshin 0.0.19
denshin runterminals 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 Reliabilitydenshin runanddenshin attachterminals 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
- A session moving to another Mac stands still about one second less: the transfer now ends as soon as the other Mac holds every part. Sessions Devices
Denshin 0.0.18
- A session whose agents keep working in the background no longer looks idle: the session list and its header say how many are at work and which one waits for you. Sessions The window
- Above the message box, one row per agent still at work: its task, what it is doing, for how long and its tokens. Click one to read its own conversation. In the conversation, the work a turn hands to several agents folds into one block that says how each one ended. Sessions The window
- 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
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
- 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
- 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
Denshin 0.0.16
- 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
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
Denshin 0.0.14
- The denshin command finds the Mac app after you move it, and running sessions keep their files outside its folder. Command line Sessions Reliability
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
- If that server stops anyway, your sessions come back by themselves in about a second, each in its own tab, on its account, where it left off, and your phone tells you once. Sessions Notifications
- A session that cannot safely come back by itself waits in Activity, one click away on Resume, rather than risk running twice. Activity Sessions
- Closing the window or quitting Denshin never ends a session: they keep running, and you find them when you come back. The window Sessions
Denshin 0.0.11
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
- 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 0.0.9
- A session waiting to move to another account no longer waits forever when nobody types to it: it moves as soon as it is idle, and never while the agent is asking you something. Accounts Sessions
denshin runon a session that is already open elsewhere now offers to open it here, take it over or fork it into a new session, instead of refusing. Command line Sessions
Denshin 0.0.8
- A session you just started says it is ready for your first message, and while the agent works on its first answer, a line under your message says it is writing. Sessions
Denshin 0.0.7
- Pictures and videos a conversation mentions now show in place, in the conversation. Sessions
- From the inspector, open a file a session changed in your editor, or show it in the Finder. Sessions
- Resume on… in the session menu and in ⌘K moves a session to another of your linked Macs, and Bring back here… returns it. This Mac and your other devices are in Settings > Devices. Devices Sessions
Denshin 0.0.6
- ⌘K finds any session, action or setting. ⌘N starts a new session: pick the folder, the agent, the account (Denshin suggests the one with the most left) and your first message. ⌘/ lists every shortcut. The window Sessions
- ⌘I opens a session's inspector: its sub-sessions, the files it changed and what it used on each account. Sessions
- From a session you can now rename it, attach files to your message, stop it, or switch it to another account. Add an account by signing in right from the Accounts page. Sessions Accounts
- When a session moves to another account because its own hit its limit, the agent now picks up where it stopped. You can turn this off in Settings. Accounts Sessions
Denshin 0.0.5
- Conversations now show what happens to them, one line each: an account switch planned or done, a restart of Denshin in the background, and the files a burst of work changed, as one card. Sessions
Denshin 0.0.4
- A stopped session stays readable, with one clear way to resume it, and you can search the list of sessions. Sessions
Denshin 0.0.3
- Long conversations: scroll back without losing your place, scrolling up is no longer pulled down by new output, and a conversation you have not opened in a while opens on its latest exchanges. Sessions
- Read a stopped session's history without restarting its agent. Your sound setting carries over. Sessions