When should you use it?
- Support cases need code-level answers
- Context lives in several tools
- Engineers handle escalations
Not for: Front-line support without code access; Teams that cannot connect customer data safely
What do you need, and what do you get?
You need
- Local copies of product repos
- MCP connections to customer data, logs and past threads
- Saved commands for common lookups
You get
- A traced explanation of the behavior
- Relevant past threads with why they matter
- A draft reply for review
How does it work, step by step?
- Start from the symptomAsk the agent to trace backwards from what the user sees.
- Group repositoriesKeep front end, back end and docs in one workspace so a single thread can answer.
- Connect data sourcesBring in account settings, event logs and previous conversations through MCP.
- Script repeated lookupsSave commands that search by ticket ID or error text over a default recent window.
- Review before sendingCombine everything into a single draft a support engineer edits and sends.
The prompt
Our own prompt, inspired by Kody Fisher & Zach Hudson and written to work in Custom agent. Values in lime are placeholders.
Ticket [ID] says: [symptom]. Trace why this happens using the repositories in this workspace. Look up their plan and settings, recent errors in the event log for the last 7 days, and up to three past threads on the same error. Summarize the cause in one or two sentences, list evidence with links, and draft a reply. Leave the customer reply unsent.
Inspired by Kody Fisher & Zach Hudson: How technical support at Cursor uses Cursor · Cursor. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Customer data in an agent session needs strict access rules.
- Searches without a time range return stale threads.
Our take
Most support teams cannot give agents the whole codebase, but the pattern from Kody Fisher and Zach Hudson scales down: one place, symptom first, every source attached. Always set a time window on log and database searches, a small rule that prevents accidentally pulling years of customer data. Be strict about which customer fields the agent can see, and log every lookup it makes for later audit. Start with escalations to engineering, where the payoff from code context is largest, before rolling the workflow to front-line chat. Review every merged reply before it reaches the customer. Prefer read-only database credentials. Redact secrets from past conversation pastes. Measure not only throughput but reopen rate and customer satisfaction, so speed does not hide worse answers. Keep a short playbook of slash commands so new support engineers inherit the same lookups. Rotate access tokens on a schedule and revoke them when engineers leave support.
Where the time goes back: Gathering context was the slowest part of each case; bringing every source into one session removes most of it.
FAQ
What share of support uses this?
Do agents reply to customers?
Source and credit
Inspired by Kody Fisher & Zach Hudson. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How technical support at Cursor uses Cursor · Cursor
- Creator
- Kody Fisher & Zach Hudson
- Published on
- cursor.com
- Original date
- Mar 3, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.