Connect Task, Chat, Proposal, and Archive into one traceable decision path via lineage, and make every Agent follow the same evolving rules.
FylloCode does not replace your IDE, CI/CD, or project management system. It adds a persistent, structured, and traceable governance layer above the codebase and engineering tools you already use.
Expose project-level conventions to every Agent so architecture boundaries, naming rules, and forbidden paths remain consistent across Agents and sessions.
Keep each proposal's context, tradeoffs, and rejected options as structured records instead of losing them inside a single chat.
Connect intent, discussion, implementation, review, and archive with clear artifacts so future maintainers can explain why a change happened.
Turn confirmed practices into durable project knowledge so the next Agent run starts from the latest rules.
From Task to Chat, then Plan or Proposal, and Apply & Archive, every input, decision, and artifact is recorded into one lineage. The rules and knowledge that survive the task become the starting point for the next one.
The starting point of the path. Tasks can be created locally or synced from connected engineering systems.
Agents analyze requirements, inspect code evidence, and help compare tradeoffs before a decision is made.
Work that doesn't change the contract becomes a lightweight plan; work that touches a public API, schema, or similar contract escalates to proposal, design, specs, and tasks so reviews have concrete artifacts and future work can trace the rationale.
Agents implement within the approved boundary, then archive decision context, spec updates, and guideline evolution for future tasks.
The product is organized around the full lifecycle of a change: the task board collects entry points, the Proposal page carries review and archive, the chat panel drives Agent work, and the Workflow editor keeps the process explicit.
FylloCode connects Coding Agents through ACP and writes task outcomes back to existing engineering systems through integration providers. Keep your current toolchain while adding the governance layer Agent collaboration needs.