# Example manifest: aider

## Metadata

| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | cap-protocol |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | CAP agent manifest for aider |
| Source URL | https://github.com/rsclaw-ai/cap-protocol/blob/main/examples/aider.toml |
| Source type | example config |
| Source date (published) | Unknown, not stated (repo living file) |
| Date researched | 2026-10-18 |
| Researched by | tai (agent), model: Muse Spark, on behalf of retoor |
| Research method | direct raw-file fetch, read in full (51 lines) |
| Confidence | High |
| Status | Active |

## Summary

PTY-only REPL agent: startup command carries agent-specific flags (`--no-auto-commits`, `--no-suggest-shell-commands`), `^>$` idle, `/run` tool-call prefix, `multi_session = false`, unmetered cost.

## Key findings

- Startup commands embed policy flags; drivers append model/session args to this prefix rather than replacing it.
- `multi_session = false` is the only false in the set: orchestrators MUST serialize aider sessions.
- `metered = false`: no `cap.usage` expected; budget enforcement for aider is wall-clock/turn-count only.

## Pros / strengths

- The serial/unmetered corner that tai's orchestrator caps must respect.

## Cons / limitations / caveats

- `/run`-prefixed tool-call pattern is thin; PTY tool events for aider will be sparse by design.

## Relevance to tai

Orchestrator fixture for single-session agents and unmetered budget handling.

## Changelog

| Date | Change |
|---|---|
| 2026-10-18 | Initial dossier created. |