Every team chat has the same ritual.

Someone posts a link. You click it. A new tab opens. Maybe a login screen. The page loads, you read it, you come back to chat and type "lgtm 👍". Then you go back to the tab, because you still haven't pressed the button.

Do that for every pull request, every ticket, every crash and every design review, and most of your day is tabs. All that, just to say "lgtm".

So in Drum, a link isn't a link. It's the thing itself.

A pull request in three lines

Type /pr, pick the pull request, and it lands in the channel as a card:

What it is. The title, repo#number, who opened it, and the labels. A small glyph shows the state: green for open, grey for draft, violet for merged, red for closed.
Where it stands. One line covers checks, reviews and the diff. Checks collapse to their worst result, so nine green and one red reads as red.
What to do next. One button.

The button is the part we're proudest of. Its main half does whatever you most likely want to do next. If the PR is approved and green, it says Merge. If it's waiting on you, it says Approve. If neither applies, it says View diff. Everything else is behind the arrow: request changes, comment, squash and merge, open on GitHub. Anything you can't do yet is greyed out, with the reason next to it: 2 checks failing, Changes requested, Your PR.

Merge asks once, right there in the card, Squash-merge into main?, with no pop-up. Click the card itself to open the full diff.

And the card is live. An open PR refreshes on its own while you're looking at it, so the spinner turns into a green tick without anyone asking "is CI done yet?"

Share a few PRs at once, say for a release thread or a standup round-up, and they stack into one tidy list, one line per PR. Use /review instead and the PR becomes up for grabs. Someone claims it ("Maja is reviewing"), and it ends as Reviewed, so two people never review the same thing while a third PR sits untouched.

Linear: status and assignee are buttons

Paste a Linear issue link and you get the issue, not a preview of it. The status and the assignee are pills you can click. Move it to In Progress, hand it to someone else, or leave a comment, all without leaving the channel. Jira issues work the same way.

Figma: the file, not a file name

Paste a Figma link and Drum asks how you want it: a plain link, a thumbnail, or the live file embedded right in the conversation. Design review happens where the discussion already is.

Sentry: resolve it where the alert lands

Connect Sentry and new issues post to #sentry, with nothing else to set up. Every alert arrives as a card showing whether it's new, regressed or escalating, with the stack trace one click away. Resolve, Archive or assign it right there. Whoever picks it up says so by picking it up, not by typing "I'm on it".

It's still you doing it

Cards act through your own accounts. Connect GitHub once and you can see private repos, and every approval and merge is made as you. GitHub's history says you approved it, not "Drum Bot". If you haven't connected yet, the card says so and offers a single button to fix it.

Why bother

Chat is where the decision gets made: ship it, not yet, who's got this? It should also be where the decision gets carried out.
Your real work, not just a link to it.