The future of work with @Claude

1. 0:00 – 1:36

   From autocomplete to agentic work: how engineering workflows changed fast

   1. SPSpeaker0:00

      What do you do if there's no Claude in the channel?

   2. SPSpeaker0:02

      I don't know. I can't remember a world without Claude in the channel. [laughing] [upbeat music] Walk me back. So three years ago, we were just starting to adopt AI into our day-to-day workflows. What was it like back then? And take me all the way to where we are today.

   3. SPSpeaker0:27

      I remember two years ago, I was still using Typeahead. [laughs] That was, like, what AI could do as an engineer. And, you know, we built Claude Code, we brought agents and kind of the next generation of ways to do your coding, and it's just changed so much since. Like, you know, with Typeahead, I was still deciding I wanna write this line of code, and the agent was helping a little bit. It was just writing the line. And then we got to the point where it was writing whole functions, whole files, whole features, and I feel like now with Tag, it just does the whole thing. Like, it can write the feature, it can do an entire experiment end to end. It does my data analyses. It's been, like, two leaps in two years. When I think back the last couple years, it's almost like there's this, like, transition. We went from a person always in the loop. It's one person sitting there, and they're just typing a line at a time. And we got to one person sitting there with, like, 10 Claudes, you know, [laughs] typing a bunch of features at a time.

   4. SPSpeaker1:26

      [laughs]

   5. SPSpeaker1:26

      Now we're at the point where Claude is actually driving a little bit more, and it's not just one person anymore. It's, you know, an entire team that's interacting with it.

2. 1:36 – 2:34

   What Claude Tag is: proactive AI that joins the channel and drives work

   1. SPSpeaker1:36

      So what is Claude Tag?

   2. SPSpeaker1:39

      In the past, you had to open Claude, and you had to ask it something, and then Claude will do the work, and it'll use your tools, it'll use your computer. It'll get the task done. That's the way that it used to be. With Claude Tag, Claude jumps in. It's proactive. It knows when to jump in. It'll do the work, even if it takes days or weeks, and it'll follow up. And I think the coolest thing is it'll remember what I told it for next time. So before, I would have to prompt Claude every time, and I would have to say, "Okay, Claude, now do this," or, "Now do this." I would have to remember to do that. Now we just add Claude to a channel. It will proactively jump in and do the work. Everyone gets to see it. Everyone gets to participate because multiplayer, and it'll remember for next time. Okay, so what on the research side actually enabled this? How is it that Tag is so good?

3. 2:34 – 3:15

   Why it works now: long-running autonomy and self-scheduling

   1. SPSpeaker2:34

      For many years, we've been working on making our models more long-running and autonomous. So if you look at the latest MMLU evals, our latest models can work for 16 hours at a time and are now in the zone where we can't even accurately detect how long it's able to work for. In something like Claude Tag, Claude is able to self-schedule work for itself, and so you can take this one 16-hour task, and it actually increases over time because Claude can schedule a follow-up after days or weeks or months. I feel like the tasks that it, we couldn't trust it to do before, now it can get almost every single time.

4. 3:15 – 3:32

   Real usage: long-running experiments, daily check-ins, PRs and bug fixes

   1. SPSpeaker3:15

      I have a bunch of these Claude Tag sessions personally that are running for, like, days, weeks. I think I might have one that's, like, a month, and it's essentially this long-running experiment, and it, it's just checking in every day. Checks the data. Once in a while, it sends a bug fix if there's some bug that needs to get fixed. I just see the pull requests coming in, and I get these data readouts every day.

