Big News: Socket raises $60M Series C at a $1B valuation to secure software supply chains for AI-driven development.Announcement
Sign In

frontagent

Package Overview
Dependencies
Maintainers
1
Versions
16
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

frontagent - npm Package Compare versions

Comparing version
0.1.10
to
1.0.1
+84
CHANGELOG.md
# Changelog
All notable changes to this project will be documented in this file.
## [Unreleased]
## [1.0.1] - 2026-04-30
### Added
- Added the first FrontAgent VS Code desktop extension with an Activity Bar task console.
- Added task input, current-file/selection context, browser URL context, run/cancel controls, phase and step progress, approval cards, and run log access in VS Code.
- Added SDD initialization and validation commands to the VS Code extension.
- Added shared `@frontagent/runtime-node` runtime APIs for CLI and VS Code execution.
- Added cooperative `AbortSignal` cancellation support across FrontAgent execution boundaries.
### Changed
- Updated the npm package metadata for the `1.0.1` release.
- Documented the two supported FrontAgent usage modes: CLI and VS Code extension.
- Refactored `fa run` to reuse the shared Node runtime while preserving the existing Ink terminal workflow.
## [0.1.8] - 2026-04-29
### Added
- Added `fa -v` as a short alias for CLI version output.
- Added `fa version` as an explicit version command.
## [0.1.7] - 2026-04-29
### Added
- Added a progressive exploration protocol so file-system changes are planned as observe-first workflows before writes.
- Added built-in FrontAgent identity context for query answers so identity and capability questions answer from stable agent facts.
### Changed
- Shortened the published CLI command from `frontagent` to `fa`.
- Simplified default `fa run` output to status, tool-call summary, and final answer while keeping verbose internals behind `--debug`.
### Fixed
- Fixed the ESM bundle bootstrap so `fa run` no longer crashes on packages that expect `__filename`.
- Normalized OpenAI-compatible base URLs that already include `/chat/completions`.
- Made query tasks report a clear failure when no final answer is generated instead of presenting tool-only fallback as success.
## [0.1.6] - 2026-03-22
### Added
- Added Weaviate-backed semantic vector storage for RAG while keeping BM25 local.
- Added RAG cache bundle export/import workflow for distributing prebuilt knowledge-base indexes.
- Added a retrieval-only LLM query rewrite step that rewrites user input into frontend-oriented search queries before RAG.
### Changed
- Clarified all RAG-facing terminology so remote RAG evidence is referred to as "knowledge base" instead of the current workspace repository.
- Updated English and Chinese documentation with Weaviate, query rewrite, and cache bundle usage examples.
### Fixed
- Prevented the planner from treating remote RAG hits as local workspace files during query tasks.
- Improved semantic index resilience for Weaviate-backed retrieval and related RAG execution flow.
## [0.1.5] - 2026-03-16
### Fixed
- Corrected npm publish metadata:
- `bin.frontagent` uses `dist/index.cjs` to avoid npm auto-removal during publish.
- `repository.url` normalized to `git+https://github.com/ceilf6/FrontAgent.git`.
- Added changelog tracking for release visibility.
## [0.1.4] - 2026-03-16
### Added
- Introduced an executor skills layer and extracted reusable execution logic into dedicated skills.
- Added planner skill registry APIs for runtime registration/introspection and custom planning extension.
- Added built-in repository-management phase injection skill for post-validation repository workflow steps.
### Changed
- Unified browser tool naming to `browser_*` in planning/execution paths.
- Added backward-compatible aliases in the CLI MCP web client for legacy browser tool names.
- Updated English and Chinese documentation with skill extension usage examples.
### Fixed
- Tightened planner snapshot typing with `ReadonlyMap` semantics to avoid accidental mutation in skills.
- Corrected `search_code` examples to use supported parameters (`filePattern`) instead of unsupported `directory`.
## [0.1.3] - 2026-03-14
### Released
- Previous stable release. See GitHub Release and tag history for details.
# 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:
```bash
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.
+18
-12
{
"name": "frontagent",
"version": "0.1.10",
"description": "Enterprise AI agent platform for frontend engineering with planning/execution architecture, SDD constraints, and MCP-controlled code generation",
"version": "1.0.1",
"description": "FrontAgent CLI and VS Code extension for frontend AI engineering with SDD constraints, MCP-controlled execution, and RAG planning",
"type": "module",

@@ -16,4 +16,16 @@ "bin": {

"README.md",
"CHANGELOG.md",
"docs/releases/**/*",
"LICENSE"
],
"scripts": {
"build": "turbo build && node build.mjs",
"bundle": "node build.mjs",
"dev": "turbo dev",
"lint": "turbo lint",
"typecheck": "turbo typecheck",
"test": "turbo test",
"clean": "turbo clean && rm -rf node_modules dist",
"prepublishOnly": "pnpm build"
},
"keywords": [

@@ -27,2 +39,4 @@ "ai-agent",

"cli",
"vscode",
"vscode-extension",
"developer-tools"

@@ -53,14 +67,6 @@ ],

},
"packageManager": "pnpm@9.0.0",
"engines": {
"node": ">=20.0.0"
},
"scripts": {
"build": "turbo build && node build.mjs",
"bundle": "node build.mjs",
"dev": "turbo dev",
"lint": "turbo lint",
"typecheck": "turbo typecheck",
"test": "turbo test",
"clean": "turbo clean && rm -rf node_modules dist"
}
}
}
+10
-1

@@ -37,4 +37,13 @@ # FrontAgent

## TL;DR
## Two Ways to Use FrontAgent
FrontAgent now supports both terminal-first and VS Code desktop workflows:
- **CLI**: use `fa init`, `fa run`, RAG commands, Skill Lab, and automation-friendly workflows directly from your terminal.
- **VS Code Extension**: use the FrontAgent sidebar task console to run tasks, attach the current file or selection, provide a browser URL, review phase/step progress, approve sensitive actions, initialize/validate SDD, and open run logs from inside VS Code.
Install the VS Code extension from the Marketplace by searching for `FrontAgent` or the extension id `ceilf6.frontagent`.
## CLI Quick Start
```bash

@@ -41,0 +50,0 @@ # 1. Install globally via npm

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display