FylloCode: baixar versions anteriors

This release makes attachments easier to bring into Chat and adds explicit scope and model selection to cross-Agent delegation. The ACP Agents page now uses a curated catalog, while managed installation covers more cross-platform archive formats and verifies download digests when available. Tool activity also presents the additional operations defined by ACP 1.3 with accurate semantics.
Added
- The Chat composer now accepts pasted clipboard images and dropped images or regular files. Mixed text-and-image paste keeps the text, dragged text retains native behavior, and directories are not traversed; supported files from the same batch can still join the draft
- Cross-Agent delegation can select one Folder from the parent Session's authorized snapshot on the first call. Omitting the Folder still inherits the complete Workspace; the scope remains fixed after creation and appears as Workspace or Folder in spawned Session details
- fyllo-spawn prompt_to_agent can select a semantic model and thought level without a probe task. When a value cannot be resolved uniquely, it returns the real candidates without dispatching the original prompt, and the same spawned Session can continue after a selection
Changed
- The ACP Agents page now shows registry Agents only from FylloCode's curated catalog, without merging or falling back to the official Registry. Agents found only in historical installation records but absent from the curated catalog no longer participate in discovery or connection warmup; custom Agents are unaffected
- Managed Agent installation now supports ZIP, TAR, TAR.GZ/TGZ, and TAR.BZ2/TBZ2 without system extraction commands. FylloCode verifies SHA-256 before extraction when the catalog provides a digest, and stages an update before commit so a failure preserves the existing installation and record
- Chat tool activity now uses distinct icons and summaries for ACP 1.3 kinds such as delete, move, think, fetch, and switch mode. Unknown kinds continue to use the generic tool presentation
Fixed
- Fixed streamed ACP argument fragments replacing an established tool title. A tool now keeps a stable name during execution and still accepts a later explicit title from the Agent
Notes
- The application version is 0.15.5.
- The fyllo-spawn MCP server is now 0.3.0, adding single-Folder scope, semantic model / thought-level configuration, and the recoverable configuration_required result. Its five tools, background default, ownership checks, and RPC protocol version 1 remain compatible.
- The fyllo-cortex MCP server remains at 0.7.0, and fyllo-specs remains at 0.11.1; neither server changed in this release range.
- Installation remains available when a registry record has no SHA-256 digest, but FylloCode does not present that installation as verified.

This release completes asynchronous control and observability for cross-Agent delegation: spawned Sessions now run in the background by default, can be cancelled on request, stream their completion notifications into the parent Session, and remain visible at any time through a persistent per-session activity bar. Every real session also gets its own URL for direct access, refresh recovery, and navigation from other pages.
Added
- Every real session now uses its own /chat/<session-id> subroute. Task pages, session search, and lineage open the session directly, and a refresh stays on the same session; /chat remains the draft entry before the first message, and an invalid or out-of-Workspace session route falls back to /chat with a notice
- Added a child-Agent activity bar at the bottom of the Chat conversation area. When the current session owns spawned Sessions, the bar shows the total as 子 Agent N plus the running count; its list orders Sessions by active first, then by most recent update, with each entry's Agent, synchronous or background mode, status, prompt preview, and update time. Opening a Session shows read-only details organized by Turn, with the latest Turn selected by default and earlier Turns available, each showing its original prompt, aggregated Activity, compacted Transcript, status, and response IDs
- Added the cancel_session tool to fyllo-spawn. The parent Agent can request cancellation of a running spawned Session it owns; { cancelled: true } only means the request was triggered, the turn settles as error with code TURN_CANCELLED_BY_PARENT, and the final state is confirmed through check_session_status
Changed
- fyllo-spawn's prompt_to_agent now runs in the background by default (background defaults to true): the call returns accepted once Main owns the turn, so the parent Agent can keep working and later collect the result through check_session_status and read_response. Callers that need synchronous blocking must pass background: false explicitly. This is an incompatible default change; older calls that omit the parameter behave differently
- When a background spawned turn completes, its completion notification now streams into the parent Session like a normal reply: the Session shows a running state and sending is temporarily disabled during the notification turn, and multiple pending notifications for the same parent are delivered one at a time in order. The notification turn lifecycle remains owned by Main; closing the window only interrupts the live projection and does not cancel or lose the reply
- The spawn.session Signal changed from a required discovery step to an optional contextual deep link. Main automatically exposes newly created and continued spawned Sessions through the parent Session's activity bar, so omitting the Signal does not affect visibility
Fixed
- Fixed the missing loading feedback and silently rejected sends in the parent Session while a spawn notification reply was running: once dispatch is accepted the Session enters submitted, and turns to streaming when the first content chunk arrives
Notes
- The application version is now 0.15.4.
- The fyllo-spawn MCP server is now 0.2.0. This version adds cancel_session and changes the background default to true; the latter is a breaking change, and callers that rely on synchronous blocking must pass background: false explicitly.
- The fyllo-cortex MCP server remains at 0.7.0, and the fyllo-specs MCP server remains at 0.11.1; neither server changed in this release range.
- The child-Agent activity bar and Turn details are read-only and read from Main's durable records and live state; no continue, cancel, or retry entry points were added to the UI, and completion-notification delivery semantics are unchanged.

