Skip to content

Kiro/Amazon Q CLI - Is there any way to resume the task on the specific part it stops?

0

I know that Kiro and Amazon Q are under pressure. But unfortunately it's completely unusable right now.. so for example, I'm going through a task implementation, and thank I get the throttling error message. If I retry, It goes all the way to the start of the task, so I get in an endless loop.

I tried changing the models but still fails both on 3.7 or 4.0

ps - I got the amazon q business pro version, so I expected better handling in this situation

asked a year ago693 views
1 Answer
0

Yes, Amazon Q Developer CLI now offers conversation persistence features that can help you resume where you left off. With the q chat --resume command, your conversations are automatically saved by working directory, allowing you to pick up exactly where you left off when you return to a project.

Additionally, Amazon Q Developer has added two specific commands to give you more control over conversation states:

  • /save - This allows you to explicitly save the current conversation state
  • /load - This lets you restore a previously saved conversation

These features are designed to help manage multiple conversation threads related to different aspects of your project. You can save a conversation about one feature or task, switch to something else, and then load the previous conversation when you're ready to continue.

This should help with your issue of having to restart from the beginning after encountering throttling errors, as you can save your progress before potential throttling points and then resume from there if needed.
Sources
Exploring the latest features of the Amazon Q Developer CLI | AWS DevOps & Developer Productivity Blog

answered a year ago
  • Thanks - what about Kiro?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.