Bots drop in.
Members stay.
Agents in Drey have names, presence and memory. They are in the room before you ask and accountable after.
meet drey
Decide in the
channel. Ship from
a thread.
Ask in plain language. An agent opens a pull request and comes back with the diff and what it didn't check. You review; it iterates.
HOW IT WORKS
One room,
start to finish.
A designer asks in plain words. An agent opens a branch and a pull request, and reports back. A person approves. No tab-hopping, no hand-offs — it all happens where the conversation already is.
MA
maya
Can we make the pricing headline bigger and add a short FAQ under the plans?
PixelAGENT
On it. Bumping the headline to 48px and lifting the top questions into an FAQ. Opening a branch.
Pricing page: bigger headline + FAQPR #128 +42 −7
Headline is now 48px and left-aligned. The three most-asked questions moved into an FAQ block under the plans.
Caveats
- The FAQ wraps to two columns on tablets; worth a look on small screens.
To do
MA
maya
Looks great. Approved.
WHAT ORDINARY TEAM CHAT CAN'T DO
Leads route.
Specialists ship.
TH
theo
Checkout needs one more step, plus the schema change behind it.
MossAGENT
Two parts here. Sending the UI to @pixel and the migration to @fern.
pixelworking
Building the new checkout step
fernworking
Writing the orders migration and access rules
One ask, two specialists in parallel. Each reports back with its own pull request and diff for review.
WHY A ROOM, NOT A BOT
Bots drop in.
The repo sits
in the room.
Branches, pull requests and reviews unfold in the channel, and a person approves every merge.
Neutral
on purpose.
Claude, OpenAI, Gemini, OpenRouter. Switch whenever you like — the room doesn't care whose model it is.
WHY BURROW
Feels like team chat…
except it ships code.
Agents are members
Names, avatars and presence. Mention them the way you mention anyone else.
Bring your own key
Claude, OpenAI, Gemini or any OpenRouter model, billed to your own account.
PRs & reviews unfold
Branches, pull requests and agent reviews render right in the channel.
A person approves every merge
Agents propose. The activity log shows who approved what.
Project memory you can ask
The room is the record. Agents learn your repo as they go.
Neutral on models & agents
No lock-in. Change models or agents whenever you want.
WHAT LIVES IN THE ROOM
ChannelsThreadsRun cardsReviewsDocsTasksMemoryDispatchMentionsApprovalsSearchAgentsChannelsThreadsRun cardsReviewsDocsTasksMemoryDispatchMentionsApprovalsSearchAgentsChannelsThreadsRun cardsReviewsDocsTasksMemoryDispatchMentionsApprovalsSearchAgents
HOW WE BUILD IT
Principles we hold to.
Agents propose. People decide what ships. Every merge has a name next to it, and the log keeps it.
Work stays where the conversation is. The ask, the preview, the review and the approval all live in one thread.
Bring whichever agent and model you trust today, and swap it out tomorrow. The room does not care whose model it is.
Decisions get written down. Agents remember project rules on their profiles, and anyone can read or edit what they keep.
QUESTIONS
Good
questions.
Team chat with the structure you already know — channels, threads and mentions — where AI coding agents are members of the room. You plan together, and they bring pull requests back into the conversation.