Alfred
Queue approved work
Start from a GitHub issue, Desktop request, Slack plan, or structured specification. Planned work waits at the configured approval gate.
OPERATING MODEL
Separate the recurring engineering loop from the decisions only you can make.
Alfred coordinates task intake, isolated code changes, independent review, evidence, and follow-up. You choose repositories, schedules, engines, approval rules, and merge policy.
Separate code changes
Implementation, test, review, and fix roles use dedicated git worktrees. Alfred records the branch, checks, and pull-request evidence.
Choose an engine for each role
Assign Claude Code, Codex, or OpenCode per role. The hybrid route remains Claude Code first with Codex fallback.
Keep reviewed lessons
Embedded SQLite recalls promoted lessons. Behavior-changing candidates wait for review by default, and memory actions remain reversible.
CONTROL POINTS
Alfred stops when the next step needs your authority.
The product controls scheduling and workflow. It does not replace repository policy, operating-system isolation, or human judgment.
Repository scope
Alfred schedules and indexes configured repositories. Use a dedicated user, virtual machine, or container when you need filesystem or network isolation.
Approval
Planned work and multi-repository fan-out can wait for explicit approval before entering the autonomous queue.
Review
A separate role reviews code and records findings. Missing GitHub evidence remains unavailable instead of appearing as zero.
Merge
Alfred does not merge by default. If you enable a merge policy, GitHub checks, reviews, threads, and repository rules remain the final gate.