This release makes past Chat sessions easier to recover and collects an Agent's file changes from one turn into a read-only Diff view. ACP tool events, message audit metadata, and JSONL writes now follow consistent semantics, while multi-root Workspaces choose and create Proposals independently for each Project. Sidebar, timeline, and tool-detail layout changes reduce wasted space and horizontal overflow in long conversations.
Added
- Added current-Workspace session search to the Chat sidebar. It finds past sessions by title, FylloCode Session ID, or visible User and Assistant text; excludes reasoning, Tool input and output, and system reminders; orders results by match type and update time; returns at most 50 entries; and opens a result through the existing session flow
- Added turn-level file-change review to tool details. Changes aggregates ACP diffs from visible normal tools in the current assistant message into added, modified, and deleted files in a read-only Diff Slideover whose items start collapsed and allow several files to remain expanded; Locations opens absolute paths and line numbers through the existing local-file preview
Changed
- ACP tool-call pending, in_progress, completed, and failed states, diffs, locations, failure text, and replacement semantics now remain consistent across live messages, Main persistence, and history reload. New messages also record updatedAt and the optional model / effort used at actual Prompt dispatch, with per-file serialization and atomic rewrites protecting JSONL history
- Multi-root Chat now separates a goal by Project and chooses Direct, Plan, or Proposal for each owner independently. When several Projects change behavior contracts, the Agent lists owners, specific contract changes, and cross-repository dependencies for confirmation, then creates one repository-owned Proposal per owner; Projects below the threshold can still use Direct or Plan
- A short pinned-session group now shrinks to its content, up to 50% of the available sidebar height, while Recent Sessions uses the remainder. The prompt timeline is narrower and uses a vertically centered transparent overlay on the left, without changing its surface on hover
- Updated ACP, MCP, Vue, Nuxt UI, Pinia, MarkStream, Monaco, and development dependencies. stream-monaco is now 0.0.49 with a local compatibility patch that keeps Diff Editor code lines aligned
Fixed
- Fixed renaming a Session during an Assistant reply replacing the Renderer running state with server metadata and hiding the runtime indicator too early
- Fixed re-entering the same new-session draft cancelling an in-flight probe and losing the Agent Session configuration loaded by that first probe
- Removed status-suffix DOM for all four normal-tool states. In-progress tools keep shimmer, failed tools keep an error-colored icon and Error details, and expanding an Activity group no longer lets hidden suffixes widen the message column
- Fixed fyllo-specs Proposal creation instructions to preserve the complete .openspec.yaml, and unified metadata serialization across Create, MCP Apply, and Archive so status writes neither truncate other fields nor add unrelated quotes to ISO timestamps
Notes
- The application version is now 0.15.3.
- The fyllo-specs MCP server is now 0.11.1. This patch keeps tool names, inputs, outputs, transports, and storage locations compatible while adding per-Project single-owner guidance and metadata write-safety fixes.
- The fyllo-cortex MCP server remains at 0.7.0, and fyllo-spawn remains at 0.1.1; neither server changed in this release range.
- New message JSONL records can include optional updatedAt, model, effort, and tool metadata. Historical messages need no migration: missing updatedAt falls back to createdAt in memory, and other absent fields remain absent.
- Session search reads existing Session metadata and message JSONL on demand without creating an index, cache, or new persistence format. Large Workspaces can take longer to query; the R

This release lets each Chat session choose between FylloCode collaboration and the Agent's native behavior, and adds cross-Agent delegation with background execution and read-only inspection. Proposal Apply and Archive entry points now return to Chat: the user message expresses intent, while actual task and archive state drive the interface.
Added
- New Chat sessions can select FylloCode or Native before the first message. FylloCode mode continues to inject project specs, guidelines, knowledge, and built-in MCP servers; Native mode keeps the fixed Workspace scope and Agent Session configuration without FylloCode reminders or bundled MCP. Historical sessions default to FylloCode mode
- Added the fyllo-spawn MCP server. An Agent in FylloCode mode can delegate focused work synchronously or in the background to another installed ACP Agent, then query status, continue the owner-scoped Session, and read long responses in bounded chunks
- Chat can inspect spawned Sessions. A new delegation can render a clickable spawn.session Signal, and the detail Slideover shows trusted status, the original prompt, Activity, Transcript, and response IDs. The composer also summarizes background tasks running for the current parent Session
- Added a Session Actions menu to the Chat header for copying the current FylloCode Session ID, with success and failure feedback from the clipboard operation
Changed
- The Proposal detail Slideover is now for review and status inspection; it no longer starts Apply, Archive, or run history directly. Start Applying and Archive in the Chat Event Rail send owner-qualified user messages so the current Chat drives the next stage
- Proposal archive readiness now comes from the actual completion state in tasks.md. Main watches task and status changes and keeps tracking the same linked Proposal as it moves into archive, merges into the main worktree, and loses its linked worktree
- Draft attachments remain local previews until the first message is submitted instead of creating a Session early. First submission persists attachments and the message under one Session, and a failure removes the uncommitted Session while preserving the draft for retry
- Context usage now moves through yellow, orange, and red guidance at 75%, 90%, and 95%. The tooltip focuses on current Context use and recommends starting a new session or summarizing the conversation when risk increases
- The static startup page, the first renderer frame, and the Vue startup overlay now share the dot-matrix logo, wordmark, and startup status, reducing white flashes and visual jumps while preserving light, dark, and reduced-motion behavior
- Production dependency classification now avoids copying renderer-bundled libraries into app.asar/node_modules; the verified macOS arm64 package size dropped from 364 MiB to 284 MiB
Fixed
- Fixed draft attachment selection creating multiple empty Sessions, leaving a New Session title, and later causing cross-Session attachment rejection
- Fixed races that could access an already-destroyed Renderer or clean Chat probes twice during startup cleanup, Workspace cleanup, or shutdown
- Fixed internal FylloCode system reminders appearing as ordinary messages in Chat history
- Fixed completed Proposal tasks still displaying Applying, and linked Proposal archive relocation being misreported as removal after the worktree moved back to main
Notes
- The application version is now 0.15.2.
- The fyllo-spawn MCP server makes its first stable-app release at 0.1.1. It exposes four HTTP-only tools; Agents without HTTP MCP support and Native-mode Sessions do not receive this server.
- The fyllo-specs MCP server is now 0.11.0, adding archive-metadata persistence and a partial-success recovery state. Tool names and inputs remain compatible, while callers that inspect failed results must accept the new archive-metadata-update recovery kind.
- The fyllo-cortex MCP server remains at 0.7.0; that server did not change in this release range.
- Compatibi

