Spatial
Start Building
Browse docs

Get Started

WelcomeQuickstartLayout modesPrompting guidelinesContext basicsFAQ

Core Concepts

Auto-compactionSubagentsMemoriesModels and capabilitiesToken costsSession hygiene

Workflows

Stash and pop promptsAttachments and contextBrowser preview workflowReview and request changesWidgets sidebarWorking with integrationsTroubleshooting

Desktop App

Settings and preferencesVoice inputMax modeCodebase indexingPopout chatPlatform supportProjects and sessionsAgent modesKeyboard shortcutsCLI toolClaude Code sessionsCodex sessions

Session Environments

Git worktreesSSH sessionsCloud sessionsLocal container sessions

Integrations

OverviewGitHubVercelRailwayLinear

Usage & Billing

Tokens and contextPricingPlans and rate limitsUpgrade subscriptionDowngrade subscriptionRefundsCancel subscription

Tutorials

Snake game starter

Get Started

Layout modes

Use the right layout for the task: split layout for visual web iteration, default layout for logic-heavy work.

Default layout

Default layout keeps focus on conversation and code actions. It is usually best for library work, backend logic, architecture planning, and non-visual refactors.

  • Use for APIs, tooling, CLIs, and algorithm-heavy tasks.
  • Use when browser preview is not central to validation.
  • Pair with widgets sidebar if you still need integration visibility.

Split layout

Split layout adds browser preview next to chat so you can inspect UI behavior as you iterate. It is ideal for frontend and full-stack web app work.

  • Use for responsive design, visual QA, and interaction bugs.
  • Capture screenshots or inspect elements directly from preview controls.
  • Keep quick iterative loops: change -> preview -> adjust.

Simple rule

If preview feedback is required to judge correctness, use split. If correctness is mostly logic/data/tooling, use default.