aislop agent is the local repair workflow for findings that need judgment. It keeps the deterministic scanner in charge, creates an isolated git worktree by default, runs safe mechanical fixes, streams a headless provider session, verifies the result with aislop scan --json, and leaves the diff for review.
Use it when aislop fix has cleared the obvious cleanup and the remaining findings need a coding agent to understand context.
Basic usage
The foreground run uses a terminal UI with the current step, live activity, edited files, score and target, finding count, passes, token usage, and in-terminal decisions. Non-TTY and CI sessions keep plain streamed output.
Provider setup
aislop does not ask for OpenAI, Anthropic, or other API keys. Provider CLIs use their own local auth.
Supported repair providers are codex, claude, and opencode. The saved default lives in .aislop/agent/provider.json and is added to the repo’s local Git exclude so it stays out of commits.
Plan before editing
Use agent plan to preview what will happen before a repair session starts.
The plan shows the selected provider, provider source, worktree mode, current score, findings passed to the provider, apply behavior, commit message, and PR mode. It also reports blockers such as an unauthenticated provider, dirty checkout in isolated worktree mode, or --background --apply without --yes.
Apply and publish
By default, isolated sessions leave the repaired worktree for review. Apply or publish only after you inspect the diff.
Useful publishing flags:
Session review commands
Every session writes a local JSONL transcript under .aislop/agent/sessions/. Raw provider output stays in the transcript, while the terminal stream normalizes provider JSONL into readable progress.
Background sessions
Use --background when you want the repair to continue locally while you move on.
Background runs return immediately with a session id, transcript path, and log path. --apply --background requires --yes because a detached run cannot prompt.
Monitor mode
Monitor mode watches git changes and reacts after local edits settle. By default it scans and reports only. Automatic edits require both --repair and --in-place because the monitor edits the checkout you are actively using.
Main flags
Use aislop agent plan with the same flags before a real run when you are about to apply, commit, or open a PR.