This release improves Session configuration and long-conversation navigation in Chat, and fixes Plan creation in multi-root Workspaces. The configuration entry stays compact as Agents expose more options, while the prompt timeline keeps the complete history accessible at a fixed visual density.
Added
- The Chat prompt timeline can preview up to five nearby prompts and pin a complete prompt list. Dragging, scrolling the wheel, clicking, and keyboard controls can navigate the full history, while the pinned list scrolls independently.
Changed
- The ChatPrompt footer now collects Agent-provided non-mode Session configuration in one menu. The trigger prioritizes a model and thought-level summary, select options use submenus, and boolean options can be toggled directly as top-level checkboxes.
- The prompt timeline shows one guide for each of 2–10 prompts, then stays at 10 guides for longer conversations. A separate teal thumb tracks the current reading position without increasing the timeline height as the conversation grows.
Fixed
- Fixed fyllo-specs create-plan failing in multi-root Workspaces because it incorrectly required a unique Folder owner. Plans remain isolated by Workspace and Session, while Proposal ownership and validation are unchanged.
Notes
- The application version is now 0.15.1.
- The fyllo-specs MCP server is now 0.10.1, fixing create-plan in multi-root Workspaces without changing tool inputs, outputs, or the session-scoped Plan semantics.
- The fyllo-cortex MCP server remains at 0.7.0; this release does not modify that server.

FylloCode now supports Workspaces containing multiple Projects. Launcher, Chat, Overview, Specs, Guidelines, Proposal, Task, Integration, and bundled MCP server contexts use the Workspace scope. Startup and shutdown lifecycle handling is tighter, and Projects without Git history retain their governance information.
Added
- Workspace management now supports up to 16 Projects, a primary Project, missing or degraded members, directory relocation, recycle-bin deletion, restore, permanent cleanup, and recent switching
- Multi-root ACP Sessions now pass additional directories to capable Agents, keep a fixed Workspace snapshot, show the active scope in Chat, and cover member Projects and their worktrees for local files and attachments
- Specs, Guidelines, Proposal, and Overview browsers now aggregate results across Workspace Projects and filter or mark ownership by Project, status, and governance capability
Changed
- Workspace and Folder now use stable identity models. Upgrade migration settles and retires verified legacy Project storage; data with unverified ownership is not deleted blindly, and a failed settlement blocks normal runtime and retries on the next launch
- Proposals are now repository-owned: { folderId, changeId } forms a ProposalRef, and create, apply, and archive always resolve to the owning Project's fixed target so same-named changes in different Projects cannot be mixed
- Bundled MCP servers are authorized by the active Workspace activation, with one Workspace v2 context model for HTTP and stdio. Callers no longer control Proposal target paths or rely on legacy Project environment variables, request headers, or working-directory fallbacks
- Startup is organized into startup shell, required gate, normal runtime, and background phases. ACP/MCP warmup moves to the background, shutdown is phased and time-bounded, and single-instance startup handoff is enforced
- Tasks can bind Workspace members through targetFolderIds, while Integration resources use explicit Project bindings. Removed members remain identifiable as stale soft references instead of being treated as current resources
- Project / Workspace terminology and icon hierarchy are now consistent, and Project scope moves into a Chat header popover to reduce context ambiguity in the message area
Fixed
- Fixed Overview clearing Specs, Guidelines, and Proposal governance counts for Projects without Git history. These Projects now show only Git evolution as empty; real Git errors still report partial failure
- Fixed MCP grants being revoked too early on normal completion or cancellation, and removed the fixed one-hour expiry that could interrupt long-running ACP Sessions; grants now follow the actual activation lifetime
- Fixed ACP binary-download handling for stream interruption, idle, and timeout cases so downloads do not wait indefinitely or leave incomplete results
Notes
- The application version is now 0.15.0.
- The fyllo-specs MCP server is now 0.10.0. This is a breaking contract update: Proposal operations use folderId in multi-root Workspaces, create-proposal uses worktreeMode, and caller-controlled target paths and legacy Project-context fallbacks are removed.
- The fyllo-cortex MCP server is now 0.7.0. This is a breaking contract update: knowledge and lineage use Workspace v2, repository evidence identifies ownership with folderId, and legacy Project paths, headers, environment variables, and cwd fallbacks are removed.
- The first launch may run the legacy Project-storage settlement migration. A failed migration preserves data and retries on a later launch; orphaned data whose provenance cannot be confirmed is not silently deleted.

