Aider

Aider's session model is diff-centric. The Viewport adapter captures the working set and diff stream so reviewers see the pending edits as part of the plan.

How it's wired

1. Aider exposes session events via its --watch-files and --hook plugin mechanism.
2. vpd install adds a Viewport hook that posts session start, diff-applied, and session-ended events.
3. Diff content is shipped as part of the plan artifact (when the workflow requires plan review). It is not sent for routine sessions.

Install

vpd install

You'll see:

[+] aider found at /usr/local/bin/aider
[+] Installing Aider hook... done

Verify:

cd ~/code/api
aider --message "convert auth middleware to bearer tokens"

Watch frames:

vpd logs --follow

Plan template

Aider's plan template includes a diff summary block:

Files to change:
  apps/api/src/middleware/auth.ts  (-12 / +28)
  apps/api/src/routes/login.ts     (-4 / +6)
  apps/api/tests/auth.test.ts      (-0 / +14)

Net: +32 / -16 across 3 files

The full diffs are deferred to "view diff" on the plan detail page, kept off the inbox-list preview.

Conventions inheritance

If your repo has a .viewport/config.yaml declaring an aiderProfile, Aider will inherit:

• Default model and temperature.
• Conventions / coding style.
• File include/exclude patterns.
• Pre/post-edit hooks (lint, format).

See Reference: Workflow YAML. Aider profile.

Limitations

• Streaming transcript granularity is coarser than Claude Code or Codex. Frames arrive when a file is touched or a diff is applied.
• Approval gates are at the diff level, not per-tool. Aider doesn't have a fine-grained tool-permission model.

Where to go next

• Concepts: Plans. How diffs render in the plan artifact.
• Reference: Workflow YAML.