Why does my AI assistant dump a wall of possible causes instead of one command I can actually run?
Watch how experienced developers answer a tooling question in a chat channel. One reply is 200 words of "it could be your env vars, or DNS, or a firewall rule, or…"; the other is a single line like nslookup yourapp.com 8.8.8.8. The user reads the essay, runs nothing, and waits. They run the one-liner in five seconds and either have the answer or have output to paste back. For the first turn of a debugging conversation, the copy-paste-able command wins almost every time.
The reason is that the cognitive cost is asymmetric. Long advice makes the reader do four jobs — read, prioritise, plan, execute. One command makes them do one: copy and paste. The bug in most long-form AI answers is that they always dump the entire decision tree instead of the first branch that would actually narrow the problem.
A useful triage rule for the first turn:
- Is there one command that distinguishes your top two hypotheses? Send it and wait for output.
- Is it almost certainly one cause with a one-line fix? Send the fix, skip the diagnosis.
- Are there 5+ possible causes? Send the single diagnostic that eliminates the most of them — not the taxonomy.
Concrete examples: curl -i https://api.example.com/health -H "Authorization: Bearer $TOKEN" tells you in five seconds whether a 500 is network, auth, or server-side. EXPLAIN ANALYZE on a slow query plus \d+ tablename narrows a Postgres problem faster than a paragraph about pooling and indexes ever could.
Longer replies are the right call in three cases: the user already pasted diagnostic output and now needs interpretation; the fix has ordered prerequisites (config, restart) that must happen in sequence; or it's a "should I" design question where the tradeoff genuinely needs explaining. Even then, structure it as direct answer, then one paragraph of why, then the command — not paragraphs of preamble with a command buried at the bottom.