DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to verify a bug fix by reading live component state with Medula

Let an agent read and check a running app's component state after a fix, without editing source files.

Who it is forA developer or coding agent fixing a production bug in a Vue, React, Svelte, or Solid web app, who needs to confirm the fix at the verification step.

The problemChecking a bug fix often means clicking through the running app by hand to see what state the components hold, which is slow and easy to miss.

The outcomeThe agent reports the current component tree and state of the running page, so the fix can be confirmed against what the app actually holds.

What you need first

  • A web app built with Vue 3, React, Svelte 5, or Solid, run through Vite 8, Nuxt (with Nuxt DevTools 4), or Next.js (App Router)
  • pnpm and Node.js available to install the package
  • An MCP-capable coding agent to connect to devframe
  • A browser tab open to the running app

Steps

  1. Install Medula and Vite DevTools with pnpm add -D medula @vitejs/devtools.
  2. In vite.config.ts, set devtools: true and add medula() next to your framework plugin.
  3. Add the MCP server to your agent's configuration with command npx and args devframe connect.
  4. Start your dev server, open the app in your browser, and complete any DevTools connection code prompt.
  5. Keep the app tab visible while the agent works, then ask it to show the components on the page and their current state.

Prompt for your agent

Using the medula MCP tools from the medula repo, connect to the running dev server for <app-port> and list the components on the current page with their state. Expected output: a list of components with their state values. Verify that the values match what the open browser tab shows.

Caveat. Changes affect only the running page and do not edit your source files, so any real fix still has to be made in code.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page