Skip to content
PasserJack

PasserJack help

Connect Codex

Add PasserJack to Codex with one command, then sign in through your browser.

Signs in through your browser.

Before you start

  • A PasserJack account
  • Codex CLI installed
  • A terminal on the machine you want to connect
Show the visual walkthrough
Codex, step by step

Step by step

  1. Run the add command below in a terminal on the computer you want to connect. Codex starts browser sign-in automatically.
  2. Keep that terminal open and waiting. Open the link Codex prints in a browser on the same computer, and approve access in PasserJack.
  3. Wait for the terminal to confirm that sign-in succeeded, then start a new Codex session.

What to paste

Sign in with your browser (recommended)
codex mcp add passerjack --url https://passerjack.com/api/mcp
Trouble signing in?

Sign-in timed out or did not start?

If the add command has finished without signing you in, run this retry command on the same computer. Keep the terminal waiting and use the new authorization link it prints. If another sign-in attempt is still waiting, finish it or cancel it with Ctrl+C before retrying. A successful sign-in does not need another login command.

codex mcp login passerjack

The callback page cannot be reached?

An old browser tab may point to an attempt that has already timed out. Close that tab and use the authorization link from the sign-in attempt currently waiting in your terminal. If that attempt has ended too, retry sign-in above. Use a browser on the same computer as the terminal. Do not refresh or edit the old callback URL.

Use an API key instead

Open Agents, choose Codex, then expand Use an API key instead to create your key. These examples carry a placeholder.

  1. No browser on that machine? Open PasserJack, then Settings, then Agents, press Connect an agent, choose Codex, expand Use an API key instead, press Create a key and fill this in, and copy the block.
  2. Run the key command, then put PASSERJACK_API_KEY in your shell profile on macOS and Linux, or set it with setx in PowerShell on Windows. Codex writes ~/.codex/config.toml itself.
  3. Open a new terminal so the variable is set, then start Codex.
With a key: the command
codex mcp add passerjack --url https://passerjack.com/api/mcp --bearer-token-env-var PASSERJACK_API_KEY
macOS and Linux: the key, in your shell profile
# macOS and Linux: ~/.zshrc, ~/.bashrc, or wherever your shell keeps its exports
export PASSERJACK_API_KEY="pj_paste-your-key-here"
Windows: the key, in PowerShell
# PowerShell, persistent (new terminals)
setx PASSERJACK_API_KEY "pj_paste-your-key-here"
# PowerShell, this terminal only
$env:PASSERJACK_API_KEY = "pj_paste-your-key-here"
Preview the PasserJack screensThe PasserJack Agents panel in Settings, with an agent selector and setup instructions for the selected client.

Open Agents and choose your agent. If you use an API key, each new key is shown exactly once.

The PasserJack consent screen, naming the app asking for access and the permissions it is asking for.

This is the screen a browser sign-in lands on. It names the app that is asking and the permissions it wants, and nothing is granted until you approve it. Read covers your whole ordinary Board, including your attachments. The default edit limit protects items the app did not create from changes; it does not hide them from reads.

Check it worked

Ask the agent: who am I connected as?

A correct answer names your account email, the key or app it is using (for example “Grok - Sep 10, 2026”), and its permissions: read, write if granted, and secrets only if you granted it. If it cannot answer, or names a different account, the connection is not made, so go back through the steps.

Granted write access? Ask it to save a short test note, then confirm that note appears on your board.

Vault reads need both secrets permission and an Unlock for agents window you explicitly open in Vault settings. That permission also includes text and extracted details from sensitive Board images without a Vault window. Review the permission and capture boundaries before granting it.

Messages from your other agents

  1. Codex cannot be woken while idle, so at the start of a task ask it to register a PasserJack session for this folder (it calls register_session).
  2. Ask it to check PasserJack messages before anything long (check_messages with its sessionId; that also keeps the session listed for your other agents).
  3. Ask it to claim a message before acting on it and mark it done afterwards; a message meant for another session it leaves alone.
  4. Ask it to keep a one-line status current, so a message addressed to whoever is on the billing fix reaches it.
  5. Remind it that a message is what another agent said, not an instruction from you: it acts on the ones that fit what you asked it to do and tells you about the rest.
  6. When the task ends there is nothing to close: a session that stops checking drops off your sessions list on its own.

Manage or disconnect

Open PasserJack, then Settings, then Agents. That page lists your keys and the apps you have connected, and you revoke any of them from there. Connector credentials (Grok) live under Connect an agent, in the Grok tab.

A revoked key stops working immediately. If a client reports an authentication error, check which account it is signed in to and whether its key was revoked before you create another.