The tool I have quietly run my work week on is now open source.
Kiro Crew is a persistent agent workspace built on Kiro. I have been on the internal version since April, and it changed how I think about what AI at work actually is.
A while back I wrote about terminal productivity as a TPM and how far the command line can take a non-engineer. This is the next chapter: the terminal now runs itself.
I am a technical program manager, not a software engineer. My setup today: around a dozen scheduled jobs work on my behalf. They prepare my morning brief, watch releases and metrics, keep task trackers and reviews in sync, and speak up only when something needs me. The agent carries months of memory. My projects, my writing rules, the decisions I have already made. I never re-explain anything. It is not a chatbot I visit. It is a colleague already working when I arrive.
Under the hood it is one always-on gateway on my machine: a scheduler for the standing jobs, persistent memory that survives every restart, subagents for parallel work, and a lessons system that saves every correction I make so it never repeats a mistake. That last part matters more than any of it.
