Claude Board
A permission approval console for Claude Code - approve or deny permission requests from your phone or (future) a physical hardware device.
Requirements
Important: Claude Board requires Claude Code CLI in terminal for full functionality.
Environment Compatibility
| Environment | Permission Approval | TODO Tracking | Notes |
|---|---|---|---|
Terminal (claude command) |
✅ Full support | ✅ Full support | Recommended |
| VS Code Extension | ⚠️ Known bug | ✅ Works | See below |
| Claude Desktop (CLI mode) | ⚠️ Known bug | ✅ Works | See below |
| Claude Desktop (Chat interface) | ❌ Not supported | ❌ Not supported | Different architecture |
Known Issue: PermissionRequest Hook Bug
The PermissionRequest hook does not trigger in VS Code Extension and Claude Desktop's built-in CLI. This is a known upstream bug in Claude Code:
- Issue #13203 - PermissionRequest hook does not trigger in VSCode extension
- Issue #17036 - VS Code extension does not trigger hooks during permission prompt
- Issue #13339 - VS Code Extension ignores hook
permissionDecision: "ask"
Workaround: Use Claude Code in terminal (claude command) for full permission approval functionality. TODO tracking works in all CLI environments.
Why doesn't Claude Desktop chat work at all?
Claude Desktop's chat interface and Claude Code CLI are completely different products:
- Claude Code CLI uses
~/.claude/settings.jsonand supports Hooks - Claude Desktop Chat uses
claude_desktop_config.jsonand supports MCP Servers only
The chat interface has no "permission request" concept, so hooks cannot intercept anything.
Features
- Web UI: Approve/deny requests from any device with a browser (phone, tablet, desktop)
- Real-time updates: WebSocket-based instant notifications
- Sound & vibration: Get alerted when permission is needed
- YOLO mode: Auto-approve all requests with one click
- TODO tracking: See Claude's task list in real-time
- Keyboard shortcuts: Y/Enter to approve, N/Escape to deny
Installation
Using pip
pip install claude-board
Using uv
uv tool install claude-board
From source
git clone https://github.com/pescn/claude-board.git
cd claude-board
pip install -e .
Quick Start
1. Install hooks into Claude Code
claude-board install
This adds hooks to ~/.claude/settings.json. Your existing hooks are preserved.
2. Start the server
claude-board serve
3. Open the URL on your phone
The server will display a URL like http://192.168.x.x:8765 - open it on your phone.
4. Restart Claude Code
Claude Code needs to be restarted to load the new hooks.
That's it! Now when Claude Code needs permission to run a command, you'll get a notification on your phone.
Commands
# Start the web server
claude-board serve [--port 8765] [--open]
# Install hooks (preserves existing hooks)
claude-board install [--scope user|local]
# Uninstall hooks
claude-board uninstall [--scope user|local] [--all]
# Check status
claude-board status
# View/modify configuration
claude-board config [--port PORT] [--yolo/--no-yolo]
# Show version
claude-board --version
Configuration
Environment Variables
CLAUDE_BOARD_HOST: Server host (default:127.0.0.1)CLAUDE_BOARD_PORT: Server port (default:8765)
Safe Tools (Auto-Approved)
These tools are automatically approved without sending to your phone:
Glob,Grep- File searchingTodoWrite,TodoRead- Task managementTask- Subagent tasksWebSearch,WebFetch- Web operationsRead(within project directory)
Dangerous Tools (Require Approval)
Bash- Shell commandsWrite- Creating/overwriting filesEdit- Modifying files
Roadmap
Phase 0 (Current): Web UI ✅
Pure software solution with web-based approval.
Phase 1: Raspberry Pi (Planned)
Physical console with:
- Mechanical key switches (Approve, Deny, Retry, YOLO)
- E-ink display for task status
- Wired connection
Phase 2: Bluetooth (Planned)
Wireless physical console with BLE connectivity.
Phase 3: ESP32 Standalone (Planned)
Battery-powered portable device.
Development
# Clone and install in development mode
git clone https://github.com/pescn/claude-board.git
cd claude-board
uv sync --extra dev
# Run tests
uv run pytest
# Start server in development
uv run claude-board serve --port 8765
License
MIT
Contributing
Contributions are welcome! Please open an issue or pull request.
Metadata
Release files for claude-board 0.3.21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| claude_board-0.3.21.tar.gz | 80.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| claude_board-0.3.21-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 182.3 kB
Release files / claude_board-0.3.21.tar.gz
| Download URL | claude_board-0.3.21.tar.gz |
|---|---|
| Size | 80.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4bd09f926d6a1929a1239cc5a821f9e26943e8dc27ab44c91488e0c7ce88dcbc
|
|
BLAKE2b-256 checksum How to use checksums |
98b8a1cfefc64b5e2ebc55ba974d88ce1b6303ce6d116620aa16d5e574ee837b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 3, 2026.
Transparency logRelease files / claude_board-0.3.21-py3-none-any.whl
| Download URL | claude_board-0.3.21-py3-none-any.whl |
|---|---|
| Size | 101.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
522d5a4a1b8b53cfdd35fd3d241cda1a5b3c2b81ae3a5c2ae9c5197bf719e4a8
|
|
BLAKE2b-256 checksum How to use checksums |
2bbdd2e2f8b8a731ff2c9e26054360977e1e9b07694a665aa8633772b245448f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 3, 2026.
Transparency log