Mission
What is Scape?
I believe CLI-based agents — Claude Code, OpenCode, and the rest — are the most powerful way to interact with any model, and that trying to re-create that in a chat interface will always be a step behind. Even in Claude's own tools.
So Scape does not rebuild chat. It is a wrapper around a real terminal that pre-loads your default model, and around that terminal it gives you everything the terminal alone doesn't: somewhere to keep your process, and a way to hand that process to your agents.
Scape is a tool to help you define and scale your process, and to have total ownership and control over it. It works wonderfully for engineers — but it's for anyone who understands what is possible with an agent running on their computer.
Concretely, Scape is a locally running Notion / Airtable / Zapier / browser and IDE, with a very opinionated design about the best way to do things. Every project, automation, table, and note created in Scape is stored on your device and synced to your iCloud. That's it.
Build and codify your process
The way you work is worth writing down. In Scape you codify it with playbooks — step-based automations that can connect to anything, APIs, Jira, whatever you use — tables backed by SQLite that you can view as a table, kanban, or gantt, notes, and visuals built against those tables.
Connect it with agents
This is the primary use case for Scape. Agents can use the tools you create, based on the rules you determine. Orchestrator agents — Scape calls them Argus — can manage other agents in how to use your tools. An Argus can act like a project manager for you: keeping track of everything in a table (i.e. ticketing) and running reports. How you use it is up to you.
Own it completely
Everything is logged, with edit history and run history for the tools. Once a playbook works the way you want, lock it — it becomes a deterministic script for your agents. And all of it lives on your device, synced to your iCloud, not in someone else's cloud.
That ownership is also insurance. If your current process all lives in Claude Desktop, and the government declares Anthropic an enemy of the state (as a ridiculous example), all your work is basically locked up. Keeping it in a third-party tool like Scape keeps you model agnostic — you can change the primary driver for your infrastructure in a single click. One day, when open source models are cheap enough to run locally, you won't have to change anything.
Backchannels
Scape has E2E-encrypted ephemeral chat between you and other Scape users. Scape only provides a signal relay server on Cloudflare — the encrypted messages pass between devices and are never stored anywhere. You can send API keys and other secure data without worrying about them living on some server.
A backchannel can also become an agent rendezvous: a secure chatroom with you, your agents, and anyone you invite in Scape, plus their agents. When the rendezvous ends, every agent receives a wrap-up document so next steps are aligned across all parties.
A delightful, intentional interface
I use Scape all day. When you spend 10+ hours in a product, it needs to be delightful and fun. So Scape has a crew: agents are robots, orchestrators are aliens, humans are heads in jars, and playbooks are space-pets. You're in the future on a ship, and it's better when it's a friendship with your agents.
We must own the value we create
The way I work is based on my experience — it belongs to me. If I can build an agent that works like me, it belongs to me. My value as a designer, engineer, manager, increases with my ability to scale my own process and expertise. I need the confidence to know I'm not building my replacement at my place of work.
Why not free or open source? Many open source projects in this space have raised money from investors. I'm bootstrapping Scape so I can always focus on my customers and not worry about some legal obligation to shareholder value.
Scape is currently macOS only — I plan to add support for Linux and Windows in 2027. It's free to try for 7 days, with paid tiers after that.