Security

Lobu is designed so agent execution is isolated while sensitive auth and network control stay centralized.

Security Model

• Worker execution is isolated per conversation/session.
• Gateway is the control plane for routing, auth, and policy.
• Outbound traffic is policy-controlled through the gateway proxy.

For deeper details, see the repository security document: docs/SECURITY.md.

Secrets

• Provider credentials and integration auth are managed on the gateway side.
• Workers should not depend on long-lived raw credentials in their runtime context.
• Settings links and integration flows are used to collect/refresh auth safely.

MCP Proxy

• Workers access MCP capabilities through gateway-managed MCP config/proxy paths.
• OAuth callbacks and token handling are centralized in the gateway.
• This keeps tool access extensible without exposing global secrets directly to workers.

Permissions Section

Permissions are managed as domain-level policies (for example Always, Session, or time-limited access):