Learn PaneScale by doing.
Short paths through the docs, each ending with something real working on your machine. Pick the one that matches what you want to get done today.
Your first hour
From installer to two agents working side by side in separate lanes.
Keep track of many sessions
Six agents at once without losing the thread: names, status and who needs you.
Set up a night shift
Queue well-scoped tasks in the evening and review diffs in the morning.
Fix UI by pointing
Connect your dev server to the browser pane and fix a real component.
Build a release workflow
Agent, tests, a browser check, a Git review and your approval — every time.
Keep costs predictable
Your subscription limits, daily budgets per engine, loop detection and what “measured” means.
Make a product video
A short launch teaser, written as scenes of code and exported locally.
Connect other agents via MCP
Turn on the bridge so any MCP client can use your PaneScale board.
Practical reading.
Longer pieces on working with coding agents — most of them useful with or without PaneScale.
One terminal is not enough anymore
Coding agents got good enough to work in parallel. Our tools didn’t. Here is the idea behind PaneScale.
Five ways an agent can fake a green build
Agents rarely cheat on purpose, but under pressure to make tests pass they find shortcuts. Here is what to look for — and what PaneScale flags automatically.
Checkpoints that never touch your branch
How PaneScale snapshots a working copy byte for byte without moving HEAD, the index or any branch — and why rewinding refuses to overwrite your edits.
Write tasks an agent can finish
The difference between a task that runs overnight and one that wanders is usually a single sentence — the finish line. A short template and examples.
Bypass mode: a decision table
Skipping an agent’s permission prompts saves hours — and occasionally costs a lot more. When it is reasonable, and what to put in place first.
Why the second pane opens instantly
Starting a coding CLI takes seconds. Pre-warmed sessions hide that wait — here is how we do it without eating your memory.