MuyueWorkspace

Muyue/MuyueWorkspace

Fork 0

Commit Graph

Author	SHA1	Message	Date
Muyue	a7d4b31a0d	feat(studio): force advanced reflection during browser-test sessions (v0.7.2) All checks were successful PR Check / check (pull_request) Successful in 55s Details When at least one browser_test session is connected, every chat message in Studio now auto-enables advanced reflection regardless of the user toggle. The intent: during AI-driven UI testing, having a second model produce a preliminary [RAPPORT PRÉALABLE] materially improves which clicks the active model decides to perform and the quality of the final ✓/✗ report. - handlers_chat: derive wantReflection from body.AdvancedReflection OR (browserTestStore has any active session). The user toggle still works for normal conversations; tests just override it. - Silent fallback when no inactive provider is configured (no error, no behaviour change for single-provider setups). - Tests.jsx: add a hint explaining the auto-on behaviour so the user understands why the Studio toggle appears bypassed. - Version 0.7.1 → 0.7.2 + CHANGELOG entry.	2026-04-27 12:02:04 +02:00
Muyue	c820d55710	feat: AI-driven browser tests — Tests tab + browser_test agent tool Some checks failed PR Check / check (pull_request) Failing after 33s Details New feature: give Studio's AI control of any browser tab to test buttons, read the console, and report which buttons work / fail. Backend (internal/api/browser_test.go, ~480 LOC): - WebSocket endpoint /api/ws/browser-test, auth by single-use 5-min token - BrowserTestStore: session map (capped at 16, LRU evict), token store - REST: /api/test/snippet (issues token + JS snippet), /api/test/sessions, /api/test/console/{id} - Agent tool 'browser_test' wired into the registry, with actions: list_clickables / click / eval / console / current_url / type / wait / summary. click returns the console_delta produced during the click. - Embedded JS runner: opens WS, hooks console + window.onerror + unhandledrejection, dispatches dispatcher commands, replies with correlation IDs, watches for URL changes. Frontend: - New Tests tab (web/src/components/Tests.jsx): snippet copy + connected sessions list + live console viewer - App.jsx: 5th tab + Ctrl+4 shortcut (Config moves to Ctrl+5) - api/client.js: getTestSnippet / getTestSessions / getTestConsole Studio prompt: - internal/agent/prompts/studio_system.md: added browser_test entry to the tools table + <browser_test_strategy> section explaining the recommended loop (summary → list_clickables → click → check console_delta → report) Versioning: - v0.6.0 → v0.7.0 - CHANGELOG.md: full entry under v0.7.0	2026-04-27 11:02:05 +02:00

Author

SHA1

Message

Date

Muyue

a7d4b31a0d

feat(studio): force advanced reflection during browser-test sessions (v0.7.2)

PR Check / check (pull_request) Successful in 55s

Details

When at least one browser_test session is connected, every chat
message in Studio now auto-enables advanced reflection regardless of
the user toggle. The intent: during AI-driven UI testing, having a
second model produce a preliminary [RAPPORT PRÉALABLE] materially
improves which clicks the active model decides to perform and the
quality of the final ✓/✗ report.

- handlers_chat: derive wantReflection from body.AdvancedReflection
  OR (browserTestStore has any active session). The user toggle still
  works for normal conversations; tests just override it.
- Silent fallback when no inactive provider is configured (no error,
  no behaviour change for single-provider setups).
- Tests.jsx: add a hint explaining the auto-on behaviour so the user
  understands why the Studio toggle appears bypassed.
- Version 0.7.1 → 0.7.2 + CHANGELOG entry.

2026-04-27 12:02:04 +02:00

Muyue

c820d55710

feat: AI-driven browser tests — Tests tab + browser_test agent tool

PR Check / check (pull_request) Failing after 33s

Details

New feature: give Studio's AI control of any browser tab to test buttons,
read the console, and report which buttons work / fail.

Backend (internal/api/browser_test.go, ~480 LOC):
- WebSocket endpoint /api/ws/browser-test, auth by single-use 5-min token
- BrowserTestStore: session map (capped at 16, LRU evict), token store
- REST: /api/test/snippet (issues token + JS snippet), /api/test/sessions,
  /api/test/console/{id}
- Agent tool 'browser_test' wired into the registry, with actions:
  list_clickables / click / eval / console / current_url / type / wait /
  summary. click returns the console_delta produced during the click.
- Embedded JS runner: opens WS, hooks console + window.onerror +
  unhandledrejection, dispatches dispatcher commands, replies with
  correlation IDs, watches for URL changes.

Frontend:
- New Tests tab (web/src/components/Tests.jsx): snippet copy + connected
  sessions list + live console viewer
- App.jsx: 5th tab + Ctrl+4 shortcut (Config moves to Ctrl+5)
- api/client.js: getTestSnippet / getTestSessions / getTestConsole

Studio prompt:
- internal/agent/prompts/studio_system.md: added browser_test entry to the
  tools table + <browser_test_strategy> section explaining the recommended
  loop (summary → list_clickables → click → check console_delta → report)

Versioning:
- v0.6.0 → v0.7.0
- CHANGELOG.md: full entry under v0.7.0

2026-04-27 11:02:05 +02:00

2 Commits