Feature Overview
FylloCode is not organized like a generic chat tool. Its features follow the governance path of one Agent coding task.
Product Path
| Page | Problem Solved |
|---|---|
| Project Overview | The default project entry point, collecting governance status, active changes, recent lineage, and specification evolution. |
| Task Board | A central task entry point for local tasks and tasks from connected engineering systems. |
| Chat and Execution | Align with Agents in one project context, create plans, and move execution forward. |
| Proposal Review | Review proposal, design, and tasks, then run Apply & Archive. |
| Workflow Orchestration | Use YAML to codify your approved execution stages and Agent assignments. |
| Knowledge | Browse project-level knowledge the Agent flags and captures after user confirmation. |
| Guidelines | Browse the project engineering conventions the Agent maintains. |
| Specs | Browse OpenSpec capability specs synced after a Proposal is archived. |
| Work Lineage | Browse every project lineage subject and trace Plans, Proposals, and Commits by Session. |
| ACP Agents | Install, detect, and manage Coding Agents that support ACP. |
| Engineering Integrations | Connect engineering systems such as Yunxiao and write task results back to the existing toolchain. |
| Settings | Manage application preferences, ACP Agents, service connections, and version information. |
How to Read It
Start from a Task, decide in Chat whether this change should take the direct, Plan, or Proposal path, then follow Apply & Archive — these are the pages you'll use day to day. Knowledge, Guidelines, Specs, and Work Lineage are background knowledge: fyllo-cortex helps the Agent maintain the first two at explicit checkpoints, Specs is the formal contract left after a Proposal archives, and Work Lineage is the full browsing entry for the lineage that connects every step on the main path. ACP Agents, engineering integrations, and Settings are supporting capabilities.
