Security
Hard limits, not good intentions.
Boundaries decide before an action runs. A blocked action is never an approval, so an agent can’t talk its way past it. You choose how strict each session is.
Four levels. Pick one per session.
The most specific setting wins: the session, then the project, then your default. Only your own apps can change a level; the connector can’t. New accounts start at Off.
Protection level for this session
Balanced. Work freely, but no risky changes outside the project.
- Arcon’s own files and hooks
- Secrets: .env, SSH keys, credentials
- Sending data out: uploads, piping env
- Other people’s folders
- Config and dotfiles, /etc, shell profiles
- sudo, infra, production deploys
- Force pushes and protected branches
- Anything outside the project and temp folders
Set it per session, per project, or as your default. Only your own apps can change a level; the connector can’t.
You hear about it. The agent gets a no.
When a boundary stops an action, you get a notification with a plain explanation. Repeated severe breaches pause the session, and a pause is never silent.
Arcon itself
Its own credentials and hook settings, so an agent can’t switch Arcon off.
Your secrets
SSH keys, .env files and cloud credentials, also behind sudo or a shell wrapper.
Data leaving
Uploads, and secrets piped to the network.
What every level except Off protects. The full rule list for each level is in the docs.
Your code stays on your computer.
The connector only dials out, and your code and credentials stay where they are. Read what stays on your computer and what we store on the trust page.
Private beta · free while in beta
Keep the guardrails. Lose the babysitting.
Android app · web app (add it to your iPhone Home Screen) · Windows app in early access