This release improves reading, preview, and recovery in Chat. Absolute local file links can now be previewed safely inside the app, Markdown files gain source, rendered, and wrapping modes, and Fyllo Signal gives Agents a lightweight display channel that requires no confirmation. ACP Agent connections are prewarmed in the background and confirmed session configuration is restored after restart or reconnection; bundled MCP servers also move to a reusable application-level HTTP host while retaining stdio fallback.
Added
- All shared MarkStream hosts can now preview absolute local text-file links. Files under the project root or a registered worktree open directly; files outside trusted roots require either one-time access or trust for the current window before content is read. Preview accepts regular UTF-8 files up to 5 MiB and supports :line[:column] locations.
- Local Markdown previews now offer Source / Preview and Content Overflow / Wrap Lines controls. Preview uses MarkStream rendering, Source remains the default, and display choices affect only the current Slideover without modifying the file or persisting a setting.
- Added the passive Fyllo Signal display protocol. The initial show.time type renders the current time as a non-interactive pill without creating a Fyllo Action, entering the session event rail, or producing durable side effects.
- The Pinned Sessions and Recent Sessions groups in Chat can now be collapsed independently. Expanded groups share the remaining height and retain their own scroll positions.
Changed
- After launch, FylloCode now prewarms installed and valid custom ACP Agent connections with application-level concurrency limits. Installation, upgrade, and custom-Agent saves also schedule incremental warmup, and Chat reuses the same in-flight or ready connection.
- The ACP capability cache now retains complete authentication, prompt, MCP, and session capability snapshots while remaining compatible with older prompt-only cache files and preserving current attachment and prompt-capability behavior.
- fyllo-specs and fyllo-cortex now use an application-level shared HTTP host. HTTP-capable Agents reuse a stable loopback proxy, application bearer token, and request-scoped project/session context; Agents without HTTP support, or unavailable backends, continue through stdio.
- Fyllo Action and Fyllo Signal now share MarkStream rules for top-level standalone blocks, streaming closure, and exact literal-source preservation while keeping separate schemas, state, and rendering contracts.
Fixed
- Fixed confirmed session options such as model, mode, and thought level being replaced by Agent defaults after app restart or Agent reconnection. Compatible values are restored before the first resumed prompt, while incompatible options fall back to the Agent's current schema.
- Fixed Chat prompt-timeline container sizing, scroll targeting, and summary-popover details, and added syntax-safe Mermaid guidance for flowchart and state-diagram labels to reduce unrenderable Agent output.
- Fixed the Chat message area not filling its available height in some layouts.
Notes
- The application version is now 0.14.4.
- The fyllo-specs MCP server is now 0.9.0, adding HTTP transport, request-scoped context, and Mermaid guidance. Tool names, inputs, outputs, storage behavior, and stdio transport remain compatible.
- The fyllo-cortex MCP server is now 0.6.0, adding HTTP transport and request-scoped context. Tool names, modes, inputs, outputs, storage behavior, and stdio transport remain compatible.
- Older ACP capability caches are read through the compatibility path and are gradually rewritten in the new format after Agents initialize successfully; no manual migration is required.
- Trust in this window for files outside the project is kept only in Renderer Window memory. Closing the window or restarting the app requires confirmation again.

This release improves readability in long Chat sessions and while Agents are working. Chat can now pin important sessions, streaming assistant messages show a runtime indicator, and consecutive Thinking / Tool activity is grouped into expandable Activity groups. Claude Code subagent calls also get a dedicated inspector for parent-child tool relationships, runtime statistics, and final responses, while dependency pinning and release workflow guidance reduce upgrade and release risk.
Added
- Chat sessions can now be pinned and unpinned; the pinned state is persisted with project session metadata, the sidebar shows Pinned Sessions and Recent Sessions groups, and the pinned group is height-limited so recent sessions remain visible
- Streaming assistant messages now show a message-level runtime indicator with a 4×4 dot matrix animation, generic status text, and natural elapsed-time units; the state exists only in renderer runtime and is not stored in historical messages
- Added a Claude Code subagent call inspector: parent Agent tools render as standalone cards, and details show prompt, status, model, tokens, duration, tool statistics, child tool activity, and final response
- Added OpenSpec capabilities for assistant-stream-indicator, pinned-sessions, subagent-call-inspector, assistant-activity-display, and chat-prompt-timeline to capture this release's Chat observability and navigation contracts
Changed
- Chat prompt timeline now uses a compact line index with continuous nearest-prompt hit testing, drag-to-locate, one summary popover, keyboard navigation, and more stable reading-position synchronization
- Consecutive Thinking and normal tool calls in assistant messages are grouped into collapsible Activity groups; tool details use separate Input and Output sections and show the complete final output returned by Codex MCP calls
- The ACP event mapper is split into an Agent-neutral baseline, Claude / Codex adapters, a tool-call mapper, and update normalizers, preserving multi-Agent mapping boundaries while improving Claude Code and Codex session update compatibility
- The default Settings entry now opens /settings/preferences, and the Preferences and About pages are tightened around preference and release-update information
- Dependencies were updated to the current locked set, with markstream-vue 1.0.5 and stream-monaco 0.0.46 explicitly pinned together with compatibility notes for future upgrades
- references/ is reorganized into designs/ and third-party/, with added research and designs for ACP subagents, the Claude MCP initialization race, built-in MCP HTTP, and bundled MCP work
- The repository release skill now has tighter versioning, documentation-audit, release-note timing, and MCP server version decision rules
Fixed
- Fixed a Claude Code MCP initialization race by waiting for MCP startup before treating the session as ready, reducing early tool-unavailable failures
- Fixed Claude Code and Codex ACP session update mapping details so session titles, tool names, MCP call titles, and subagent output remain more stable while streaming
- Fixed prompt timeline summary popovers potentially stealing focus, reopening immediately, or shifting the summary window during hover, click, and focus transitions
- Fixed Chat session item width, config dropdown hover behavior, confirmation dialogs, and local layout/state details in lineage, task, and settings pages
- Removed redundant dynamic imports from the main process so runtime dependency paths stay direct
Notes
- The application version is now 0.14.3.
- fyllo-specs MCP server is now 0.8.2, containing only an internal archive outcome parsing type normalization with no changes to tool names, inputs, outputs, instructions, or archive behavior.
- fyllo-cortex MCP server remains at 0.5.0; that server did not change in this release range.
- Pinned sessions add an optional isPinned field to existing session metadata. Historical sessions without the field are read as unpinned and require no manu

