Tool
watch
You cannot improve what you cannot measure. watch launches a process with RepoQL as its OpenTelemetry collector, and everything it emits lands in tables while it is still running — alongside sampled CPU and memory for the whole process tree. Evidence you can query repeatedly, not output you read once.
The process keeps running while you query it. Its telemetry sits in the same database as the code that produced it, so a slow span and the method behind it are one join apart.
Run it yourself
Or say it to your agent
“run the app and show me which spans are slowest”
Parameters
| Parameter | What it does | |
|---|---|---|
| executable | required | A binary on the PATH, or a path to one. |
| arguments | optional | Arguments to pass to it. |
| environment | optional | Extra variables as key=value;key2=value2. Use it to switch on an application's own telemetry. |
| workingDirectory | optional | Where to run it. Defaults to the caller's directory. |
What lands in the tables
- Traces — spans with their timings, attributes, and parentage.
- Logs — every record the process emits, with severity and structure preserved.
- Metrics — whatever the application reports, as time series.
- Resource use — sampled CPU and memory for the whole process tree, whether or not the application is instrumented at all.
The run's life
The call returns as soon as the process starts, with a run id and the schema to query. The run ends when the process exits. Telemetry from a finished run stays queryable — that is the point of putting it in a database rather than on a terminal.
This page names what exists. The depth behind every name — the bounds, the failure modes, how they compose — ships inside the binary at help:///, and answers to explore and read exactly like your code does. Install it, and your agent has the manual.