Monocle Studio exposes CLI commands to query your local telemetry data without opening the browser. Useful for quick checks, scripting, or piping data into other tools.
These commands are also great for AI coding agents. Instead of copy-pasting logs from your terminal into Claude or Codex, your agent can call monocle studio errors or monocle studio traces directly and get full context on its own.
Dev
Start the local Studio server. This is the main entry point for Monocle Studio.
Traces
Fetch recent traces from Studio. Each trace shows the HTTP method, path, status code, duration, and service name.
You can filter by service name or trace ID, and control the output format.
Logs
Fetch recent logs with optional severity and search filters.
Errors
Fetch recent exceptions with type, message, and stack trace preview.
Install agent instructions
Append a managed Monocle Studio block to AGENTS.md or CLAUDE.md so your agents know about Monocle Studio and how to use it.
The command prompts for the target file, appends the block at the end, and updates only that managed block on later runs.
The traces, logs, and errors commands support three output formats via the --format flag.
Common options
The traces, logs, and errors commands share these options.
Make sure Monocle Studio is running (monocle studio dev) before using the query commands. They connect to the local Studio server over HTTP.
