Creytix

Browser tab

Preview a page inside the IDE, read its console, and send a picked element straight to the AI agent.

AI

Preview — early access.

Overview

The Browser tab is an embedded page preview — by default pointed at your local dev server — with its own console feed and an element picker that can hand a clicked element straight to the agent as a ready-made instruction.

How it works

Load a URL and the page renders through a proxy inside the tab, with console messages (log/info/warn/error/debug) streaming alongside it. The element picker captures a selector, tag, and a text preview for whatever you click, and — when it can — a best-effort guess at the source file behind it, including pulling a src/... path straight out of a console error message. Picking an element and sending it to the agent prefills an instruction in the agent panel rather than making you describe the element in words yourself.

Steps

  1. Open the Browser tab

    It's the first tab in the strip, defaulting to http://localhost:3025.

  2. Load the page you're working on

    Enter the URL of the page or app you want to preview.

  3. Watch the console

    Errors and warnings stream into the console feed as the page runs.

  4. Pick an element

    Click an element on the page to capture it — selector, tag, text preview, and a source-file guess if one's available.

  5. Send it to the agent

    Hand the picked element to the AI panel as a prefilled instruction instead of describing it yourself.

Capabilities

  • Embedded page preview through a proxy, without leaving the IDE.
  • Live console feed — log, info, warn, error, and debug messages as they happen.
  • Element picker — selector, tag, and text preview for anything you click.
  • Source-file guessing — pulls a workspace-looking file path out of a console error when it can.
  • One click into the agent — a picked element becomes a prefilled agent instruction.

Limits & honest scope

  • The preview goes through a proxy — some sites or paths (strict CSPs, certain auth flows) may not render correctly inside it.
  • The source-file guess is a best-effort pattern match on error text, not a guaranteed source map lookup — it can be wrong or absent.
  • Console history is capped; very chatty pages will drop older entries.