Skip to content
Denshin.dev

Changelog

What’s new

Only the changes about Command line, newest first.

  1. 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 install once, then load the Denshin extension in Chrome with the one step it shows (Developer mode, then Load unpacked); denshin browser chrome status says when it is ready, and an agent adds --chrome to its denshin browser commands. 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 trace reads them. Updates keep it working with nothing to install again; when the extension itself changes, status asks you to reload it in chrome://extensions. Sessions Command line
  2. 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 trace lists the latest session's, --why adds what the agent was doing from its own transcript, --session, --tab and --since pick others. Typed values, passwords and tokens are masked, and the log keeps 14 days at most. denshin browser guide also tells an agent that a script it keeps checks its own result before saying it succeeded. Sessions Command line
  3. Denshin 0.0.48

    • Agents now have a browser of their own: in a session started from Denshin, denshin browser open followed by an address opens a page, then snapshot, click, fill and 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, with denshin browser close, or past its memory cap (3 GB unless the agent sets another). denshin browser status says whether it runs and what it uses, and denshin browser guide prints what an agent needs to know to drive it. Sessions Command line
  4. Denshin 0.0.47

    • From 12 hours without an exchange, denshin sessions and denshin top mark a session « to close », so you can close it first or pick it up again. denshin tidy --dry-run says what would close and why, denshin tidy --log lists what closed, and denshin tidy off turns it off (denshin tidy on --after 36h sets another delay). Sessions Command line
  5. Denshin 0.0.41

    • Automatic rotation can now spend a reset credit when every other account of that CLI is at its limit, or a few hours before a credit would expire unused on a well-used window: denshin rotate codex resets on (off by default). It spends the credit that expires soonest, at most one per account per day, and tells you each time. Accounts Command line
    • denshin reset-credit codex lists your Codex reset credits across accounts, soonest to expire first, with what each covers. Spending one now says what happened in plain words (spent, already done, nothing to reset, none left) instead of always "credit spent", and a spend cut by the network is retried as the same attempt, never a second one. Command line Accounts
    • For a Claude account, denshin reset-credit claude with --open opens claude.ai Settings › Usage, where Claude offers its resets, then reads the account again; it never says a reset was spent. Command line Accounts
    • denshin model says the session states in the same words as the window and the phone. Command line
  6. Denshin 0.0.40

    • The command palette (⌘K) now always opens on an empty search. Before, it could reopen on the previous search: a title typed quickly was added to the old text, nothing matched, and Enter offered it as the first message of a new session. The window Command line
    • 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
  7. 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
  8. 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
  9. Denshin 0.0.35

    • Codex in yolo (--yolo, or denshin 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
  10. Denshin 0.0.34

    • One verb to go back to a session: denshin open. denshin run claude --resume 2f6c1a0b, -r 2f6c1a0b and denshin run codex resume 01a1b942 still work and now take the same path, with their own options kept; denshin run is for new sessions. Sessions Command line
    • One --yolo for every agent: denshin run claude --yolo, denshin run codex --yolo, denshin open claude/2f6c1a0b --yolo, and claude --yolo in 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 on makes it the default for new sessions; it is off unless you turn it on, and --no-yolo opts out once. Command line Sessions
    • denshin close takes the tab id or the session id that denshin run --detach --json answers, as open and view do. Command line
  11. Denshin 0.0.33

    • The session list behind claude -r, codex resume, /sessions and $sessions now fits one screen: 20 sessions per page, this folder first and the ones at work before the rest, n and p to 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-command takes 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. --all still lists everything. Sessions Command line
    • denshin view --jsonl now 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
  12. Denshin 0.0.32

    • New: with Denshin’s shell functions installed (denshin shell claude codex --install --yes), claude -r, claude -c, codex resume and codex resume --last open 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, d and a number opens it in the background, q quits. An id given explicitly opens through denshin open. Sessions Command line Setup
    • New: denshin sessions-command install claude adds a /sessions command to Claude Code, and denshin sessions-command install codex a $sessions skill 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 --all lists every session with no cap on the number of rows, and a session that old can now be opened too. Sessions Command line
  13. 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
    • New: denshin open claude/2f6c1a0b --detach opens any session in a tab of the background service with no terminal attached, and --json names the tab, so an agent or a script can reopen a session for you. Without --detach, denshin open still attaches your terminal. Sessions Command line
  14. Denshin 0.0.30

    • One version number for Denshin everywhere: denshin version and denshin --version now print Denshin’s own version and the commit it was built from, for example Denshin 0.0.30 (1a2b3c4d). The background service no longer shows a number of its own. When it, or a session started with denshin run, still runs an older build, a second line says so and how it catches up. Command line Updates
  15. Denshin 0.0.29

    • denshin sessions now 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 where reads the same model, and the new denshin model shows 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; --json gives 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 with denshin run keeps its own row, so close and switch still act on it, and denshin sessions --json keeps 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 perf says 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 perf shows 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, --top and --json choose 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
  16. 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
  17. Denshin 0.0.24

    • New: denshin where says 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 own gh, its pull request and CI. What waits for you comes first, a question before a finished turn. --waiting keeps only those, --path names the other sessions in the same repository, worktrees included, and --json gives 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; --fleet was checked between two test Macs, not yet across real ones. Sessions Command line Devices
    • Wherever accounts are listed (the menu bar, the window and its account menus, denshin list, denshin pick), the ones with the most left come first, then those with no fresh reading, then those at their limit, the soonest back first, and last those signed out or missing. The account your terminal uses keeps its mark in its new place. denshin list --json keeps its order. Checked surface by surface in tests, not yet seen in the running app. Accounts The window Command line
  18. 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
  19. Denshin 0.0.22

    • From this version on, a denshin run session 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 a Ctrl-C typed 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 with DENSHIN_RUN_SWAP_OFF=1 to keep just that one. Sessions Command line Updates
    • Text a program copies in a tab now reaches the terminal where you run denshin run or denshin 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
  20. Denshin 0.0.21

    • 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
  21. Denshin 0.0.20

    • In native terminals such as cmux, denshin run and denshin attach now 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
    • 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
    • Terminal.app, screen and 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 attach asks for 256 colours in any terminal. Sessions Command line
  22. 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
  23. 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
  24. Denshin 0.0.14

  25. Denshin 0.0.12

    • The disk image opens on a window that shows where to drag Denshin. Or install and update it from the Terminal with curl -fsSL https://denshin.dev | sh: it checks that the app is signed by its developer and notarized by Apple before it puts it in Applications. Setup Command line
  26. Denshin 0.0.11

    • denshin update now goes through the app: it updates Denshin, and the service and the command follow. Command line Updates
  27. Denshin 0.0.10

    • The denshin command speaks plainly: accounts by email address, sessions by title. denshin status says in four lines whether Denshin works for you, denshin doctor gives each problem with the command that fixes it, and denshin usage shows what each account used, day by day. The old command names still work. Command line
  28. Denshin 0.0.9

    • denshin run on 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 top shows what needs you first and groups the copies of the same session, and the command's first errors say what happened and what to type next. Command line