5. 3:32 – 4:25

   Memory as the second breakthrough: retaining instructions and channel preferences

   1. SPSpeaker3:32

      The other big innovation is just being able to have memory in the model so the model can not only set reminders for itself, but it can also remember just all the instructions that all the users have given it over time.

   2. SPSpeaker3:46

      Memory took a long time to crack. Like, I think we tried to get it right for Claude Code for years, and it feels like we finally got it right. It just, it feels really good to use.

   3. SPSpeaker3:55

      Yeah. So if you're working with Claude Tag in a channel, and you tell it, "Hey, I want you to monitor only for this type of issue, but not these other categories," it'll do that. It will remember that for that channel forever after. And then if someone else says, "Hey, actually, let me expand your scope to this new thing," it'll adjust. Another big thing that people love is Claude's personality and EQ. So sometimes when I talk with people about adding Claude Tag into a channel, they say, "Oh, how

6. 4:25 – 4:53

   Staying helpful, not annoying: EQ, discretion, and adjustable involvement

   1. SPSpeaker4:25

      do I know it won't jump in on every thread and be annoying?" Well, Claude is trained to have a good sense for when it's needed, and it can take the back seat. And if it ever goes too much in the wrong direction, you can just tell it to do something different, to jump in less or jump in more, and it'll just remember it for the future. So when you look at the internal usage, and when you talk with our customers who are just getting started on Claude Tag, what are the patterns that you see?

7. 4:53 – 5:33

   Customer patterns and emergent workflows: channel automation that sticks

   1. SPSpeaker4:53

      The coolest thing to me has been how customers are figuring it out. It can write your pull requests. Uh, it can debug production issues. It can do data analysis. All you have to do is hook it up to your tools. I think that's only possible because the memory is just so good, and I've seen people do this kind of emergent stuff where, you know, for example, this is a channel for Q&A. Anytime a question is answered, you must check it off. You tell Claude Tag this, and it'll just do that. It'll answer the questions, and then it'll react with a check every time, and it'll just do this for you. Like, we have a channel for data questions, and now Tag just answers all the questions, or we have a channel for, uh, Claude Code feedback, and Tag just fixes everything now.

8. 5:33 – 5:47

   From “tag it” to “always respond”: hands-off assistance via remembered defaults

   1. SPSpeaker5:33

      The most common way that I ask a data question is I post in our data channel, but I tag Claude Tag.

   2. SPSpeaker5:38

      Yeah.

   3. SPSpeaker5:38

      And then it takes the first pass, and normally it's pretty good.

   4. SPSpeaker5:41

      I, I kept doing this in a bunch of channels, and then I just got tired of tagging it, so I just told it, "Please respond every time."

   5. SPSpeaker5:46

      [laughs]

9. 5:47 – 6:42

   Best-practice diffusion: learning AI in public, shared channels

   1. SPSpeaker5:47

      I think it goes to show how powerful the memory is that you're able to do something like this. You can just tell it, "Hey, remember to always do this thing," and it just has your back. It's been a huge shift in how we all do work. I think this also is a way for more people to understand how to work with AI. Because Claude Tag is working in public channels, everyone is able to observe how the expert users leverage it. And then they take those patterns, and they bring it to new projects that they're working in. And so both internally and in the customers that we've been working with, we've been seeing this diffusion of Claude Tag best practices that is, I think, very novel to AI tools.

   2. SPSpeaker6:28

      It was surprising how fast it took over. Like, I feel like now I see Tag in just every channel that we have. Like, every feedback channel, every data channel. It started with just a few people using it, but I think as other people saw those people using it, they really quickly picked it up.

10. 6:42 – 7:58

    Why it changes team workflows: objective-based, multiplayer AI embedded in collaboration

    1. SPSpeaker6:42

       It's been very empowering to be able to have Claude Tag have my back. So for a lot of our existing tools, like Chat, Cowork, and Claude Code, you typically have to remember to open it, and so it's a more reactive experience. And one thing that's great about Claude Tag is you give it this, like, higher level objective, like put up PRs for every bug in this channel, and it just has your back and puts up a PR for every single one without you needing to remind it. The second thing that's really cool is that it's multiplayer. So almost all of the AI tools that people use right now are just you and Claude working together and then copy and pasting this output to your team. And I think the big shift that Claude Tag allows is it brings Claude right into the middle of your work so that multiple people can guide the session to a better output. Like, there's so many, like, dynamics here. Like, one, we're all learning about how to use Claude Tag better by observing other people. Claude Tag is learning how to better work with us by hearing the guidance that we're giving it. And at the end of the day, the customer gets a better result because it's not just my opinion of how we should solve it, it's our whole team is able to jump in to, like, nudge this PR to the best possible state.

