Aayush Poudel

Life is a simulation and reality is an illusion.
...

[Aayush Poudel @Aayush__Paudel]

@suryanshbuilds both actually. it reads V8's runtime coverage right before and after the click, so no code changes to your app. then it maps those byte ranges back through source maps to your real files and lines

[Aayush Poudel @Aayush__Paudel]

coding agents can read your code. they can't see which lines a click actually ran.

so I built a small MCP server that lets claude code click the button itself #ClaudeCode #MCP #buildinpublic #opensource #webdev

[Aayush Poudel @Aayush__Paudel]

I built Lightpath, an MCP server so my AI agent stops asking me to "click it and tell me what happens"

It clicks the button itself and sees every line that ran, browser and server, plus the lines that didn't.

https://t.co/FDYx4bBYZD

[Aayush Poudel @Aayush__Paudel]

@naveendas96 no DOM diff. it returns the code that ran, plus each request's method, path and status, and any thrown errors or failed requests. no bodies, on purpose. and no selectors either, you name the button like a person would, and if it misses it lists the closest ones on the page

[Aayush Poudel @Aayush__Paudel]

@j3rah_ exactly. and clicking is only half of it. the other half is seeing what ran after the click, browser and server. that's the part that turns "I think it's this file" into "it's line 16"

[Aayush Poudel @Aayush__Paudel]

@michias_hailu fresh each time lightpath starts, so you sign in once per session. claude fills the login form with run_action and it stays logged in until lightpath stops. keeping a saved profile between runs isn't in yet, it's on the list

[Aayush Poudel @Aayush__Paudel]

@sachintwtss yep, react is the main target. vite works as is, webpack just needs source maps on. pair it with a node backend (express, fastify, nest) and you get both sides of the click in one trace. chrome or edge for now

[Aayush Poudel @Aayush__Paudel]

@progerallworld yes, that's exactly what compareTo is for. run the click, fix the code, then run_action with compareTo: "last". you get the new trace plus what changed: functions that ran in only one, and lines that switched between run and not run. one call

[Aayush Poudel @Aayush__Paudel]

@1sylvanluo yep exactly how it works. click requests get an x-lightpath-trace header and the node agent reads coverage around each request so server lines only join their own click. if two requests overlap in one process, the trace says "overlapped" instead of guessing

[Aayush Poudel @Aayush__Paudel]

@DEVIN__SETH building lightpath, an MCP server that lets claude code click a button in your app and see which lines actually ran (and which didn't). free + open source

https://t.co/FDYx4bBYZD

[Aayush Poudel @Aayush__Paudel]

@anupamrjp building lightpath, an MCP server that lets claude code click a button in your app and see which lines actually ran (and which didn't). free + open source

https://t.co/FDYx4bBYZD

[Aayush Poudel @Aayush__Paudel]

@notaryannnn clean one each run. for logins, claude fills the sign in form first and stays logged in while it runs. reusing your own profile isnt in yet, good idea though

[Aayush Poudel @Aayush__Paudel]

@kemal_codes oh nice, memory + runtime would be a good combo honestly. claude remembers the project and sees what actually ran. how are you storing the memory, files or a db? if you try lightpath next to it I'd love to hear how they play together

[Aayush Poudel @Aayush__Paudel]

@builtbyamrit thanks honestly got tired of being its hands 😅 the notrun lines ended up being my favorite part, thats usually where the bug hides

[Aayush Poudel @Aayush__Paudel]

https://t.co/FDYx4bBYZD

feedback welcome, and a ⭐ helps a solo project get found

[Aayush Poudel @Aayush__Paudel]

works with claude code, cursor, vs code, kiro or any MCP client. react + node.

runs locally, sends nothing anywhere. free and MIT.

[Aayush Poudel @Aayush__Paudel]

@thewitcher Hi kelpie