-
-
Notifications
You must be signed in to change notification settings - Fork 0
Architecture
🌍 English narrative is auto-generated on release. See the French version for the current full content.
High-level map of the WorkPilot AI codebase: Electron frontend, Python backend, IPC bridges, and agent orchestration.
WorkPilot AI runs as a desktop application combining a Python backend with an Electron/React frontend, orchestrating an autonomous multi-agent pipeline: Planner → Coder → QA Reviewer → QA Fixer, followed by human review and merge. Every task executes inside an isolated git worktree, so the main branch is never touched directly; changes are reintegrated through an AI-powered semantic merge that resolves conflicts intent-aware rather than line-by-line.
The backend is Python and owns all agent logic. It has grown into 90+ specialized modules, with the core ones being:
| Area | Responsibility |
|---|---|
core/ |
LLM client factory (client.py, the only sanctioned entry point via the Claude Agent SDK), auth, worktree isolation, platform abstraction |
agents/ |
Planner and coder execution logic, session management |
qa/ |
Reviewer, fixer, and the QA validation loop |
spec/ |
Spec creation pipeline (complexity assessment → specification) |
runners/ |
~66 standalone entry points (spec, GitHub, Azure DevOps, self-healing, etc.) |
merge/ |
Intent-aware semantic merge |
integrations/ |
Graphiti memory, GitHub/GitLab, Linear, Windsurf |
prompts/ |
60+ system prompts, one per specialized agent |
A declarative workflow engine (workflows/) resolves a build's phases against the user's chosen effort level, the provider's capabilities, and the files touched, printing the resolved profile before the build starts.
An Electron application with a React 19 + TypeScript renderer. The main process manages agent queues, Claude profile credentials, PTY-based terminals, and 100+ domain-organized IPC handlers; the renderer holds the Kanban board, terminals, and settings UI backed by ~96 Zustand stores; a preload layer bridges the two via a safe electronAPI.
Task creation → spec generation → planning → parallel-capable coding → QA validation → issue resolution → merge. State is tracked across dedicated stores (project, task/spec, terminal, agent, settings), giving real-time visibility into each phase.
A three-layer model governs agent actions: OS-level sandboxing of Bash commands, filesystem restrictions to the project directory, and a dynamic command allowlist derived from the detected project stack. Credentials use OS-native secure storage (Keychain / Credential Manager) with automatic OAuth token rotation.
➡️ Continue: CLI usage
Getting started / Pour débuter
- 🏠 Home
- 📘 Introduction · fr
- ⚡ Installation · fr
- 🚀 First project · fr
- 🧠 Key concepts · fr
- ❓ FAQ · fr
Usage
- 🖥 User interface · fr
- 📝 Creating a spec · fr
- 🔁 Multi-agent pipeline · fr
- 🤖 Specialized agents · fr
- 🔌 Integrations · fr
- 💡 AI providers · fr
- 🧩 Memory system · fr
Advanced / Avancé
Community / Communauté