Connect your AI tools to PromptBeat in under 60 seconds
Before you begin, make sure you have:
After creating your account, generate an API key:
pb_Open a terminal on your development machine and run:
The installer will:
The installer configures each tool differently based on what it supports:
Configures ~/.claude/settings.json with a PermissionRequest hook. No changes to your workflow — just start Claude Code as usual and permission requests appear in the app.
Configures ~/.gemini/settings.json with a BeforeTool hook. Same seamless experience — just run gemini as usual.
Creates a promptbeat-aider alias. Use it instead of aider:
Creates a promptbeat-codex wrapper that acts as a JSON-RPC client to codex-app-server. Use it instead of codex:
Creates a promptbeat-goose wrapper that bridges Goose's approval system to PromptBeat:
Configures ~/.config/github-copilot/hooks/promptbeat.json with a preToolUse hook. No changes to your workflow — just run copilot as usual and tool approvals route through PromptBeat.
You can also use the web dashboard from any browser.
PromptBeat also lets you run full AI chat sessions from your phone or web dashboard. To enable this:
The installer sets these automatically, but you can configure them manually:
| Variable | Description | Default |
|---|---|---|
PROMPTBEAT_API_KEY | Your API key (pb_...) | — |
PROMPTBEAT_SERVER | Server URL | https://promptbeat.online |
PROMPTBEAT_TIMEOUT | Seconds to wait for mobile response | 120 |
PROMPTBEAT_POLL_INTERVAL | Seconds between poll attempts | 2 |
PROMPTBEAT_ENCRYPTION_KEY | Optional E2E encryption passphrase | — |
For extra security, enable E2E encryption so tool inputs are encrypted before leaving your machine:
Then set the same passphrase in the mobile app under Settings → Encryption. The server never sees plaintext tool inputs.
PROMPTBEAT_API_KEY is set: echo $PROMPTBEAT_API_KEYcurl https://promptbeat.online/api/configsource ~/.zshrc~/.promptbeat/agent.logpython3 ~/.promptbeat/agent.pyContact us at support@promptbeat.online for assistance.