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:

$ codeep account
  Opening browser...
  https://codeep.dev/auth/cli?code=...
  Waiting for GitHub login.......
  Connected as @your-username

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.

⚠

The code expires in five minutes and works once. On its own it is useless: it grants nothing until someone already signed in opens it, which is why it is safe to paste into a chat window to get it onto your phone. The token the terminal receives afterwards is not — that one lives on the machine and is what you revoke below.

ℹ

You can run 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

★

No code, no prompts, no file paths are ever sent. Stats reporting is completely silent and only activates after you run 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
  📋 3 pending tasks for my-project:
  [bug] Fix login redirect loop
  [feature] Add dark mode toggle
  [task] Update dependencies

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 synced to any machine with a single command.

$ codeep account sync
  Pulling keys from codeep.dev... synced 3 keys.

$ codeep account push
  Pushing 3 keys to codeep.dev... done.

ℹ

Keys are stored encrypted at rest. Only you can decrypt them — the server never sees the plaintext key outside of the encrypted value.

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.

$ codeep account push
  Pushing config to codeep.dev... 4 personalities, 2 commands.
$ codeep account sync
  Pulling config from codeep.dev... updated 4 personalities, added 2 commands.

ℹ

A manual 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.

★

Hooks and MCP server configs are deliberately not synced: hooks run arbitrary shell, and MCP configs often embed tokens, so both stay local to each machine.

Preferences & profiles sync

Sync your learning preferences and saved profiles across multiple machines using the /sync command.

$ /sync
  ✓ Learning preferences pushed
  ✓ 2 profile(s) pushed

You can also sync individual parts:

$ /sync learning
  ✓ Learning preferences pushed
$ /sync profiles
  ✓ 2 profile(s) pushed

ℹ

Profiles saved on one machine are automatically pulled to any other machine that doesn't already have them locally.

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).

Git Integration MCP Tools