The Problem with Vision-Based Agents
Every vision-based agent today follows the same brittle loop: capture a screenshot, send it to a vision model, infer a pixel coordinate, click, and repeat. At 85% per-action accuracy, a 50-step task has a 0.03% end-to-end success rate. The agent isn’t the weak link — the interface is.Performance Comparison
NSP and vision-based agents are not in the same category. The table below uses real benchmarks from supported JavaScript applications.How It Works
The NSP daemon runs on the host machine alongside your applications. It has four layers that work together to deliver structured state to your agent.Process Watcher
Continuously scans all running OS processes, classifies their runtime (V8 / JVM / CLR), and manages probe attachment lifecycle. New processes are detected within 500ms of launch.
Runtime Probes
Language-specific probes attach to live processes and extract semantic state — without source code, UI automation, or any developer instrumentation of the target app.
Semantic Engine
Converts raw runtime data (heap nodes, JVMTI fields, CLR metadata) into structured SSF JSON with stable, human-readable dot-notation keys your agent can reference reliably.
Agent API
A hardened REST and WebSocket server on
localhost:7842 that any AI agent can call to read state and execute actions. Auth, rate limiting, and safety validation are built in.Runtime Coverage
NSP supports the three major managed runtimes used by enterprise and consumer applications today. Support for native C/C++ processes is coming next month.Next Steps
Quickstart
Up and running in 5 minutes. Install the daemon, launch Chrome, and call your first state endpoint.
Architecture
Deep dive into how the four layers fit together and how each request flows through the system.
Python SDK
The official SDK.
pip install nelieo-nsp. Full async support, typed models, and WebSocket streaming.API Reference
Complete reference for every REST and WebSocket endpoint the daemon exposes.
