traceway
Traceway
Drive a Traceway instance from the terminal with the traceway CLI. The first word of the argument decides the flow:
| Invocation | Flow |
|---|---|
/traceway login |
Login: install the CLI if missing, authenticate, select a project |
/traceway debug <issue ref or bug description> |
Debug: resolve the issue and investigate to root cause |
/traceway perf <endpoint or symptom> |
Performance: diagnose latency/slowness to root cause against a checklist of common bottlenecks |
/traceway <anything else> |
Query: answer the observability question with CLI reads |
/traceway (no argument) |
Ask what they want: log in, debug an issue, or run a query |
The CLI is under active development. If a flag documented here does not appear in
traceway <command> --help, trust the binary. If atracewayMCP server is connected, prefer its tools over shelling out to the CLI: they wrap the same API with the same semantics, and this skill's knowledge is available as its resources. The server is this same binary (traceway mcp). This skill only reads. To change anything (archive issues, acknowledge or resolve pages, snooze alerts, run monitors, write post-mortems), the user installs the separatetraceway-writeCLI and thetraceway-writeskill. When the user asks how a part of Traceway works (schedules, escalation, status pages, alert rules, impact score and the rest), use thetraceway-learnskill. It is the full product guide.