I enter the bridge of my ship, the Kiro Enterprise. I see my crew ready for my command.
The agent scheduler welcomes me with a report on all the tasks I was working on yesterday and their state today. Prototyper is working really hard on its new project. Builder greets me and asks, “What is next, Commander?”
The Maintainer, the Code Reviewer, the Deployer, and the Security officer are all waiting. I look out the window, ready to go to the next frontier.
This sounds like a dream, right? It is like having your own crew waiting for you, like if you were in command of the USS Enterprise in Star Trek. It feels like science fiction, but now it is no longer fiction. This is now possible with Kiro Crew.
In this article, I am not going to explain the specifics of Kiro Crew and all its functionality. I am going to explain how it works for me, how I find it useful in my daily work, and why this is a tool I have been waiting for for almost half a year.
Why Kiro Crew works for me
I have been using Kiro CLI since the start of 2026. Over time, I have gained more confidence in the quality of its code and the guardrails I have with Kiro. That confidence was enough to make me move from the IDE to the CLI. I stopped watching the code while Kiro was running. I still review the code, but I trust the CLI enough to let it work through a task without me having to check in the code for every step.
On top of that, I have been multiplying my output. Instead of having one IDE, I now have five or six Kiro CLI sessions open at the same time, across different terminals. Each can be working on a different project, or sometimes on different parts of the same one. The CLI allows me to do this while having lower resource consumption.
I also use Knowledge (a Kiro CLI feature) a lot as an internal brain or memory for my previous sessions. But I want to take this to the next level. There are still many things missing from my current setup that I feel can take me to the next level.
This is what Kiro Crew fixes for me. Kiro Crew has a pool of sessions that acts more or less as an agent manager. For me, this is a game changer. I can have different workspaces in different folders. I can even have a folder containing multiple workspaces working on the same area. Here are a few things that I find really useful in Kiro Crew.
Scheduled tasks
This is important to me because I have tasks that I run every day and every other day. Before I have to do them manually or through some type of automation in AWS. Now I can just have them in the scheduler.
I am also working on a morning scheduler that will check the open pull requests across my repositories and tell me whether anything needs my immediate attention, including vulnerabilities I need to fix.
Artifacts
I often work with Kiro on documentation, fix grammar from articles and, of course, to generate Specs. Now with Kiro Crew I can then save that work as artifacts. This is useful in a working environment, where reports and summaries are good things to preserve as artifacts and read elsewhere.
Knowledge
I use the Kiro CLI Knowledge tool extensively, and it is a feature that I love. Kiro Crew has its own Knowledge capability as well. I can view it as a node graph and import content from different places. This feels like taking everything I already had to the next level. I now have a visual way to see my Knowledge, which I didn't have before.
Apps and agent capabilities
Kiro Crew also has apps like Issue Radar and a Task Runner. You can create your own apps and attach them to Kiro Crew too!
I created a funny Flappy Bird version of Kiro that I recently open-sourced. I can play Flappy Kiro while Kiro Crew is building my stuff, which is really cool.
Kiro Crew also has agent capabilities. It includes terminal capabilities, agent templates, MCPs, skills, steering, hooks, and prompts inside Kiro Crew itself. This works well for me and my other product: Kiro Hub, which I have been trying to integrate with Kiro Crew. That is something I am going to work on next, so I can have the +10,000 resources from Kiro Hub as a registry available for Kiro Crew.
Voice
One feature I have been waiting a long time for is voice. I was mainly looking for speech-to-text inside the terminal, which is difficult to do, but I got more than just that. Kiro Crew also supports text-to-speech, so Kiro can talk back to me. This makes consuming the artifacts such as Markdown documents, specifications, and similar content way much easier. I no longer have to read long documents, now I can just listen to them and all within Kiro Crew.
Channels and remote access
The other thing I want to mention is channels. You can connect Kiro Crew to Slack, Telegram, Discord, and Microsoft Teams. I have it connected to my Discord.
Kiro Crew can also be deployed to an EC2 instance or another remote machine. It has a CloudFormation stack that makes it easier to deploy, along with a few commands that I am going to add here:
# Check prerequisites and AWS access
kirocrew cloud doctor --region eu-central-1
# Install Kiro Crew
kirocrew cloud launch --region eu-central-1
Trust and permissions
The other thing I want to mention is trust. I talked earlier about how I moved from the IDE to the CLI because I started trusting the process more. I would usually allow reads, writes, and probably the web browser tools, but there were certain tools and commands I would never allow.
I'm used to allowing reads, writes, and similar operations in Kiro CLI. At the beginning, Kiro Crew kept asking for all these permissions and I couldn't find a way to allow the tools like in the CLI.
Kiro Crew comes with system security settings, including built-in tool approvals and denied commands, which are really, really good. But I did ignore this initially.
Then I started thinking: if these guardrails are good, why am I not trusting them? Why not give more trust to Kiro Crew and start allowing more tools, to the point where I trust all.
I started doing that. I enabled broader trust and had placed my actual trust in Kiro Crew guardrails. The trust I have in Kiro and Kiro Crew is helping me go faster while remaining secure.
And more
I could keep going on and on. The more I use Kiro Crew the more features I keep discovering. Like the prompt improver, the worlds app, auto-generate skills from sessions, remote crew (here it comes another use case for my Raspberry Pi), and all the monitoring in place which I love.
The next frontier
What is next for my crew and me is integration with existing tools. I would love to integrate Kiro Hub as a registry for the agent capabilities, making it easier to discover steering files, hooks, agents, and perhaps even crews.
I am slowly migrating from Kiro CLI to Kiro Crew, It is still a work in progress, but I am enjoying every step of it. If you are using Kiro Crew or are interested in trying it, share your experience in the comments.
You can download Kiro Crew from the official site or from its GitHub repository.
Now I have to get back to my Kiro Crew and prepare for our next adventure.
🖖 Live long and prosper.
Top comments (0)