Use a Slack agent for support lookups and bug checks

Spur’s team hands Slack requests to an agent that researches issues in a sandbox and reports back with evidence.

Done with Custom agent· Intermediate· Oct 2026

What they did
People at Spur mention Doozy in Slack when they need help with a customer problem or bug. It starts in a clean E2B environment with no saved secrets, and separate gateways add the needed access on demand. From there, it can pull information from Postgres, Stripe, GitHub, Linear, PostHog, MCP servers, or the web, then return the results and any files in the thread.
How it went
Thirteen people use it each day, mostly on support and success work instead of engineering. The team says it is now a critical part of how they operate. The earliest version was brittle and could hardly interpret files dropped into a thread.
Tips
Store credentials outside the sandbox and leave dangerous actions disabled until someone turns them on. Even with those limits, a granted tool can still be abused, so check anything sensitive before it goes out.

Try it yourself with Claude Code

Act as my Slack triage assistant. When I paste a [customer issue, failed payment, bug report, or account question], investigate it using read-only access to [Postgres, Stripe, GitHub, Linear, PostHog, MCP servers, and/or the web] as needed. Run in a fresh sandbox with no credentials inside it; use outside gateways only for the access you need. Reply with a brief summary and the records or links that support it. If any step would [change data, send a message, delete something, or submit a form], stop first and show me the exact action for approval before proceeding.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.