This release adds a project-level Work Lineage browser so tasks, Chat sessions, Plans, Proposals, and Commits can be reviewed by Session on one page. Settings now uses stable child routes with consistent Service Connections terminology, while confirmation actions remain visible when a dialog contains a long description.
Added
- Added /lineage, which lists every project lineage subject by most recent update, supports All, Active, Archived, and Unlinked filters, and shows the Plan, Proposal, and Commit path grouped by Session
- Work Lineage details reuse existing entry points to open Chat sessions and Proposals, go to Task Board, and copy full Commit hashes; missing Session, Plan, or Proposal metadata keeps its stable ID without blocking other subjects
- Added a Work Lineage entry to the Project Overview governance health grid, showing the total project subject count and opening the complete lineage browser
- Added a bilingual durable knowledge design article covering the admission boundary for retained knowledge, the two-stage knowledge.flag and capture mechanism, and the roles of knowledge, guidelines, and lineage
Changed
- Settings now uses independent /settings/acp-agents, /settings/connections, /settings/preferences, and /settings/about child routes inside one shared layout; /settings remains the stable entry and opens ACP Agents by default
- The Settings sidebar now uses the fixed Preferences, Agents, Service Connections, and About order; the former Integration Providers label is now Service Connections, and project integrations use the focus parameter to locate a provider that needs configuration
- Repository Agent release support is consolidated into the prepare-release skill, which covers release-range auditing, bilingual documentation, changelogs, version synchronization, release notes, validation, and commit/tag/push/publish approval checkpoints; contributor guides now document the maintainer flow
- Chinese and English documentation now includes Work Lineage and Settings product references, with matching updates to Overview, lineage, ACP Agents, and engineering integrations
Fixed
- Fixed confirmation dialog actions scrolling out of view when the description is long; the description now scrolls independently while confirm and cancel actions remain visible
- Fixed ACP session_info_update overriding the Chat session title established by FylloCode; the mapper now ignores this upstream update so the existing session title remains stable
Notes
- The application version is now 0.14.2.
- The fyllo-specs MCP server remains at 0.8.1, and the fyllo-cortex MCP server remains at 0.5.0; neither server changed in this release range.
- The lineage browser is a read-only projection of existing local lineage, Session, Plan, and Proposal data. It does not change storage formats, and existing projects require no migration.
- Compatibility: /settings?tab=integration-providers|preferences|about no longer selects a Settings section and is not redirected for compatibility. Use /settings/connections, /settings/preferences, or /settings/about instead.

This release lets FylloCode keep multiple projects open in independent windows and completes the project-level durable knowledge path from discovery and capture through review, browsing, and cleanup. Fyllo Action persistence, execution idempotency, and Markdown recognition are hardened throughout, while the underlying cross-process structure moves to a domain-first architecture with clearer ownership boundaries for future capabilities.
Added
- One-project-per-window behavior and a project-free launcher: reopening a project focuses its existing window, opening another project does not replace the current project context, and launcher/project window bounds and maximized state are persisted independently
- Project-level durable knowledge workflow: agents can mark valuable findings with knowledge.flag, users can trigger batched capture, and knowledge.review opens the app-data knowledge document for review and editing
- New fyllo-cortex knowledge tool with capture, update, retire, and audit modes, plus file, package, and URL anchor checks that classify entries as active, suspect, or unknown
- Overview Knowledge summary and a dedicated /knowledge browser for grouped project, reference, and feedback entries, full Markdown reading, status and scan-error visibility, and confirmation-protected single-entry deletion
- Persisted Fyllo Action ready state, authoritative registration and command-based transitions, plus per-session attention badges so unresolved Actions remain visible after an app restart
- .nvmrc and a worktree environment preparation script that align the Node version and validate or install dependencies from the lockfile
Changed
- Cross-process and module structure now follows six domains—platform, workspace, session, proposal, insight, and automation: preload APIs use window.api.<domain>.<area>, IPC channels use <domain>:<area>:<action>, and lint rules enforce main-service, renderer-store, and feature dependency direction
- Fyllo Action shared contracts, main services, and renderer code are split into explicit layers; the main process now validates registration, transitions, and side-effect idempotency so task creation and batched knowledge-flag handling do not repeat business effects during state-sync retries
- Inline Fyllo Action rendering, EventRail projection, and action identity now share one source analyzer; only complete tags in standalone top-level Markdown blocks are executable, while inline code, fenced code, lists, blockquotes, and explanatory examples stay literal Markdown
- Multi-window runtimes isolate Chat probes, Proposal status watchers, and stream cancellation by project, while app-level ACP agent events fan out to every active window
- Renderer feature boundaries are enforced by generic ESLint rules, with expanded project guidance for architecture, comments, testing, and worktree environment setup
- fyllo-specs archive-change now requires generated capability specs to receive a substantive ## Purpose before an archive can be reported as complete
Fixed
- Fixed unresolved Fyllo Actions disappearing after restart, invalid transitions overwriting authoritative state, and retries potentially creating durable business objects more than once
- Fixed Action tags in inline code, code examples, lists, blockquotes, normal prose, or incomplete streaming fragments being misrecognized and causing swallowed text, incorrect registration, or disagreement between Inline and EventRail state
- Fixed matching sessionId, changeId, runId, or agent keys in concurrent projects potentially overwriting runtime state, leaking events, or cancelling work in another project
- Fixed knowledge review edits potentially being lost after autosave rejection or component unmount, and malformed knowledge files being hidden instead of surfaced explicitly
Notes
- The application version is now 0.14.1.
- fyllo-cortex MCP server is now 0.5.0, adding the durable knowledge tool and status-audit workflow.
- fyllo-specs MCP server is now 0.8.1, addi

