I know that I cannot be the only person who gets so frustrated with the permission requests. I will tell it to always allow a PowerShell command for all workspaces, but then Kiro will immediately make the same call and ask permission again. This cannot be that hard to fix.
I have noticed that if you add a folder to the existing workspace while in the middle of a chat session, it will close that session and you cannot load it back from the history. It does not even show. This is really distressing when you have been diving into some code for requirements and it needs code from another folder.
The latest version of the Kiro IDE (1.0.116) has gotten very stupid when it comes to writing the tasks.md format. It seems to always get it wrong now and I have to prompt it. It then finds an existing one that is in the correct format, lets me know it made a mistake, and proceeds to fix it.
Is anyone else seeing this lately?
It doesn’t mean that much, but 1.089 and 1.0116 seem to have forgotten that they should create the dependency graph in the tasks. I’ve had to remind it a few times.
Anyone else seen any oddities like this?
Using version 1.0.89. Is anyone else seeing the system ask for allowance to do things much more than it used to in previous versions? They have changed the trust system and it’s a bit confusing now.
So, the Kiro IDE does not automatically prune old sessions. I was trying to figure out why my drive is down to 1.9 gig of space. There are 12 gig in folders out here from old sessions that I have finished on various projects.
Kiro needs some way to let us prune those old sessions.
Has anyone tried MemoryLake with the Kiro? I have been using the memory MCP, but was looking for something more robust.
I click to start a task in the tasks.md and every once in a while, when Kiro goes to start the task, this is the interaction. It marks the task with the "-" when I click on it and then thinks it has been skipped. The IDE gets confused.
**User:**
Execute Task: 7.2 Remove IKeyCloakService registration and KeyCloak configuration
---
**Assistant:**
The task system has task 7.2 marked with `[-]` in the tasks.md (skipped status), so it's not appearing as a normal task. Let me look at what's needed and handle this directly by delegating to the subagent.
The task 7.2 is marked with `[-]` in the markdown (skipped), meaning it's already been intentionally skipped. Let me verify this by reading the relevant section in the tasks.md:
Task 7.2 is marked with `[-]` which means it was intentionally skipped. However, the user is explicitly asking me to execute it now. Let me proceed by delegating to the subagent.
Has anyone else tried the Qwen3 model in Kiro? I used it for a while today on some tasks in a spec session. It seemed to go completely off the rails when working on an integration unit test.i was wondering what experience others might have had.
One thing that is driving me crazy lately is that Kiro will delegate everything to a spec-task-execution subagent. It's like a black box and you cannot see what's going on. It gets confused, because I click to start a task and it delegates and it then thinks it is already complete before it has ever executed anything.
This really started happening when they introduced the parallel task execution. I don't think this is working well right now.
I haven’t played FS25 for a while until this weekend. I used AI for one of the first times. I had been using drive assist. Anyway, is it just me or is the AI in this game all whacked out? I set an AI worker off to plow a field and after a couple of passes, I come back and see it going over what it has already plowed. Or it will do a couple of passes and then go back to the start and make a partial pass on the headlands.
I am seeing what appears to be a timing issue today when working in Kiro IDE. I click on the "Start task" above a task. The UI immediately changes the task to [-] showing it is in process, but as the AI begins to work on it, it thinks it is already complete. I have seen this message a couple of times this morning.
>It looks like task 4.3 is already marked as completed (with the [-] marker in the tasks.md, which indicates it was skipped/partially done).
Has anyone else seen this behavior? It is not a blocker, of course... just an inconvenience.
Is anyone else using v0.12.155 seeing the "Start task" options disappear when you run a task and not come back after it is complete? I know that I could just type in the prompt and tell Kiro to run the next task, but having the clickable option is just easier.