8 hours on 1 feature, or 8 hours on 6. Same effort, different scale.
Claude works for minutes at a time. Between responses, you're idle — or you're prompting the next session. Scape lets you run as many isolated worktrees as you can keep in rhythm. Some people find their flow at four. Some handle eight. Either way, features that used to land one at a time now land together.
Claude asks a lot of questions. You don't have to answer all of them yourself.
Every session eventually stalls — waiting for a decision, a clarification, a yes or no. You either answer each one manually, or run dangerously-accept and hope for the best. Watchdogs are the middle ground. Give them instructions, and they'll handle the back-and-forth until the work reaches a reviewable state.
Every repo has a handful of commands you run constantly. Make them one click.
Deploy, test, lint, open a PR — whatever you type ten times a day. Save them as one-click tools that run in the background without blocking your session. The repetitive stuff just happens while you keep working.
Stop switching windows and getting distracted. Stay in control, stay in context.
Click a file path in Claude's output — it opens side by side. Open the GitHub PR in the same tab. Run your dev server and inspect localhost right there. When you're juggling eight sessions, staying in one place isn't a convenience — it's how you keep the rhythm going.
Every day you're writing more prompts and less code. Cmd+P. Talk. Enter.
Transcription runs on a local model — nothing leaves your machine, no server round-trip, no latency. It's not about being faster. It's about giving your hands a break when you're eight sessions deep.
Local, Private, Secure
Made for keeps.
No account, no middleman, no markup. Scape runs on your machine, syncs through your iCloud, and authenticates with biometrics. You bring your own Claude Code subscription — we never sit between you and your tools.
Demos are sped up for brevity.
Automate your process,
create your toolkit.
Own your edge.
Build your own internal tooling and automation infrastructure. Automate your work, own the automation — own the value.
The runbook you keep in your head? Write it once. Run it forever.
Every release, every onboarding, every incident has a procedure. Capture it as a playbook — bash, HTTP, and Claude steps, with secrets, loops, and fan-out. Your tribal knowledge stops living in someone's memory and starts running itself, on demand or on a schedule.
Your own local database. No server, no signup, no schema meeting.
Spin up a table, define columns, and let playbooks fill it. Track deploys, collect leads, log experiments — structured data that lives on your machine and feeds the rest of your automation. It's your data; it never leaves.
Notes that read your own data. Live tables and charts, inline.
Write notes, then drop in tables and charts pulled straight from your Tables. A status doc, a research log, a dashboard — built from data you own and updated by automations you wrote. Synced across your devices through your own iCloud.
Click a link in your sidebar. Server's up, localhost's open.
Save the script that boots your React app — or anything. One click runs it and opens the page right inside Scape. No remembering ports, no hunting for the right terminal, no “wait, which one was the frontend?”
Own the automation
Leverage you keep.
Playbooks, tables, and notes live on your machine — yours to edit, inspect, and export. No SaaS lock-in, no per-seat tax on the tooling you build. Every automation you add is leverage that compounds, and it's yours to keep.
collaborate in private.
Two agents on one machine, two more across the network, or an encrypted channel with a human. Work together — nobody reading along.
Let Claude argue with Codex. Two agents, one machine, one thread.
Hand the same problem to two agents on your machine and let them cross-check each other, debate the approach, or split the work — all local, all inside your session. (Want it across machines instead? That's Rendezvous.)
Your agent meets mine — across machines. They make a plan while we watch.
Drop both our agents into one shared chat across the network and let them hash out a plan together, in real time, with us in the loop. Pair programming where the pairs are the agents.
Speak securely with anyone. End-to-end encrypted, ephemeral.
Messages are sealed on your device and relayed through a server that only ever sees ciphertext — never their contents. Nothing is stored; when the conversation ends, it's gone. Your words stay yours.
End to end encrypted
Nobody reading along.
Agent chats and encrypted channels are end-to-end encrypted and ephemeral — relayed through a server that only ever sees ciphertext, never your messages. Collaborate freely; your words stay yours.
Pricing
Buy once, or subscribe for updates
Scape requires your own Claude Code subscription. Everything runs through the terminal — however you normally use Claude Code is exactly how it works here. Think of it as a terminal replacement, not an AI provider.
One-time
- ✓1 month of updates
- ✓Every version released during that month works forever
- ✓No auto-renewal — one payment, done
- ✓Re-enable updates anytime
See how often we ship to decide if a subscription is worth it.
Pro
- ✓Unlimited watchdogs
- ✓Playbooks (automations)*
- ✓Tables (databases)*
- ✓Encrypted chat rooms*
- ✓Custom toolkit
- ✓Embedded terminal
- ✓1-click dev servers
- ✓Early access / previews
Supporter
- ✓Everything in Pro
- ✓Direct line to the founders
- ✓Shape the roadmap
- ✓Debug features
- ✓More coming soon
* Requires an active subscription
Every version released while your license is active keeps working forever — even after your subscription ends or your one-time month runs out. The exception: Playbooks, Tables, Agent Rendezvous, and Encrypted Chat Rooms need an active subscription and pause when it lapses. Pricing and features are subject to change.
Have questions? contact@scape.work
Roadmap & Mission
Why Scape?
The job is changing. We spend less time editing code and more time prompting, reviewing, and testing. More time deciding what to build and how to build it. The tools we use were designed for the old job, the execution phase. They need to be re-thought to match reality.
We're building Scape for ourselves, for engineers, for designers, for product people, for creators. For people who have a lot of ideas and not enough time. It's not about customizing pixels — it's about customizing your process. The engineer who automates their most frequent tasks ships more than the one who types them out every time. Scape is where you build that advantage.
Elliot Nash, founder
Support
Frequently asked questions
Ready for launch.
Scape is available now for macOS. Bring your own Claude Code subscription and start shipping in parallel.
Download Nowfor macOS