Troubleshooting - IDE 1.x - Docs - Kiro Loading image... Product * About Kiro * IDE * CLI * Web * Mobile * Crew * Pricing * Downloads For * Enterprise * Startups * Students Community * Overview * Ambassadors * Discord * Events * Powers * Shop * Showcase Resources * Docs * Blog * Changelog * FAQs * Report a bug * Suggest an idea * Billing support Social * * * * * * * English Site Terms License Responsible AI Policy Legal Privacy Policy Cookie Preferences English Loading image... * Apps * CLI * Web * Enterprise * Pricing * Docs * Community * Resources SIGN IN DOWNLOADS Loading image... Get Started Installation Authentication Your first project Models Overview Available models Reasoning effort Features How Kiro works Specs Steering Hooks MCP Permissions Custom agents Agent Skills Powers Cloud sessions Compaction Kiroignore Checkpoints and rewind Built-in tools Configuration scopes IDE 1.x What's new in 1.0 Setup & First Run Editor Chat Experimental Troubleshooting 0.x reference CLI What's new in 3.0 Setup & First Run Terminal UI Chat Voice mode Headless mode ACP Auto complete Experimental 2.x reference Crew Quick start Installation Running 24/7 Chat Agent Capabilities Features Interfaces Apps System & storage Configuration Security Troubleshooting Web Setup & First Run Identity Center Connect your repositories Working with the agent Autonomous mode Automations Memory Configuration Sync Sandbox Mobile - Preview Overview Commands and Reference CLI commands Slash commands Built-in tools Exit codes Settings Billing Overview Managing your subscription Upgrading your plan Downgrading your plan Cancelling your plan Purchasing add-on credits Managing your payments Managing usage notifications Managing your taxes Contacting billing support Deleting your account Related questions Enterprise Concepts Onboarding quickstart Connecting your identity provider Deployment options Subscribe your team Manage subscriptions Governance Monitor and track Settings Managed updates Billing IAM Supported regions Privacy and Security Overview Data protection Code references Compliance validation Infrastructure security IAM permissions Firewalls, proxies, and data perimeters VPC endpoints (AWS PrivateLink) Guides Overview Language support Learn by playing Migration Migrating from Q Developer Migrating from VSCode Upgrading from Q CLI * Docs * * IDE 1.x * * Troubleshooting Copy page View as Markdown Troubleshooting Copy page View as Markdown This page covers installation issues, network connectivity, authentication, shell integration, and MCP server problems. For post-upgrade migration steps (sessions, hooks, permissions), see What's new in IDE 1.0 . Kiro Installation Issues macOS: Kiro is damaged and can’t be opened On macOS, you may encounter this error when trying to open Kiro: Kiro is damaged and can't be opened. You should move it to the Trash. This pop-up is due to a false positive in macOS security features. To resolve this error: * Go to System Settings → Privacy & Security and click Allow or Open anyway for Kiro. * Drag Kiro.app to your desktop, and then drag it from your desktop to the Applications folder. * Restart your computer. * Open your terminal and run: sudo xattr -d com.apple.quarantine /Applications/Kiro.app Network connectivity issues Some users can connect but others cannot If Kiro works for some users in your organization but not others, the issue is likely related to network configurations specific to the affected users. A common cause is TLS inspection — corporate firewalls performing TLS inspection may block or interfere with connections to Kiro endpoints. Symptoms * Kiro IDE shows "No profiles available" after successful sign-in * Client logs show Failed to retrieve profiles {"error":""} (empty error string indicates a network-level failure) * Sign-in completes but chat and code assistance are unavailable Verify connectivity Affected users can test connectivity directly: bash curl -v https://runtime.us-east-1.kiro.dev curl -v https://management.us-east-1.kiro.dev A successful TLS handshake (even with an HTTP error response) confirms network connectivity. A connection timeout or TLS error indicates a firewall or proxy issue. If these commands fail, review the firewall allowlist and work with your network team to ensure the required endpoints are reachable from the affected users' network path. Authentication issues Browser redirect failures during authentication If while authenticating with Kiro you are not redirected to the browser, try these platform-specific solutions: Windows Run Kiro with logging enabled to identify potential issues: * Open Command Prompt as administrator * Run the following command (replace with your actual Kiro installation path): C:\path\to\app.exe --enable-logging * Check the logs for any errors * If you see access denied errors, ensure your user has administrator permissions to run the app macOS Use the developer tools to diagnose the issue: * Open Kiro * Go to Help → Toggle Developer Tools * Navigate to the Console tab * Observe any errors reported during the sign-in process * If the error indicates a missing dependency, ensure it's available in your PATH * One common issue is the missing ioreg command * Verify ioreg is included in your PATH variable: bash echo $PATH which ioreg * If ioreg is missing, it's typically located at /usr/sbin/ioreg AWS IAM Identity Center issues Subscription status not active If you see an error There was an error signing you in when attempting to authenticate with Identity Center, ensure your subscription status is active. IAM Identity Center authentication requires an active subscription. Kiro profiles are currently supported in the US East (N. Virginia) and Europe (Frankfurt) regions. Session duration and timeouts Identity Center sessions have a default timeout of 8 hours, which means you'll need to re-authenticate periodically. To extend session duration, administrators can configure longer session timeouts. For detailed configuration instructions, see the AWS documentation on configuring user session duration . Shell integration issues Shell integration connects Kiro to your terminal, enabling automatic command execution and result processing. Without it, you'll need to manually copy-paste terminal outputs. Quick fix: "shell integration unavailable" * Update Kiro : Command Palette ( Cmd + Shift + P / Ctrl + Shift + P ) → Kiro: Check for Updates * Enable Integration : Command Palette ( Cmd + Shift + P / Ctrl + Shift + P ) → Kiro: Enable Shell Integration * Restart : Quit and reopen Kiro Manual installation If automatic setup fails, add to your shell config: Zsh ( ~/.zshrc ): bash [ [ " $TERM_PROGRAM " == "kiro" ] ] && . " $( kiro --locate-shell-integration-path zsh ) " Bash ( ~/.bashrc ): bash [ [ " $TERM_PROGRAM " == "kiro" ] ] && . " $( kiro --locate-shell-integration-path bash ) " Fish ( ~/.config/fish/config.fish ): bash string match -q " $TERM_PROGRAM " "kiro" and . ( kiro --locate-shell-integration-path fish ) PowerShell ( $Profile ): powershell if ( $env :TERM_PROGRAM -eq "kiro" ) { . " $ ( kiro -- locate-shell-integration-path pwsh ) " } Kiro Stuck in 'Working...' Status on Terminal Commands or Kiro Does Not See Terminal Output If Kiro is unable to read terminal output, gets stuck in Working... status, or you see strange characters and formatting issues, this is typically caused by shell customizations that interfere with terminal integration. Common culprits include customizations like bash-it on bash or Oh My Posh on zsh, and themes such as Powerlevel10k/9k. Powerlevel10k theme users If you're using Powerlevel10k theme, add this line to your .p10k.zsh file: bash typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION = true Alternatively, you can also disable these customizations when running in Kiro. zsh ( ~/.zshrc ): bash if [ [ " $TERM_PROGRAM " == "kiro" ] ] ; then # Leave empty else # Your themes or customizations ZSH_THEME = "powerlevel10k/powerlevel10k" fi Fish shell users If you're using Fish shell and experiencing terminal output issues, you may need to manually add Kiro to the existing shell integration script. The Fish shell integration file is located at: /Applications/Kiro.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/common/scripts/shellIntegration.fish By default, the integration script only checks for "vscode": bash status is-interactive and string match --quiet " $TERM_PROGRAM " "vscode" and ! set --query VSCODE_SHELL_INTEGRATION or exit You need to update it to include "kiro" as well: bash status is-interactive and string match --quiet " $TERM_PROGRAM " "vscode" "kiro" and ! set --query VSCODE_SHELL_INTEGRATION or exit Windows issues Updates disabled due to administrator installation On Windows if you experience this error: Updates are disabled because you are running the user-scope installation of Kiro as Administrator. This occurs as Kiro does not support system-level installation, which requires administrator privileges. To remove run as administrator, you can: * Right-click on the Kiro icon * Select Show more options * Select Properties * Navigate to the Compatibility tab * Uncheck the Run this program as an administrator checkbox * Select Apply and then OK to save the changes After completing these steps, Kiro should be able to update normally. Unable to run scripts In PowerShell 7+ set execution policy: Check current policy : powershell Get-ExecutionPolicy Set execution policy : powershell Set-ExecutionPolicy - ExecutionPolicy RemoteSigned - Scope CurrentUser Onedrive path issue If you use OneDrive on Windows, your desktop path might cause issues: * Launch Command Prompt as administrator * Create a symbolic link: mklink /J "C:\Users\<username>\Desktop" "C:\Users\<username>\OneDrive\Desktop" * Restart your IDE MCP server connection issues Common MCP connection problems If you're having trouble connecting to MCP servers: * Check server status : * Open the Kiro panel and navigate to the MCP servers tab * Check the connection status indicator for your server * Verify configuration : * Ensure your MCP configuration file has the correct syntax * Check that the server command and arguments are correct * Check prerequisites : * Make sure all required dependencies are installed * For AWS Documentation server, verify Python 3.10+ and uv are installed * Review logs : * Open the Output panel in Kiro * Select "Kiro - MCP Logs" from the dropdown * Look for specific error messages Fixing specific MCP issues AWS documentation server * Connection failures : bash # Verify uv installation uv --version # Verify Python version python --version # Test server directly uvx awslabs.aws-documentation-mcp-server@latest --help * Search or read failures : * Check your internet connection * Verify the URL format for documentation pages * Try with a simpler search query GitHub MCP server * Authentication errors : * Verify your personal access token is valid * Ensure the token has the required scopes (repo, user) * Generate a new token if necessary * Rate limiting issues : * GitHub API has usage limits * Check the rate limit status in the MCP logs * Consider using a token with higher rate limits Getting help If you've tried the troubleshooting steps above and still need assistance: * Check our FAQ for common questions * Join our community Discord for help * Submit an issue on GitHub with: * Your operating system details * Kiro version * Steps you've already tried * Error messages (if any) Page updated: August 4, 2026 Agent Focus Mode 0.x reference