Menu

1 / 4

AWS's Kiro Bots Start in Trust Mode, and Crew's Default Sandbox Leaves ~/.ssh Visible

DEV Community: aws·Gabriel Anhaia·11 days ago
#FNuPnwbE
#devtoaws#devto#dev#crew#kiro
Reading 0:00
15s threshold

Book: Observability for LLM Applications

Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go

My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools

Me: xgabriel.com | GitHub

On November 5, AWS's Kiro team made bots generally available in Kiro Crew ( InfoWorld ). A bot is a named agent that owns one ongoing job, like triaging issues or watching CI, with its own memory, its own worker sessions and an optional schedule.

The launch post shows careful examples: a deployment bot that needs your approval before each change, and a review bot that "can leave comments and request changes, but it can't approve or merge." Those are bots you configure that way. A new bot doesn't start like that.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.