Remodex

What is Remodex?

Remodex is an open-source iOS app and “bridge” for controlling Codex from your iPhone. It lets you initiate and steer active Codex runs, perform follow-up actions, and interact with git commands from your mobile device.

The project is designed to be local-first: the Node.js bridge runs on your Mac and the repository stays on your machine. Communication uses end-to-end encryption so the transport layer cannot decrypt your code.

Key Features

• iOS remote control for Codex from your iPhone, enabling fast interaction without restarting runs
• Lightweight app behavior paired with a local Node.js bridge on your Mac, keeping the repo in place
• Multiple interactive modes: Fast mode for low-latency iteration and Plan mode for structured thinking
• Steering for active runs mid-execution, plus the ability to queue follow-up prompts rather than restarting
• Git workflow support from iPhone: commit, push, pull, switch branches, stash, and inspect diffs
• Encrypted QR-code pairing with automatic reconnection to trusted devices, avoiding repeated scans
• Local session resume and shared thread history with Codex.app via a “resume” command (as described on the page)
• Command-style interface for referencing files and invoking skills (e.g., @files, $skills, $-prefixed skills, and commands like /review, /status, /subagents)

How to Use Remodex

1. Install the bridge on your Mac using the provided npm command: npm i -g remodex@latest.
2. Start the bridge with remodex up. This connects to Codex and prints a QR code.
3. Pair from your iPhone by scanning the QR code in the iOS app. Then run remodex status to confirm the bridge is live.
4. Use the iPhone app to begin or steer Codex interactions, switch between modes (Fast/Plan), and issue git actions or review/status commands as needed.

Use Cases

• Iterating on an active coding run from your phone: start a task on Codex and later steer the same run by queuing follow-up prompts from iOS without restarting.
• Reviewing and tracking progress while mobile: use command options such as /review and /status to check what’s happening during a session.
• Running git operations remotely: commit, push, pull, switch branches, stash, and inspect diffs from your iPhone rather than directly using your Mac’s terminal.
• Structured prompts with planning: choose Plan mode when you want more structured thinking before producing or modifying code.
• Launching parallel sub-agents: use /subagents to spawn parallel agents as part of your workflow.

FAQ

• How does pairing work? Remodex uses QR-code pairing to establish a cryptographic session, and trusted devices auto-reconnect without needing a re-scan.

• Is my code encrypted in transit? Yes. The site describes an end-to-end encryption approach using X25519 key exchange and AES-256-GCM encryption, with replay protection.

• Do I need an account or cloud service? The page states there are “no accounts” and “no cloud,” and that pairing does not require a login.

• Where does the bridge run? The bridge is described as running on your Mac via a Node.js process started with remodex up.

• What commands are available? The page references command-style interactions such as @files, $skills, /review, /status, and /subagents, plus mode control and git-related actions.

Alternatives

• Local terminal-based Codex workflows: using a CLI or local tooling to send prompts directly from your computer. This keeps everything in one place but doesn’t provide iPhone-based steering and remote control.
• Other remote-control apps for LLMs (general category): apps that let you manage prompts and sessions from mobile. Compared with Remodex, they may not offer the same local-first bridge setup or QR-based end-to-end encrypted pairing.
• General-purpose mobile coding assistants: mobile apps for coding help and chat. These typically don’t include the same git workflow and “steer active runs” behavior described for Remodex.
• Self-hosted or local secure messaging integrations for coding assistants (category): solutions focused on encrypting communications between devices and an assistant runtime. They may cover security but may require more setup than the QR + bridge flow described here.