Skip to main content
Never install a Platform key in an agent. A Connection key cannot administer the workspace or select another resource by changing the request body. List views expose metadata, not secrets.

Use the generated configuration

For agent and MCP connections, the CLI writes one value to the repository’s git-ignored .env:
rippletide connect removes superseded discrete Rippletide variables, including RIPPLETIDE_PROXY_URL. Do not re-add it. The app/manual path supplies:
Both formats remain supported. A valid connection string takes precedence over legacy fields; explicit client configuration can override environment settings. Use the complete block generated by your chosen path rather than mixing credentials from different connections. Keep staging and production credentials separate. Legacy key prefixes identify the environment; the connection string includes the endpoint explicitly. Codex uses ~/.rippletide/codex.env, not the repository’s .env. Its setup command claims the Connection key on the machine that runs Codex. The app’s single-use session token is a setup token, not a runtime key.

Tide-1 keys

Open Tide-1 in the selected workspace. The app uses your signed-in account session. An Admin’s first visit creates the workspace’s memory bank and its Connection key; later visits reuse them. Editors can use Tide-1 without receiving the secret. Provisioning, copying and replacing the key require an Admin account session. Backend calls use this bank’s Connection key in Authorization: Bearer <connection-key> for memory, policies, decisions and feedback. It also authorizes Policy inference from document text and explicit Policy edits. Inference returns suggestions; saving or activating them requires a separate Policy write. Agent/MCP and direct-integration policy guards use their own Connection keys in x-api-key; those credentials do not authorize Tide-1. An Admin can copy the same active secret again from Tide-1. Copying does not rotate it. Store the copied value in your application’s secret manager. Platform-key management scripts can manage separate issuer-owned banks; they cannot provision or manage the workspace’s default bank or its key.

Rotation and revocation

  • Agent/MCP Connection key: replace it from the connection’s page and update the runtime configuration. The previous key is revoked when replaced. For a CLI-managed repository, rerun connect to refresh its configuration.
  • Direct API integration keys: replacement keys can overlap. Revoke the old key explicitly after switching the integration.
  • Workspace Tide-1 key: expires after 90 days. An Admin explicitly replaces it in Tide-1; replacement immediately revokes previous keys for that bank and preserves its memory and policies. Update your backend secret after replacement. Expired or revoked keys cannot be copied and are not automatically replaced; account access remains available.
  • Platform keys: creating a new one does not revoke older keys. Revoke obsolete keys in Settings after switching your scripts.
  • CLI login: a repeated login reuses a valid stored key. Use logout then login to replace it or change accounts. Logout revokes the key before clearing local credentials; failed revocation preserves the local login for retry. CLI-issued keys expire after 90 days.
A Workspace Admin authorizes CLI access. workspaces use changes the CLI’s authorized workspace through browser approval, independently of the workspace open in the app.

Local files and removal

To disconnect a repository, remove instrumentation, remove the project binding and Rippletide runtime variables, and revoke its Connection key. Keep unrelated .env values. Account logout is a separate operation. For Codex use its uninstall command.