Getting Started with Prompt Cellar

Connect your CLI tools to Prompt Cellar to automatically capture and sync prompts across all your AI assistants.

1. Install and Connect

The fastest first run is a single bootstrap command that installs the CLI, links your account, and configures hooks/wrappers:

npm install -g @promptcellar/pc && pc login && pc setup

If the CLI is already installed on this machine, rerunning pc login && pc setup is safe and refreshes the device link plus hook installation.

The setup step detects and configures:

Claude Code

Installs a native hook at ~/.claude/hooks/ that automatically captures prompts.

Codex CLI

Adds a shell wrapper that captures prompts when you use the codex command.

Gemini CLI

Adds a shell wrapper that captures prompts when you use the gemini command.

2. Push Prompts to Sessions

Send prompts from your Prompt Cellar library directly to your active CLI sessions.

How it works

  1. Your CLI tools connect to Prompt Cellar via WebSocket when active
  2. You'll see "Connected Sessions" on your project page and prompt pages
  3. Click Push to Session to send any prompt to your CLI
  4. The prompt appears in your terminal, ready to use

From the command line

You can also push prompts directly from the terminal:

pc push my-system-prompt

3. Open in Apps

Quickly send prompts to any AI assistant:

Web Interfaces

  • Claude.ai - Opens with prompt pre-filled
  • ChatGPT - Opens chat.openai.com
  • Gemini - Opens gemini.google.com

Desktop Apps

  • Claude Desktop - Copies prompt and opens the app
  • ChatGPT Desktop - Copies prompt and opens the app

Prompt Cellar remembers your last-used app, making it quick to send prompts to your preferred tool.

4. Troubleshooting

Check connection status

pc status

Re-run setup

If hooks or wrappers aren't working, re-run setup:

pc setup --force

Update PC CLI

pc update

Common issues

  • Sessions not appearing: Make sure pc login completed successfully
  • Prompts not capturing: Run pc setup and restart your terminal
  • Push not working: Check that your CLI tool has an active session with pc status