Agents get operations, not secrets.

RightSide separates browser identity from deployment authority and exposes a bounded MCP surface instead of arbitrary remote shell access.

Credentials

• Browser authorization grants explicit deployment scopes.
• The local credential file is mode 0600.
• MCP registration does not contain the bearer token.
• Tokens and device codes are stored server-side as hashes.
• Runtime and build logs are redacted before returning to CLI or MCP.

Rules for agents

• Never ask a user to paste a token, password, one-time code, cookie, session ID, or database URL into chat.
• Never place credentials in source, command arguments, MCP registration, or container images.
• Use browser authorization for people. Use an explicit token only for a trusted recovery or CI path.
• Do not turn a deployment failure into arbitrary infrastructure access.

Scope

The current founder path covers bounded project creation, deployment, status, redacted logs, rollback, and login status. Database configuration is an explicit opt-in path, not the default.