What You Can Do

• Start, resume, and monitor sessions from phone, iPad, or the native macOS app
• Use an adaptive workspace with multi-pane layouts on iPad and macOS
• Handle approvals quickly for commands, file edits, MCP requests, and agent questions
• Queue Codex follow-up messages while a turn is running, then edit or cancel queued input
• Use Codex image generation results with generated images kept visible in the session
• Review code with File Peek and git diff tools including syntax highlighting, changed-file navigation, image diffs, staging, reverting, and commit-message generation
• Write richer prompts with Markdown, completions, voice input, and image attachments
• Switch usage display modes to see usage limits in the format that fits your workflow
• Tune Codex sessions with profiles, approval policy, Auto Review, plan mode, sandbox mode, and additional writable directories
• Run parallel work safely with git worktrees and .gtrconfig copy/hooks
• Stay notified with push notifications for approval requests and session results
• Manage machines remotely with saved hosts, SSH start/stop/update, QR codes, and mDNS discovery
• Keep macOS current with the native desktop app and in-app updates

Why CC Pocket?

AI coding agents are getting autonomous enough to write entire features on their own. Your role shifts from writing code to making decisions: approve this tool, answer that question, review the diff.

Decisions do not need a keyboard. They need a screen and a thumb.

CC Pocket is built for this workflow: start a session from your phone, let your machine's Codex or Claude do the heavy lifting, and make decisions from wherever you are.

Who It's For

CC Pocket is for people who already rely on coding agents and want an easier way to stay in the loop when they are away from the keyboard.

• Solo developers running long agent sessions on a Mac mini, Raspberry Pi, Linux server, or laptop
• Indie hackers and founders who want to keep shipping while commuting, walking, or away from their desk
• AI-native engineers juggling multiple sessions and frequent approval requests
• Self-hosters who want their code to stay on their own machine instead of a hosted IDE

If your workflow is "start an agent, let it run, step in only when needed," CC Pocket is built for that.

CC Pocket vs Remote Control

Claude Code's built-in Remote Control hands off an existing terminal session to your phone: you start on your Mac and continue from mobile.

CC Pocket takes a different approach: sessions start on your phone and run to completion there. Your Mac works in the background; your phone is the primary interface.

| | Remote Control | CC Pocket | |---|---------------|-----------| | Session origin | Start on Mac, hand off to phone | Start on phone | | Primary device | Mac (phone joins later) | Phone, iPad, or macOS app (host runs in background) | | Use case | Continue a desktop task on the go | Start coding from anywhere | | Setup | Built into Claude Code | Self-hosted Bridge Server |

What this means in practice:

• You can start a brand-new session and run it entirely from CC Pocket
• You can reopen past sessions from history stored on your host machine
• You cannot attach to a live session that was started directly on your Mac

Session Modes

On the Bridge side, Claude sessions are powered by the Claude Agent SDK. Session history remains compatible with Claude Code, so you can reopen past Claude Code sessions from CC Pocket and continue them in Claude Code when needed.

Claude uses a single Permission Mode that controls both approval scope and planning:

| Permission Mode | Behavior | |----------------|----------| | Default | Standard interactive mode | | Accept Edits | Auto-approve file edits, ask for everything else | | Plan | Draft a plan first, then wait for your approval before executing | | Auto | Let Claude's auto mode handle approval behavior when available | | Bypass All | Auto-approve everything |

Codex separates concerns into independent controls:

| Setting | Options | Description | |---------|---------|-------------| | Approval Policy | Untrusted / On Request / Auto Review / Never Ask | Controls when Codex asks for approval, including the Auto Review flow. | | Plan | On / Off | Toggle planning mode independently of approval policy. | | Sandbox | On (default) / Off | Run in a restricted environment for safety. | | Profile | Codex config profiles | Start or resume with a selected Codex CLI profile. | | Additional Writable Directories | Optional paths | Make another project or directory writable alongside the selected project. |

Codex defaults to Sandbox On for safety. Claude defaults to Sandbox Off.

You can also enable Worktree to isolate a session in its own git worktree.

Supported Models

CC Pocket does not expose every model available in the Codex CLI or Claude. Instead, the Bridge Server provides a curated list of recent, commonly used models, and the mobile app falls back to that same curated set when needed.

This keeps the setup and model picker simpler on mobile while still covering the models most users are likely to want. Adding support for more models is usually straightforward because the available model list is defined on the Bridge side.

If a model is available in Codex CLI or Claude but not shown in CC Pocket, please open an issue with the exact model name you want to use.

Remote Access and Machine Management

Tailscale

Tailscale is the easiest way to reach your Bridge Server outside your home or office network.

1. Install Tailscale on your host machine and phone.
2. Join the same tailnet.
3. Connect to ws://<host-tailscale-ip>:8765 from the app.

Saved Machines and SSH

You can register machines in the app with host, port, API key, and optional SSH credentials.

When SSH is enabled, CC Pocket can trigger these remote actions from the machine card:

• Start
• Stop Server
• Update Bridge

This flow supports macOS (launchd) and Linux (systemd) hosts.

Service Setup

The setup command automatically detects your OS and registers the Bridge Server as a managed background service.

npx @ccpocket/bridge@latest setup
npx @ccpocket/bridge@latest setup --port 9000 --api-key YOUR_KEY
npx @ccpocket/bridge@latest setup --uninstall

Global install variant:

ccpocket-bridge setup

macOS (launchd)

On macOS, setup creates a launchd plist and registers it with launchctl. The service starts via zsh -li -c to inherit your shell environment (nvm, pyenv, Homebrew, etc.).

Linux (systemd)

On Linux, setup creates a systemd user service. It resolves the full path to npx at setup time so that nvm/mise/volta-managed Node.js works correctly under systemd.

Tip: Run loginctl enable-linger $USER to keep the service running after logout.

Worktree Configuration (.gtrconfig)

When starting a session, you can enable Worktree to automatically create a git worktree with its own branch and directory. This lets you run multiple sessions in parallel on the same project without conflicts.

Place a .gtrconfig file in your project root to configure file copying and lifecycle hooks:

| Section | Key | Description | |---------|-----|-------------| | [copy] | include | Glob patterns for files to copy (for example .env or config files) | | [copy] | exclude | Glob patterns to exclude from copy | | [copy] | includeDirs | Directory names to copy recursively | | [copy] | excludeDirs | Directory names to exclude | | [hook] | postCreate | Shell command(s) to run after worktree creation | | [hook] | preRemove | S