2 ms·
It's hard to directly compare, but 3000 interactions should be very, very high. Think of each of these 3000 interactions as you supplying a prompt that potentia
by NathanKP 1y ago
It's hard to directly compare, but 3000 interactions should be very, very high. Think of each of these 3000 interactions as you supplying a prompt that potentially runs for 3-5 minutes of Kiro iterating away on writing code. With appropriately sized prompts (most likely aided by spec mode), you could write a ridiculous amount of code.
For reference 3000 interactions * assumed 3 mins of AI work per interaction / 60 mins per hour / 8 working hours per day equals 18.75 working days of nonstop back to back AI coding. Typical month has 20-23 working days. But realistically you likely won't be using Kiro nonstop all day back to back, so 3000 interactions per month should more than cover your work month.
- steve_adams_86 1y agoThanks, this is exactly what I wondered. In practical terms I can’t imagine hitting that limit. It’s a bit more than I pay in CAD, but I’d pay quite a bit more just to stop hitting the limits I have with Claude, even if the rest of the service was identical. It’s a pain. My usage is also very bursty so I spend several days getting no usage, then repeatedly hit limits while I brainstorm and spec things out. I’m thinking out loud here in case it’s useful feedback. It seems like a great pricing schemes for my use case.