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