Widget

Enrai is planned to expose a widget mode for embedded usage.

Purpose

The widget is meant to be injected into external sites or internal tools so Enrai can work closer to the running application instead of only from the standalone editor.

What the widget should do

The main value of the widget is access to runtime context from the page where it is injected.

That includes:

• console logs
• client-side errors
• warnings
• network failures
• runtime traces or structured events exposed by the host app

Agent-facing value

When those logs are collected by the widget and sent into Enrai, they can be made available to the coding agent as live debugging context.

That gives the agent more than just source code. It also gives it:

• what is failing right now
• where the failure happens
• what the browser is reporting
• what the host application is emitting at runtime

In practice, that means the coding agent can consume logs from the injected site and use them while debugging or generating fixes.

Expected workflow

1. Inject the Enrai widget into a target application.
2. Capture browser-side logs and events.
3. Stream or upload those events to Enrai.
4. Expose the collected runtime data to the coding agent as task context.
5. Let the agent reason over both the codebase and the live runtime signals.

Typical use cases

• debugging frontend errors faster
• reproducing environment-specific failures
• capturing console output before opening a coding task
• attaching runtime evidence to queued tasks or chat turns

Current status

This should be considered a product capability description for now.

The main idea is clear:

• inject Enrai into a site
• collect logs
• make those logs available to the coding agent

The exact transport, storage model, and UI surface can evolve later.