See
Inspect runtime evidence.
Screenshots, visual tree, logs, telemetry, navigation state, app state, and database rows.
Early Access · .NET MAUI in Beta
Give Coding Agents Eyes and Hands into Live App's Runtime
Ansight connects coding agents to your running app through a local MCP bridge, so they can capture screenshots, inspect the UI tree, read logs and telemetry, query SQLite, push files, drive workflows, and act on real runtime evidence.
What the agent does
Agents can reason from runtime evidence, not just code.
Three captured-session examples: rebuild a user's path, explain a missing data panel, and correlate telemetry with logs. The same evidence surface works for any MCP-capable agent.
Reconstruct a path
Hey Codex, reconstruct what the tester did after opening Red-Point.
ansight_get_session_artifacts 514 screenshots, 182 logs, 6 telemetry channels ansight_search_logs NAVIGATION home?tab=map -> menu -> managedata -> settings ansight_search_logs SCREENVIEWED ManageDataPage, MapPage, SettingsPage ansight_get_screenshot_frame nearest frames attached to each step Explain missing data
Hey Claude, why are amenities missing after the tester opens Castle?
ansight_search_logs AreaPage opened for Castle ansight_search_logs AmenitiesWebClient 404 Not Found ansight_get_log_context AmenitiesDataSource could not load parent area -> likely cause preview data missing amenities for this area Correlate telemetry
Hey Cursor, did the captured map session drop frames or grow memory?
ansight_summarize_telemetry_window FPS min 3, avg 57.6, max 66 ansight_summarize_telemetry_window physical footprint 137 MB -> 476 MB ansight_get_logs ManageDataPage PushAsync completed in 624ms ansight_get_nearest_artifacts logs, screenshot, and telemetry aligned Runtime surface
See. Drive. Mutate. Analyze.
Ansight exposes the same app evidence and controls to Studio and any MCP-capable agent: screenshots, logs, telemetry, UI actions, app state, files, preferences, and captured-session analysis.
Drive
Operate the app like a tester.
Tap controls, type into fields, invoke commands, and capture the result.
Mutate
Mutate running state.
Push files, update preferences, set bindable properties, invoke methods, and adjust registered objects.
Analyze
Turn sessions into answers.
Package screenshots, logs, telemetry, and timeline events so an agent can explain what happened.
How it works
Three layers. One local path.
Capture in your app. Inspect and act through tool packages. Bridge it all through Ansight Studio — for you and for the agent.
Ansight SDK
Lives inside your .NET MAUI app. Streams logs, screenshots, telemetry. Hosts the seven opt-in tool packages.
LAN pairing Signed, expiring config
Ansight Studio
Desktop debugger for you. Local MCP server for the agent. Same tools, two front ends.
MCP protocol HTTP or stdio, local-only
AI Agent
Codex, Claude, Cursor, Gemini, Copilot — or any MCP client. Connects to Ansight Studio and queries the live app.
Team handoff
Share captured sessions with your team.
Share a Studio capture to Portal when another teammate needs the same evidence. They get a browser link with the session timeline, screenshots, logs, telemetry, annotations, and captured artifacts. When they need the full local workflow, they can download the session into Ansight Studio and work against it there.
- Share to Portal. Choose the owning team and publish a session reference.
- Review in browser. Inspect timeline evidence, screenshots, logs, telemetry, and annotations.
- Download to Studio. Pull the shared session into Studio for local review, exports, and agent-driven investigation.
Ansight Portal · Session viewer shared
Frameworks
Current and planned mobile stacks.
| Framework | Platforms | Languages | Status |
|---|---|---|---|
 .NET | In Beta | ||
 Flutter | Planned | ||
 React Native | Planned | ||
 iOS | Planned | ||
 Android | Planned |