FrontAgent v2.1.1

FrontAgent v2.1.1 is a patch release after v2.1.0. It focuses on maintainability, security hardening, workflow reliability, and test coverage across the agent execution path, Filesense, hybrid RAG, memory persistence, runtime MCP handling, and the VS Code webview.

Highlights

• Decomposed the core agent and executor orchestration paths into smaller, focused helpers.
• Split Filesense engine responsibilities for helpers, indexing, notes, query, and schema orchestration.
• Extracted memory persistence writers and preload/recall helpers.
• Extracted semantic search orchestration from the hybrid RAG knowledge-base path.
• Hardened VS Code webview nonce generation and split webview renderers.
• Restored and hardened local GitNexus contract gates and worktree bootstrap checks.
• Expanded focused unit coverage across CLI, runtime MCP, executor, agent, context, Filesense, memory, RAG, and VS Code webview behavior.

Changed

• Executor orchestration: Tool-call handling, validation skip handling, progress enforcement, step feedback, and step trace recording now live in focused modules. This keeps execution behavior stable while reducing the size of the central executor implementation.
• Agent orchestration: Context gathering, facts update flushing, project prescan preparation, task execution setup, and execution callback wiring were extracted from the main FrontAgent flow.
• Context management: Fact serialization, facts merging, filesystem fact updates, and module dependency graph updates were split out of ContextManager.
• Planner phases: Planner phase helper logic was split into dedicated modules with additional tests.
• Filesense engine: Engine helper logic, index persistence, notes generation, query result handling, and schema orchestration were separated into focused modules.
• Memory store: Memory preload/recall behavior and persistence writer behavior were extracted from MemoryStore.
• Hybrid RAG: Semantic search orchestration was extracted from the knowledge-base implementation.
• Runtime MCP: MCP task invocation setup was split from the runtime MCP server handler path.
• VS Code extension: Webview body, script, style, and template rendering were decomposed into smaller helpers.
• Code quality subagent: Prompt policy logic was split into a dedicated helper.
• Tooling: The temporary GitNexus release-candidate patch was removed and the Biome schema version was aligned.

Fixed

• VS Code security: Hardened webview nonce generation.
• Filesense query: Preserved relative path semantics in query results.
• Filesense notes: Preserved notes schema path ownership.
• Workflow contracts: Restored the local GitNexus contract gate.
• Bootstrap checks: Resolved relative core worktree paths and guarded bootstrap against mismatched worktrees.

Tests

• Added focused CLI command router coverage.
• Added runtime MCP contract tests and schema assertion coverage.
• Added hybrid RAG knowledge-base coverage.
• Added executor tests for validation skipping, progress enforcement, step feedback, tool-call handling, and trace recording.
• Added agent tests for context gathering, facts flushing, project prescan preparation, execution callbacks, and task execution setup.
• Added ContextManager tests for fact serialization, facts merging, filesystem fact updates, and module dependency graph behavior.
• Added Filesense tests for engine helpers, indexing persistence writes, notes generation, query behavior, and schema orchestration.
• Added memory tests for preload/recall helpers and persistence writers.
• Added VS Code webview tests for body, script, style, and template renderer extraction.
• Cleaned Biome warnings in executor, shared utility, and LLM service tests.

Dependencies

• Updated production dependency lockfile entries from the Dependabot production dependency group.

Compatibility

• CLI package version: frontagent@2.1.1.
• VS Code extension version: frontagent@2.1.1.
• Node.js requirement: >=20.0.0.
• VS Code requirement: ^1.120.0.

FrontAgent v2.1.0

FrontAgent v2.1.0 is a minor release after v2.0.0. It adds Open Memory Gateway integration, publishes the OSS Harness workflow assets, expands test coverage across core runtime paths, and tightens CI, dependency, and maintainer workflow checks.

Highlights

• Added opt-in Open Memory Gateway integration for managed long-term memory.
• Added OSS Harness assets for contributions, PR review, GitNexus contracts, local hooks, and repository workflow checks.
• Expanded focused unit coverage for FrontAgent, Executor, PhaseRunner, ContextManager, LLM service, planner, memory, security, SDD workflow, mcp-filesense, and workflow rules.
• Upgraded the development and runtime dependency set, including Biome 2.x, TypeScript 6.x, Vitest 4.x, Playwright 1.60.x, Turbo 2.9.x, AI SDK, MCP SDK, and LangChain-related packages.
• Updated CI to run the full quality gate on Node 20 and Node 22 with one aggregate status check.
• Packaged the VS Code extension as frontagent-2.1.0.vsix.

Added

