like Dominic. And these things are incredibly valuable. And then lastly, once you get more comfortable with all those first four things, your pinned threads with automations, these things that wake up these threads over time, they're going to feel like teammates. And more interestingly, now that threads can talk to each other, so every thread has the ability to list other pin threads, has the ability to rename threads, and it has the ability to send messages to each other. Not only can you have teammates, but you can have teammates that work together and you can effectively start having managers, right? And so you you went from an IC enabled by an IDE, then you have pin threads that feel like a team where you're the manager. And very quickly in the future, as models get better, this is where the the puck is going to skate to. You're going to start having your like manager threads and then your IC threads. And I'm sure in the future there's going to be some other crazy orchestration, right? And all of this really is due to the fact that compaction works. Even six months ago, I don't know like how many people here have been told this, but you were always told if a conversation goes very long, start a new thread, right? After 20 messages, it's it's not going to be that good. Um, every feature should be its own its own uh conversation. If you do a code review, start a new session. Those things basically aren't true anymore. And a lot of it has to do with compaction. just pin the thread, rename it to the project ID, and that project thread should be able to delegate to sub agents, create new threads, and have conversations, and then write to your memory vault, which will allow you to just log what's happening. And then with automations, you can just wake them up.