Ep 762: Agentic Context Carry: 3 Steps to Improve Cowork and scheduled AI Workflows (Start Here Series Vol 22)

This is the Everyday AI Show, the everyday podcast where we simplify AI and bring its power to your fingertips. Listen daily for practical advice to boost your career, business and everyday life. In the past 24 hours, two of the biggest players in the AI space, open AI in Google, both launched updated versions of their simple drag-and-drop agents that work for you with your contacts around the clock. And that got me thinking of the common features versus benefits methodology when it comes to marketing. If you've never heard of it, it's pretty simple. Features describe the technical facts or the specs of what a product does and well, the benefits explain the personal value the human gets from using static products. And in AI, we've seen a similar features versus benefits narrative take shape over the past few years. The feature large language models are smarter and faster than humans when used correctly. The benefit humans can be more productive. But the feature side has completely exploded over the past two months and the benefit side is still being written. Stick with me here. So as large language models have become overly agent by default overnight and as capable as humans, there's a new benefit paradigm for AI agents that has flown completely under the radar. And I know that this is the next big trend coming. It doesn't have a name, but I'm going to go ahead and name it now and explain the concepts. I'm calling this schedule agentic context carry or SAC, S-A-C-C. And I think the companies taking the time to understand and iterate on this new concept now are going to be the ones crushing their year end goals and KPIs in quarter four. So let's unwind this kind of new concept together because I think understanding this now is one of the most important investments you can make on your AI journey this year. So let's start there with our start here series. If you're new here, welcome to every day AI and this is our here series. But let's first start with the big picture of what's going on in traffic, open AI, Microsoft and a perplexity have all shipped scheduled agents just this spring. And most business leaders are still using AI just like a chatbot. I'm going to go in and I'm going to technically reactively ask an AI chatbot for something and probably have to re-explain a lot to waste a lot of time. But there's been a quiet workflow pattern merging beneath every one of these recent product launches. And that's why we're talking about this new concept of scheduled agentic context carried. So on today's show, that's exactly what we're going to over kind of go over and here's what you're going to learn. You're going to learn what agentic context carry actually means and why you've ever heard of it. And but why it absolutely matters. You're going to know how this hidden workflow bridges chatbots and the fully autonomous AI future. You're going to understand the timing of all these things coming together. And specifically these now huge one million token context windows that have quietly changed everything in this spring. And you're going to know the exact three steps to deploy this pattern inside of your business today. All right, let's get started. Welcome to every day. I my name is Jordan Molson. And this is the start here series. So after 750 plus podcasts, I'd never had an answer when someone was like, I'm new. Where do I start? Well, you start here, our start here series is an ongoing efforts to help business leaders both better understand trending and emerging concepts. But also for those who are brand new to get caught up. So I recommend you start with episode one of the start here series in listen in order. But go ahead and listen to this one. And then you can go backtrack. But make sure you go to start here series.com because well, it's going to make it much easier to do that. That's going to give you free access to our inner circle community. Right now, there's no other way for the general public to sign up except start here series.com. And then inside the start here series space, there will be an updated Spotify playlist where you can go listen to all of the start here series very easily in order and a dedicated playlist. All right. And if you miss our last start here series episode, we in volume 20. So this is volume 21. We talked about AI change management that works. Five moves. The top five percent make. All right. But let's get into this concept of a genetic context carry. And y'all every single major AI lab and the big third party players launched something. So from Mike was the big four. Right. So that's inthropic Microsoft Google open AI and then even perplexity and you know, open clock technically fall under this category. But literally everyone launched something and it's all very timely. So I did mention just the past 24 hours with big announcements from Google Gemini at their cloud next conference. And then with open a eyes new agents that we're going to talk about here in a minute. But also cloud code routines right that can bring automated scheduled agent runs to your guest. So it is kind of like the maybe this open claw movement that happened, you know, really in February and March of this year. Actually kind of forced the hint of all of the big companies to say, okay, it seems like we essentially to oversimplify it. We need an AI agent that can run on a crown, right? Run on a schedule where someone can go in and they say, hey, AI agent at this time every single day, I want this to happen. So we had the quad code routines, which I absolutely love that runs on your desktop. Similarly open AI in their codex platform, just at a schedule work and a persistent memory two days after that cloud code routines, announcement in mid April. And then we also just got wind that co pilot code work officially launched in front here. So you have essentially all these scheduled agent platforms slash co working platforms, right? So like cloud co work is the big one. Microsoft co pilot uses essentially the cloud co work technology because they are an investor in anthropic. So you have those kind of two places coming together. You have these co working kind of elements that allow for scheduling and it brings all your context. And then you have these scheduled agents and it's all literally exploded out of nowhere. And although, you know, this may technically be a more timely episode with all of these things happening now. The reason why I'm doing it in the Start Here series, whether you are listening to this in April or you're listening to it, I don't know, in the year 2027 is because I think that this is going to be a noticeable pivot in how the enterprise starts to interface with AI agents because here's the reality, right? We've been hearing since probably late 2024 that oh, it's the year of AI agents and it didn't happen in 2025. It didn't happen. But I think we've now come to that realization in 2026 in a certain way because we've noticed that the fully autonomous AI agents where you just give them a goal and that they go off and run on their own, not as reliable as we like, mainly because of safety concerns, guardrails, et cetera. So I think that this new kind of co-working scheduled agents is the stepping stone to where we will ultimately be when we have more of like, oh my gosh, this is artificial general intelligence. We have AGI because I give an agent a goal and it doesn't need me for anything, right? We're not there yet. So we are in this in-between phase. I don't know if this phase is going to last for a couple of quarters, a couple of years. I'm not sure. But it is definitely taken shape so quickly over the last few weeks. And that's led to kind of again, this feature benefit because when I think of traditional large-linguage models, right, essentially once companies understood their utility, right, the immediate benefit was, oh, more time, productivity, right? We can do more. You know, do do more, more, same time. But what about for the actual agents, right? I think when we thought about AI in the future versus benefits, kind of paradox, we thought about the benefit on the human, but what about the benefit on the AI system? Because as they start to get agentech and more human like and how they can work, well, they start to benefit as well. And that benefit is the agentech context carry that we're talking about today. And this is huge. And then like I said, just in the past 24 hours, right, we had Google launched their Gemini Enterprise agent platform and OpenAI launched their workspace agents inside of Chatcha, GT. So we're going to be going over that a little bit more on tomorrow's show and FYI. We did kind of go over some good examples of this context carry on yesterday's show on codex, all right? So if you miss that, well, yeah, I'm unplugged both of these shows. So make sure to go listen to the codex kind of super app preview 762. And then make sure to join us tomorrow more on these two recent launches. But here's a little bit on what the chat GVT schedule agents can do just so we can kind of set the stage for why this context carry is extremely important. All right. So how OpenAI says it in their recently released blog posts, they say, build once scale across your team, right? Great. Nature wants to share it with your team work that runs itself. So you can run agents on scale. the actual, the handle recurring tasks, and then keep the work moving across tools. Right, so you can, the agents use your tools to gather information, take action without needing step-by-step guidance. So, now, yeah, I had to do a little, little wind up here, because I wanted everyone to really understand how big this is and how quickly it's happening, before I really unwrapped this kind of concept that I coined, right, of agentic context carry. It's so new even, even, I don't just wanna say sack, right, but scheduled, agentic context carry. So this means, right, I wanna break down each of the four words and how they work together. So, schedule, obviously, means that the agent wakes up or runs on a cadence, not only when it prompted. So that can be both a time cadence, like we just talked about in the chat to the agents, or as an example, in clot routines, it can be a trigger, right, when you get a certain type of email, then an agent is going to run. That's what schedule means. Next, context carry. That means your memory, either your personal memory and preferences, your companies, data, all of those things, dynamic data pipelines, tool access, all those things that persists between runs. All right, and that is the big piece there. That is the context and the carry. And honestly, these agentic models, all by default, are able to do this, right? So the models themselves, they can call tools, right? They can call on, these connected apps on these MCP servers that you can bring in thousands of different apps that you use. But the actual carry, that's what's important, because as we've gotten these new context windows, which I'm going to get into a little bit more, that's what makes this all possible. In the ability now for an agent to go out and learn something, right, about you or your company without you having to teach it. So let's just say you have a scheduled agent, right? You give it information about your company, your company's goals, maybe you're looking to acquire a new client or a new customer. But the industry, whatever industry you're working at is moving fast. Let's say you have an agent that goes out every Sunday night, it pulls up the industry's most recent white papers, industry news, et cetera. And all of a sudden, when you didn't know it, it found out that you have a huge new potential, buyer moving in into your state that wasn't there before, right? And the reason that this can happen is because it's able to carry the context with you. All of those documents that you share, preferences, the memory of your recent chats, but also that can run in essentially the same context window over and over. So not only can it carry in the context that you give it according to your information, but also the persistent memory of that actual conversation. So it's going to know, right? If you have a run that goes every single day, it is going to carry that trend line with it. So it does start to turn into, oh, it's like when you hire a junior employee, after a couple days on the job, they kind of start to get it. After a couple of weeks on the job, you're like, okay, it's picking up momentum. The same thing. That's, I think, why this is a very exciting time in AI. And this, I think, is that bridge, between the simple chat bots to the fully autonomous agent. Because as much as every open-claw, efficient auto wants you to believe, we are not yet at the point where we have true autonomy in agents, where you give them a goal and they can safely go execute that goal without constant human intervention. Is it possible? Sure. If you have a very well-defined goal, if you have strict guardrails, and if you are using it in a narrow capacity, I don't think we have autonomous general agents. I think we have autonomous narrow agents that can do one very, very simple task if you give it, or a goal, if it's very, very specific, right? But what happens if the guardrails are changed? What happens if the industry's changed? What happens if your data is corrupted, right? An autonomous agent would, in theory, be able to figure those things out. We don't have that right now. And I think that this agentic context carry is that stepping stone that's going to help us get there. I've also talked about this a little bit before. Previously, I'd call that kind of like the human AI duct tape. It's all those intermediate steps in between that a human had to do, right? If you run something in deep research inside CHEBT, well, now I have to copy that. I have to go put it in a doc, and then I have to upload it to this project folder as an example. That is where this context carry in the larger context windows starts to erase all of that manual human AI duct tape that those steps that us humans working with multiple AI systems would have to continually make. Because now these agents also have right ability, right? Whereas before three to six months ago, they didn't have the ability to write to your Google Docs. They didn't have the ability to send Gmail's, right? Now they do, right? If you give the permissions and if you're feeling spicy, and you want to roll the dice. But that agentic context carry layers the schedule and the memory over that. But no one is really talking about this. I don't know. Maybe I'm too dorky and excited about where we are. But the reality is, I think that there's been this-- [CLICK] AI moves too fast to follow, but you're expected to keep up. Otherwise, your career or company might lag behind while AI native competitors leap ahead. But you don't have 10 hours a day to understand it all. That's what I do for you. But after 700 plus episodes of every day AI, the most common questions I get is, where do I start? That's why we created the Start Here series, an ongoing podcast series of more than a dozen episodes you can listen to in order. It covers the AI basics for beginners and sharpens the skills of AI champions pushing their companies forward. In the ongoing series, we explain complex trends in simple language that you can turn into action. There's three ways to jump in. Number one, go scroll back to the first one in episode 691. Number two, tap the link in your show notes at any time for the Start Here series. Or you can just go to StartHereSeries.com, which also gives you free access to our inner circle community, where you can connect with other business leaders doing the same. The Start Here series will slow down the pace of AI so you can get ahead. Narrative right now. And I'm actually going to call out a recent tweet I saw or an X. What do you call a tweet on X? Or I don't know, so this is why I call it Twitter. You can't ferv X. But there was a recent viral tweet out on Twitter. So ChatchityT had a recent integration with Starbucks. Someone said, oh, why are all of these apps? Why do they exist? It doesn't make sense, because it's going to take me two minutes at the absolute fastest to make an order on this Chatch-U-T Starbucks app integration. I'm just using this as an example. Throw in any business app that you're using inside or connector that you're using inside Gemini, co-pilot, Cloud, or Chatch-U-T. But this kind of viral incident with Starbucks. It's like, OK, well, it takes two minutes to order it via the app. And if I-- the Chatch-U-T app, but if I go into the actual Starbucks app, I can do it 20 seconds. So this is done. But I think people are missing the points, because it's not just about one app. It's not just about Chatch-U-T interfacing with one app, because in the new agent builder, as an example, the brand new agent builder, you can go to create agent all by hand. I'm literally clicking around as I do this now. You can connect 20 apps, right? You're Gmail, you're Slack, you're Notion, you're Teams, you're Outlook email, you're Google Calendar, Google Drive, whatever, right? MCP servers. You can do all those things. You can connect agent skills. You can upload files. You can manage the memory, right? So it's not just about, oh my gosh, using a single app to do a task is so much slower than it is to just do it individually in that platform or on that website. That's not what it is. It's about eliminating that human AI duct tape. It's about the 30 small human steps in between that are required. That is the context carry. Us humans have been the one carrying the context, because AI agents didn't have the ability. They didn't have the tools to do that. Now, they do. That's the thing. Yes, I can much more quickly go open my Gmail, read an email and respond to it, then a connection in Gemini, change of ET, quad, etc. Right? But what about when? There's a Google Doc that goes with it. I have to look at my calendar. Oh, there's actually three or four different emails. Oh, there's that file in my drive. There's a Slack conversation about that. Now all of a sudden, yes, it might be quicker to do all of those small tasks individually in those apps or all of those websites, but when you have to carry the context yourself manually as the human, that's where you can start, right? This has essentially been the mundane nature of knowledge work in front of a computer over the past 20 years, as SaaS and applications have exploded, but that's what we do. And that is where the true benefit of now eGentic context carry, because us humans no longer have to do the duct tape and have to remember and have to bring that context from app A to app B to app C to storage D to messaging platform E and F. The agent does it all for us in one swoop. So yes, it might take you five times as long to accomplish a goal inside of an AI agent, but that's not counting the human error, the human lookup, the human retrieval that has to happen every single step of the way in between. That's the big unlock here, y'all. But also, I don't know, I start to forget things fairly quickly, maybe it's just me. Like I literally use this concept of agentic context carry all the time, right? I was actually walking, I was actually walking to my office, right? Sometimes I record from my kind of home office, sometimes I record from my actual office, and I'm working on a cool partnership here with a group Sage. And I had a couple different email friends with travel, there was Google docs, there was all these things. And I'm like, which, you know, and I have multiple emails, right, I have multiple email accounts, certain forms, go different places. And I'm like, my gosh, like this is gonna take you a long time instead, right? Just use in this instance, use cloud, it might carry that context. But what about when you can schedule those things, right? And to say, hey, every day at, you know, two a.m., I want you to go through my email, my calendar, notion, slack, all of these things. Yeah, it might take the agent longer to do that than if you were to, but it's gonna do it on its own schedule. And it's gonna carry the context from app to app. So that's where the new breakthrough comes. It's the capabilities that have made the cross app technology possible. So here's where the unlock and the timing all comes into play, right? I love Venn diagrams, right? But this is where it's kind of the capabilities and the technology and the need have all overlapped with this perfect timing. So this is, you know, if you think of like, co-work or agentic scheduling, the features, and then the context window all coming together and exploding at the same time, right? So cloud, and traffic has really led the way of this. So now they have that one million token context window by default, right? Codex a little bit, you know, behind, although there is an experimental, one million token context window in the command line interface, but on the app, I believe it's 258,000 tokens. So what does that mean, right? If you're not too technical, that just means, right? The free version of chat to BT, last time I checked, I didn't check the free version in a while. But let's just say in 2025, it was about 8,000 token context with it, right? So now you're looking at one million. So do the math there, or, you know, or, you know, going to 208,000. Essentially, now AI models and AI agents can remember things over a very longer period of time, right? Whereas before, they essentially had very short-term memory. You would, you know, especially if you were on a free plan or, you know, early in 2024 or 2025, AI models forgot things very quickly. So especially when it came to handling your data. So if you upload a file, you're working with it, right? Maybe updating a job description and doing some research on recent law changes to make sure that your job description reflects those or something like that, right? And it's going well, and all of a sudden it's, oh, wait, it's done, right? That's because it ran over the context, but the context was used to be very small. But now as they become bigger and bigger and bigger, right? It's essentially, you're working with an AI model that has a bigger brain that's able to carry the conversation for longer. So now you know this kind of trending concept that's happening. It's not just going in and working with one app or one connector, right? It's bringing in all of the different tech stack that you have to use on a daily basis, that your company has to use on a daily basis. Eliminating all of those manual steps in between, because the reality is just like a large language model, us humans, we have a context window as well. How much time do you spend, right? Even pre-AI, it was obviously way worse. But sometimes you spend just as much time trying to either track, remember, or find certain information where it lives within your kind of SaaS database, as it actually takes to create that new business value once you do find it or reply to a certain email or to finish a certain deck or a project or fill out a spreadsheet, right? Sometimes you spend as much time just trying to retrieve that information. So that's where the multiple apps is a big context window and the new agent capabilities, those three things coming together come to play. So now that you know it's here and you know that this, I think, is the intermediate stepping stone until we have those fully autonomous agents. You need to take advantage of this scheduled agent context carry, SAC. Here's that. Step one, three steps, right? I'm gonna go quick. Connect your live data sources and your preferences first. Make sure to do this. You know, I do have to, you know, put out the normal disclaimer, right? The responsible AI person I am, right? I'm a business owner. I decide if this is safe for my organization, but you need to do the same, right? You should be doing this with shadow AI tools. You need to be doing this with approved tools. So make sure you go through the proper channels. But let's just say you have, you know, called approved or you have chat, you can see approved whatever it is, right? And you have these connectors for apps approved as well. So you need to authorize those live connectors to your, as an example, your email, your calendar, your Slack, your drive, all of those important things, your CRM, right? It's huge. Then you need to understand how each system's computer use and access works and then ensure your custom instructions and memory are updated accordingly. So first, you have to get your data sources, your preferences and your memory in line because when you talk about context carry, well, context is the base, right? We did an earlier show in the start here series on the importance of context engineering. So make sure you go back and listen to that one as well. And then also all these platforms, they support MCPs. So even if you're, you know, your app of choice, whatever you're using, does it have any of the, you know, oh, it doesn't have an app connection to Jet you can see or it doesn't have an app connection to Claw and well, chances are you just use an MCP server and get that cooked up right away. So that's step one. Step two, you need to context stuff and a dedicated memory threat. Here's a little, I wouldn't necessarily call this a cheat code per se and this is much different, right? I've, I've obviously talked taught, you know, this concept of prime prompt polish, you know, the basics of prompt engineering 101. With the context window, it doesn't throw away those best practices, but it does kind of change what can get done. So here's a little, little cheat sheet one for you for listening to this episode now for 26 minutes of running. These systems now, the context windows are enormous. You can work on it in theory for a very, depends on what tools you're calling, but you know, in Cloud Code as an example, you know, running your routines all in the same threat, a daily schedule. It's gonna hold, right? I have some that run every single day that started when it first came out, you know, two ish weeks ago and they're not even close to hitting the context window, right? So at a million tokens, the agent can hold just weeks of regular usage working memory at once. So here's what I like to do. Connect everything to one threat, right? These all work a little differently, right? You know, codex works a little bit differently than Cloud Code works a little bit differently than these brand new, you know, ancient builders, essentially that we got from from chat, CVT and from Google Gemini, but essentially, if you do connect things on a thread by thread or a folder by folder basis, have one where you just context stuff, right? Put all your context in there at once. And then that can be your daily drive 'cause the good thing is, is then also, if you need to take it into a different direction, you can just fork that threat at that point, right? So you at least have this unified base where you can every single day, right? Have it be the one that brings you your morning triage, the one for your, you know, most common day to day tasks but aren't necessarily specifically project base that require a lot of different directional feedback, et cetera, right? So from that, you can iterate on the reasoning until it matches your standard. That's the big thing. You need to context step two is technically context stuff and iterate as well. Well, iterate will actually get a little bit more into step three, sorry. Hey, hey, jump. ahead of myself. So step two, context stuff and context stuff and a dedicated memory thread, and then step three, iterate with chain of thought. If you listen to the show at all, you know how important this is. You saw this in my little demo that I did yesterday on Codex, right? You need to understand how these models work because they are generated. They are not deterministic. They're going to work slightly different each time. So you can't just run something once, right? Especially as these capabilities become greater and greater. A lot, I see a common mistake a lot. People will run something once, and I think, "Oh, yeah, this is great. Let's put it out in production." Okay. Well, that's could be dangerous, especially if you're doing something public-facing or client-facing. You probably wouldn't want to do that just yet, right? Because there's always going to be edge cases. You can run this same schedule run every single day for seven days, and it might two of the days, it might call the tool that you didn't want it to, or maybe it's not calling a tool that you are telling it to. So you really do have to review the chain of thought and iterate. So what that means, both systems, you can kind of have some level of observability, traceability as they go by looking at the system. So if they're scheduled, you can go, you know, usually you might click on, you know, might say, "Oh, thought for one hour," and you can click that, and then see every single tool, every single step, and kind of get how that schedule will run or that co-work session, how it works. And you can kind of trace it the same way, right? When you think of, like, Baff, right, where you had to show your work, I don't understand, like, that you've common core Baff stuff, right? But back in my day, right, we just, I don't know, wrote down the numbers at a college, right? But you had to show your work. So you should always be checking the work of your co-working run of your scheduled agents task, and then iterating it. You need to refine the prompt, make it better. And then once it is kind of, quote, unquote, ready for production, and you've built those guardrails in place, that's when you can save it as a routine or a schedule of automation. Then once refined, that is that hidden workflow. So it is those three steps that really allow that agentic context theory. Again, faster. Step one, connect your live data sources and preferences. First, step two, context stuff in a dedicated memory thread. And then step three, iterate with chain of thought reasoning before you put it out into production. But then schedule that thing and take advantage of this stepping stone that I think is going to be huge. And the time is now. So like I said before, this is not the final destination. I think that truly autonomous agents with persistent memory are the next big deal. But we that could be far off. Who knows? I mean, maybe we'll have that, you know, next month, but it could still be another year, two years or more. And so we actually see autonomous agents that you can give them a goal and they don't really require much else. This is the now or the next. So understand, and really push this agentic context carry the leaders pulling ahead this quarter are building scheduled context on autopilot, not just, you know, better one off prompts, not just, you know, sharing skills within your organization. That's no longer enough, right, to really be pushing in your space. So pick one recurring task this week, take it through those three steps and then deploy your first kind of hidden workflow inside of it. That's taking the advantage of scheduled agentic context carry. I hope this was helpful. Y'all, if it was, please go to start here series.com. That's going to take you straight to a side up form to get access to our community for free the everyday AI inner circle. And then in the start here series space, you can go find every single start here series podcasts, read every single start here series newsletter all in one space connect and network with others who are doing the same. All right, I hope this was helpful. Thanks for tuning in. Hope to see you back tomorrow and every day for more everyday AI. Thanks y'all. And that's a wrap for today's edition of Everyday AI. Thanks for joining us. If you enjoyed this episode, please subscribe and leave us a rating. It helps keep us going. For a little more AI magic visit your everyday AI.com and sign up to our daily newsletter so you don't get left behind. Go break some barriers and we'll see you next time.