# How Quinn Slack actually uses coding agents

Co-founded Amp and Sourcegraph

**If you take one thing:** `"I'm feeling Pucky" button`, starts half their work. a Slack button that turns a bug report into an agent thread with one click, and he says about half the team's work starts there.

- **Agent:** Amp (web) ([source, 2026-09-11](https://ampcode.com/podcast/season-02/episode-04))
- **Model:** Amp Dial: medium ([source, 2026-07-27](https://ampcode.com/time-capsules/1))
- **Review:** Agent reviews first, he scans diffs for red flags ([source, 2026-08-11](https://ampcode.com/podcast/season-02/episode-02))
- **Harness:** Amp threads in cloud orbs, previews in portals ([source, 2026-07-27](https://ampcode.com/time-capsules/1))
- **Rules file:** AGENTS.md (20 lines) in qdiff ([source, 2025-11-15](https://github.com/sqs/qdiff/blob/6864ee32171e2affd27ce86de5835256764a3ca6/AGENTS.md#L9))

## In their words

> these days I'm really only using Amp, which is F2, and Chrome, which is F5

> I'll do it in an orb. I think medium is probably fine for this

> Yeah. It's tough because I still draw a lot on my background as a developer when I have the agent review the code and it makes, you know, I probably accept two-thirds of its suggestions.

> as recently as like a month ago, I had like five different worktrees on my machine and I had a way to make their dev servers run independently, but it like, it was so messy. Now with orbs, it just works.

> - **Type**: TUI Git client (Magit clone).


Archetype (our label): Orchestrator. Newest source: 2026-09-25.
Card: https://www.prehistoriq.com/stacks/sqs/ · Data: https://github.com/prehistoriq/stacks/blob/main/data/stacks/sqs.json