Security model
The boundaries that keep agents, credentials, computers, and paired devices scoped.
GlinkBot is designed around a local owner, explicit capabilities, and narrow process boundaries. Local-first does not mean risk-free: an agent with tool or computer access can still act on the resources you grant it.
Core boundaries
- The harness owns agent processes and listens on loopback.
- The renderer receives configured-or-not credential state, not secret values.
- Provider-specific credentials are injected only into the process that needs them.
- Bots start at Ask for approval. Full access must be explicitly selected; it runs the engine in its most permissive mode. Real questions and missing credentials always come to you.
- Local computer control is a separate opt-in and per-bot selection.
- Paired phones use a default-deny API allowlist and per-device bearer tokens.
- Cloud and VPS backends are validated before reuse.
- Usage analytics are optional. In the desktop app, the switch in Settings turns them off, and a server's page its window shows starts with them off too (once that server runs the same version); in a browser, each server's page has its own switch. They send counts and fixed words, never keys, names, addresses or content; Usage analytics lists every event.
Your responsibility
- Review approvals, especially shell commands, file writes, and actions in connected services.
- Use dedicated environments for untrusted or destructive work.
- Keep provider accounts and connected apps scoped to what a bot needs.
- Revoke lost companion devices immediately.
- Keep GlinkBot and agent CLIs updated.
Security reports should be filed through the repository's documented security channel rather than disclosed in a public issue before a fix is available.
GlinkBot documentation, reviewed for the 0.0.4 codebase. Public download availability can differ. Licenses and acknowledgments.