Local-first visual context for AI coding agentsGet started

Visual context for AI coding agents

Give your coding agent eyes on the UI.

Viskod is a local-first visual context engine for AI coding agents. Point at the element behind a frontend bug and it captures a context packet—visual, DOM, computed-style, runtime, and best-effort source evidence—then makes a grounded handoff available through MCP.

Local-first · MCP-compatible · Human-reviewed
Live workflow preview
localhost:3000 / dashboard
JD
Good morning, JamieToday · 9:41 AM
Open tasks24
In review08
Shipped142
Today’s focus3 tasks
↗Review landing pageDesign · 2h ago
◌Update empty stateProduct · Yesterday✓
Selected elementbutton.fake-action
Built for the moment your agent is stuckReactNext.jsViteChromiumAny MCP client

The missing context

Your agent can read the code. It still cannot see what you are seeing.

“The third button in the card on the left is misaligned” leaves an agent hunting through routes, components, and CSS. Viskod connects the report to the running interface: the selected target, surrounding evidence, and ranked source leads give your agent a grounded place to start instead of a guess.

“The button looks wrong.”

Without visual context: search, guess, repeat

“This selected target is backed by its screenshot, DOM, computed styles, runtime signals, and ranked source leads.”

With Viskod context: inspect, hand off, verify

How it works

Point. Explain. Verify.

A local workflow that turns a vague visual symptom into evidence your agent can use—and a fix you can judge.

01 / REPORT

Start with the element, not a selector.

Open your local app in Studio, choose Report UI issue, and click the element that needs attention. Viskod identifies the target while you stay focused on what the user sees.

Open →
+
Target selected in the running app
◎

Evidence, not automatic truth. A changed screenshot never auto-accepts a fix. The human decides.

Inside the packet

Not just a screenshot.
A context packet.

The agent gets the evidence it needs to reason about the interface you actually ran.

01
target

Visual evidence

The selected element, its bounds, viewport, URL, and screenshot metadata.

02
<button class="fake-action">Open →</button>

DOM + styles

Element hierarchy, text, attributes, and computed styles.

03
consolenetwork  200 OKrender   42ms

Runtime evidence

Console and network signals from the page context.

04
src/components/TaskCard.tsxconfidence-rated lead

Source hints

Ranked leads into the codebase with confidence and reasoning. They narrow the search; they are not claims of exact ownership.

Fits your workflow

Works beside the agent you already use.

Viskod does not become another editor or chatbot. Use local Studio to select and review a running app; use its MCP server to expose the context and handoff to your existing coding agent. The agent changes the code; you decide whether the result is correct.

Claude CodeCursorOpenCodeAny MCP client
quickstart

# install the CLI
$ npm i -g @viskod/cli

# verify the project and start local Studio
$ viskod setup --project-root .
$ viskod studio --project-root .

✓ Local Studio ready at 127.0.0.1:3001

Local by default

Your UI stays on your machine.

Viskod is designed for local development and proprietary applications. Capture is explicit, services bind to localhost, telemetry is disabled by default, and sensitive values are redacted before context reaches the agent.

⌂Local-first executionNo hosted service or cloud account required for the core workflow.
◉Explicit captureViskod observes the element you choose, when you choose it.
⊘Sensitive-value redactionSecrets, tokens, emails, and other sensitive values are filtered.

Focused by design

Viskod supplies context.
Your agent writes the code.

Not another IDE

Use the editor and agent you already trust.

Not a browser replacement

Observe your running app without changing how you build it.

Not an autonomous fixer

You review the evidence and decide whether the fix is correct.

Start with the next visual bug

Stop describing the screen.
Show the agent.

Install Viskod, point at the issue, and give your coding agent the context it was missing.

$ npm i -g @viskod/cli