Why Tag
Why work should begin where the team already talks.
Multiplayer AI, in the workspace you share.
A coworker in the thread, on your own setup
Your @Tag works where your team already talks. Everyone in the thread sees what it does and can build on it, the way they would with a coworker. It just runs on your setup and takes instructions from you.
It runs on a computer you control, using your own AI connection through Codex or Claude Code. You choose its skills, connect your accounts, and give it a place to work. Add your weekly report template or the checklist you use before a launch. Make it yours.
We don’t host your conversations or working files. Your AI provider and connected services still process the information needed for your requests, under their own data policies.
By default, only you give your @Tag instructions. Your teammates can bring their own, with their own setup. You share the conversation and the results, and you decide who can ask your Tag. See Sharing access to your Tag when you need to authorize another person to make requests.
See Your own @Tag and Adding integrations for how to make it yours.
Work already happens in Slack
Most work doesn’t begin as a tidy brief. It starts in a Slack thread: a question, a few links, some back-and-forth, and eventually a decision someone needs to act on.
Slack stands for “Searchable Log of All Conversation and Knowledge.” That includes the discussion behind a decision, like why the launch moved from Friday to Monday.
Take that discussion into a private AI chat and you’ve given yourself a relay job. Copy over the context, work through the answer, then bring it back to Slack. If someone questions it, you’re explaining a conversation they never saw.
Mention @Tag in the thread and work through it there. You ask your assistant for help; teammates can add a missing detail, question the answer, or take on the next step. Everyone can follow how you got there.
@Tag, Slack is all you need.
A little help working together
A thread has gone back and forth all morning. Are we agreed? Who's doing what? Did anyone answer the question about support?
Ask your @Tag to pull it together. Someone spots a missing detail. Someone else volunteers to take it on. You ask it to update the plan.
Your teammates don't need to set up an assistant or learn how to prompt one. They can just join the conversation.
The missing detail might be in your inbox
You remember an email about the launch moving to Monday. Everyone in Slack is still talking about Friday.
With your email connected, you can ask @Tag to find that update and share the relevant details. The team gets the context it needs without needing access to your inbox. You choose what to bring into the channel, where the people there can read it.
That's one less "hang on, let me find it" between a question and a decision. Try it with Gmail.
Leave with something you can use
Once you've worked it out, ask @Tag to save the plan. It could be a checklist in your working folder or, with Canvas access enabled, a reference the team can open in Slack.
The files are ordinary files. Open them yourself, edit them in another tool, or ask your assistant to pick them up again when things change. They stay in place when you upgrade.
See Working with files to try it.
Last updated