Skip to content

PasserJack help

Connect Gemini CLI

Add PasserJack to Gemini CLI with one command, then start Gemini and finish browser sign-in if prompted.

Signs in through your browser.

Before you start

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

Step by step

  1. Run the add command below in a terminal. --scope user adds PasserJack for every project on this machine.
  2. Start Gemini CLI. It may start browser sign-in automatically. Keep Gemini running and approve access in a browser on the same computer when prompted.
  3. Once PasserJack is connected, use its tools. Only if it is not connected and no sign-in is waiting, use the manual sign-in command below inside Gemini CLI, not in your shell. Do not run it after a successful sign-in.

What to paste

In your terminal
gemini mcp add --scope user --transport http passerjack https://passerjack.com/api/mcp
Sign in manually if needed

Skip this if browser sign-in already succeeded.

Only if not connected: inside Gemini CLI, not your shell
/mcp auth passerjack
Use an API key instead

Open Agents, choose Gemini CLI, 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 Gemini CLI, expand Use an API key instead, press Create a key and fill this in, and copy the block. Run that command instead.
With a key
gemini mcp add --scope user --transport http passerjack https://passerjack.com/api/mcp -H "Authorization: Bearer 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. Gemini CLI 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.