- No network of its own
- Armada makes no network connection by itself. The one exception is the update check, off until you turn it on. It reads one file,
armada.mgcrea.io/appcast.xml, and sends no identifier: not your licence key, not a machine id. - A licence checked on your Mac
- The key is verified offline, with a signature check. The app never contacts a licence server.
- Read only, where your agents write
~/.claude* and ~/.codex are opened read only. Armada never writes to Claude Code's or Codex's configuration, holds no vendor credentials, and never opens Codex's auth.json.- Only its own files
- Its preferences, usage history in
~/Library/Application Support/io.mgcrea.armada (kept 30 days, deletable from Settings), and a startup script in its own temporary folder when you start a session. - Checked on every build
make audit sweeps every Mach-O in the built app for URL loading, DNS and TLS symbols. The one allowance is narrowly named, for Sparkle, the update framework.- Out of your way
- A menu bar app with no Dock icon. A session you start or fork runs in your own terminal, and Armada never owns the agent process.
Armada is not sandboxed, by design: it has to read other tools' folders. And one program it runs does use the network. The claude it asks for your plan limits talks to Anthropic over your own sign-in, as it does whenever you use it. The full inventory is on theprivacy page.