Oops, sorry about that! I just enabled discussions 🙂

Both manifests could feed into the same relay though, so the agent could resolve elements from both apps via MCP. The multi-app experience just isn't seamless yet. Would love if you opened a discussion on GitHub; I'd like to understand your workflow better.

The tricky part is the iframe boundary. Iframes are separate document contexts, so the parent app's Domscribe instance can't see into the iframe's DOM. Each app would need its own runtime. You'd be working with one app at a time, not reaching across the frame.

Interesting setup! Honest answer - this isn't supported today. Each app would need its own Domscribe plugin and would get its own manifest. The relay is one-per-workspace so that part works fine.

Is it a monorepo? Domscribe can handle monorepos, but only a single app root for now. Interested to learn more about your use case though!

Domscribe: Give your AI coding agent eyes on your running frontend | Product Hunt AI coding agents edit your files blind; they can't see your running frontend. Domscribe closes the gap. Code → UI: Query any source location via MCP, get back live DOM, props, and state. No screenshot...

Open source (MIT), works with React, Vue, Next.js, Nuxt. Plugins for Claude Code, Cursor, GitHub Copilot, and Gemini CLI.

Would love your support 🙏
producthunt.com/posts/domscribe
github.com/patchorbit/domscribe

Two workflows:

→ Code to UI: Your agent queries a file:line via MCP, gets back live DOM, props, and state

→ UI to Code: Click any element in the browser, describe what you want, your agent edits the right file on the first try

No screenshots, no guessing.

Just launched Domscribe on Product Hunt 🚀

Every time I asked an AI agent to fix something in the UI, it burned thousands of tokens grepping through files before writing a single line of code.

So I built a tool that maps every DOM element to its exact source location.

GitHub - patchorbit/domscribe: Domscribe is a pixel-to-code development tool that bridges the gap between running web applications and their source code. Domscribe is a pixel-to-code development tool that bridges the gap between running web applications and their source code. - patchorbit/domscribe

Woke up to 65 stars on Domscribe this morning 🤯

Turns out @antfu.me starred it. Floored.

Bridges your live browser DOM to source code - click any element, see live props/state, giving your coding agent full context.

React/Vue + AI agent devs 👇
github.com/patchorbit/domscribe

GitHub - patchorbit/domscribe: Domscribe is a pixel-to-code development tool that bridges the gap between running web applications and their source code. Domscribe is a pixel-to-code development tool that bridges the gap between running web applications and their source code. - patchorbit/domscribe

Cool - I've been building something complementary. Domscribe maps every DOM element to its exact source location at build time via MCP, so agents know which file and line owns an element before automating it. github.com/patchorbit/domscribe