Choose an agent
Use Codex from Android with FireCursor
FireCursor can route a run to Codex through its supported desktop integration. Codex authentication and model availability remain governed by the user’s OpenAI setup; FireCursor provides the mobile control surface around that runtime.
Quick answer
The shortest useful version.
Configure Codex on the paired computer first, verify FireCursor reports it ready, choose Codex explicitly, send a bounded task, and use Android for questions, approvals, live evidence, and review.
Step by step
Do this with confidence.
- 01
Prepare Codex on desktop
Complete the supported Codex sign-in and confirm it can operate in the workspace before introducing remote control.
- 02
Read the readiness state
Use FireCursor’s provider inventory to distinguish configured, unavailable, and attention-needed states.
- 03
Select Codex explicitly
Provider routing is a decision, not a silent fallback. Confirm the project and task boundary before the run starts.
- 04
Supervise the evidence
Follow the plan and tool events, respond to prompts, and verify the resulting changes using the project’s own checks.
Authentication stays a provider concern
FireCursor does not sell or replace an OpenAI plan. The supported Codex runtime handles its own authentication, model access, and service terms. FireCursor reports readiness and carries supported control events.
That boundary prevents a polished mobile screen from implying access the underlying account does not have.
Give Codex a strong operating contract
- Name the files or subsystem in scope
- State whether edits are authorized
- Require the relevant test or build
- Protect unrelated user changes
- Ask for a concise evidence-backed handoff