Message your agent straight from the page
Stop pasting 4 MB Retina screenshots or switching back to your editor. Alt + Click any component (or type directly inside the HUD “Make this CTA indigo”) with ~300 tokens of exact context. In return, your agent can ask questions or live-preview CSS via its Spotlight Popin before touching disk.
Your agent sees the real page — without locking you out
No browser extension to maintain, no sandbox network popups: everything syncs over local .jolt/ files and MCP. During an active watch session (jolt-mcp listen), the HUD enters LIVE mode — click Stop anytime to end listening and take back IDE control.
Your AI agent becomes
a true frontend sidekick.
Forget debugging plumbing: Chrome or Safari, React, Vue, Svelte or Vanilla, Cursor, Claude Code or Antigravity — Jolt stays local-first in dev with 0 bytes in production.
5× fewer tokens, zero guesswork
- 4 MB Retina screenshot (~1,500+ vision tokens)
- 3 back-and-forth prompts to describe the component & file
- Manual copy-paste of console stacks & Vite build errors
Alt+Click→file:line:col+ React/Vue chain (~280 tokens)- 54.1 KB npm package · ~19 KB gzip dev probe · 0 B in prod
- Automatic secret redaction + Vite compile, console & A11y errors
Connect Zustand, Pinia, Redux or Three.js in 1 line
Your agent inspects live state, dispatches actions (jolt_mutate_runtime), simulates network latency delayMs, or moves Three.js / R3F meshes with zero boilerplate.
import { joltZustand } from 'vite-plugin-jolt/adapters';
joltZustand('cart', useCartStore); // 0 bytes in prod
“Simulate an HTTP 500 response for me”
No need to build a throwaway mock server to verify an edge case. Ask your agent to inject a 500 failure on POST /api/checkout: you experience the failure live in the UI while the agent sees exactly how your app handles it — and fixes it on the spot.
Your GPU and 3D scene,
finally legible to your agent.
Stop guessing blindly why a 3D scene drops frames: inspect Three.js or WebGL2 meshes just as easily as HTML elements.
Manipulate 3D objects just like HTML
In a 3D or Three.js scene, screenshots never reveal draw call budgets or which mesh is slowing the frame. Hold Alt over the viewport to isolate item-1, item-2, or item-3: your agent reads FPS (including 1% low) and adjusts position or shaders safely.
Connect Jolt to your app in 30 seconds
Install the dev plugin and auto-generate your AGENTS.md and .mcp.json in one CLI command. Issues & PRs welcome!
npm install -D vite-plugin-jolt && npx jolt-mcp init --write