- Personalization — your own instructions, applied to every investigation you run: Slack (channels and DMs) and the web app.
- Channel custom instructions — instructions applied to every investigation in a Slack channel, no matter who runs it.
What to include
Anything you’d otherwise find yourself repeating — the preferences and hard-won context that apply to you or your team:- Investigation steps — where to look first, or what to rule out. “Always check the deploys dashboard and recent releases before anything else.”
- Known failure modes — the usual suspects for your systems. “Latency spikes on checkout are usually the payments provider rate-limiting at peak — check that first.”
- Runbooks and references — point Traversal at the docs and dashboards you trust. “For database incidents, follow our failover runbook:
<link>.” - Response format — how you want findings written up. “Lead with customer impact, then the root cause with evidence. Keep it to a few bullets.”
- Priorities — what matters most. “Prioritize customer-facing services; always call out anything touching checkout.”
Personalization
Set your instructions in Settings → Personalization, under Instructions for Traversal. They follow you across every investigation you start, in Slack or the web app.Channel custom instructions
Set a channel’s instructions in Settings → Channel management, under Custom instructions. They apply to every investigation in that channel — from anyone, including auto-triggered ones — so they’re ideal for alert channels, auto-trigger channels, or a shared debugging channel where the whole team wants consistent output.Custom instructions shape how Traversal works, not when it runs — use triggers to control what starts an investigation.