Overview
Aider is an AI pair programming tool that automatically commits changes to git. The plugin:- Launches Aider with prompt delivered inline
- Detects activity by monitoring git commits and chat history
- Uses Aider’s auto-commit feature to track completed work
- Supports one-shot and interactive modes
Aider focuses on simple, git-integrated workflows. It lacks session introspection and metadata tracking compared to Claude Code or Codex.
Installation
Configuration
Configure inagent-orchestrator.yaml:
Configuration Options
string
Model to use (e.g.,
gpt-4-turbo, gpt-4, claude-3-opus)enum
Approval mode:
skip: Auto-approve all changes (--yes)- Other values: Prompt for approval (default Aider behavior)
string
Custom instructions passed via
--system-promptstring
Path to system prompt file (loaded via shell command substitution)
string
Initial message sent via
--message flagHow It Works
Launch Behavior
Aider is launched with the prompt included in the command:Activity Detection
The plugin uses two signals to detect activity:- Recent Git Commits: Checks if any commits were made in the last 60 seconds
- Chat History Mtime: Monitors
.aider.chat.history.mdmodification time
Activity state classification
Activity state classification
Default threshold: 30 seconds
Auto-Commit
Aider automatically commits changes after each successful edit:Usage Examples
Spawn an Agent
Monitor Progress
Attach to Session
Limitations
No Session Info
Aider does not expose structured session data. The plugin returnsnull for:
getSessionInfo(): No summaries, token counts, or cost trackinggetRestoreCommand(): No native resume support
No Metadata Updates
Unlike Claude Code and Codex, Aider does not automatically update session metadata. You must manually track PRs and branches:Limited Activity Detection
Activity detection relies on git commits and file mtime:- Long-running tasks without commits appear idle
- Chat history updates are less granular than JSONL events
- No distinction between “ready” and “waiting for input” states
Troubleshooting
Agent shows 'idle' but is still working
Agent shows 'idle' but is still working
Cause: Aider hasn’t made a commit or updated chat history recentlySolution:
- Attach to session to check actual status:
- Check if Aider is waiting for approval (if
permissions != skip) - Reduce
readyThresholdMsin config:
Chat history file not found
Chat history file not found
Cause: Aider hasn’t created the file yet, or using non-standard locationSolution:
- Check if file exists:
- Wait for Aider to make its first API call (file is created lazily)
- Verify Aider is running with chat history enabled (default)
No cost or token usage data
No cost or token usage data
Cause: Aider does not expose this dataSolution: Track costs manually via:
- OpenAI/Anthropic billing dashboard
- Shell history parsing (if using API keys with per-request tracking)
- Aider’s built-in cost reporting (if available in CLI output)
Process detection fails
Process detection fails
Cause: Process name doesn’t match “aider”Solution: Check actual process name:If Aider is installed as
aider-chat or similar, the detection regex may fail. The plugin searches for the substring “aider” in the command line.Comparison with Other Agents
Use Aider for simple, git-integrated workflows. For production deployments with cost tracking and metadata updates, use Claude Code or Codex.
Environment Variables
The plugin sets these variables:string
required
Session identifier for orchestrator tracking
string
Project identifier (set by caller, not the plugin)
string
Issue/ticket identifier if applicable
