Skip to content

feat: browser-agent#159

Merged
ndthanhdev merged 1 commit into
mainfrom
feat/browser-agent-core-wrap
Jul 12, 2026
Merged

feat: browser-agent#159
ndthanhdev merged 1 commit into
mainfrom
feat/browser-agent-core-wrap

Conversation

@ndthanhdev

Copy link
Copy Markdown
Owner

Summary

  • Removes the LLM-provider settings UI and DrivenLlmProvider wiring from apps/m2/apps/m3; only apps/ext-wxt drives the browser agent today.
  • Adds a browser-agent boolean feature flag (packages/core-feature-flags) and wires minimal flag-reading plumbing into apps/ext-wxt/entrypoints/background.ts.
  • Adds per-app feature flag overrides (packages/driven-feature-flags) so browser-agent resolves to false on apps/m2/apps/m3 and stays at its manifest default (true) on apps/ext-wxt, without adding per-app targeting to the shared manifest.
  • Renames ExtensionBootstrapExtensionLifecycle (and ExtensionTabBootstrapExtensionTabLifecycle) to match the ServerLifecycle naming convention already used in packages/core-server; renames the extension-driving-bootstrap package to extension-driving-lifecycle.
  • Updates docs/architecture.md for the renames and current flag wiring.

Test plan

  • moon run m2:build passes
  • moon run m3:build passes
  • moon run server:build passes
  • moon run ext-wxt:build passes
  • moon check --all shows zero TypeScript errors (remaining failures are a pre-existing, unrelated Biome .wxt/.output exclusion gap)
  • Verified built bundles directly: apps/m2/apps/m3 embed "browser-agent": false; apps/ext-wxt keeps the manifest default (true)

🤖 Generated with Claude Code

…ionLifecycle

- Remove the LLM-provider settings UI and DrivenLlmProvider wiring from
  apps/m2 and apps/m3; only apps/ext-wxt drives the browser agent today.
- Add a `browser-agent` boolean feature flag (packages/core-feature-flags)
  and wire minimal feature-flag-reading plumbing into
  apps/ext-wxt/entrypoints/background.ts.
- Support per-app feature flag overrides (packages/driven-feature-flags)
  so `browser-agent` resolves to `false` in apps/m2 and apps/m3 and stays
  at its manifest default (`true`) in apps/ext-wxt, without adding
  per-app targeting to the shared manifest.
- Rename ExtensionBootstrap to ExtensionLifecycle (and ExtensionTabBootstrap
  to ExtensionTabLifecycle) to match the ServerLifecycle naming convention
  already used in packages/core-server; rename the
  extension-driving-bootstrap package to extension-driving-lifecycle.
- Update docs/architecture.md for the renames and current flag wiring.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@ndthanhdev ndthanhdev changed the title Gate browser-agent per app, rename ExtensionBootstrap to ExtensionLifecycle feat: browser-agent Jul 12, 2026
@ndthanhdev
ndthanhdev merged commit 5811f29 into main Jul 12, 2026
5 checks passed
@ndthanhdev
ndthanhdev deleted the feat/browser-agent-core-wrap branch July 12, 2026 19:08
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