Setup guide

1. Choose how to run Digg

There are two ways to run Digg, and they use the same capture engine, so pick whichever fits how you work. You only need one.

2. Set up the terminal CLI

Requires Node 18 or newer (Node 22+ also captures Cursor's in-editor chat). Works on macOS and Linux.

1. 1
   Install the CLI
   This downloads the digg command to a folder on your PATH.

   curl -fsSL https://digg.sh/cli.sh | bash

   If it warns that the folder is not on your PATH, copy the export PATH=… line it prints into your ~/.zshrc (or ~/.bashrc) and open a new terminal.
2. 2
   Run guided setup
   One command signs you in, connects this machine, and starts capturing:

   digg

   Prefer to do it step by step? Run digg login, then digg connect, then digg start.
3. 3
   Approve the sign-in in your browser
   Digg prints a link like https://app.digg.sh/link?code=… and a short confirm code. Open the link (you must be signed in to Digg in that browser), check the code matches, and approve. No account yet? Create one first.
4. 4
   Confirm it is running

   digg status

   You should see Signed in: yes, Connected: yes, and Capturing: yes. From here, capture runs in the background and uploads on its own, with no further commands. Secrets are stripped before anything leaves your machine.
5. 5
   Capture your past sessions (optional)
   To include the coding history you already have on disk, run:

   digg backfill

   then restart capture with digg stop and digg start. Already-uploaded events are skipped, so it is safe to run more than once.
6. 6
   Watch it fill up
   Check anytime with digg earnings and digg sessions, or open your dashboard. Publish a session to Discover with digg share <id> public.

3. Set up the editor extension

For VS Code or Cursor.

1. 1
   Install the extension
   One line, auto-detects VS Code or Cursor and installs, even if the editor CLI is not on your PATH:

   curl -fsSL https://digg.sh/install.sh | bash

   Prefer to do it by hand, or want the raw .vsix? See the download page.
2. 2
   Reload the editor
   Open the command palette with ⌘⇧P (Ctrl+Shift+P on Windows/Linux) and run Developer: Reload Window.
3. 3
   Sign in
   In the command palette, run Digg: Sign in and approve in your browser. Capture starts automatically once you are signed in, there is no separate start step.
4. 4
   Capture past sessions (optional)
   Run Digg: Re-capture past sessions to upload the history already on disk. Safe to run more than once.
5. 5
   Watch it fill up
   Sessions land on your dashboard. Check status anytime with Digg: Workflow capture status.

4. How you earn

Per-session rewards are capped during launch (a daily and a monthly ceiling) to keep things fair. Your dashboard shows how much of each window you have earned. Licensing revenue is never capped.

5. Privacy and redaction

Redaction happens on your machine, before anything is uploaded. Digg removes three classes of sensitive data and reports a counts-only summary per session, it never stores or shows the removed value itself:

• Secrets, API keys, tokens, and private keys, both well-known formats and bespoke credentials found next to a key name.
• Personal data, emails, public IPs, phone numbers, card numbers, and SSNs, each validated per match to avoid false positives.
• Identity in paths, your username in home paths like /Users/<name>/…, anonymized while keeping the path shape.

When a batch reaches the server it is re-scanned as a second gate. Each session on your sessions page shows the exact counts removed and anything the server caught on re-scan. You can delete any session at any time.

6. Manage or stop capture

7. Command reference

8. Troubleshooting