> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tempo.new/llms.txt
> Use this file to discover all available pages before exploring further.
# Migrating From Web to Desktop
> A step by step guide
On **June 14** we'll wind down the Tempo web editor and move everything to the desktop app. Until then, keep using it at [app.tempo.build](https://app.tempo.build) — your prompt credits work in the new app too, and we're **doubling available credits** during the migration.
Our new **local desktop app** is a significant rebuild of Tempo from the ground-up — faster, more feature-complete, and far more powerful.
**Why are we making the change?** Short answer: we couldn't fully build Tempo using Tempo (meta, I know). Our own engineers were gravitating back to tools like Cursor \~70% of the time, and we only wanted to sell a product we use ourselves. The new app fixes that — the whole team is now on it **8+ hours a day, every day**. We love it and hope you will too.
The new app brings with it a few key changes:
1. **Local** — run your code on your machine. Better performance, code privacy, and security.
2. **Frontier agents** — handle tasks of any size and complexity, with tokens direct from Anthropic / OpenAI / OpenCode.
3. **Git Worktrees** — run chats across multiple copies of your codebase in parallel so you can work on multiple features at once.
Watch the quick intro below, then follow the steps to get set up.
Here's how you get started:
Download from [tempo.new](https://tempo.new) and sign in with your existing account.
You'll need **[Node.js](https://nodejs.org/en/download)** and **[Git](https://git-scm.com/downloads)** installed on your machine. Tempo will alert you if either is missing.
Click **+ Add Project**, paste your repo's git clone URL, or pick a local folder with a copy of your codebase checked-out.
**If you haven't already please commit then push your project to git** from the git tab.
The new app gives you the choice of three coding agents — each works with different subscriptions.
Agent
ChatGPT
Claude
Tempo Inference
API key
Claude Code
—
✅
✅
✅
Codex
✅
—
✅
✅
OpenCode
—
—
✅
✅
Pick the option that matches your setup and follow the login instructions below.
**Paying for Tempo on the web app?** Your subscription and any unused prompt credits carry over automatically. [Learn More](/guides/tempo-web-billing)
1. Click the **Terminal** tab at the bottom of any workspace (some layouts call it **CLI**).
2. Type `claude /login` and press **Enter**.
Prefer an API key? Choose **"Use an API key"** at the browser prompt and paste one from [console.anthropic.com](https://console.anthropic.com).
1. Click the **Terminal** tab at the bottom of any workspace.
2. Type `codex login` and press **Enter**.
Prefer an API key? Pick **"Use an API key"** at the prompt and paste one from [platform.openai.com/api-keys](https://platform.openai.com/api-keys).
1. Click the **Terminal** tab at the bottom of any workspace.
2. Type `opencode login` and press **Enter**, then follow the on-screen prompts.
OpenCode accepts API keys from Anthropic, OpenAI, and other supported providers.
No sign-in needed. Open the **Chat** tab, pick any model from the dropdown at the bottom, and start chatting — your Tempo plan covers it. [Learn More](/guides/tempo-web-billing)
For users on base plans (\<\$100), it is strongly recommended to use Sonnet/GPT-5.4 on low effort as **Opus**/**GPT-5.5** on **high** effort burn credits extremely fast.
🎉 You're all set. Open the **Chat** tab and start prompting.
To see a live preview, just ask the AI to:
* **Configure a run script**, then click **Play** in the top bar — or edit `tempo.config.json` yourself ([reference](/guides/setup-run-scripts)).
* **Create a canvas** for a Figma-style design surface — or right-click the Canvas tab → **New Storyboard**.
## Once you're in — 3 quick tips
A short follow-up walkthrough covering the most common things to set up after install:
1. **Add a run script.** Configure one in `tempo.config.json` (or ask the AI to do it), then hit **Play** to see your live preview. [Reference](/guides/setup-run-scripts)
2. **Set your environment variables.** Anything your app reads from `.env` lives in the project's env panel — don't forget API keys, DB URLs, etc.
3. **Generate a canvas with storyboards.** Ask the AI to create a canvas, or use "Route" storyboards to map full pages. Heads up: the chat now lives on the right *inside* the canvas tab.
Still stuck after that? It's almost always a git or AI authentication issue — DM me and I'll get you unblocked.
## What happens after June 14
On June 14 we'll wind down the Tempo web editor and move everything to the desktop app. Until then keep using it at [app.tempo.build](https://app.tempo.build) — your prompt credits work in the new app too, and we're **doubling available credits** during the migration ([Learn more](/guides/tempo-web-billing)).
A few things to know:
* **Your plan comes with you.** Subscriptions and remaining credits carry over automatically, and you can manage billing right inside the desktop app under **Settings → Plan**. [app.tempo.build](https://app.tempo.build) will also stay up as a read-only billing portal if you ever need it. [Learn more](/guides/tempo-web-billing).
* **As long as your project is on GitHub, you're set.** Push from the web app's git tab and you can clone it into the desktop app in seconds. Prefer a local copy? Hit **Download ZIP** on any project. If you'd rather we handle it, email [support@tempo.new](mailto:support@tempo.new) — we'll retain old repos for **60 days** after June 14 and can export them for you on request.
## Get help
We're running **1:1 onboarding sessions** — email [support@tempo.new](mailto:support@tempo.new) to grab a slot, or for any other questions or concerns.