| Version | Supported |
|---|---|
| 0.1.x | Yes |
If you discover a security vulnerability, please report it responsibly:
- Do NOT open a public issue
- Email the maintainers with details of the vulnerability
- Include steps to reproduce if possible
- Allow reasonable time for a fix before public disclosure
Orchestrator spawns Claude Code agents as subprocesses. Each agent has an automatic permission sandbox that prevents:
- Reading other agents' workspaces (
~/.orchestrator/agents/<other-id>/) - Accessing orchestrator config files (
squads.json,variables.json,orch.db) - Reading the IPC socket directly
Variables in ~/.orchestrator/variables.json may contain sensitive values (API keys, database URLs). These are:
- Excluded from git via
.gitignore - Only interpolated at runtime into workflow prompts
- Accessible via the REST API on localhost only (port 47821)
The REST API binds to 127.0.0.1:47821 (localhost only). It does not support authentication — it is designed for local use by the app and its agents. Do not expose this port to the network.
The WhatsApp bridge stores credentials in ~/.orchestrator/whatsapp/auth/ with restrictive file permissions. QR code pairing uses WhatsApp's Linked Devices feature. Only phone numbers explicitly listed in the config can send commands.
- Never commit
variables.jsonwith real credentials - Keep
~/.orchestrator/out of version control - Review agent
CLAUDE.mdfiles for any hardcoded secrets before sharing - Use the permission sandbox — don't disable agent deny-lists