Dashboard & Account
Added in v1.2.93
Link your Codeep CLI to codeep.dev/dashboard to track model usage, session history, and command stats — and to manage tasks and API keys across all your machines.
Connecting your CLI
Run the following command in your terminal:
A browser window opens where you sign in with GitHub. Once authorized, your CLI is linked and will automatically report session stats to the dashboard.
A server, or a machine you do not want to sign in on
The browser does not have to be on the same machine. The printed URL carries a one-time code; whoever opens it while signed in to codeep.dev approves that code, and the waiting terminal is handed its own token.
So on a server, or on someone else's laptop: run codeep account there, copy the printed URL, and open it on a device where you are already signed in — your own laptop, or your phone. You never sign in to GitHub on the remote machine.
codeep account on multiple machines. All sessions will appear under the same dashboard account. Each machine gets its own token, so Settings → Connected devices can cut off one without touching the others.What is tracked
Each time an agent task completes, Codeep sends a small metadata event:
- Model name and provider
- Session ID (random UUID, not linked to file paths)
- CLI version
- Slash command used (if any)
- Project name and programming language
- Whether the project is a git repository
codeep account.Dashboard features
- Total sessions and active this week
- Model usage breakdown with percentages
- Provider share chart
- Session trend over the last 30 days
- Projects list with language and git tags
- Project archiving — hide old projects with one click
- Tasks — create and manage bug/feature/task items per project
- API keys — store provider keys securely, sync to any machine
- Personalities & custom commands — sync across machines, view and prune from the dashboard
Tasks
Create bug reports, feature requests, and tasks from the dashboard and pull them into any CLI session with /tasks.
Tasks are scoped to the current project (by folder name). Mark them done from the dashboard once complete.
API key sync
Add your provider API keys once on the dashboard — they are encrypted with AES-256-GCM — and pull them to any machine. Cloud key sync is off by default and is turned on per machine, with your consent: codeep account sync --keys does it and pulls the keys in one step.
On a new machine, link it first. Codeep then offers to sync, asks before it turns key sync on (No by default), and picks a provider from the keys it pulled, so the next codeep opens the chat and not the provider screen.
To send the keys of this machine up, use push. It uploads the keys stored on the machine — in the system keychain, or in the plain-text fallback — and leaves out any key that only comes from an environment variable, naming the provider it skipped.
--keys or /keysync on. Turn it off again with /keysync off, and remove the keys from the server with codeep account purge-keys.Personalities & commands sync
account sync and account push also carry your personalities and custom slash commands — the Markdown files in ~/.codeep/personalities/ and ~/.codeep/commands/ — between machines.
sync treats the dashboard copy of a personality as current. If it differs from the local file, Codeep first preserves the local version in ~/.codeep/backups/personalities/, then applies the cloud edit atomically. Custom commands still merge additively and are never overwritten by a pull. View and prune both under Agent Studio and Custom commands on the dashboard.Preferences & profiles sync
Sync your learning preferences and saved profiles across multiple machines using the /sync command.
You can also sync individual parts:
Privacy
The dashboard uses GitHub OAuth for authentication — only your GitHub username and avatar are stored. No email, no private repo access, no code is ever sent or stored. Stats events contain only metadata (model, provider, session ID, version).