• Open Memory Gateway: FrontAgent can now use an opt-in Gateway adapter to write Gateway-compatible Markdown memories, keep draft and active memories separate, and recall active memories while retaining the existing .frontagent/memory fallback path.
• OSS Harness: Added contributor guidance, workflow documentation, GitNexus knowledge contracts, CODEOWNERS, issue templates, PR template, git hooks, and workflow rule tests.
• Local workflow scripts: Added agent:bootstrap, quality:predev, quality:precommit, quality:ci, quality:local, contract:*, and test:workflows.
• Dependency maintenance: Added .env.example and Dependabot configuration.

Changed

• Extracted PhaseRunner from Executor and step callback handling from FrontAgent.
• Split Skill Lab behavior benchmarking, trigger benchmarking, improvement, reporting, and scaffolding into focused modules.
• Introduced structured logging and migrated core debug output to shared logger utilities.
• Tightened source type safety with stricter noExplicitAny coverage.
• Raised the VS Code extension engine requirement to ^1.120.0.

Fixed

• Patched high-severity dependency vulnerabilities through dependency upgrades and pnpm overrides.
• Fixed Biome formatting and stricter typing failures introduced by merged test and Skill Lab changes.
• Unified Node 20 and Node 22 CI matrix results under a single aggregate CI status.

Test And CI

• Added broad focused unit coverage for core, memory, planner, security, executor, LLM, ContextManager, mcp-filesense, SDD, shared logger, and workflow rules.
• Added Contract Guard for PRs targeting develop.
• Added Repo Guard workflow support for PR, issue, and issue-comment review paths with fork and actor safeguards.
• Upgraded GitHub Actions dependencies to actions/checkout@v6, actions/setup-node@v6, and pnpm/action-setup@v6.

Compatibility

• CLI package version: frontagent@2.1.0.
• VS Code extension version: frontagent@2.1.0.
• Node.js requirement: >=20.0.0.
• VS Code requirement: ^1.120.0.

Highlights

• Architecture Refactoring: All large monolithic source files decomposed into focused, single-responsibility modules
• 565 Unit Tests: Coverage increased from near-zero across the monorepo
• Biome: Project-wide linter and formatter replacing ad-hoc ESLint configs
• Performance: Lazy-load ts-morph (~400ms cold-start savings), async file I/O in RAG modules, 2MB bundle reduction
• Type Safety: Eliminated all as any assertions across CLI, shared, and core packages

Breaking Changes

• Internal module paths changed due to refactoring. Public API from each package's index.ts remains unchanged.
• Minimum Node.js version is now 18+.

See CHANGELOG.md for full details.

Bug Fixes

• mcp-shell: Enforced the timeout parameter that was previously accepted but never used, preventing runaway commands from hanging indefinitely (default 60s with SIGTERM/SIGKILL escalation)
• mcp-shell: Added a 10MB output size cap to prevent OOM when commands produce excessive stdout/stderr
• shared: Fixed matchGlob to escape regex metacharacters (., (, ), [, ], +, {, }) before glob-to-regex conversion — previously src/utils.ts would incorrectly match src/utilsXts
• shared: Fixed deepMerge to skip undefined source values instead of overwriting existing target values
• mcp-file: Fixed isRegularFile and isDirectory to return false for non-existent paths instead of throwing ENOENT

Improvements

• shared: Extracted DEFAULT_LLM_TEMPERATURE (0.2) and DEFAULT_LLM_MAX_TOKENS (4096) as shared constants, fixing inconsistent model behavior between CLI (0.2) and runtime-node (0.7)

Install

npm install -g frontagent@1.0.9

Full Changelog: ceilf6/FrontAgent@v1.0.8...v1.0.9

规格驱动工作流引擎 (Spec-Driven Workflow Engine)

将 SDD 从静态约束层进化为规格驱动工作流引擎，融合 Spec Kit、Superpowers、OpenSpec 三个项目的核心理念。

新增模块

• Constitution — 项目原则层 (Tier 1)，解析 constitution.yaml 并生成最高优先级 LLM prompt
• Workflow Engine — 多阶段状态机：specify → clarify → plan → tasks → implement → verify
• Checklist Gate — 阶段转换质量门禁，内置 spec 完整性 / plan 质量 / 验证覆盖检查
• Artifacts — 文件系统持久化产物存储（.frontagent/specs/）
• Verification — 验证纪律模块：证据收集 + 覆盖率评估（"Evidence before claims, always"）
• Quality — 计划质量验证器（no-placeholders / 原子粒度 / 单一动作）+ 跨产物一致性分析

管线集成

