diff --git a/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.installer.yaml b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.installer.yaml new file mode 100644 index 00000000000..cb1b2520254 --- /dev/null +++ b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.installer.yaml @@ -0,0 +1,18 @@ +# Created with YamlCreate.ps1 Dumplings Mod +# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.12.0.schema.json + +PackageIdentifier: Fioooooooo.FylloCode +PackageVersion: 0.15.5 +InstallerType: nullsoft +Scope: user +InstallerSwitches: + Upgrade: --updated +UpgradeBehavior: install +ProductCode: fb4850cb-f98d-5a6d-8287-16734ebbc07c +ReleaseDate: 2026-08-24 +Installers: +- Architecture: x64 + InstallerUrl: https://github.com/Fioooooooo/FylloCode/releases/download/v0.15.5/FylloCode-0.15.5-win-x64-setup.exe + InstallerSha256: CB4C8074DE71A6D651D169A3AD097496A5CE777E61ED0F8DAC735D5A95F318B6 +ManifestType: installer +ManifestVersion: 1.12.0 diff --git a/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.locale.en-US.yaml b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.locale.en-US.yaml new file mode 100644 index 00000000000..fa746a2df71 --- /dev/null +++ b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.locale.en-US.yaml @@ -0,0 +1,94 @@ +# Created with YamlCreate.ps1 Dumplings Mod +# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.12.0.schema.json + +PackageIdentifier: Fioooooooo.FylloCode +PackageVersion: 0.15.5 +PackageLocale: en-US +Publisher: Fio +PublisherUrl: https://github.com/Fioooooooo +PublisherSupportUrl: https://github.com/Fioooooooo/FylloCode/issues +PackageName: FylloCode +PackageUrl: https://github.com/Fioooooooo/FylloCode +License: AGPL-3.0 +LicenseUrl: https://github.com/Fioooooooo/FylloCode/blob/HEAD/LICENSE +ShortDescription: A desktop app that turns Coding Agents into reliable teammates — by splitting every change into Task → Proposal → Apply → Archive, with you reviewing the plan before any code is written. +Description: |- + In this new era, the work that really needs our attention is no longer repetitive coding, but higher-level business understanding and architecture design. The future workflow I have in mind is: understand the business → think through the architecture → write a Proposal → review the Proposal → let the Agent implement it automatically, then move on to the next Proposal. + That thinking led me to build FylloCode — a step from Vibe Coding toward Agentic Coding. + + How FylloCode Solves It + FylloCode enforces a structured workflow that separates thinking from doing: + ┌──────────┐ ┌────────────────┐ ┌───────────┐ ┌───────────┐ + │ Task │ ──→ │ Chat/Proposal │ ──→ │ Apply │ ──→ │ Archive │ + │ │ │ │ │ │ │ │ + │ What to │ │ Agent explores │ │ Agent │ │ Specs │ + │ work on │ │ codebase and │ │ implements│ │ updated, │ + │ │ │ writes a plan │ │ the plan │ │ change │ + │ │ │ │ │ │ │ recorded │ + │ │ │ ➜ YOU REVIEW │ │ │ │ │ + └──────────┘ └────────────────┘ └───────────┘ └───────────┘ + Task — Pick a task from your local list or synced from platforms like Yunxiao. One click sends it to Chat. + Chat / Proposal — The Agent explores your codebase, asks clarifying questions, and produces a structured proposal (what to change, which files, acceptance criteria). The Agent is prohibited from writing code in this stage. You review, edit, and approve the proposal before anything else happens. + Apply — A fresh Agent session implements the approved proposal task-by-task. It reads only the proposal artifacts — not the Chat history — so every decision must be captured in writing, not left in context-window memory. + Archive — Specs are updated, the change is recorded with full traceability. Your project's knowledge base grows with every shipped change. + Why Separating Thinking from Execution Matters + Most Coding Agents understand a task and write code in the same session. Any misunderstanding becomes code directly, and code is expensive to review. FylloCode physically separates understanding from execution. Misunderstandings can only become proposal text — and text is cheap to review. A 2-minute proposal review catches problems that would take 20 minutes to find in a diff. + + Features + + Agent Protocol (ACP) + FylloCode connects to any Coding Agent through ACP (Agent Client Protocol). Claude Code, Codex, or any ACP-compatible agent — one protocol, one interface, without juggling a pile of terminal windows. + There are currently 35 agents available in the ACP Registry, with support for parallel chats and parallel Proposal Apply runs. + + System Reminders + Each workflow stage injects a system reminder that constrains what the Agent can and cannot do. In Chat, the Agent is instructed to explore and propose, not code. In Apply, it follows the approved task list. This isn't a suggestion — it's a hard boundary enforced at session start. + + Task Panel + View and manage tasks from your local list or synced from external platforms. Tasks serve as the entry point to the entire workflow — select a task, start a Chat, and the Agent begins with full context. + + Integration with Development Platforms + Connect to platforms like Yunxiao (Alibaba Cloud DevOps) at the provider level — one authentication, multiple tools across task management, source code, and CI/CD. More platform integrations (GitHub, TAPD, Jira, etc.) are planned. + Task integrations use APIs instead of Agent Skills by design. API calls are fast and do not spend tokens, so tokens stay focused on the work that actually needs reasoning. + + Workflow Editor + Define and customize multi-stage workflows. Built-in templates get you started; edit the YAML to fit your team's process. + + OpenSpec-Driven Proposals + Proposals are structured artifacts — not chat messages. Each proposal contains a design document, spec changes, and a concrete task list with file paths and acceptance criteria. The built-in fyllo-specs MCP server manages the full lifecycle: explore → create-proposal → apply-change → archive-change. + + Streaming Rendering Engine + FylloCode uses markstream-vue as its streaming rendering engine. It is fast and smooth, with built-in integration for Monaco Editor, KaTeX, and Mermaid. While working on Proposals, it can render flowcharts and formatted specs in real time, making architecture flows and business logic easier to inspect. + Engineering Guardrails + FylloCode provides two layers of engineering guardrails: + - Soft constraints — Capture engineering conventions as Guidelines and continuously maintain them through the built-in fyllo-skills MCP server, without manual upkeep. + - Hard constraints — Agents may not always follow Guidelines perfectly, so FylloCode's health checks establish engineering-level enforcement through lint, test runners, git hooks, and CI. +Tags: +- agent +- agentic +- ai +- chatbot +- code +- coding +- large-language-model +- llm +- programming +ReleaseNotes: |- + 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. +ReleaseNotesUrl: https://github.com/Fioooooooo/FylloCode/blob/HEAD/CHANGELOG.en.md#0155---2026-08-24 +ManifestType: defaultLocale +ManifestVersion: 1.12.0 diff --git a/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.locale.zh-CN.yaml b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.locale.zh-CN.yaml new file mode 100644 index 00000000000..f79cdbfccab --- /dev/null +++ b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.locale.zh-CN.yaml @@ -0,0 +1,84 @@ +# Created with YamlCreate.ps1 Dumplings Mod +# yaml-language-server: $schema=https://aka.ms/winget-manifest.locale.1.12.0.schema.json + +PackageIdentifier: Fioooooooo.FylloCode +PackageVersion: 0.15.5 +PackageLocale: zh-CN +ShortDescription: 一款桌面应用,通过将每个更改拆分为任务 → 提案 → 应用 → 归档的流程,将编程智能体转变为可靠的团队成员,并在编写任何代码之前由您审查计划。 +Description: |- + 在这个新时代,真正需要我们处理的不再是重复性的编码工作,而是更高层面的业务理解和架构设计。我设想的未来工作方式是:接触业务 → 想清楚架构 → 写 Proposal → 审查 Proposal → Agent 自动编码落地,然后接着搞下一个 Proposal。 + 基于这些思考,我开发了 FylloCode——从 Vibe Coding 走向 Agentic Coding。 + + FylloCode 怎么解决 + FylloCode 用一套结构化的工作流,把 思考 和 执行 物理隔离: + ┌──────────┐ ┌────────────────┐ ┌───────────┐ ┌───────────┐ + │ 任务 │ ──→ │ 对话 / 提案 │ ──→ │ 执行 │ ──→ │ 归档 │ + │ │ │ │ │ │ │ │ + │ 做什么 │ │ Agent 探索代码 │ │ Agent 按 │ │ 规格更新 │ + │ │ │ 库,写出方案 │ │ 方案逐条 │ │ 变更留档 │ + │ │ │ │ │ 实现 │ │ │ + │ │ │ ➜ 你来审查 │ │ │ │ │ + └──────────┘ └────────────────┘ └───────────┘ └───────────┘ + 任务 — 从本地任务列表或云效等平台同步过来的工作项中选一个,一键发起对话创建提案。 + 对话 / 提案 — Agent 探索你的代码库,提出澄清问题,然后生成结构化的提案(改什么、改哪些文件、验收标准)。在这个阶段,Agent 被禁止写代码。你审查、修改、确认提案后,流程才会继续。 + 执行 — 一个全新的 Agent session 按提案逐条实现。它只读提案产物,看不到对话历史——所以所有决策必须写进提案,不能留在上下文窗口的记忆里,同时以这种方式将决策产物持久化留存。 + 归档 — 规格文档更新,变更完整归档。你的项目知识库随着每次交付不断增长。 + 为什么把思考和执行分开很重要 + 大多数 Coding Agent 在同一个 session 里理解任务并写代码。任何误解都会直接变成代码,而代码的审查成本很高。 FylloCode 把理解和执行物理隔离了。误解只能变成提案文字——文字的审查成本极低。花 2 分钟审一遍提案,能拦住你在 diff 里要花 20 分钟才能发现的问题。 + + 功能特性 + + Agent 协议(ACP) + FylloCode 通过 ACP(Agent Client Protocol)连接任意 Coding Agent。Claude Code、Codex 或任何 ACP 兼容的 Agent——一个协议,一个界面,不用再开一堆终端来回切换了。 + 目前 ACP Registry 中已有 35 款 Agent 可用,同时支持多聊天并行和多 Proposal 的 Apply 并行。 + + System Reminders + 每个工作流阶段会注入 system reminder,约束 Agent 能做和不能做的事。对话阶段,Agent 被指示去探索和提案,而不是写代码;执行阶段,它只按已批准的任务列表走。这不是建议——是在 session 启动时强制执行的硬边界。 + + 任务面板 + 查看和管理本地任务,或展示从外部平台同步的工作项。任务是整个工作流的入口——选中任务,发起对话,Agent 带着完整上下文开始工作。 + + 开发平台集成 + 以 Provider 为单位连接平台(如云效)——一次认证,任务管理、源码管理、CI/CD 等多个工具全部可用。更多平台集成(GitHub、TAPD、Jira 等)在路线图中。 + 任务集成走的是 API 而不是 Agent Skill——这是有意为之。API 调用速度快而且不消耗 Token,好钢要用在刀刃上。 + + 工作流编辑器 + 定义和自定义多阶段工作流。内置模板开箱即用,也可以编辑 YAML 适配你的团队流程。 + + OpenSpec 驱动的提案 + 提案是结构化的产物,不是聊天消息。每个提案包含设计文档、规格变更和具体的任务列表(文件路径、验收标准)。内置的 fyllo-specs MCP server 管理完整的生命周期:explore → create-proposal → apply-change → archive-change。 + + 流式渲染引擎 + FylloCode 采用 markstream-vue 作为流式渲染引擎,速度快、效果丝滑。内置集成了 Monaco Editor、KaTeX 和 Mermaid,在做 Proposal 时可以实时渲染出流程图和格式化的规格说明,架构流程、业务逻辑一目了然。 + 工程规范保障 + FylloCode 提供两个层面的规范保障: + - 软约束 — 把工程规范沉淀为 Guidelines,通过内置的 fyllo-skills MCP server 在工作流中自动持续维护,无需人工干预。 + - 硬约束 — Agent 不一定完全遵守 Guidelines,FylloCode 的健康检查会在工程层面建立硬约束(lint、test runner、git hooks、CI),从根上把质量卡住。 +Tags: +- 人工智能 +- 代码 +- 大语言模型 +- 智能体 +- 编程 +- 聊天机器人 +- 自主智能 +ReleaseNotes: |- + 本次发布让 Chat 更自然地接收附件,并补齐跨 Agent 委派时的目录和模型选择。ACP Agents 页面改用精选目录,安装过程覆盖更多跨平台归档格式,并在可用时校验下载摘要;工具活动也能准确呈现 ACP 1.3 新增的操作类型。 + 新增 + - Chat 输入区支持直接粘贴剪贴板图片,以及拖放图片和普通文件。文字与图片混合粘贴会保留文本,文本拖动继续使用原生行为;目录不会被递归读取,同批次中受支持的文件仍可加入草稿 + - 跨 Agent 委派可以在首次调用时显式选择父 Session 授权范围内的单个 Folder。省略 Folder 时仍继承完整 Workspace;创建后的 scope 固定不变,并在 spawned Session 详情中显示为 Workspace 或 Folder + - fyllo-spawn 的 prompt_to_agent 支持直接指定语义化 model 与 thought level,无需先运行探测任务。无法唯一匹配时会返回真实候选并保持原 Prompt 未发送,选择后可继续使用同一 spawned Session + 调整 + - ACP Agents 页面只显示 FylloCode 精选目录中的 registry Agent,不再合并或回退到官方 Registry。只存在于历史安装记录但已移出精选目录的 Agent 不再参与发现和连接预热,自定义 Agent 不受影响 + - FylloCode 管理的 Agent 安装支持 ZIP、TAR、TAR.GZ/TGZ 和 TAR.BZ2/TBZ2,无需系统解压命令。目录提供 SHA-256 时会在解压前校验;升级在 staging 目录完成后再提交,失败时保留已有安装与记录 + - Chat 工具活动新增 delete、move、think、fetch 和 switch mode 等 ACP 1.3 类型的图标与摘要语义;未知类型继续使用通用工具展示 + 修复 + - 修复 ACP 工具流式参数片段可能覆盖已有工具标题的问题;工具可以在执行期间保持稳定名称,并在 Agent 后续提供正式标题时正常更新 + 说明 + - 应用版本为 0.15.5。 + - fyllo-spawn MCP server 升级到 0.3.0,新增单 Folder scope、语义化 model / thought level 配置和可恢复的 configuration_required 结果;五个 tool、默认后台模式、owner 校验与 RPC protocol version 1 保持兼容。 + - fyllo-cortex MCP server 保持 0.7.0,fyllo-specs MCP server 保持 0.11.1;本次发布范围没有修改这两个 server。 + - Registry 记录未提供 SHA-256 时仍允许安装,但 FylloCode 不会把该安装表述为已验证。 +ReleaseNotesUrl: https://github.com/Fioooooooo/FylloCode/blob/HEAD/CHANGELOG.md#0155---2026-08-24 +ManifestType: locale +ManifestVersion: 1.12.0 diff --git a/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.yaml b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.yaml new file mode 100644 index 00000000000..7f2933a589d --- /dev/null +++ b/manifests/f/Fioooooooo/FylloCode/0.15.5/Fioooooooo.FylloCode.yaml @@ -0,0 +1,8 @@ +# Created with YamlCreate.ps1 Dumplings Mod +# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.12.0.schema.json + +PackageIdentifier: Fioooooooo.FylloCode +PackageVersion: 0.15.5 +DefaultLocale: en-US +ManifestType: version +ManifestVersion: 1.12.0