Visual evidence
The selected element, its bounds, viewport, URL, and screenshot metadata.
Visual context for AI coding agents
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.
The missing context
“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, verifyHow it works
A local workflow that turns a vague visual symptom into evidence your agent can use—and a fix you can judge.
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.
Describe what is wrong and what should happen. Viskod combines the selected element with visual, DOM, style, runtime, and source evidence, then makes a copyable handoff available to your agent.
After your agent changes the code, Viskod reloads and recaptures the same target. Compare the evidence, then choose Accept fix, Issue persists, or Needs follow-up.
Evidence, not automatic truth. A changed screenshot never auto-accepts a fix. The human decides.
Inside the packet
The agent gets the evidence it needs to reason about the interface you actually ran.
The selected element, its bounds, viewport, URL, and screenshot metadata.
Element hierarchy, text, attributes, and computed styles.
Console and network signals from the page context.
Ranked leads into the codebase with confidence and reasoning. They narrow the search; they are not claims of exact ownership.
Fits your workflow
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.
# install the CLI
$ npm i -g @viskod/cli
# verify the project and start local Studio
$ viskod setup --project-root .
$ viskod studio --project-root .
Local by default
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.
Focused by design
Use the editor and agent you already trust.
Observe your running app without changing how you build it.
You review the evidence and decide whether the fix is correct.
Start with the next visual bug
Install Viskod, point at the issue, and give your coding agent the context it was missing.