IFleet
weautomatehq1/IFleet
Frota autônoma Claude + Codex entregando PRs 24/7
Ver no GitHubAgent autônomo que executa o padrão pipeline canonical sem supervisão humana. Orquestra workers Claude (Opus/Sonnet/Haiku) e Codex para pegar tarefas, dividir entre modelos adequados, revisar, testar, corrigir e abrir PRs draft após CI passar. Roda em VPS gerenciado por PM2 com entrada via GitHub Issues e Discord.
Instalação
npx convez-ai weautomatehq1/IFleet1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automação contínua de tarefas de desenvolvimento sem intervenção
- Orquestração de múltiplos modelos Claude para diferentes etapas do pipeline
- Processamento de fila de trabalho com CI/CD integrado e PR automation
- Controle e observabilidade de agentes via Discord e GitHub Issues
Veredito

IFleet é uma implementação produção-ready de orquestração de agentes IA para DevOps. Requer profundo entendimento de arquitetura de sistemas distribuídos, mas entrega automação genuína de ciclo completo de desenvolvimento. Claramente advanced-tier e voltado para equipes que precisam escalar CI/CD com IA.
README
A tradução para o português deste README ainda está na fila.
IFleet
IFleet is the autonomous-mode implementation of the canonical pipeline pattern. Spec: ~/.claude/skills/CANONICAL-PATTERN.md.
Where the manual pipeline (/audit-scan, /audit-fix, /splittasks at ~/.claude/skills/) is Sebastian's supervisor-mode toolchain at the terminal, IFleet runs the same pattern unattended on a PM2-managed VPS — picking up tasks, splitting across the right models (Claude Opus/Sonnet/Haiku + Codex), reviewing, testing, fixing, opening draft PRs after CI passes.
The current trigger surface (GitHub Issues queue + Discord) is one of several possible inputs — not the canonical input. The canonical input is project context + a task description.
Status
Operational. The control plane, worker pipeline, GitHub queue, Discord control
surface, audit loop and observability stack are implemented (~25k LOC) and run
on a PM2-managed VPS. Architecture overview in
docs/ARCHITECTURE.md; day-to-day operation in
docs/RUNNING.md and docs/LAUNCH.md.
Cross-repo milestones live in weautomatehq1/factory/ROADMAP.md.
Stack
- Runtime: Node 20+, TypeScript via
tsx(no build step) - Workers: Claude Code Max (
claude -p --permission-mode auto) + Codex CLI (codex exec --json) - Auth juggling: CCS for Claude, codex-lb for Codex
- Queue: GitHub Issues with labels
- Isolation: one git worktree per task
- Triggers: Discord (herdctl) + GitHub Issues + cron
- CI gate: typecheck + lint + test before any PR opens
Quick start
pnpm install # Node 20+, pnpm 10
pnpm typecheck # tsc --noEmit
pnpm test # node:test + vitest
Running the fleet (env, PM2 services, Discord control) is documented in
docs/RUNNING.md. Launch sequence in
docs/LAUNCH.md.
Layout
IFleet/
├── config/ worker registry, routing rules, channel map
├── docs/ architecture + brief library
├── src/ orchestrator, workers, queue adapters
└── .github/ CI + CODEOWNERS
License
Private. Internal tooling.