This release adds 1 notable feature for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+14 more
Summary
AI summaryFixed cwd path-check so the open project is scored instead of defaulting to ~/Projects.
Full changelog
.FAF Context v2.3.1
Fixed — the cwd path-check. faf_score (and every no-path tool) now scores the project you have open, not ~/Projects.
Previously findBestWorkingDirectory() forced ~/Projects as a "universal default" above process.cwd(), so in Cursor / VS Code / any IDE it scored the wrong folder (a stale ~/Projects score). The caller's actual cwd now wins — prefer a real FAF project (cwd has project.faf), else a usable non-root cwd; ~/Projects is a fallback only when there's no workspace. Regression test: tests/wjttc-cwd-resolution.test.ts.
faf-cli, the scorer and the WASM kernel were never at fault — this was purely working-directory resolution.
Patch — inherits The Curated Edition. Curated core tools by default, full set via FAF_TOOLS=all.
Built on 100,000+ downloads across the FAF ecosystem.
FAF defines. MD instructs. AI codes.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Wolfe-Jam/faf-mcp
Universal persistent project context for Cursor, Windsurf, Cline, VS Code, and all MCP-compatible platforms (including Claude Desktop). IANA-registered format (application/vnd.faf+yaml). 17 native tools, AI-readiness scoring.
Beta — feedback welcome: [email protected]