✅ - I notice a bug or I dont know if you encounter this but when I use steering

[blazing plaza]

I was developing a new project using kiro and start experimenting on steering. now here is that I notice

1. when you mention the steering like make them understand ofcourse they need to read it right but if kiro failed to generate like select model feature and lets say I click the same model. kiro then proceed to re read the steering file which is a good thing. but would that be possible to let kiro know at the first of conversation ? because repetitng reading the steering use also token especially when the steering is long, kiro need to re understand it again which burn token and re read the task which burn token and then read what its current taks which burn token and start doing its taks which is sometime it burns a lot of token

2. when you have existing steering file and you decide to update it, kiro will become wild card more where it vibe code every thing dont follow the steering which is frustrating because every conversation. kiro need to read the steering files. im against to the thing that you need to click the refine just to make kiro understand that we have new steering which infact kiro needds to understand that we change something on it and we start the conversation it should read the file since kiro promote automation

3. only specs read the steering file but if you do the vibe code it will never read the steering unless you told so.

4. Agent hook is kinda meh for me. not gonna lie, there is no repetive task if I combine specs and steering. also the most scary part for this agent hook is the file on save, its a token eater, you see I have this existing giant project and I use the agent hook to hear every file save, its say I ask kiro to do prettier and linting check so there is no need to do the husky work at pushing the branch. but after I just ask kiro to change stuff after the command I reach the limit for today. so the big projects are frustrating to kiro because there is a lot of happening, Agent hook is like a token eater that eats token

ok, continuation, since Im from asia and pricing to dollar is very expensive for us and as a future customer, Im raising this concern so there is no token eater that could make my tokens last in 1 day.

5. I also want to report this feature, there is this feature in kiro which is a trust command right, now if you add rm in it which is also a dumb move of mine but im coding at 3am that time so what you expect, then I forgot that I trust command rm, I move to the project that I been working on and I just ask kiro to rework a certain fuction. it freaking remove al the migration files and other code because kiro thought my code its bad. I think its better to have a safety net for this by asking if you want to remove this again even its on the trust command but if people watns to push it further, they can just toggle the yolo mode to allow the deletion

6. git branch is a live saver in development in kiro, since kiro is good at automation i think its a killer feature that every task that you create there is automatically create a branch for you because I notice most of the vibe coders they just start task and then after that task, start again but once kiro start hallucinating. the progress is at risk 100% because you need to rework everyhing which will lead a frustration

7. showing the token at the chatbar is also a feature that needed to integrate so we know if its our last prompt for today. because its frustrating that your on the flow of debugging and you found it then you ask kiro to fix it because you know its from different file. kiro will start change file and at the middle it stop because it hit the limit or the seassion is at max. which really piss me off beause there is changes now and I need to manually revert it so it work perfectly again

[tacit dove]

Until kiro staff response, read this https://chatgpt.com/share/6885b8a7-9bb0-8000-9ee3-9c81660a5c5e

[woeful pine]

Thank you for your detailed feedback about Kiro's steering functionality and token usage concerns. We appreciate this kind of detailed feedback as it helps us improve the product.

I'd like to note that we recently released version 0.2.38 (September 4, 2025) which includes several improvements that address some of your concerns:

• Enhanced Tool Call Recovery: We've improved how Kiro handles repeated failures to protect your usage limits and prevent loops
• Faster Response Times: We've optimized request handling for more efficient interactions
• Improved Session Management: Enhanced backend processing to reduce interruptions and allow for longer continuous work sessions
• Model Update: Claude Sonnet 4 is now the default model with improved performance across all interactions

Please ensure you're running the latest version of Kiro to benefit from these improvements. You can find more details about these updates in our latest changelog.

If you continue to experience issues after updating, please don't hesitate to open a GitHub issue so we can investigate further.

I'll mark this thread as answered, but we appreciate your continued feedback as we work to improve Kiro. Feel free to open a new Discord thread, and I would recommend to keep a thread to one particular subject/concern/issue for the community to better find and respond to. Thank you!

[undone vault]

✅ - I notice a bug or I dont know if you encounter this but when I use steering