Sessions, history & cloud sync
Last updated
Where your conversations live, what syncs between machines, and how a dropped connection never loses an agent run.
Saved sessions
Every conversation is a session you can come back to — full chat history, rendered Markdown and all.
| Plan | Saved sessions |
|---|---|
| Standard | One saved session at a time |
| Pro | Multiple saved sessions |
| Teams | Multiple, shared tooling across the org |
What syncs to the cloud
On Standard and above, your setup follows you across machines:
- Chat sessions — pick up a conversation on another box.
- Tool preferences — which agent tools are enabled and how they're scoped.
- Custom agents (Pro and Teams) — agents you define sync with you; Teams shares them org-wide.
Your provider API keys are stored encrypted at rest and never shared across accounts — see Providers & BYOK for how key storage works.
Turning cloud sync off
Cloud sync is on by default. You can turn it off for your whole account, on every machine and in every extension, from any of these places:
- The portal — the Cloud sync card on the Profile page.
- Visual Studio, VS Code and JetBrains IDEs — the Cloud sync switch on Tempr's settings screen (the gear in the chat panel; in Visual Studio also Tools > Tempr Settings).
While it's off, chats stay on each machine, and Tempr's servers neither accept nor return your chats, tool preferences, custom agents, or Visual Studio's code search index. Turning it off doesn't delete what's already synced: choose to delete it when you turn sync off, or use Delete synced data in the same places at any time. Deleting synced data also ends any share links, and deleting a single session in the extension deletes its synced copy.
Runs that survive a dropped connection
The multi-turn agent loop executes server-side: when the model works through a task — reading files, planning, editing — that loop keeps running even if your IDE disconnects. Tool execution (the actual reads, edits, and commands) still happens locally in your IDE; reconnect and the run picks back up mid-turn instead of starting over.
The same sessions in the CLI
CLI runs are saved automatically too. List and resume them from any terminal:
tempr history
tempr --id <SESSION_ID> "continue where we left off"