Send with Composer
The Composer is the input area at the bottom of the Thread screen. It is the main place you use when asking Codex to do something from the iPhone.
The usual flow is simple: write the request and send it. Only when needed do you reach for the top controls or the + menu.
Basic send flow
- Write the request in
Composer. - Add an image or command if needed.
- Tap the send button on the right.
After sending, you can stay on the same screen and follow the Work Log and Answer.
What the + menu can do
ImagesAttach an image from the photo library.CommandsPick from common slash commands.SkillsChoose a Skill available in that workspace.StatusCheck the current Host,Project, branch, model, and related state.ExecStart a separate one-shot execution.
You do not need to memorize every command name. When unsure, choosing from + is usually safer.
What the top control row changes
ModeLeave it at the default unless you specifically want to start from planning.SpeedChanges how response speed is biased.ModelSwitches the model.ReasoningRaise this only when you want deeper thinking.ApprovalChanges how command execution confirmation works.Follow-upChooses how additional instructions are sent while work is running.
For normal use, starting with the defaults and changing only when needed is enough.
Common commands
/statuscheck the current state/modelreview the model choice/approvalsreview the approval mode/imagesattach images/execrun something once outside the mainThread/forkbranch the current conversation
If the workspace has its own prompts or Skills, they can also show up as options.
When to use each Follow-up mode
Queuesends the next request after the current run finishesSteerinserts additional direction into the run that is already in progress
Steer is useful when you are away from the desk and want to add just one quick correction. Queue is better when you want the next request to wait its turn calmly.
No need to panic if the connection pauses
Even if Composer shows that updates have stopped, the work on the Mac usually keeps running. Often only the live stream on the iPhone was interrupted.
When the connection returns, the content is synced again. First keep the Thread open and wait a little, or reopen it to confirm the latest state.