Example
… in https://github.com/org/repo), mention it in an earlier turn, rely on GITHUB_REPOSITORY, or let OpenSRE infer it from the current git checkout’s origin remote when GitHub is connected.
The dim · gathering via <source> · <tool> — <query hint>… line shows which integration the assistant reached for while it works. When the same tool runs more than once, a (2), (3), … suffix and the query hint distinguish each call.
More questions that trigger live gathering:
| You ask | The assistant gathers from |
|---|---|
| ”check the GitHub issues for the Windows crashes” | GitHub issues |
| ”what do the datadog logs say about the payment service?” | Datadog logs |
| ”are there recent Sentry errors on checkout?” | Sentry |
| ”what’s the recent error rate in grafana for prod-api?” | Grafana |
How it works
- You ask a question in plain language.
- The assistant runs a short, bounded tool-gathering pass over the tools your configured integrations expose.
- Tools are read-only data fetches, so they run autonomously — no per-call confirmation, just like an investigation.
- The gathered results are folded into the answer the assistant writes back to you.
When nothing is configured
If you have no integrations configured, behavior is unchanged: the assistant answers from text only, exactly as before. There is nothing to enable or turn on — connect an integration and the relevant questions start returning live data. Run/health to see which integrations are connected, and /tools to list the tools currently available to the assistant.
Related docs
- Interactive Shell Commands — slash commands and natural-language actions
- Integrations Overview — connecting data sources
- GitHub — configuring the GitHub integration used by the issues example
- Investigation overview — the full RCA pipeline these tools also power
Tracer