
- See the full trace waterfall for every request
- Spot slow queries before they become production issues
- Browse structured logs with stack traces and JSON attributes
- Catch exceptions before they ever reach your users
- Connect your AI coding assistant via MCP to query your traces
How it works
Your app uses the same Monocle agent as in production. In development, the agent automatically sends telemetry to Monocle Studio instead of the cloud. Studio receives it, stores it locally, and serves a dashboard — all on a single port (localhost:4200). Data persists between restarts so you can review past sessions.
Features
Traces & Requests
HTTP requests with full span waterfall, timing, and attributes
Logs
Structured logs with severity filtering, JSON viewer, and stack traces
Exceptions
Exceptions with stack traces, grouped by type
Database Queries
SQL queries with duration and statement preview
Background Jobs
Job execution, queue name, duration, and success/failure tracking
CLI Commands
Traces for CLI scripts and scheduled tasks with custom spans
MCP Server
Let Claude Code or Cursor query your local traces and logs
Real-time
New data appears instantly — no manual refresh needed
Quick start
That's it
Dev mode activates automatically when
NODE_ENV=development (the default in AdonisJS during node ace serve). No extra config needed — the agent detects it and sends data to Monocle Studio instead of the cloud.CLI options
Data storage
Monocle Studio stores data locally at~/.config/monocle/studio.db. Data persists between restarts — use monocle dev --clean to start fresh.