Working with sessions

Accepting and denying edits

When an edit needs your approval — because the session's permission mode asks, or because your policy forces review — Ropenode shows it as a side-by-side Monaco diff with the agent's own reasoning for why it wants to make the change.

You answer with one of three choices:

  • Yes — apply it.
  • Yes, and don't ask again this session.
  • No, and tell Claude what to do differently — your note goes straight back into the conversation, so "no, use the existing helper in utils.ts" is one step away.

A proposed edit as a side-by-side diff, with the keyboard-only Yes / Yes, and don't ask again / No prompt beneath it.

Keyboard only, on purpose

The prompt is answered with the arrow keys and Enter. A mouse click deliberately does not answer it: one of the choices grants "don't ask again this session", and that is not something a stray click should be able to do.

This is the point of the product

Reviewing every change before it lands is the whole quality and liability story. AI-written code is churned at a materially higher rate than hand-written code, and it introduces more security defects. A diff you actually looked at is the cheapest control you have.

Scope

Claude Code sessions. A Codex console shows no diff prompts — see What is supervised.

Last updated Oct 11, 2026