This stable release consolidates the 0.14 beta cycle around session-scoped planning, project guideline governance, and clearer project governance views. Chat now has a more explicit split between direct implementation, Plan, and Proposal flows, while Overview, Proposal, Task, and the new Guidelines browser form a fuller operating surface for project governance. The bundled MCP servers are updated as well: fyllo-specs now handles linked-worktree exploration and archive guidance more accurately, and fyllo-cortex focuses its guidelines tool on maintenance workflows.
Added
- Session-scoped Plan workflow: agents can create lightweight plans, users can review, edit, save, and approve them in-app, approvals are recorded in lineage, and plan.create Fyllo actions connect them back to the current Chat session
- Read-only /guidelines project guidelines browser, reachable from the Overview Guidelines stat card, showing recursive guidelines/**/*.md entries, frontmatter metadata, document bodies, empty states, and error states
- Chat user prompt timeline, message copy actions, sent-time display, and collapsible session sidebar for more stable navigation and reading in long conversations
- Task board entries for linked Chat sessions, allowing users to inspect and reopen conversations related to a task; local tasks also gain a clearer close-task card action
- Unified linked-worktree indicators across Proposal, Overview, and Chat EventRail, with the related worktree path shown on hover or focus
- New OpenSpec capabilities for project-health, guidelines-browser, local-task-actions, task-linked-conversations, proposal-browser, fyllo-specs-explore, and related governance/workflow contracts introduced during the release
Changed
- Chat system reminders now use a three-lane decision model: direct implementation, Plan, and Proposal. Chat and Apply stages also inject a project guidelines/**/*.md index so agents spend less effort rediscovering repository conventions before making changes
- Overview now uses a clearer dynamic/static two-area structure, making active proposals, recent lineage, governance health, spec growth, and guideline evolution easier to scan
- /proposal is simplified into a complete proposal-list entry point, removing duplicate stats, status tabs, and local filtering while keeping the detail Slideover
- Local task actions now distinguish routine closing from permanent deletion: task cards close open tasks, and deletion lives inside the task detail edit dialog
- fyllo-specs instructions for create-plan, create-proposal, apply-change, and archive-change were tightened to report progress in the user's language, reread approved plans, and write concrete guideline-maintenance tasks
- fyllo-specs explore now discovers active changes in both the main workspace and registered linked worktrees, returning workspace metadata and non-fatal warnings in state
- fyllo-specs create-proposal now writes an accurate ISO created timestamp for new OpenSpec changes; archive-change guidance now emphasizes the proposal's delivered work instead of archive mechanics in commit subjects
- fyllo-cortex guidelines tool changed from read/write to three maintenance modes: init, create, and update, returning scenario-specific <tool_instruction> content and current <state>
- FylloCode's own guidelines, OpenSpec baseline, README, and documentation site were refreshed for Overview, Plan/SDD workflows, Loop Engineering, and MCP server references
Fixed
- Fixed Chat EventRail proposal state not always refreshing after Proposal details close
- Fixed Proposal detail headers failing to distinguish ready-to-archive, archiving, and base states, and fixed stale task counts, statuses, or dates after reopening details
- Fixed Proposal workflow menus escaping the Slideover and Proposal overlays stacking below the task origin banner
- Fixed Proposal archive actions appearing available when run metadata belongs to another proposal or an archive operation is already in progress
- Fi

