(MOT-4259) feat(browser,console): ship the browser page + renderers as injectable console UI - #612
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 7 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (42)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
skill-check — worker0 verified, 49 skipped (no docs/).
Four for four. Nicely done. |
|
@coderabbitai review |
✅ Action performedReview finished.
|
…le-ui # Conflicts: # console/web/src/App.tsx # console/web/src/hooks/use-hash-route.ts # console/web/src/lib/nav-options.test.ts # console/web/src/lib/nav-options.ts # pnpm-lock.yaml
|
@coderabbitai review |
✅ Action performedReview finished.
|
What
Moves the console's browser page AND its chat/function-call renderers to an injectable UI shipped by the browser worker, per
docs/sops/injectable-console-ui.md(state worker as the reference). Part of the console injectable-UI migration (MOT-4256).browser/ui (injectable)
page.tsx:setup(host)registers the browser page (#/ext/browser, nav labelbrowser) + the browser function-call renderers viahost.functionTriggers.register.src/page/: session rail, live viewport, console + network panels ported to@iii-dev/console-ui+host.iii.trigger. Live frames viauseLiveFrames(engine-pushes/client-appends):host.iii.on(...)+registerTrigger({ type: 'stream', function_id: '<fn>::<browserId>', config: { stream_name: 'browser:frames', group_id: sessionId } }), with seq guarding + session-change reset + await-start-before-teardown.styles.cssscoped[data-iii-ui="browser"], tokens only, 0 unscoped.build.mjsesbuild with the five shared externals.iii-console-uicrate,ConsoleUi::new("browser").script(...).style(...).register(&iii);build.rsrespectsSKIP_UI_BUILD.pnpm-workspace.yamljoinsbrowser/ui.console (deletions)
pages/Browser/,components/chat/browser/,hooks/use-browser-{status,events}.ts,lib/browser.ts; editedApp.tsx,ChatView.tsx,nav-options.ts(+test),use-hash-route.ts,conversations-context.tsx,components/function-trigger/renderer-registry.tsx. No leftover browser-page refs (remainingbrowserhits are theiii-browser-sdkpackage).Verification
ui::tests + integration/manifest/schema).tsc -bexit 0, biome clean on 7 changed files, nav-options tests 5/5.Closes MOT-4259.