Session Persistence
Your terminal session runs on the task’s cloud container, not in your browser. This means:- Refreshing the page reconnects you to the same session — your running processes, working directory, and environment are all preserved.
- Closing and reopening a task picks up right where you left off.
- Switching between tasks keeps each task’s terminal running in the background.
Reconnection
If your connection drops — whether from a network interruption, switching Wi-Fi, or waking your laptop from sleep — the terminal reconnects automatically. During reconnection:- The terminal attempts to re-establish the WebSocket connection with a short backoff.
- Cached output is displayed immediately so you don’t see a blank screen.
- Once the connection is live, fresh output resumes streaming in real time.
Switching Between Tasks
Whim caches your recently viewed terminals so switching between tasks is instant — you don’t have to wait for a fresh connection each time. The cache holds your most recent tasks:| Device | Cached terminals |
|---|---|
| Desktop | Up to 15 tasks |
| Mobile | Up to 8 tasks |
| iOS Safari | Up to 5 tasks |
iOS Safari has a lower cache limit because it aggressively suspends background tabs. The smaller cache prevents connection failures on iPhones and iPads.
Shell History Sync
Whim syncs your shell history across all tasks in your workspace using Atuin, so commands you ran in one task are searchable from any other. Press Ctrl+R in any shell terminal to search your cross-task command history. This is especially useful when you need to re-run a command from a previous task without remembering the exact syntax. Shell history is scoped to your workspace — commands from other workspaces won’t appear in your search results.Multiple Sessions
Each task provides two independent terminal sessions:- Whim terminal — where the AI agent runs. This is the primary view when you open a task.
- Shell terminal — a separate shell for your own use, running alongside the agent in the same container.
Resource Limits
Terminal sessions run inside the task’s cloud container, which has finite memory and compute. A few things to keep in mind:- Scrollback is limited to 10,000 lines per terminal. Older output scrolls off the top of the buffer.
- Cached output for reconnection is limited to keep browser memory usage reasonable. If you need to review output beyond what’s cached, check the task’s conversation in read mode.
- Idle containers may be suspended after a period of inactivity to free up resources. When you open a suspended task, its container restarts automatically.