I have a Kiro bot whose whole job is helping me write this blog. But if I'm honest, about 75% of my work happens somewhere else, in the standard bot I talk to every day. A few specialists cover the rest.
In my last post, Persistent self-learning systems and my productivity, I said I'd write more about my flow and the conductor pattern. This is that post, sort of. Mostly it's about how my workflow keeps changing, and how much of that depends on the tools.
Not that long ago, everything I did with AI happened in a session. I'd open the Kiro CLI or ChatGPT, work through something, and move on. While OpenClaw was intriguing, I never really tried it. Grokbot was one of the first tools I tried that gave you a bot with memory, something that sticks around. I also tried Muse. I liked the UX and the integrations (I used it from the app and from WhatsApp), but I never felt like I had sufficient control. But for the last three months or so, most of my work has happened inside Kiro Crew.
Even with Crew my setup has changed. I started with sessions organized around the PARA method, the same Projects and Areas I use in Obsidian. That still works. But most of my day now runs through one primary bot. I use it to manage my weight, plan trips, like the one to Africa, and call other agents when something needs more depth. Health is one example of where my workflow changed. I used to track it in a dedicated session, but once I started using bots (they just got announced but have been in the product for a while), I realized I didn't need a separate channel. It's part of my day-to-day life. I weigh myself every day and check my diet, so it moved into the main bot. That's the thing I like about the main bot. It's all there. All my thinking, all my interactions.
Specialists need to earn their place. Finances started in the main bot too, until I decided I wanted my finances to have their own space, unadulterated by anything else. That bot is called "Jerry Maguire". (Show me the money!) The blog bot is the same idea. I want my writing in its own memory space.
So what happens to sessions? One way to think about sessions and bots is to apply the PARA approach. Project work and ad hoc tasks remain as sessions, anything I return to repeatedly moves to bots. The bots are memory-scoped spaces for long-running, never-ending sessions. What I like is that I can switch between project work and bot work quite easily. The thing to note is that I don't have a bot per area, at least not right now. I have a bot that covers most of my areas and the ones I want separate get their own. I suspect this will get refined over time as the capabilities of the underlying system change.
In a future post, I will write about sessions and the conductor pattern.
While Kiro Crew is the hero of this post, in the end it's about how you work. And that keeps changing.
Disclosure: I run the Kiro team at AWS and recently tweeted about how I use bots.
Post cover image generated with Gemini
