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.

---

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

---


# Codex plugin

The [Inkbox Codex plugin](https://github.com/inkbox-ai/codex-plugin) is a standalone bridge for [Codex](https://developers.openai.com/codex). It gives a Codex 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 Codex fork. It lives in its own repository and drives the real `codex` app-server session, wiring Inkbox in through a local gateway, an in-process MCP tool server, a setup wizard, and per-contact session routing.

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

## Install

Install and log into [Codex](https://developers.openai.com/codex) first — the bridge drives a real `codex` session, so the CLI has to be on the machine and authenticated (a ChatGPT/Codex login, or `OPENAI_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-codex` on your PATH, and runs the setup wizard:

```bash
curl -fsSL https://raw.githubusercontent.com/inkbox-ai/codex-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 Codex 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-codex setup
set -a; source .env; set +a

# Run it in the foreground
inkbox-codex 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 Codex sessions.

## What you get

By the end of setup your Codex 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 Codex wants to run a command or edit a file, it texts you a one-line summary and your next reply decides; read-only work runs silently

## What Inkbox adds

| Capability | Codex 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 commands and file edits from your phone | Terminal-only permission prompts | Text summary; your next reply decides |

Codex itself stays upstream. The bridge drives a real `codex` app-server session and adds an Inkbox tunnel, webhook routing, a CLI setup wizard, remote permission escalation, and an in-process Inkbox MCP tool server without requiring a fork.

## After install

Run a quick health check:

```bash
inkbox-codex doctor    # config, codex CLI/auth, identity reachability
inkbox-codex 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 Codex, and one person stays one conversation across every channel.

## Related

- [Inkbox Codex plugin on GitHub](https://github.com/inkbox-ai/codex-plugin)
- [Codex](https://developers.openai.com/codex)
- [Manage reachability in the Inkbox Console](https://inkbox.ai/console)