← Mini-apps

Slack conversation producer

A conversation you can hand to an agent. The page holds the cast, the channels and the messages as entities and exposes a command API; you copy the API reference into a local agent, describe the culture you want to show, and paste back what it writes.

  1. 01

    Copy the agent brief

    The full command API, written as a prompt. One button, top left.

  2. 02

    Ask your agent for a conversation

    "Here's the API. Write me a good/bad pair showing how we handle incident handoffs."

  3. 03

    Paste what it wrote

    Drop the JSON into Run commands. Present, or copy a share link.

Examples

Load one, then hit Copy as commands to see the script behind it.

Good

Async-first

#proj-atlas

Atlas launch — decisions land here, not in calls

24
Maya Okonkwo9:12 AM
Decision needed: Atlas billing cutover date.
Writeup with the three options and my recommendation (option B, cut over Mar 4): RFC — Atlas billing cutover
Comment in the doc by Thu 5pm your time. If nobody blocks, we go with B on Friday. No meeting needed — if you think we do need one, say so in this thread and I'll book it.
👀4✅6
2 repliesLast reply 4:20 PM
Devin Raso3:48 PM
Caught this at the start of my day in Lisbon — no context lost, the doc had everything. Left two comments on the migration window. Not a blocker, B works.
🙌2
Lin Zhao4:20 PM
Same, commented on the empty state. B from me too.
Sam Brenner9:30 AM
Adding the on-call angle so it's written down: cutover Friday means the weekend rotation owns any fallout. @Devin Raso is on next week — flagging now so it's not a surprise then.
🙏1
Thursday, March 2
Maya Okonkwo5:04 PM
✅ Decided: option B, cutover Friday Mar 4.
Four comments, no blocks. Doc is updated with the reasoning and the two changes Devin asked for. Rollback plan is in the appendix.
If you're seeing this Monday, you have missed nothing — everything is in the doc.
🎉8🚀3
Message #proj-atlas

The decision, the deadline, and the way to object are all in one message. Devin reads it six hours later in Lisbon and is not behind.

Bad

Sync-only

#proj-atlas

Atlas launch — decisions land here, not in calls

24
Maya Okonkwo9:12 AM
can everyone hop on a quick call in 5? need to sort out the billing cutover
2 repliesLast reply 9:15 AM
Devin Raso9:14 AM
It's 6pm here and I'm about to pick up my kid. Can this be async?
Maya Okonkwo9:15 AM
it's easier to just talk it through, we'll fill you in
Lin Zhao9:16 AM
I'm in back-to-backs until 2. Go ahead without me I guess 😅
Sam Brenner10:47 AM
good call everyone 👍
👍2
Monday, March 6
Devin Raso8:02 AM
So what did we land on for the cutover? I've read this channel three times and I genuinely can't tell.
👀3
2 repliesLast reply 11:41 AM
Sam Brenner11:30 AM
I think we said the 4th? Maya would know, she's out until Wednesday.
Lin Zhao11:41 AM
I wasn't on the call either. Has anyone told support it's happening?
Message #proj-atlas

Same decision, same people. The context lives in a call two of them couldn't attend, so Monday starts with an archaeology dig instead of work.

Paste the JSON array your agent produced. Commands apply in order; a bad one is skipped and reported rather than dropping the batch.