When the docs run out, it reads the code.
Ask why the product actually behaves the way it does and a support employee investigates your real codebase: a deep read inside an ephemeral sandbox, answered in plain language, with the evidence kept in the flight recorder.
What it does
The real behavior, not the wiki's memory
Docs drift; code does not. Deep answers come from reading the current repository, so "does it retry?" gets the actual retry semantics.
Sandboxed by construction
Each investigation runs in an ephemeral sandbox that dies minutes later. Your model keys never enter it: the sandbox holds only a scoped, budget-capped relay token.
Plain language out, evidence kept
The channel gets a short human answer. Every command the investigation ran is recorded in the flight recorder for anyone who wants the receipts.
Costed like everything else
A deep investigation is ordinary metered usage against the workspace allowance, itemized on the payslip like any other work.
How it works
- 01
Connect the code host
A read-only connection to the repository, granted like any other tool.
- 02
Ask the hard question
Anything the knowledge base cannot answer about real behavior can trigger a deep read.
- 03
Get the answer, keep the proof
A plain-language reply in the thread; the full investigation trail in the employee's records.
