Inkbox

> # Documentation index
> Fetch the complete documentation index at: https://inkbox.ai/sitemap.xml
> Use this file to discover all available pages before exploring further.

---

# Claude Code plugin
description: Give your Claude Code agent an Inkbox email address, phone number, iMessage, and tunnel

---


# Claude Code plugin

The [Inkbox Claude Code plugin](https://github.com/inkbox-ai/claude-code-plugin) is a standalone bridge for [Claude Code](https://claude.com/claude-code). It gives a Claude Code agent its own Inkbox identity: mailbox, phone number, SMS/MMS, voice calls, iMessage, contact rules, and an Inkbox tunnel for inbound webhooks and WebSocket connections — so you can step away from the keyboard and keep working with it from anywhere.

This is a plugin, not an Inkbox SDK skill or a Claude Code fork. It lives in its own repository and drives the real `claude` CLI through the Claude Agent SDK, wiring Inkbox in through a local gateway, an in-process tool server, a setup wizard, and per-contact session routing.

<YouTubeEmbed id="MTVkW_EG-Y4" title="Claude Code plugin + Inkbox demo" />

[Plugin on GitHub ->](https://github.com/inkbox-ai/claude-code-plugin)

## Install

Install and log into [Claude Code](https://claude.com/claude-code) first — the bridge drives a real `claude` session, so the CLI has to be on the machine and authenticated (a Claude Pro/Max subscription, or `ANTHROPIC_API_KEY` set). You also need Python 3.10+ on macOS or Linux.

One command finds a Python 3.10+, installs the bridge in its own virtualenv, puts `inkbox-claude` on your PATH, and runs the setup wizard:

```bash
curl -fsSL https://raw.githubusercontent.com/inkbox-ai/claude-code-plugin/main/install.sh | bash
```

The wizard creates a fresh Inkbox agent for you (or takes an existing API key), provisions a phone number, connects iMessage, mints a webhook signing key, picks the project directory Claude works in, and offers to keep the bridge running on every boot. Re-running is safe. Useful flags: `--start` launches the background gateway when done, `--no-setup` installs without running the wizard.

Prefer to install by hand in any Python 3.10+ environment:

```bash
# Install the bridge
pip install -e .

# Interactive wizard — writes .env for you
inkbox-claude setup
set -a; source .env; set +a

# Run it in the foreground
inkbox-claude run
```

Keep the bridge process running. On startup it opens an Inkbox tunnel, configures mail, text, and iMessage webhook subscriptions plus the incoming-call channel, and routes inbound email, SMS, iMessage, and calls into Claude Code sessions.

## What you get

By the end of setup your Claude Code agent has:

- **An email address** - send, receive, and reply from an Inkbox mailbox
- **A phone number** - SMS/MMS and voice calls, inbound and outbound
- **iMessage** - reach and be reached over iMessage on the same identity
- **An Inkbox tunnel** - inbound webhooks and WebSocket connections reach the local bridge without a public server
- **Contacts and contact rules** - persistent Inkbox records and server-side allow/block controls
- **Remote tool approval** - when Claude reaches for a `Bash`, `Write`, or `Edit`, it texts you a one-line summary and your next reply decides; read-only tools run silently

## What Inkbox adds

| Capability | Claude Code alone | With Inkbox plugin |
| --- | --- | --- |
| Agent-owned mailbox | Bring your own integration | Built in |
| SMS/MMS and voice calls | Bring your own integration | Built in |
| iMessage | Bring your own integration | Built in |
| Inbound webhook and WebSocket tunnel | Bring your own tunnel/server | Built in |
| Contact and reachability controls | Agent memory or external tools | Built in |
| Approve `Bash`/`Write`/`Edit` from your phone | Terminal-only permission prompts | Text summary; your next reply decides |

Claude Code itself stays upstream. The bridge drives a real `claude` session through the Claude Agent SDK and adds an Inkbox tunnel, webhook routing, a CLI setup wizard, remote permission escalation, and an in-process Inkbox tool server without requiring a fork.

## After install

Run a quick health check:

```bash
inkbox-claude doctor    # config, SDKs, claude CLI, identity reachability
inkbox-claude status    # is the background gateway up? where are the logs?
```

Then text `START` to the agent's Inkbox phone number from every phone the agent needs to text. This opts that phone number in to SMS from the agent. You can also email the agent mailbox, iMessage it, or call the agent phone number; the bridge routes those inbound events into Claude Code, and one person stays one conversation across every channel.

## Related

- [Inkbox Claude Code plugin on GitHub](https://github.com/inkbox-ai/claude-code-plugin)
- [Claude Code](https://claude.com/claude-code)
- [Manage reachability in the Inkbox Console](https://inkbox.ai/console)