Monitor and steer Codex CLI runs from your phone
Junction helps Codex users keep local agent work visible after they leave the terminal. Watch runs, catch blockers, and decide when a branch is ready for review.
Best for
Codex users running local repository tasks from a CLI.
Why Junction
Use Junction when you want Codex visibility on mobile without moving the repository into a separate hosted coding environment.
What it means
Junction is the local-first control plane for AI coding agents.
Codex work should not disappear into one terminal
When Codex is editing a real repository, the next useful decision is often small: keep going, fix a blocker, stop drift, or review the result. Junction keeps those decisions visible.
Local execution remains the center
Codex keeps running where your repository, package manager, tests, and credentials already exist. Junction adds the browser control plane around that work.
Works across agents
Teams often compare Codex and Claude Code on different tasks. Junction gives those runs one shared dashboard instead of scattering them across terminal tabs.
Field notes
Related Junction guides
How to Monitor Codex from Your Phone Without a Cloud Sandbox
Watch Codex runs on mobile, keep execution local, and review blockers, diffs, and PR state without handing the repo to a hosted workspace.
Codex CLI vs Codex Web for Local-First Workflows
Compare Codex CLI and Codex web by execution location, local environment needs, review flow, and when Junction fits.
Use Claude Code and Codex Side by Side
Run Claude Code and Codex in separate local sessions, keep context isolated, and compare results without mixing agent work.
Get started
Keep agent work visible from anywhere.
Install the daemon where your projects already run, connect Junction, and use one browser workspace for active AI coding agents.