Vibeocus Lens icon

Vibeocus Lens

Vibeocus Lens is a Chrome extension that captures frontend element context—DOM, selector, visual state, and notes—and streams it into a local Vibeocus MCP workspace. It helps developers hand off precise browser context to AI coding agents for bug fixing and refactoring.

Vibeocus Lens

Browser captures for AI-assisted frontend work

Vibeocus Lens is a browser-to-workspace capture tool for frontend debugging and AI-assisted development. It is presented as a Chrome extension that turns a selected browser element into structured context for Vibeocus Desktop and MCP-compatible agents.

Instead of asking an AI to infer a bug from a screenshot or a vague description, Lens packages the exact DOM snippet, a precise selector, a localized visual state, and your annotation into a payload that can be streamed through a local bridge. The result is a more concrete handoff from the live frontend to the local workspace where agents such as Cursor or Claude Code can inspect the same component context.

Core capabilities

DOM snippet extraction

Captures the inspected component’s exact HTML or computed string so the agent can work from the real structure instead of a summary.

Exact CSS selectors

Records precise target paths such as `#hero .btn-primary`, which makes it easier to point an AI tool at the correct element.

Visual state capture

Pins a localized viewport screenshot to the selected element, annotation, and task state for visual context.

Annotations tied to the element

Lets you add a comment, expected behavior, or task note directly to the selected element.

Local MCP sync

Uses a localhost bridge to send browser captures into Vibeocus Desktop and its MCP context.

On-page demo and payload preview

Supports the built-in demo flow on the site, where you can select an element and see the structured payload preview before installing the extension.

Practical use cases

  • Frontend bug reports

    Select a broken button, input, or panel in the browser, attach the expected behavior, and pass the exact selector and DOM snippet to an AI agent for a more precise fix.

  • Component-level debugging

    Capture the live state of a component directly from the page when a screenshot alone does not show the relevant DOM structure or nested elements.

  • Workspace-linked handoff

    Send browser context into a local Vibeocus workspace so the capture is tied to the right project, task, and agent workflow.

  • Evaluation and onboarding

    Use the built-in demo to understand how the payload is assembled before installing the extension and connecting it to the desktop app.

Pros and Cons

Pros

  • Captures multiple forms of context in one flow: DOM, selector, screenshot, and annotation.
  • Uses a local bridge and states that transmission stays local rather than going through a cloud backend.
  • Connects browser captures to Vibeocus Desktop, where they can be organized as project context and MCP-readable data.
  • Provides a built-in demo on the product page, which helps users understand the capture workflow before installing anything.

Cons

  • Pricing details are not published on the pricing URL; the page currently returns 404.
  • The site does not show a full technical spec for browser compatibility or extension permissions.

FAQ

How do you set up Vibeocus Lens?

Lens is installed as a Chrome extension. The page says you can start with the demo on the site, then install from the Chrome Web Store and connect it to Vibeocus Desktop from Settings > Lens.

What does Lens send to the AI workspace?

Lens captures exact DOM snippets, precise CSS selectors, a localized visual screenshot, and your annotation or task note, then streams that structured capture through a local MCP bridge.

Is Lens cloud-based or local-first?

The source describes a local bridge on localhost and says the data transmission is local, with no cloud backend for Lens captures.

Does Lens require the desktop app?

The site shows Lens paired with Vibeocus Desktop to open a local MCP gateway. That pairing can map target websites to projects and make the captures agent-readable inside the workspace.

What problem is Lens designed to solve?

The page positions Lens for frontend bug reporting and precise component identification. It is meant to reduce guesswork when an AI agent needs the exact component, selector, and visual state.

Quick Facts

Category
Developer Tool
Product
Vibeocus Lens
Platform
Chrome extension; Vibeocus Desktop companion
Integration
MCP-compatible local workspace
Primary use
Frontend bug capture and context sharing
Website
vibeocus.com