• AgentConfig 新增 constitutionPath 和 sddWorkflow 配置
• Constitution prompt (Tier 1) 在 SDD prompt (Tier 2) 之前注入
• WorkflowIntegration 提供统一的工作流操作接口

向后兼容

所有新功能通过 sddWorkflow.enabled: true 可选启用，不启用时行为与 v1.0.7 完全一致。

Summary

• Unified the npm package and VS Code extension versions at 1.0.7.
• Updated the build flow so the root build generates the VS Code .vsix package alongside the npm CLI bundle.
• Published frontagent@1.0.7 to npm.

Artifacts

• npm package: frontagent@1.0.7
• VS Code package: frontagent-1.0.7.vsix

FrontAgent v1.0.3

This release catches the GitHub Release page up with the already published npm package frontagent@1.0.3.

Highlights

• Added a local stdio MCP Server entry point: fa mcp serve.
• Exposed six high-level FrontAgent MCP tools: frontagent_status, frontagent_run_task, frontagent_plan_task, frontagent_validate_sdd, frontagent_list_skills, and frontagent_init_sdd.
• Added MCP Sampling-first LLM backend behavior, with direct OpenAI/Anthropic configuration as fallback.
• Added a plan-only runtime path for MCP hosts: context collection, skills/RAG/SDD injection, and planning without executor-side writes.
• Kept external MCP hosts behind the FrontAgent safety boundary: raw file, shell, browser, and RAG tools are not exposed directly.
• Made MCP approval-required actions fail closed when no interactive approval UI is available.
• Improved VS Code extension runtime with sidebar chat flow, streaming output, real-time status updates, Activity Bar icon, settings/secrets/env configuration, and run log access.
• Fixed VS Code extension activation by bundling the extension entry as CommonJS and lazy-loading Playwright.
• Optimized query planning to avoid unnecessary expensive LLM planning when deterministic read/search steps are enough.

Release Artifacts

• npm package: frontagent@1.0.3
• npm tarball: frontagent-1.0.3.tgz
• VSIX artifact: frontagent-1.0.3.vsix

Checksums

55361681196e77182a3a0b086b4e61f327460459fc5cfb51f4e503cd703f4c30  frontagent-1.0.3.tgz
fa0c9bdd82fb9952399f23ab0800bdc9476fac4db4e65981ea0b72aaf1b8cd01  frontagent-1.0.3.vsix

Notes

• The attached npm tarball was downloaded from the npm registry for frontagent@1.0.3.
• The release tag v1.0.3 points to commit a53c4af.
• For MCP Host setup, start with fa mcp serve. If a GUI host cannot find fa or node, configure absolute paths for both commands.

FrontAgent v1.0.1

FrontAgent v1.0.1 aligns the npm CLI package, VS Code extension, and GitHub Release messaging around the new two-mode workflow: use fa from the terminal, or use the FrontAgent sidebar directly inside VS Code.

Highlights

• Added the first FrontAgent VS Code desktop extension.
• Added an Activity Bar task console for running FrontAgent tasks from VS Code.
• Added current-file, selected-text, and browser URL context entry points.
• Added VS Code approval cards for sensitive tool actions.
• Added phase/step progress, final result rendering, and run log access.
• Added SDD initialization and validation commands in VS Code.
• Added shared @frontagent/runtime-node APIs reused by the CLI and VS Code extension.
• Added cooperative cancellation support via AbortSignal.

Usage

Use FrontAgent from the terminal:

npm install -g frontagent@1.0.1
fa init
fa run "Create a user login page"

Use FrontAgent from VS Code:

1. Install the Marketplace extension ceilf6.frontagent.
2. Open a workspace folder.
3. Run FrontAgent: Configure and set your API key.
4. Open the FrontAgent Activity Bar view and run a task from the sidebar.

Release Artifacts

• npm package: frontagent@1.0.1
• VS Code extension: ceilf6.frontagent@1.0.1
• VSIX artifact: frontagent-1.0.1.vsix

Notes

• VS Code support is desktop-only in this release because FrontAgent depends on Node.js, local file-system access, shell execution, browser automation, and MCP packages.
• Only one active VS Code run is allowed per workspace in this first extension version.
• Cancel is cooperative and stops at phase/step boundaries.

Fixed

• Removed hard-coded CLI version reporting.
• fa -v, fa --version, fa version, and fa info now read the root frontagent package version.
• Added regression coverage so nested workspace package versions do not override the published package version.

Changed

• Synced GitHub main and v0.1.9 with the npm frontagent@0.1.9 release.
• Includes the latest security architecture updates from develop.

Added

• Added fa -v as a short alias for CLI version output.
• Added fa version as an explicit version command.

This release is published on npm as frontagent@0.1.8.