Steering an agent

Everything you'd change at the keyboard has a control in the session. On a computer they sit as chips under the message box and in the header's ⋯ menu. On a phone, tap More in the header for the controls sheet.

While the agent is asking you something, the controls are hidden: typing would answer the question, so they can't work until it's answered.

#Model, effort and mode

Each agent offers its own choices. Claude Code's modes are Ask each time, Accept edits, Plan, Auto and Bypass permissions. Codex's are Ask for approval, Approve for me, Read-only, Full access and Plan. OpenCode's are Build and Plan, and Copilot's Manual approval and Full access. Model lists for Codex, OpenCode, Copilot and Antigravity come live from the agent and refresh every minute, so they match what your account can use.

Inyon changes them the agent's own way, as if you'd used the agent's picker, so the terminal shows the same thing. Some can't change mid-reply: a mode change waits until the agent finishes working.

A model or effort you pick in Inyon is for that session only. Claude Code saves a /model or /effort pick as your default for new sessions, so from 0.17.1 Inyon puts model, effortLevel and modelSettings in ~/.claude/settings.json (or $CLAUDE_CONFIG_DIR/settings.json) back the way they were once Claude Code has written them. Nothing else in the file changes. To change the default, pick the model in the terminal.

#Goals

A goal is a condition the agent checks before it stops: it keeps going until the goal is met. Tap the Goal chip and write one, such as All tests pass and the PR is open, then Set goal. The chat marks when a goal is set, met or cleared, and the sheet shows the last goal's outcome. Turn off clears it.

Goals work with Claude Code and Codex, and with Antigravity (which can't clear one yet).

#Remote Control

Claude Code and Antigravity can hand a session to their own apps. Turn on Remote Control in the menu starts it; an icon in the header then offers Open on claude.ai (or Open in Antigravity) and Turn off.

#Compact, clear, rewind

In Codex, every one of your messages also has Rewind to here while the agent is idle.

#Stopping and ending

• Stop (or Esc in an empty message box) interrupts the agent, like pressing Esc in the terminal.
• Exit to shell quits the agent and leaves the pane at a shell prompt, after asking.
• End session… closes the pane, its window or the whole tmux session. The confirmation says exactly which, and the session disappears at once.
• Copy session ID copies the agent's conversation ID, for resuming it elsewhere.
• Past conversations… (History on a phone) lists the agent's earlier conversations in this folder and switches to one. See Past conversations.
• Fork conversation (Fork on a phone), from 0.17, opens a copy of the conversation in a new tmux window next to this one, in the same folder and with the same flags, and takes you there. From then on the two carry on separately, so you can try another approach without losing this one. It works for Claude Code, Codex and OpenCode once the conversation has a first message; Inyon starts the agent with its own fork option (claude --resume <id> --fork-session, codex fork <id>, opencode --session <id> --fork).

#Background work

The layers button in the header (or the side panel on a wide screen) shows what's running beside the conversation:

• Running: queued messages, subagents with their transcripts, background shells with live output, and monitors. Shells and monitors each have a real Stop.
• Changes: what changed, two ways. This chat lists every file the agent changed with its edit tools in this conversation, with the diff of each edit, newest first. Changes it made by running commands (a formatter, sed, a script) aren't there; they show under Working tree. Working tree (from 0.17) shows what git sees: every change since the last commit, whoever made it. See Reviewing changes.
• Files (from 0.17): the session's folder, read only. Open a folder, read a file with syntax highlighting, see an image, or read a Markdown file rendered (Source shows the text). Mention adds @path to your message. Files over 512 KB show their first 512 KB.
• Preview: a dev server the agent started, in a frame, with a phone-width toggle. Inyon suggests the local ports it finds.
• Artifacts (Claude Code): pages the agent published, with Open, Copy link, and a button that asks the agent to delete one.

#Reviewing changes

From 0.17, Changes → Working tree reads the git repository the session's folder is in: the branch, how many commits it is ahead of or behind its upstream, and each changed file marked M (modified), A (added), D (deleted), R (renamed) or U (not tracked yet), with line counts. Tap a file for its diff. It refreshes when the agent does something, or with the refresh button.

• Commit all commits every change shown, with your message, as git add -A and git commit would. Your git hooks and commit signing run as usual; one that needs a password typed in the terminal fails with git's message instead of waiting.
• Push appears when there's a remote and something to push. A branch with no upstream yet goes to origin under the same name.

To comment on a line, tap its number in any diff, in either view. Comments collect under the diff; Add to message puts them all in your message box as one review, each under the file, line and code it's about, so you can add to it before sending. Clear drops them. Comments stay in the app until you add or clear them, and aren't saved anywhere.

#Usage and limits

The ring in the header shows how full the context window is; it turns amber past 60% and red past 85%. Tap it, or open Usage in the side panel, for:

• the context window, with Compact now;
• the plan and its limits: the 5-hour window and the week, with when each resets, plus Codex credits;
• the session's cost (Claude Code and OpenCode), run time and turns, and lines changed;
• the model, effort, fast mode, output style, the agent's version, the git branch, the folder, and the session ID;
• how Inyon matched the pane to its conversation, from an exact hook to a best guess by folder.

For Claude Code, the live numbers come from its status line, through Inyon's optional integration (turn it on from the machine's Integration tab). If a session stops reporting numbers, a note offers to reconnect or restart it. Settings → Restart sessions that stop reporting does that by itself.