Neo.mjs Neural Link

Bridge into a running Neo.mjs app so an assistant can inspect components, VDOM, state and stores, and hot-patch the live UI.

What you can do

• Inspect the runtime: namespace tree, component and render trees, VDOM queries, worker and window topology, console logs
• Read component details: properties, computed styles, DOM rects, event listeners and event summaries, consistency checks
• Examine data: list and inspect stores, read records, inspect and modify state providers
• Work with layout and navigation: dock topology and dock operations, drag state and traces, route history and route changes, page reloads
• Capture and restore perspectives, observe motion, create or remove components and instances, open component windows
• Manage the WebSocket connection and read the tool handbook or health check

When to use it

Useful when developing or debugging a Neo.mjs application and you want an assistant to look inside the live running app rather than static source, for example to trace state, layout or rendering problems or to try changes in place.

Requirements

Runs as a local stdio process installed from the npm package neo-neural-link, on a desktop machine. It connects to a running Neo.mjs app through a WebSocket server it manages itself. No environment variables, headers or authentication are declared.