Web IDE

The Web IDE is the main way to use TabTabTab. It's a real cloud workspace, not a local browser sandbox, so the files, terminals, agents, and dev servers you see are running on the VM and stay running after you close the tab.

It's built from our OpenCode fork. TabTabTab adds the cloud compute, dashboard handoff, mobile login, repo onboarding, Secret Manager, Codex login, provider API key support, environment metrics, browser testing, and runtime previews you need to actually treat it as your daily driver.

When to use it

  • You want one place to drive an agent, watch terminals, review diffs, and open a preview.
  • You're working from mobile or a borrowed machine and don't want to install anything locally.
  • You want Codex login or model-provider API keys inside one persistent web workspace.

Open the IDE

From the Meta UI, go to https://dash.tabtabtab.ai, open an environment, then click Open. The dashboard creates a short-lived login link so the IDE opens without copying passwords around.

On mobile, sign into the dashboard in your phone browser and tap Open, or open the dashboard on your computer and scan the environment QR code.

Use the dashboard Open button for the Web IDE. CLI attach commands are for local editor and shell access; they are not the Web IDE launch path.

Work in the IDE

Use sessions to inspect code, edit files, run commands, and review diffs against the real repo. Today the first-class experience is the TabTabTab IDE backed by Codex login or model-provider API keys. We want to support switching between Claude Code, Codex, and other harnesses, but that work is still in progress.

Browser agent

TabTabTab ships with a browser agent that lives inside the Web IDE. Give it a goal ("verify the signup form works", "check the dashboard on mobile width") and it starts your app itself, opens it in a real browser on the VM, clicks through, and reports back on whether things work as expected. You don't have to spin up the dev server first or hand it a URL. It pairs naturally with the coding agents: write a change, ask the browser agent to confirm it actually runs.

Preview URLs

When your dev server is running in the cloud workspace, TabTabTab proxies it to a public URL so you can open the app in any browser, on any device. Useful for testing on real phones, sharing a work-in-progress link with a teammate, or pointing a webhook at a feature branch. See [Preview URL](/docs/preview-url) for the commands.

Review and environment state

Use the Review tab before committing agent changes. It surfaces the diff for the session so you can sanity-check what the agent did before it lands in git.

Use the Environment panel when a run is slow or noisy. It shows CPU, memory, storage, uptime, and top processes for the cloud machine, which is usually how you catch a runaway test or a dev server that's eating RAM.

Repositories and secrets

Click the plus button in the left sidebar, choose Add Repository, and paste a Git URL. After clone, Secret Manager detects env files such as .env and .env.local, supports bulk paste, writes the local env files for you, and backs values up to TabTabTab (encrypted at rest) so a new environment can be seeded without you re-pasting keys.