Kiro Not Accepting Requests: Improperly Formed Request

by Admin 57 views
Kiro Stopped Accepting Requests

Hey everyone,

I'm writing to discuss a problem I've encountered with Kiro after the most recent update. It seems Kiro stopped accepting requests, consistently returning the error message: "An unexpected error occurred, please retry." This is happening despite having ample credits (600 out of 1000) as a pro user. I am working on a Macbook Pro M1 running macOS Tahoe 26.2, with Kiro version 0.5.35. It's quite frustrating when your Kiro development workflow gets interrupted like this, especially when you're trying to be productive. This issue is particularly disruptive when you're relying on Kiro for quick checks and assistance. The expectation is that with a valid subscription and available credits, the tool should function as intended. Let's dive deeper into the specifics of the issue and what I've tried so far to troubleshoot it.

Bug Description

After updating Kiro, every request I make results in the same error: "An unexpected error occurred, please retry." This happens regardless of the prompt or the file I'm working on. It's like Kiro has suddenly decided to go on strike! Even simple prompts that used to work flawlessly are now met with this error message. I suspected it might be related to the specific prompts I was using, so I tried a variety of different queries. I also tried different files to rule out any file-specific issues. However, the problem persists across all my projects and prompts. This leads me to believe that the issue is not related to the content of my requests but rather to a more fundamental problem with the application itself. This kind of Kiro bug is a major roadblock, preventing me from leveraging the tool's capabilities effectively.

Steps to Reproduce

To reproduce this issue, simply submit any prompt to Kiro after the latest update. For example, I tried the following prompts:

  • "Check how we are handling theme selection in the theme dropdown in general settings section."
  • "The theme selection is not working in the theme dropdown, the user is not able to choose the light mode."

I've also tried other prompts related to different files, but the result is always the same: the dreaded "An unexpected error occurred, please retry" message. It's incredibly consistent, which, while frustrating, at least makes it easier to identify as a widespread issue. The fact that this happens with such simple prompts suggests the problem lies in the core functionality of Kiro, not in complex or unusual requests. This reproducible Kiro error makes it easier for developers to pinpoint and address the root cause.

Log Extracts

Here are some relevant extracts from the Kiro log:

[Chat UI Telemetry] Sending event: {type: 'messageSubmitted'}
VM23:17 [Chat UI Telemetry] Sending event: {type: 'contextProviderUsed', providerType: 'currentFile'}
workbench.desktop.main.js:523 [Extension Host] rejected promise not handled within 1 second: ValidationException: Improperly formed request.
Xms @ workbench.desktop.main.js:523
$logExtensionHostMessage @ workbench.desktop.main.js:523
...
workbench.desktop.main.js:523 [Extension Host] stack trace: ValidationException: Improperly formed request.
	at de_ValidationExceptionRes (/Applications/Kiro.app/Contents/Resources/app/extensions/kiro.kiro-agent/dist/extension.js:582392:25)
	...
workbench.desktop.main.js:547 [kiro.kiroAgent]Improperly formed request.
...
workbench.desktop.main.js:547 ValidationException: Improperly formed request.
	at de_ValidationExceptionRes (/Applications/Kiro.app/Contents/Resources/app/extensions/kiro.kiro-agent/dist/extension.js:582392:25)
	...
workbench.desktop.main.js:34   ERR An unknown error occurred. Please consult the log for more details.

The logs clearly indicate a ValidationException with the message "Improperly formed request." This suggests that there might be an issue with how Kiro is formatting or validating the requests before sending them to the server. The stack trace points to specific files within the Kiro extension, which could be helpful for developers in identifying the source of the error. The "ERR An unknown error occurred" message further underscores the severity of the problem, indicating that the application is unable to handle the exception gracefully. This log information provides valuable clues for diagnosing and resolving the issue.

Expected Behavior

Ideally, Kiro should process my requests without any errors, providing relevant and helpful responses based on the prompts I submit. I expect it to function as it did before the update, seamlessly assisting me with my coding tasks. The expected behavior includes:

  • Accepting and processing prompts related to code analysis, debugging, and code generation.
  • Providing accurate and relevant responses based on the context of the current file or project.
  • Functioning without errors or unexpected interruptions.
  • Utilizing my available credits appropriately.

When Kiro functions correctly, it significantly enhances my productivity and streamlines my workflow. However, the current issue prevents me from realizing these benefits, making it essential to find a solution quickly. The expectation is that the tool should be reliable and consistent in its performance, providing a stable and dependable coding assistant.

Conversation ID

The conversation ID for one of the failed requests is: 13973c66-1cdc-45ba-a78c-69bd9341861e. This ID may be helpful for the Kiro team in tracing the specific request and identifying any issues associated with it. By examining the conversation logs associated with this ID, developers may be able to gain further insights into the cause of the error and develop a targeted fix. This level of detail is crucial for resolving complex issues and ensuring that the application functions smoothly for all users.

Additional Context

I've included another instance of the log output below for reference:

[Chat UI Telemetry] Sending event: {type: 'messageSubmitted'}
VM23:17 [Chat UI Telemetry] Sending event: {type: 'contextProviderUsed', providerType: 'currentFile'}
workbench.desktop.main.js:523 [Extension Host] rejected promise not handled within 1 second: ValidationException: Improperly formed request.
Xms @ workbench.desktop.main.js:523
$logExtensionHostMessage @ workbench.desktop.main.js:523
...
workbench.desktop.main.js:523 [Extension Host] stack trace: ValidationException: Improperly formed request.
	at de_ValidationExceptionRes (/Applications/Kiro.app/Contents/Resources/app/extensions/kiro.kiro-agent/dist/extension.js:582392:25)
	...
workbench.desktop.main.js:547 [kiro.kiroAgent]Improperly formed request.
...
workbench.desktop.main.js:547 ValidationException: Improperly formed request.
	at de_ValidationExceptionRes (/Applications/Kiro.app/Contents/Resources/app/extensions/kiro.kiro-agent/dist/extension.js:582392:25)
	...
workbench.desktop.main.js:34   ERR An unknown error occurred. Please consult the log for more details.

This additional log output reinforces the consistency of the error and provides further evidence of the ValidationException. The repetition of the same error message and stack trace across multiple attempts indicates that the issue is not intermittent or random but rather a persistent problem that requires immediate attention. By providing this additional context, I hope to assist the Kiro team in quickly diagnosing and resolving the issue, ensuring that the application returns to its normal functionality as soon as possible.

I hope this detailed report helps in identifying and resolving the issue. Let me know if you need any further information.

Thanks for your time and attention to this matter!