Skip to content

Feature Overview

FylloCode organizes its features around the governance path of an Agent coding task inside a Workspace.

Product Path

PageProblem Solved
Project OverviewThe default Workspace entry point, aggregating governance status, active changes, recent lineage, and specification evolution by Project.
Multi-root WorkspaceOrganize multiple Projects in one window so an Agent can read multiple project directories within the authorized scope.
Task BoardA central task entry point for local tasks and tasks from connected engineering systems.
Chat and ExecutionChoose FylloCode or Native mode inside a fixed Workspace Session scope, align with Agents, delegate work, and move execution forward.
Proposal ReviewReview proposal, design, and tasks, then move Apply & Archive forward from the Chat session event rail.
Workflow OrchestrationUse YAML to codify your approved execution stages and Agent assignments.
KnowledgeBrowse Workspace-level knowledge the Agent flags and captures after user confirmation.
GuidelinesBrowse the engineering conventions maintained by each Project repository.
SpecsBrowse OpenSpec capability specs by Project after a Proposal is archived.
Work LineageBrowse every Workspace lineage subject and trace Plans, Proposals, and Commits by Session.
ACP AgentsInstall, detect, and manage Coding Agents that support ACP.
Engineering IntegrationsConnect engineering systems such as Yunxiao and write task results back to the existing toolchain.
SettingsManage application preferences, ACP Agents, service connections, and version information.

How to Read It

Start from a Task and decide in Chat whether this change should take the direct, Plan, or Proposal path. Then follow Apply & Archive through the same main path. When independent work can be split safely, an Agent in FylloCode mode can delegate it to another installed ACP Agent through fyllo-spawn. Knowledge, Guidelines, Specs, and Work Lineage provide background: 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 lets you browse the lineage that connects the path. ACP Agents, engineering integrations, and Settings support this workflow.

Proposal detail screenshot

Released under MIT