Skip to content
MelMel
Terminal > Code

Diffs & inline comments

Comment on diff lines and send the thread straight to the agent.

Reviewing a diff and noticing problems is half the job — the other half is getting them fixed. In Mel you can leave inline comments directly on diff lines in the code review panel, then hand the whole batch to the agent in one click.

Leaving a comment

  1. Open the review panel (ctrl+shift+=) and find the line you want to flag.
  2. Hover the line — a 💬 button appears.
  3. Click it. An inline comment editor opens anchored to that line.
  4. Write your note and confirm.

Each comment records the file, the line, an excerpt of the code it points at, and your text. Commented lines get a marker in the gutter so you can see at a glance where your notes live as you scroll the diff.

You can comment on as many lines, across as many files, as you like — the batch accumulates until you send it.

Send to Agent

Once you have at least one comment, a footer appears in the review panel:

N comments · Send to Agent

Clicking Send to Agent serializes all of your comments — file paths, line numbers, code excerpts, and your notes — into a single prompt and routes it to the active pane. Where it lands depends on what that pane is doing:

  • Mel agent conversation open — the prompt goes into the agent's input, ready to submit as the next turn.
  • CLI coding agent running (claude, codex, and friends in an interactive session) — the text is pasted straight into the agent's input via bracketed paste.
  • Plain terminal — the text lands in the prompt bar, where you can review it, edit it, or start an agent conversation with it.

Because the comments carry real file/line/excerpt context, the agent doesn't have to rediscover what you were looking at — it can go straight to the edit.

A practical flow

  1. Ask the agent (or a teammate, or past-you) for a change.
  2. Review the result in the panel: read the per-file cards, ctrl+click into definitions where you're unsure.
  3. Drop 💬 comments on anything wrong: an off-by-one, a missing error case, a naming nit.
  4. Send to Agent, let it apply the fixes, then reopen the panel to verify the new diff.

It's a tight review loop — comment where the problem is, fix where the agent is.

Related