What local-first means for Blackcrab
Local-first is not a vibe for this product. It is a practical constraint around where transcripts live, how Claude Code runs, and what kind of trust the app should ask for.
The CLI stays in charge
Blackcrab does not replace Claude Code. It launches and coordinates the local CLI, then reflects the state that already exists on your machine. That is a smaller promise than a hosted agent platform, and that is the point.
Keeping the CLI in charge means the same authentication, billing, tool permissions, and project files remain the source of truth. The GUI can make the workflow easier without taking ownership of the developer's account or code.
Data should be inspectable
Transcripts and session state are useful because they are durable. They are also sensitive. A local-first app should make that tradeoff visible instead of hiding it behind a sync layer.
The goal is for exported markdown, session files, project paths, and git metadata to feel like normal local developer artifacts: easy to inspect, easy to back up, and easy to remove when needed.
Local does not mean risk-free
A local agent workspace still has serious power. It can coordinate shells, open URLs, read project files, attach screenshots, and help an agent run commands. Blackcrab should make those capabilities explicit instead of sanding them down in copy.
The bar is simple: before someone installs Blackcrab, they should know what it can touch, what it stores, what it sends, and what still feels rough. If that information is buried after the download, I have already asked for too much trust.