Skip to content

LakshmanTurlapati/FSB

v0.9.64 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Updates What changed in tests, Verification, and Compatibility across a mixed release.

Full changelog

Highlights

Closes a contract-consistency gap in the v0.9.62 Implicit Visual Session Contract (Codex P2 from PR #33). The navigate recovery branch for NO_OWNED_TAB now records the implicit visual-session lifecycle tick on success, matching the existing open_tab / switch_tab bootstrap paths. Before this fix, an agent's very first navigate call (no owned tab yet) would proceed without ever starting or refreshing the implicit visual session, even though visual_reason and client were required on the call.

This is a Chrome-extension-only patch. The MCP server ([email protected]) and the showcase site are unchanged from v0.9.63.

What's fixed

  • extension/ws/mcp-bridge-client.js — The navigate + NO_OWNED_TAB recovery branch now mirrors the open_tab / switch_tab post-dispatch pattern: await the dispatch, on success === true extract dispatched.tabId, then call _recordVisualSessionTickIfPresent and _clearVisualSessionIfFinal. Failed dispatches do not record a tick (no overlay for a failed action). Result: all three bootstrap entry points (open_tab, switch_tab, navigate-bootstrap) now uniformly start / refresh the implicit visual session.

What changed in tests

  • tests/mcp-visual-session-contract.test.js and tests/visual-session-schema-lock.test.js now fail loud with an actionable remediation message (npm --prefix mcp run build) when mcp/build/tools/manual.js is older than mcp/src/tools/manual.ts. A stale build had previously masquerade as a "contract hole" by running pre-Phase-255 compiled code that lacked validateVisualSessionFields.

Version bump

v0.9.63 was a showcase-only release; the Chrome extension stayed at 0.9.62. This release lifts the extension surfaces to 0.9.64:

  • package.json
  • extension/manifest.json (name + version)
  • showcase/angular/package.json (lockstep, no showcase code change)

Compatibility

  • No protocol or schema changes. Existing agents and MCP clients continue to work unmodified.
  • To see the fix, reload the FSB Chrome extension. No MCP server redeploy is required.

Verification

  • 79/79 mcp-visual-tick-lifecycle, 66/66 recovery-tools-bootstrap, 16/16 visual-session-agent-scoped, 30/30 agent-tab-resolver, 23/23 ownership-error-codes, 116/116 mcp-visual-session-contract, 314/314 visual-session-schema-lock.
  • Staleness guard verified: touched build mtime to 2020 → both tests bail with actionable error; after npm --prefix mcp run build both pass.
  • CI on the release commit: extension ✅, mcp ✅, showcase ✅.

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

Track LakshmanTurlapati/FSB

Get notified when new releases ship.

Sign up free

About LakshmanTurlapati/FSB

All releases →

Beta — feedback welcome: [email protected]