Station guide / 02
Connect your accounts
Authenticate Claude Code and Codex inside your Station using each provider’s official flow. Your provider credentials stay on the machine.
Connect after the Station is ready
Choose Claude Code, Codex, or both when you create a Station. Installation and account authentication are separate: Station prepares the tools, then you authenticate directly with the provider from inside your workspace.
- Create a Station from mission control and wait for its status to become Ready.
- Use Open Station to enter the workspace.
- Open the connection card for Claude Code or Codex.
- Follow the official device or browser authorization flow shown by that CLI.
- Return to the workspace and run the tool’s status check before delegating work.
Never paste a key into mission control
The Station control plane does not need your Anthropic or OpenAI token. If a screen on the marketing site or dashboard asks for one, stop and report it.
Where credentials live
Provider authentication material is written by the provider’s own CLI inside your Station. It is not stored in the Station control-plane database and is not part of dashboard API responses. Destroying the Station removes its local workspace and credentials with it.
Google sign-in is different
Google may be offered as a way to sign in to the Station dashboard. That identity proves who you are to the control plane; it does not connect Google to Claude Code or Codex, and it grants no access to your repositories.
Local development mode
A locally simulated Station proves the lifecycle and dashboard flow but has no external workspace. Mission control says this explicitly and does not fabricate an access URL.