Persistent sessions
A local agent owns each shell. Close the app and the process keeps running. Reopen it to replay the retained output.
The feature guide
The familiar shell.
A lot more around it.
Every shipped capability, grouped by the work it helps you do. Windows is available now. Planned releases are called out where they appear.
01 / The core promise
Close the window. Keep the work.
Your shells live on your computer, not inside the app window.
Return after a reboot
Sessions reopen in their folders. Claude Code resumes with claude --continue; Codex uses codex resume --last. Stillshell tells you first. Other sessions tell you what was running.
History with boundaries
Output is sealed on disk with a key kept outside the database, then trimmed by age and size. “Restored” and “Live” are distinct states. A reboot starts a new process.
02 / Built around coding agents
Every agent. One glance.
See the tool, task, folder and state of each agent across your computers.
The agents attention queue with sessions that need you, search and filters, and decision cards with labelled answers
app-agents.pngPhoto coming after the next app release.
Answer from a notification
Hooks, bells and notification signals tell Stillshell when Claude Code, Codex or OpenCode needs you. Answer buttons type your exact choice into that session.
Get to the right session
Set up agent hooks in one click. Task titles tell you what is happening. Jump to the next session that needs you. CtrlShiftA
Know when work finishes
Long-command alerts tell you when a build or test completes while you are elsewhere. States say Running, Done or Needs you, with symbols.
Keep useful prompts close
Save prompts globally or per folder. Put frequent commands in buttons above the terminal. Open the prompt library with CtrlShiftP
Give the agent context
Copy last answer or Copy for AI produces clean Markdown. Send a selection, failed command or file to the agent next to it. Dropped files and pasted images become typed paths.
Read access, by choice
An opt-in MCP server lets AI tools read your terminals. It is off by default, read-only, and cannot type.
03 / AI accounts & usage
All your accounts. In the right session.
Keep Claude Code, Codex and OpenCode logins and supported keys together. Choose per session.
Separate accounts
Each subscription has its own sign-in folder. Add Anthropic, OpenAI, Google and OpenRouter API keys. Keys go only to the program you start with them.
Pick when you start
Type claude or codex to choose an account. See usage before choosing. Remember it for the folder, or let the last-used account start if you do not answer. ↑↓Enter1–9
Read usage locally
Five-hour and weekly limits, reset times and report freshness come from Claude Code and Codex on your computer. Usage is not sent to Stillshell. API-key usage reporting is not available yet.
Switch in place
Restart the tool with another account and resume the same conversation. Keep YOLO / skip-permissions, sandbox, approval and model settings. Review a busy-tool interruption first. CtrlShiftU
Codex providers
Configured Codex providers appear beside subscriptions in the switch menu. Review the destination provider and model before switching.
Encrypted account sync
Approved devices hold the keys to encrypted account records. The server stores sealed data. Subscription entries sync; sign in once on each computer because tokens rotate.
04 / The terminal itself
A terminal you can see into.
Commands, paths and links become useful parts of the workflow.
Preview paths
Hover an image for a thumbnail, code for lines around an error, or a folder for its contents. Open, open in your editor at the line, go to the folder or copy the path. CtrlClick
Check links first
See the site and full address. Open or copy the link. Plain HTTP and unusual characters get warnings; local addresses say “This computer”. Hovering never contacts the site.
Commands as blocks
Each block shows exit code and duration. Jump between commands, copy one command’s output and search the buffer. Folder, git branch and last exit stay visible.
Two views, one workspace
Put two sessions side by side. Find every action in the command palette. CtrlK
Light and dark
Keel themes keep the terminal readable. Block and line characters join correctly, including CLI logos.
Input stays yours
Interrupt even when a program captures the mouse. Programs need permission to copy to your clipboard. CtrlC
05 / Where the work happens
The work leaves a record.
See what ran, what changed, and who answered while you were away.
The session record with one search and Commands, Changed files and Activity tabs, command blocks with exit codes and durations, and Jump to command, Copy output, Copy for AI and Send to agent
app-record.pngPhoto coming after the next app release.
Session inspector
Inspect commands and changed files next to the session. Each file shows added and removed line counts, with Copy diff.
Activity timeline
Search starts, restores, AI tools, requests for attention, device replies and command exits. The record stays on your computer with the same retention as history.
Recent projects
Start a session in a folder you used before. Less navigation before the work begins.
Workspaces
Save a project’s session names, folders and layout. Open them together next time.
Task worktrees
Give an agent its own git worktree so parallel tasks do not share a working tree.
06 / Beyond this desk
Your sessions, on your other screens.
Pair another computer today. The Android phone companion is planned.
Pair deliberately
Scan a code. Compare the same eight-group safety code on both devices before approving. Every computer appears once, with its online state.
One device types
Open, watch and type into your computers’ sessions. A visible input lease names the one device that can type at a time.
Planned / Android & push
The Android companion will let you start an agent and answer it from your phone. Phone push notifications and file previews from other computers are also planned.
07 / Trust
Connection without custody.
Your shells stay on your computer. The relay forwards frames it cannot decrypt.
Device-approved trust
Only a device you have already approved can approve a new device. The cloud’s device list is not enough. Compare safety codes during pairing.
Sealed storage & checked updates
Stored history, session keys and tokens are sealed on disk. Signed updates are checked against a pinned key.
Review access
See signed-in sessions and devices, sign one out and review account activity. AI read access starts off and never grants input.
08 / Getting started and paying
One account. Browser sign-in.
Create your account and manage your plan on stillshell.com. The app opens the browser to sign you in.
Start without a card
Create an account to start the 14-day trial. Confirm your email, reset a password, redeem a code, export data or delete your account on the website.
Approve the app
Sign in in the browser and press Allow. The app proves it holds its device key; a stolen sign-in link alone cannot sign another device in.
One plan, two periods
$8 monthly or $80 yearly. Cancel any time. AI subscriptions and API usage are separate.
Promo codes
Offers can add free days, extend a trial or add free months. Card-required offers and payment discounts await payment-provider support. Those offers can give a percentage or fixed amount off the first payment, a set number of months or every payment, with monthly or yearly restrictions.
Company codes
Anyone with a confirmed matching company email can claim the offer. Free-mail domains are refused. An optional seat cap limits claims; eligible offers can appear on the account page.
Offer controls
Codes can have start and end dates, new- or existing-customer rules, and plan restrictions. Shared codes can have use limits; single-use batches export as CSV. Operators can disable codes or revoke a redemption.
Your next session starts here
The terminal caught up.
Bring your work.
14 days free. No card needed. Windows available now.