How it works
Every session. One connected workspace.
The vision: a beautiful workspace for each session, a continuous thread across tools and devices, and agents that work together.
A workspace for one session, or an army.
Denshin is being built as the super app for the solo agentic engineer. Each session should have a beautiful, readable interface of its own: a clear conversation, its context and a place to work, even with just one agent.
When you open more sessions, the goal is for agents and sessions to talk, ask each other for help and coordinate around shared projects. Each keeps its identity, with you setting the direction.
One conversation. Different accounts, agents or devices.
The aim is to continue with another account when one runs out, pass from Claude to Codex within the same conversation, or pick the work up on another device, with Denshin carrying the context through each change.
Accounts come first, and they work today: when an account runs out, the session goes on with another of yours, in the same conversation. Continuing the same thread across agent tools, and the complete experience across devices, are still ahead.
Available today: one Mac app.
Sessions, Accounts and Settings share one Mac app. Open session conversations and terminal views, follow connected accounts and keep a quick overview in the menu bar.
The shared project view, communication between agents and Den as an agent are still being built.
Come back at the right moment.
Today, the menu brings together agents asking for input and turns that have finished. Each item stays attached to its session. Den, the small pixel face in the menu bar, reflects the state of the work. It is a signal today, not an autonomous agent.
Find the sessions behind the activity.
Open your Mac’s agent sessions in Sessions. Read their conversations, use the terminal view and return to earlier exchanges. Sessions keep running when you close the window, and a stopped session’s history stays readable without resuming it. You can switch a session to another of your accounts by hand: at the end of its turn, the same conversation continues there. Available controls depend on the provider and how the session was started.
Know what your accounts can do.
See your connected accounts and the quota usage their tools report. When reset times are known, Accounts shows full dates and countdowns. Unknown or old readings stay explicit. A quota reset needs a fresh reading before availability is confirmed.
Add several accounts for the same tool, and automatic rotation keeps your sessions going. It is on by default for Claude Code and Codex: when the account a session uses runs out, Denshin moves the session to another of your accounts for that tool and relaunches it in the same conversation. The session’s terminal notes the move, and a notification names the account that takes over. Each tool has its own switch in Settings. Only sessions started from Denshin, in the app or with its command line, are moved.
Keep the terminal you like.
Denshin has a command line and a shared local engine. You can use them alongside your existing terminal and provider tools.
The Mac download combines the workspace and menu bar. The mobile remote remains separate, and full continuity across devices remains future work.
Bring the team together.
The next stages connect project context and coordination between agents through the shared engine.
The aim is for any agent, Den included, to use the same interface, including MCP. The full voice and character experience comes later. The tools and providers remain your choice.