Workstation setup

Put your queue in your terminal.

Install the CLI and MCP server, sign in once, and every Claude Code session on this machine can read and act on your Prologue queue — scoped to your account, no shared keys.

How your access is secured: you sign in with your own email. The tools talk to the database using your token, and the database enforces — at the row level — that you can only ever see and change your own notes. No admin key ever lands on your machine, and one account can never read another's data.

STEP 1 · PREREQUISITES

What you need

Node.js 18+ — check with node -v. Install from nodejs.org if missing.
A Prologue account — the same email you use in the iOS or web app. No account yet? Sign in once at the web app or request an iOS invite.
Claude Code (or any MCP-capable agent), to use the queue inside terminal sessions.

STEP 2 · INSTALL

Get the CLI and MCP

Clone the tools, build the MCP, and link the plg command onto your PATH. Keep cli/ and lib/ side by side — plg loads its sign-in helper from the sibling lib/.

# clone and build
git clone https://github.com/jaimeaguileragarcia/prologue.git ~/prologue
cd ~/prologue/mcp && npm install && npm run build

# put `plg` on your PATH
ln -sf ~/prologue/cli/plg /usr/local/bin/plg
plg --help

STEP 3 · SIGN IN

One login for everything

Sign in once. This sends the same email link the app uses, catches it on a local page, and stores your session in your OS keychain (a 0600 file elsewhere). No password, no keys to copy.

❯ plg login
email: you@email.com
# check your email on this computer, open the link → you're signed in
❯ plg whoami
you@email.com

Try a capture: plg "my first terminal cue" — then open the app or web queue and watch it appear with a terminal tag. Offline? It spools locally and syncs on your next plg run.

STEP 4 · CONNECT CLAUDE CODE

Register the MCP server

Add one block to ~/.claude.json under mcpServers. It reads the session you just created — no keys in the config.

"prologue": {
  "command": "/Users/you/prologue/mcp/run.sh"
}

Restart your session and ask "what's in my Prologue queue?". The tools available:

list_pending_cues — what's waiting, newest first, with scores
dispatch_cue — pull a cue in as the working prompt
capture_cue — capture from the session (shows on your phone too)
write_outcome · score_cue — feed the quality trend
get_resume_packet — re-hydrate the next session

STEP 5 · YOUR DASHBOARD (OPTIONAL)

Read the queue anywhere

Your notes are a Postgres table in your own account — point any dashboard at it. Server-side reads use your own service-role key (kept on your server, never in a browser or the mobile app); a ready-made Next.js panel ships for the common case. See the dashboard guide for the schema and the updated_at watermark rule.

TROUBLESHOOTING

If something's off

"not signed in" — run plg login. Confirm with plg whoami.
The email link didn't sign me in — open it on the same computer running plg login; the local page needs to catch the redirect. Links expire quickly — resend if needed.
Rate-limited — the sign-in mailer allows a few messages an hour; wait a couple of minutes and retry.
MCP not appearing — check the command path in ~/.claude.json is absolute and restart your agent. run.sh resolves Node itself.
Switching accounts — plg logout, then plg login as the other email.