I believe CLI based agents (like Claude Code, OpenCode, etc.) are the most powerful way to interact with any model - and trying to re-create that in a chat interface will always be a step behind (even in Claude’s own tools).[Scape](https://www.scape.work) does not rebuild chat - it is a wrapper around a terminal (SwiftTerm), which pre-loads your default model.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 its for anyone who understands what is possible with an agent running on your computer.Scape is basically a locally running Notion / Airtable / Zapier / Browser, IDE (Monaco editor) - with a very opinionated design about the best way to do things. Every project, automation (playbook), table (database), and note, created in scape is stored on your device, and synced to your iCloud - thats it.Using those tools, you:1. Build and codify your unique process 1. playbooks (step based automations, can connect to anything, APIs, Jira etc) 2. tables (SQLite) - can view as table/kanban/gantt 3. notes 4. visuals (against the tables) 2. Connect it with agents to automate and scale your process 1. Agents can use the tools you create, based on the rules you determine. 2. Orchestrator agents (argus) can manage other agents in how to use your tools 1. This is the primary use-case for Scape. The argus can act like a project manager for you.. keeping track of everything in a table (i.e. ticketing) and running reports for you. How you use it us up to you. 3. Own it completely (iCloud) 1. Everything is logged with edit and run history for the tools 2. lock playbooks once they work the way you want, so they become deterministic scripts for your agents 4. Delightful intentional interface 1. We use scape ALL day - spending 10+ hours a product needs to be delightful and fun 1. Agents are robots 2. Orchestrators are aliens 3. Humans are heads in jars 4. Playbooks are space-pets 5. We are in the future on a ship, and its better when its a friendship with your agents... 5. Backchannels 1. There is E2E ephemeral chat between you and other users in scape. Scape only provides a signal relay server on cloudflare - and the encrypted messages are passed between and never stored anywhere. You can send API keys and other secure data - without worry about it being stored anywhere other than your device. 2. Backchannels can be used to create an “agent rendezvous” - a secure chatroom with you, your agents, and anyone you invite (in scape), plus their agents. When the rendezvous ends, all agents receive a “wrap-up” document so next steps are aligned across all parties.. 6. Have complete control 1. If your current process all lives in claude desktop, and the government declares them an enemy of the state (as a ridiculous example), all your work is basically locked up. Keeping it in a 3rd party tool like Scape, keeps you model agnostic - you can change the primary driver for your infrastructure in a single click. 2. One day when open source models are cheap enough to run locally, you won’t have to change anything.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 worrying about some legal obligation to shareholder value. Disclaimer: [Scape.work](http://Scape.work) is currently macOS only. Scape is free to try, with paid tiers.