Privacy
A local-first AI coding tool
Loopy is a local-first coding tool: the server, dashboard, and entire work graph run on your machine with your own keys. It's an agentic coding tool that pushes code only to the repositories you connect — nothing is uploaded to a hosted Loopy service.
What "local-first" means
Most AI coding tools route your prompts, code, and context through a vendor's cloud. Local-first inverts that: the application runs on your hardware and your data stays local by default. With Loopy, you install and run it yourself, and it drives coding-agent CLIs already on your machine.
Where your data lives
- Secrets — stored in
~/.loopy/config.json, never uploaded anywhere. - Work graph — tickets, agents, runs, and evidence live in a local SQLite database.
- Code — builds happen in a local working directory; commits go only to the repo you connect.
- Third-party calls — go straight from your machine to the providers you choose, not through Loopy.
Runs offline, on your terms
The Loopy server, dashboard, and workflow work without a connection. You only reach the network for the external services you opt into — your coding agent, model provider, or research APIs. That makes it a strong fit for private codebases and regulated environments.
Local-first vs cloud AI coding tools
| Cloud tool | Loopy (local-first) | |
|---|---|---|
| Where it runs | Vendor servers | Your machine |
| Your code | Sent to vendor | Stays local |
| Keys | Held by vendor | In ~/.loopy |
| Offline | No | Core features work offline |
| Data control | Vendor policy | Yours |
Run a local-first coding agent
Your machine, your keys, your data. A team of agents that never stop working.