This patch release improves how project governance artifacts are read and traced inside the app. Overview can now drill into a read-only capability specs browser, Proposal details open as an in-context Slideover, and the new Specs tab shows how a proposal changes capability contracts. Chat also reduces tool-call noise, makes session title actions more consistent, and restores proposal associations after app restarts.
Added
- Read-only /specs capability specs browser, reachable from the Overview Capability Specs stat card, showing Purpose, Requirements, Scenarios, source path, update time, and counts from openspec/specs/*/spec.md
- Requirement quick navigation and Scenario timeline rendering in specs details, while continuing to use the shared Markdown renderer for body content
- Specs tab in Proposal details, showing capability deltas from specs/<capability>/spec.md with added, modified, removed, and renamed badges
- Controlled specs browser and proposal specs delta IPC, preload APIs, renderer stores, and shared DTOs for the read-only specs and proposal delta surfaces
- Expandable tool groups for consecutive assistant tool calls in Chat, with summaries and icons based on toolMetadata.toolKind for read, write, edit, search, and execute actions
- Newly generated assistant tool parts now preserve ACP tool-kind metadata; older messages without that metadata still collapse and fall back to a generic tool-run summary
Changed
- Proposal details now open in a right-side Slideover instead of navigating to a standalone route, preserving context from the proposal list, Overview active changes, and Chat EventRail
- Proposal detail Slideover keeps Proposal/Design/Tasks reading, implementation start, archive, run history, and applying-run recovery, and switches to the archived proposal id after archive
- Proposal list routing is consolidated into the top-level /proposal page, removing the previous shell page used only for nested detail routes
- Chat session item menu copy changed from rename to title editing, with title edits handled inline inside the session item
- Chat session deletion now uses the app confirmation dialog instead of a native browser confirmation prompt
- Chat session item overflow buttons no longer reserve permanent title space, so normal browsing shows longer session titles
- Overview's Capability Specs stat card is now clickable; Guidelines and Lineage Coverage stats remain display-only
- Documentation site adds the bilingual "Using Plan and SDD to Triage Agent Workflows" blog post, Google site verification, and gtag configuration
Fixed
- Fixed historical proposals not being backfilled into Chat EventRail from lineage after restarting or reopening a session
- Fixed archived proposals failing to match lineage change ids when archive directory names include a date prefix, causing the session proposal panel to disappear
- Fixed archived backfilled proposals still starting proposal status watches; only non-terminal proposals are watched now
- Fixed several Chat display details around reasoning content, tool calls, and normal text interleaving, and preserved Fyllo action part indexes after consecutive tool-call grouping
Notes
- The standalone /proposal/:id detail route has been removed. Open Proposal detail Slideover from the /proposal list, Overview active changes, or Chat EventRail detail entry points.

This patch release continues turning Chat into the operating surface for project governance. The session event rail can now show proposals linked to the current session and update as OpenSpec status changes are detected. Users can also start implementation, open details, or archive completed proposals from Chat. The documentation site now has a bilingual structure, blog entry points, and sitemap support, and the project license has moved to MIT to lower the barrier for external use and contributions.
Added
- Chat session event rail now includes a Session Proposals panel with linked proposals, status badges, and detail entry points for the current session
- Users can start draft proposal implementation from the Chat event rail by choosing a workflow, then archive the proposal once the apply run is complete
- Main process proposal status watching and proposal:statusChanged broadcasts, covering active and archive directory changes in the main worktree and .worktrees/*
- Pending Fyllo actions now appear in the Chat event rail, with event items that locate the original action card
- Chat session list now shows a linked-task indicator and hover popover with the task source and lineage snapshot title
- Documentation site now has an English locale, blog index pages, ACP agent layer and lineage design posts, and sitemap configuration
- Shared UiSurface component and renderer UI design guidelines for consistent cards, page hierarchy, color usage, and copywriting
Changed
- Unified the Chat plan panel and session proposal panel headers, collapse behavior, spacing, and Chinese titles
- Improved Chat main-area resizing when the event rail is visible so the message column, error block, and prompt stay aligned
- Activity Bar now uses an icon-first compact navigation with tooltips and consistent active and hover states
- App Header now uses a lighter window-frame style, with a pill-shaped project switcher aligned with macOS title-bar constraints
- Global tooltip behavior is configured through UApp, standardizing hover delay and keyboard focus behavior
- Project license changed from AGPL-3.0 to MIT, with matching updates in package.json, README, and contribution docs
- Upgraded @nuxt/ui to 4.9.0 and configured the Nuxt UI root for the updated .nuxt-ui override directory location
Fixed
- Fixed cases where a new proposal status push arrived before the proposal store was loaded and the Chat event rail could show only the raw change id
- Fixed layout issues where long change ids in Chat proposal cards could squeeze the status badge
- Fixed creating-state proposals showing unavailable action entry points
- Fixed newly task-bound sessions requiring a session-list reload before origin task information appeared

This patch release continues to tighten project governance and the Chat experience while improving ACP Agent extensibility and main-process stability. You can now register additional ACP Agents through a custom agent configuration file. The Chat execution plan panel has been merged into a session event rail, and Overview further unifies proposal navigation, archived commit clues, and active-change titles. Main-process architecture was also reorganized to make storage, process communication, and error handling more reliable.
Added
- Support custom ACP agents via custom-agents.json, enabling integration of third-party or internal agents
- Chat session event rail that incorporates the ACP execution plan panel into the session event timeline, keeping the input area clean and execution progress readable
- New lineage tool in the fyllo-cortex MCP server with trace-file mode for tracing requirement subjects and returning proposal paths
- Archive commit hashes are now persisted for requirement proposals and displayed in the Overview lineage view
- Custom agent editor moves the save button to the top for easier one-click saving on long forms
Changed
- Proposal navigation moved from a standalone page into Overview, reducing context switching across project workspace
- Chat now clears stale active session state when entering the page, preventing old state from interfering with new conversations
- Hide the Chat audio input button until the related capability is ready
- Renamed the fyllo-skills MCP server to fyllo-cortex to align with project docs and conceptual model
- Optimized Overview stats bar grid columns to preserve information density in narrower windows
- Unified ACP stream parsing through a shared driver, reducing duplicated mapping across main, preload, and renderer layers
- Normalized agent error construction onto ipcError, with agent error codes maintained by a single event-mapping function
- Relocated IO-bound pseudo-domain modules into the infra layer and routed agent-service broadcasts through an event bus, aligning the main-process layering with the id factory spec
Fixed
- Corrected inconsistent proposalStatus derivation between overview and lineage
- Guarded ACP binary archive extraction against zip-slip path traversal
- Restricted external navigation to http/https schemes to prevent unintended protocol jumps
- Fixed main-process infra continuing to broadcast to closed windows and failing to cancel restart timers on dispose
- Used atomic synchronous writes for integration and window-state stores to prevent data corruption
- Hardened storage parsing, startup flow, and log redaction against malformed input and log leakage
- Fixed active change title formatting in Overview

This release turns FylloCode into a more traceable project workspace. The new Overview page surfaces project governance, active changes, recent threads, and lineage-backed metrics as the default project entry. Chat, Task, and Proposal are now connected through a persisted lineage model, while Chat can render confirmed Fyllo actions from agent output. The release also adds the public documentation site, restores parallel chat streaming, and improves ACP tool-call compatibility across agents.
Added
- Project Overview page backed by real main-process data, combining OpenSpec counts, guideline activity, git trends, active changes, recent lineage subjects, and governance metrics in one project landing view
- Project lineage model and storage for tracing a requirement subject across tasks, chat sessions, and proposals, including lineage IPC, task-origin session links, proposal links from fyllo-specs create-proposal, and recent-thread projection for Overview
- Origin task banner in Chat sessions started from a task, so users can see the task source even after returning to the conversation later
- Chat <fyllo-action> rendering and persistence, starting with a confirmed task.create action that lets agents propose a local task from structured assistant output while FylloCode keeps validation and execution under user control
- Open-discussion task creation flow for direct Chat sessions that produce proposals, allowing unbound conversations to create and bind a local task into the same lineage subject
- VitePress documentation site with product guides, feature references, screenshots, ACP agent docs, fyllo-specs and fyllo-skills references, and docs build/preview scripts
- Codex session repair skill for recovering Codex CLI session JSONL files affected by encrypted-content parse failures
Changed
- Project entry now opens Overview first, making project governance and current work state the initial workspace surface
- Long user text messages in Chat now collapse by default with expand/collapse controls, improving scanability for pasted logs, specs, and long prompts
- ACP stream event contracts were unified across main, preload, and renderer layers, reducing duplicated mapping and preserving tool-call fields such as input, content, diff, locations, and terminal metadata more consistently
- Chat system reminders now include Fyllo action contracts and lineage context, including task titles for task-bound sessions while still avoiding full task-description injection
- Repository source layout moved under src/, tests moved into the top-level test/ mirror, and project guidelines, README, and contribution docs were refreshed for the new layout
- Contributor workflow now validates commit messages through the hook pipeline and broadens lint-staged coverage for ESM/CJS/TS/Vue files
- Runtime and development dependencies were refreshed, including ACP SDK, AI SDK, Nuxt UI, Vue tooling, VitePress, and related lockfile updates
Fixed
- Restored parallel Chat session streaming so switching sessions no longer drops chunks, status, title updates, or usage updates from other running sessions
- Fixed Chat MessagePort handoff for concurrent streams by correlating each stream with its own streamId
- Fixed ACP agent runtime spawning so npx, uvx, and binary distributions now honor registry-provided startup args and env
- Fixed Chat scroll offset issues caused by content-visibility on message rendering
- Improved tool-call card compatibility for agents that send updates before start events, include input or diff content at different phases, or report completed calls with error output
- Fixed fyllo-specs shared-type dependency resolution after the source-layout migration so lint and type-aware checks can cover the bundled server correctly
Notes
- Local task and session metadata now carries additional lineage and action-state fields. Existing data remains readable; no manual migration is required.

This patch release fixes an urgent codex-acp permission request handling issue. When allow_always was selected automatically, codex-acp only matched requests against already-approved command prefixes, so unapproved commands returned user abort and could not run. The app now selects allow_once so the current permission request can proceed as a one-time approval.
Fixed
- Fixed ACP Agent permission request auto-handling selecting allow_always, which triggered codex-acp's approved-prefix matching limit and caused unapproved commands to return user abort instead of running

This release focuses on tightening the Chat experience, exposing session execution progress, and improving version visibility. The Settings About panel can now check GitHub official releases for newer versions directly from inside the app. Chat also gains an inline ACP execution plan panel, a loading skeleton for session history, and lower Markdown rendering overhead. In addition, Agent available commands returned during the probe stage are now captured and preserved on the session, and interrupted streaming replies now keep partially generated assistant content instead of dropping it outright.
Added
- GitHub official release version checking in the Settings About panel, with direct links to the matching release page when an update is available
- Inline ACP execution plan display in Chat sessions, showing current plan progress, item status, and priority above the prompt while a session is active
- Capture and persistence of Agent available command lists on chat sessions, providing a stable foundation for Slash Commands in both draft and regular sessions
- A loading skeleton for chat history while session messages are being fetched, reducing blank waiting states
- A shared confirmation dialog component and useConfirmDialog() composable to unify confirmation flows across the renderer
Changed
- Reduced Markdown rendering overhead in chat messages, improving UI performance for long messages and streaming output
- Unified confirmation dialog behavior across settings actions, task cards, Agent cards, and related flows to reduce interaction inconsistencies
- Slash Command data is now maintained and restored per session, making command state more consistent when switching conversations
Fixed
- Fixed a case where partially generated assistant content could be lost when a streaming reply was stopped by the user or interrupted by an error
- Fixed cases where interrupted replies were not persisted correctly, causing partial assistant messages to disappear after re-entering the session
- Fixed a case where mode category config options could still appear in Chat even though the corresponding permission gating is not yet ready to expose those controls safely

This patch release focuses on consolidating the local JSON persistence model and introducing a proper migration path. The app now runs data migrations automatically at startup, bringing persisted field naming and time formats into a single consistent shape instead of letting historical formats diverge over time. It also fixes a case where the config options bar could stay empty when starting a new draft session with the same Agent as before.
Added
- Local JSON data migration framework, running migrations in version order during app startup and providing a baseline mechanism so new installs do not replay historical migrations
- Initial persistence migration scripts to rename the historical config_options field to configOptions and convert timestamp fields in several caches and install records to ISO 8601 strings
Changed
- Unified field naming conventions across persisted JSON files around camelCase
- Unified time field formats in the ACP registry cache, status cache, and installed records to ISO 8601 strings, reducing cross-module read/write inconsistencies
- Reorganized migration script registration into a dedicated scripts directory with a static registry for easier future extension and maintenance
- Corrected runtime dependency classification by moving @nuxt/ui into production dependencies so the component library is not treated as development-only
Fixed
- Fixed a case where creating a new draft session with the same Agent as the previous draft would not re-trigger config option probing, leaving the config bar empty
- Fixed migration runner tests to improve regression coverage stability for the migration flow
- Fixed invalid warning output in the icon build script

This patch release continues the Chat configuration options experience, fixes empty-state styling, and tightens repository quality checks.
Added
- Chat session creation now carries draft probe config options, avoiding an empty config bar during first-session handoff
- Repository quality constraints spec, documenting type-aware lint and coverage threshold requirements
Changed
- Strengthened ESLint type-aware checks and expanded generated type file ignore rules
- Adjusted Vitest timeout settings to improve stability for git-subprocess tests in slower environments
Fixed
- Fixed the MoreAgentsTile styling in the Chat empty state
- Fixed a structured clone failure when passing reactive-proxy config options across the IPC boundary

This patch release focuses on bundle size, Windows compatibility, and local debugging. It tightens the desktop packaging scope, improves cross-platform child process startup paths, and adds a development entry point for diagnosing renderer errors.
Added
- DevTools launcher in the top navigation for quickly opening developer tools from inside the desktop app
- Renderer error and unhandled rejection reporting flow, passing frontend exceptions to main-process logs through the app IPC / preload API
Changed
- Packaging rules now use stricter allowlist and exclusion strategies, reducing source files, project metadata, tests, examples, documentation, sourcemaps, and other non-runtime content in installers
- Windows installer strategy was adjusted to reduce waiting cost during the installer loading phase
- External child process startup now consistently uses cross-spawn across the main process, built-in MCP runtime, and script entry points for more stable cross-platform command execution
- Added and archived the OpenSpec record for desktop packaging optimization, and updated the related constraints in the Build, CodeStyle, and MainProcess guidelines
Fixed
- Fixed Windows project path persistence where paths were not safely encoded and could fail to restore correctly for special paths
- Fixed inconsistent command resolution on some platforms when using Node's native child process spawn directly

This patch release adds a project health check entry point, improves ACP shutdown so it cleans up the entire process tree.
Added
- Project health check in the top navigation, with a one-click entry that guides the agent to evaluate static constraints, test constraints, and workflow constraints, then help close gaps through the standard proposal flow
Changed
- ACP process shutdown now performs bounded session close, stdin close, and process-tree termination so agent children and MCP grandchildren are cleaned up together
- Main-process disposable timeout was raised to 8 seconds to cover the ACP teardown sequence with headroom
Fixed
- Fixed an issue where MCP child processes spawned by ACP agents could remain orphaned after app quit