Ophio runs Claude Code and Codex on your computer through their native interfaces. They use your signed-in accounts. Ophio does not turn a subscription into an API.
Start a task
- Choose a paired computer and project.
- Open Talk. For separate work, tap the task title and choose New task.
- Write the request. Use Message tools to choose the agent, model and effort. The send button opens Review for a new task; it does not start unseen work.
- Review the task’s mode, project, branch, instructions and Launch flags.
- Tap Start task.
The task’s agent picker is titled Agent for this task. It contains Agent, Model, Effort and Launch flags. Project defaults save the first three, not permission flags. A started task keeps its agent selection, branch, launcher instructions and permission policy through continuations and retries.
Features depend on the installed agent and companion versions. An unsupported feature is refused or shown as unavailable. Ophio does not silently replace a requested policy.
Work, Ask and Plan
- Work can change files and run commands under its chosen permission policy. Only one Ophio coding task can hold a project’s file-writing slot at a time.
- Ask is read-only. Use it for questions about the project.
- Plan is read-only. Use it to prepare work before allowing changes.
Read-only tasks can run beside the project’s writer. Requests to execute commands, change files or widen access are declined automatically in Ask and Plan; questions to you can still wait for an answer. Claude read-only runs omit project CLAUDE.md, skills and hooks to maintain their restrictions. Coding Work still uses project instructions, subject to the project-settings controls described in Security & access.
After a Plan finishes, Carry out this plan opens Review Work from this plan. Review the permissions, then tap Start Work. This continues the same task as Work. Its saved launch policy now applies.
For new Work tasks, Browser controls access to Ophio’s agent browser when the companion supports it. Ask and Plan do not have that browser or the person-collaboration tools. Website credentials are configured separately in Agent logins.
Launch flags
Skip permissions is on by default for new coding Work tasks, separately for Claude Code and Codex. The agent does not normally stop for native approval prompts under this policy. Codex also runs without its command sandbox. Use it only for work and repositories you trust.
To change a new task, open its agent picker and select Launch flags before starting:
| Choice | What happens in Work |
|---|---|
| Skip permissions | Native approval prompts are bypassed. Codex’s command sandbox is also bypassed. |
| Ask for approval | Restricted actions request approval in Ophio. Claude still honors actions already allowed by its native settings. |
| Accept edits | Claude Code allows file edits automatically. Restricted commands still ask. |
| Sandbox, no prompts | Codex uses its command sandbox. An action requiring approval is refused instead of prompting. |
The last two choices belong to their respective agents. Codex’s command sandbox normally disables network access for commands. It is not network confinement for the entire agent process.
In Settings → Launch flags, the defaults are Claude Code: skip permissions by default and Codex: skip permissions by default. They apply on this phone across its computers. Existing tasks and drafts with an explicit choice do not change.
Ask and Plan remain read-only regardless of these switches. A task’s policy cannot be changed after it starts. Start a new task to use another policy. Ophio does not rewrite your global Claude Code or Codex configuration.
These flags do not authorize desktop computer-use tasks, pairing, permission changes or private login steps.
Review instructions and questions
Optional Boundaries, Completion checks and Stop when fields tell the agent what you want. They are instructions, not computer-enforced restrictions or proof that checks ran.
An approval covers the action displayed. Inspect Allows, Expires where shown and Exact request when a preview is shortened. Allow sends approval. Deny… opens Reason (optional) before Deny sends a refusal. Questions use Your answer or their listed choices, then Send answer; Decline refuses the question. Questions and approvals can be answered from other authorized devices too. A settled request is no longer pending on your phone.
Use Notifications for alerts when the app is closed. Use Messages, feedback & results for steering, queued work, media and receipts.
Command status
Receipt by the computer and delivery to the agent are separate states. A request accepted by the computer may not yet have reached the agent.
If delivery or a result is unknown, reconnect and check the existing request. Do not create a new duplicate just because the first attempt lacks a confirmation. A local draft, a received command and a completed action are not the same thing.
Stop a task
Tap Stop for the named task. Talk keeps the current task’s Stop in its header. Open the activity row or task controls to reach another running task’s Stop; there is no permanent global Stop strip. Work → Project → Live agents also lists running and unresolved work. The request uses the control connection, separate from screen video, terminal output, transfers and speech.
Wait for the computer’s result. Stop requested does not mean the agent has ended. The app may offer Retry Stop, Stop again, or Force stop. Force stop is offered only for a process Ophio owns. It ends that process; it does not undo file changes and can leave an incomplete write.
Read Stop receipt and Still running / unknown in the task receipt. Contained agent subprocesses are stopped with the run. Externally delegated services, scheduled jobs or other work outside that containment can remain. A process or input result may be unknown. Check the computer before continuing if reconciliation is required. Recording your decision does not turn it into a verified result.
Pause queue prevents later queued tasks from starting. It does not stop the current task. Pause input pauses desktop input, not the coding agent process.
Agents started outside Ophio
In Work, open Live agents and find Outside the app. It observes identifiable Claude Code and Codex processes and saved session metadata. A saved session record is not evidence that a process is running. Hermes, OpenClaw and Pi are not checked there.
Opening the list gives Ophio no control over those agents. Where stopping is available, the review button includes the agent and process number, for example Review Stop · Claude Code 1234. It requires Agent tasks and Terminals access and a current observation. Confirming sends a termination signal to the process group. Detached processes may continue. Force stop is unavailable for a process Ophio did not start; stop it in its computer terminal if the result remains unconfirmed.