Approvals in chat

When a step needs your answer, the approval card shows what Oda wants to do: a command exactly as it will run, or a file change as a diff. This page covers that detail, so you can check it before you answer.

The choices and what each one does are on Your first task; the card that holds the request is described on Approvals.

Check a command before you answer

When the request is about a command, the card shows the command text exactly as Oda will run it, for example pnpm test. Read the program, its options and the paths it names, then answer.

The same detail appears when Oda asks to retry a blocked command with wider access; see Command sandboxing and approvals.

Review a file change in the diff

When the request edits or writes a file, the card shows the proposed change as a diff: the file, the lines that would be replaced, and the lines that would come in. A write has no earlier version, so its diff shows the new content and nothing removed.

Nothing is written while the request waits: the change happens only if you allow the step.

When the card shows no detail

The detail block appears only when the request can be matched to the step it is about, and that step is still waiting.

You can still answer the request; only the detail is missing. How much Oda may do without asking is set by the chat's access mode; see Workspaces, files and permissions.

Questions, answered

How do I check a command before I allow it?

The card shows the command text exactly as Oda will run it, so you can read the program, its options and the paths it names. Nothing runs while the request waits.

How do I read a file change before I allow it?

The card shows the change as a diff: the file, its replaced lines and its new lines. A write has no earlier version, so nothing is shown as removed. The change is not applied until you allow the step.

Can I copy the proposed change?

Yes. Copy places the diff on your clipboard, and the control confirms with Copied. Copying does not apply the change; it still waits for your answer.

Why is part of the proposed change hidden?

A long diff is shortened: it counts the lines it hides, for example … 3 more lines. Choose Expand 3 more diff lines to see them, and Collapse (or Collapse diff) to close the diff again.

Why does the diff word a number of files?

It counts the files the proposed change covers: 1 file when the change covers one file, 2 files when it covers several.

Has the change already been made when I see the diff?

No. The diff shows what Oda proposes to do. Nothing is written while the request waits, and the change happens only if you allow the step.

Why does the card show no command or diff?

The detail shows only when the request can be matched to the step it is about and that step is still waiting. If the step has already finished, cannot be matched, or its details cannot be read, the card shows no command and no diff. You answer the request as usual; only the detail is missing.