11. 7:58 – 8:14

    Lowering the barrier to contribution: non-engineers can ship changes through Tag

    1. SPSpeaker7:58

       I, I mean, I love this idea. I, I keep telling everyone I want everyone to contribute to the code base, and so many people are afraid because they have to, like, open a terminal, even the desktop app, because you have to, like, deal with a git and, like, code checkouts and stuff. And with Tag, they, they can just do it. It's really cool.

12. 8:14 – 8:58

    Operational requirements and self-serve knowledge: public channels + source-of-truth access

    1. SPSpeaker8:14

       The other thing that I think is really important is making sure that your collaboration platform has public channels. That way Claude Tag can monitor, uh, different projects that you're tracking. So as a PM, I'm often working on maybe five to 10 features, and I have Claude Tag look at the status for every single one and then give me a daily report. The other big unlock we've been seeing is that people can now self-serve their questions. When people onboard to our company, instead of asking legal about whether they can say this or instead of asking our HR team what our benefits are, they can just tag Claude Tag, and because Claude Tag is connected with our source of truth files, it can give them a really fast answer no matter what time they're looking for it.

13. 8:58 – 10:48

    Productivity impact and choosing Tag vs Claude Code: asynchronous delegation at scale

    1. SPSpeaker8:58

       I think the single biggest thing is just how much more productive it's made everyone. And you know, this is driven by our internal version of Claude Tag, and if you look at just the product org, so, you know, the part of the company that we sit in, the number of PRs that are written by Tag, I think it's, like, 65% now, and it's just climbing like this. Like, I thought that Claude Code was the thing that makes engineers go faster [laughs] . This is a product that makes engineers go way faster. And I, I think actually a lot of the reason is because the way you're interacting with it, you ask Tag to do something, and it'll, it'll respond, and you've moved on to the next task. So you actually want to set it up in a way where Tag can do the work, and you don't have to check in all the time.

    2. SPSpeaker9:42

       So you have hundreds of these Claude Tags running, but you're still a power user of Claude Code. How do you decide when to reach for each of them?

    3. SPSpeaker9:50

       Yeah. So I used to use Claude Code for everything, and then I started using Tag for more and more things. First, it was really simple fixes, so, you know, someone has a bug, the button's off by a few pixels or something. I'll just ask Claude, "Please fix it." Or someone has a really simple data question. I'll ask them to fix it. And I, I think what's been happening more and more over the last few weeks as I've been getting more comfortable with the product is I've been using Tag for just more and more things. And even more complicated work it's actually able to do because it can verify its work, 'cause it's running in, you know, the same remote sandbox that we use for, for mobile and for the desktop app, and it's using the same agent SDK, so it's just as intelligent. When you add memory to this, in different channels I have actually specific preferences about how I want it to verify. It's... it might be a little bit different for every channel. And so often what it does is it'll, you know, fix some bug, then it'll post back a video in Slack, and I don't even have to leave it. Okay, so what's next for Claude Tag?

14. 10:48 – 11:22

    What’s next: more collaboration platforms and org-level customization

    1. SPSpeaker10:48

       So we launched Claude Tag in Slack, and we're excited to bring it to more platforms where people collaborate, like Microsoft Teams. We want to make sure that every knowledge worker is within arm's length of Claude, no matter where they're getting their work done. And I think one of the coolest parts of Claude Tag is it's not just changing how individuals work, it's putting Claude in the center of teams and transforming entire orgs. We've built Claude Tag to be incredibly customizable, just like Claude Code, and I'm so excited to see how orgs customize Claude Tag and make it their own.

    2. SPSpeaker11:22

       I can't wait.

Episode duration: 11:25