Skip to content

v0.9.91 MCP Clients as Providers with Session Replay and Google Sheets#108

Draft
LakshmanTurlapati wants to merge 584 commits into
mainfrom
automation
Draft

v0.9.91 MCP Clients as Providers with Session Replay and Google Sheets#108
LakshmanTurlapati wants to merge 584 commits into
mainfrom
automation

Conversation

@LakshmanTurlapati

Copy link
Copy Markdown
Collaborator

Summary

This draft delivers the v0.9.91 MCP Clients as Providers milestone. FSB can discover installed Claude Code, OpenCode, and Codex clients, show them as keyless providers, and delegate side panel tasks through the existing MCP bridge.

It also includes the refinements previously tracked in #105. Those changes add MCP session replay, explicit terminal task outcomes, signed in Google Sheets capabilities, stronger terminal summary and spreadsheet redaction, and aligned Extension 0.9.91 and fsb-mcp-server 0.11.0 release metadata.

Major changes

  1. Persist MCP client identity from installer intent, local inventory, and live initialize handshakes. Present one canonical Providers view without changing existing BYOK provider behavior.

  2. Add an authenticated reverse request channel, an adapter contract, supervised process lifecycle management, and provider implementations for Claude Code, OpenCode, and Codex.

  3. Add durable delegation consent, streamed tool activity, task cancellation, tab ownership recovery, daemon diagnostics, and native host wake support across Chrome service worker restarts.

  4. Add adapter compatibility data and drift checks. Keep task mode only and preserve existing MCP wire contracts.

  5. Record MCP sessions in local history with replayable steps and confirmed completion, partial, or failure outcomes. Sanitize signed URLs and recognized standalone credential shapes before terminal summaries enter history or Task Memory.

  6. Add bounded signed in Google Sheets read and write capabilities with session isolation, multiple tab safety, redaction, and fail closed recovery.

  7. Remove completed Phase 26 through Phase 56 workspaces while retaining milestone archives and repository history. Point catalog completeness and write activation evidence at canonical archived or stable repository references, and preserve required test ordering.

  8. Refresh generated crawler metadata for the v0.9.91 release.

Security and compatibility

  1. Existing MCP message values and tool schemas remain additive and byte stable.

  2. Agent processes use validated argument arrays, scrubbed environments, bounded process tree termination, explicit consent, loopback host checks, extension origin checks, and rotating shared secrets.

  3. Unsafe permission bypass flags remain forbidden by CI.

  4. Extension 0.9.91 requires Chrome 116 or newer. MCP server 0.11.0 must be upgraded with the extension for terminal task outcome support.

Validation

  1. Full npm test suite.

  2. Catalog coverage and delegation contract tests.

  3. MCP version parity and Google Sheets session tests.

  4. Terminal summary redaction and write activation evidence tests.

  5. Git whitespace and conflict marker checks.

  6. Mergeability check against the current main branch.

Review notes

This PR intentionally includes the changes from #105. PR 105 was already closed before this draft was created. This draft does not modify it.

This remains a draft because final live milestone UAT, including the Codex adapter scenarios, is still pending.

Lakshman added 30 commits July 17, 2026 01:55
- Pin silent boot probing and advisory presence caching
- Cover one-flight wake, closed response validation, timeout, cooldown, and late settlement
- Reject delegation, storage, secret, and browser authority in the helper
- Probe host presence silently with no native message or UI state
- Coalesce exact v1 wake requests behind a tagged timed promise
- Fail closed on malformed, mismatched, late, unavailable, and cooled-down responses
- Exercise exact non-offline bypass and optional intent validation
- Pin shared wake, attempt-scoped checking fanout, bridge wait, and one rerun
- Assert exact offline fallback with zero consent, start, session, storage, or tab mutation
- probe native host registration silently after bridge dependencies load

- wake only from authoritative agent_offline preflight and fan out bounded intent events

- wait for ordinary bridge readiness before one direct pure-preflight rerun
- add nativeMessaging as the sole manifest delta

- pin all remaining manifest bytes to the prior baseline

- scan extension sources for background-only native authority
- record closed probe, offline wake, bridge rerun, and permission evidence

- advance Phase 63 tracking to Plan 09

- mark NATIVE-02 complete without touching deferred live UAT
Lakshman added 30 commits July 22, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant