kiro-agent-team 1.0.0

package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_user-activity.md

@@ -0,0 +1,123 @@
+# Viewing per-user activity
+You can configure Kiro to collect user activity telemetry of individual Kiro subscribers in your organization and present that information in a report. The report gives you insights into how specific users are using Kiro.
+## About the report[](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#about-the-report)
+Kiro generates the user activity report every day at midnight (00:00) Coordinated Universal Time (UTC), and saves it in a CSV file at the following path:
+`s3://bucketName/prefix/AWSLogs/accountId/KiroLogs/  by_user_analytic/Region/year/month/day/00/accountId_by_user_analytic_timestamp.csv` The CSV file is laid out as follows:
+  * Each row shows a user who interacted with Kiro that day.
+  * Each column shows a metric, as described in [User activity report metrics](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#user-activity-report-metrics). Metrics are calculated based on the user telemetry collected over the course of the day.
+
+
+If more than 1,000 users interact with Kiro during the day, Kiro splits the data into several CSV files containing 1,000 users each. Files are suffixed with `part_1`, `part_2`, and so on.
+**Info**
+When you enable user activity reports, Kiro collects user telemetry and stores it in the S3 bucket in your account. This is controlled at the administrator level and can't be configured by users.
+## Enable user activity reports[](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#enable-user-activity-reports)
+Use the following instructions to enable user activity reports.
+#### Prerequisite[](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#prerequisite)
+Create an Amazon S3 bucket to hold the user activity report CSV file. The bucket must:
+  * Be in the AWS Region where the Kiro profile was installed. This profile was installed when you subscribed IAM Identity Center workforce users to Kiro Pro for the first time. For more information about this profile and the Regions where it's supported, see [Kiro profile](https://kiro.dev/docs/cli/enterprise/concepts#kiro-profile) and [Supported Regions](https://kiro.dev/docs/cli/enterprise/supported-regions).
+  * Be in the AWS account where users are subscribed. If users are subscribed in multiple AWS accounts, then you must create buckets in each of those accounts. Cross-account buckets are not supported.
+  * (Optional but recommended) Be different from the bucket you might be using for [logging users' prompts](https://kiro.dev/docs/cli/enterprise/monitor-and-track/prompt-logging).
+  * Include a prefix, also known as a subfolder, where Kiro will save the CSV file. The CSV file cannot be saved in the root of the bucket.
+  * Have a bucket policy like the one that follows. Replace `bucketName`, `Region`, `accountId`, and `prefix` with your own information.
+
+
+json
+```
+
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "KiroLogsWrite",
+      "Effect": "Allow",
+      "Principal": {
+        "Service": "q.amazonaws.com"
+      },
+      "Action": [
+        "s3:PutObject"
+      ],
+      "Resource": [
+        "arn:aws:s3:::bucketName/prefix/*"
+      ],
+      "Condition": {
+        "StringEquals": {
+          "aws:SourceAccount": "111122223333"
+        },
+        "ArnLike": {
+          "aws:SourceArn": "arn:aws:codewhisperer:us-east-1:111122223333:*"
+        }
+      }
+    }
+  ]
+}
+
+
+```
+
+To learn about protecting the data in your Amazon S3 bucket, see [Protecting data with encryption](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingEncryption.html) in the _Amazon Simple Storage Service User Guide_.
+#### To enable user activity reports[](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#to-enable-user-activity-reports)
+  1. Sign in to the AWS console.
+  2. Switch to the Kiro console. To use the Kiro console, you must have the permissions defined in [Policy: Allow administrators to configure Kiro and subscribe users](https://kiro.dev/docs/cli/enterprise/iam/#policy-allow-administrators-to-configure-kiro-and-subscribe-users).
+  3. Choose **Settings**.
+  4. Under **Kiro user activity reports** , choose **Edit**.
+  5. Toggle **Collect granular metrics per user**.
+  6. Under **S3 location** , enter the Amazon S3 URI that you will use to hold the CSV reports. Example: `s3://amzn-s3-demo-bucket/user-activity-reports/`
+
+
+## User activity report metrics[](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#user-activity-report-metrics)
+The following table describes the metrics that are included in the user activity reports generated by Kiro.
+Metric name | Description  
+---|---  
+Chat_AICodeLines | Lines of code suggested by Kiro and accepted by the user. This metric includes code that was generated through the Kiro chat (not inline chat) and inserted into the IDE.  
+Chat_MessagesInteracted | Number of chat messages where the user has interacted positively with Kiro. Examples of positive interactions: clicking a link, inserting a suggestion, and upvoting a response from Kiro. This metric includes messages that were generated by Kiro chat (not inline chat).  
+Chat_MessagesSent | Number of messages sent to and from Kiro. This metric includes the user prompts and Kiro responses in the Kiro chat (not inline chat).  
+CodeFix_AcceptanceEventCount | Number of code fixes suggested by Kiro and accepted by the user. This metric applies to code fixes generated through the code review feature.  
+CodeFix_AcceptedLines | Lines of code suggested by Kiro and accepted by the user. This metric applies to lines of code generated through the code review feature.  
+CodeFix_GeneratedLines | Lines of code suggested by Kiro. This metric applies to lines of code generated through the code review feature.  
+CodeFix_GenerationEventCount | Number of code fixes suggested by Kiro. This metric applies to code fixes generated through the code review feature.  
+CodeReview_FailedEventCount | Number of code issues that were found but for which Kiro could not suggest a code fix. This metric applies to code issues generated using the code review feature.  
+CodeReview_FindingsCount | Number of code issues found by Kiro. This metric applies to code issues found using the code review feature.  
+CodeReview_SucceededEventCount | Number of code issues that were found and for which Kiro was able to generate a suggested code fix. This metric applies to code issues found using the code review feature.  
+Dev_AcceptanceEventCount | Number of code features suggested by Kiro and accepted by the user. This metric applies to code features generated through the /dev command.  
+Dev_AcceptedLines | Lines of code suggested by Kiro and accepted by the user. This metric applies to lines of code generated through the /dev command.  
+Dev_GeneratedLines | Lines of code suggested by Kiro. This metric applies to lines of code generated through the /dev command.  
+Dev_GenerationEventCount | Number of code features suggested by Kiro. This metric applies to code features generated through the /dev command.  
+DocGeneration_AcceptedFileUpdates | Number of file updates suggested by Kiro and accepted by the user. This metric applies to file updates generated through the /doc command.  
+DocGeneration_AcceptedFilesCreations | Number of file creations suggested by Kiro and accepted by the user. This metric applies to file creations generated through the /doc command.  
+DocGeneration_AcceptedLineAdditions | Lines of documentation additions suggested by Kiro and accepted by the user. This metric applies to documentation generated through the /doc command.  
+DocGeneration_AcceptedLineUpdates | Lines of documentation updates suggested by Kiro and accepted by the user. This metric applies to documentation generated using the /doc command.  
+DocGeneration_EventCount | Number of times the user engaged with Kiro using the /doc command.  
+DocGeneration_RejectedFileCreations | Number of file creations suggested by Kiro and rejected by the user. This metric applies to file creations generated through the /doc command.  
+DocGeneration_RejectedFileUpdates | Number of file updates suggested by Kiro and rejected by the user. This metric applies to file updates generated through the /doc command.  
+DocGeneration_RejectedLineAdditions | Lines of documentation additions suggested by Kiro and rejected by the user. This metric applies to documentation generated through the /doc command.  
+DocGeneration_RejectedLineUpdates | Lines of documentation updates suggested by Kiro and rejected by the user. This metric applies to documentation generated using the /doc command.  
+InlineChat_AcceptedLineAdditions | Lines of code additions suggested by Kiro and accepted by the user. This metric includes code additions generated through the inline chat (not Kiro chat).  
+InlineChat_AcceptedLineDeletions | Lines of code deletions suggested by Kiro and accepted by the user. This metric includes code deletions suggested through the inline chat (not Kiro chat).  
+InlineChat_AcceptanceEventCount | Number of inline chat (not Kiro chat) suggestions that were accepted by the user.  
+InlineChat_DismissalEventCount | Number of inline chat (not Kiro chat) suggestions that were abandoned by the user. By 'abandoned', we mean that the code suggestion was displayed but the user kept typing or performing other operations in their IDE, and did not explicitly accept or reject the code suggestion.  
+InlineChat_DismissedLineAdditions | Lines of code additions suggested by Kiro and abandoned by the user. By 'abandoned', we mean that the code suggestion was displayed but the user kept typing or performing other operations in their IDE, and did not explicitly accept or reject the code suggestion. This metric includes code additions generated through the inline chat (not Kiro chat).  
+InlineChat_DismissedLineDeletions | Lines of code deletions suggested by Kiro and abandoned by the user. By 'abandoned', we mean that the code suggestion was displayed but the user kept typing or performing other operations in their IDE, and did not explicitly accept or reject the code suggestion. This metric includes code deletions suggested through the inline chat (not Kiro chat).  
+InlineChat_EventCount | Number of inline chat (not Kiro chat) sessions that the user engaged in.  
+InlineChat_RejectedLineAdditions | Lines of code additions suggested by Kiro and rejected by the user. This metric includes code additions generated through the inline chat (not Kiro chat).  
+InlineChat_RejectedLineDeletions | Lines of code deletions suggested by Kiro and rejected by the user. This metric includes code deletions suggested through the inline chat (not Kiro chat).  
+InlineChat_RejectionEventCount | Number of inline chat (not Kiro chat) suggestions that were rejected by the user.  
+Inline_AICodeLines | Lines of code suggested by Kiro and accepted by the user. This metric includes code that was accepted as inline suggestions.  
+Inline_AcceptanceCount | Number of inline suggestions accepted by the user.  
+Inline_SuggestionsCount | Number of inline suggestions displayed to the user.  
+TestGeneration_AcceptedLines | Lines of code suggested by Kiro and accepted by the user. This metric applies to lines of code generated through the /test command.  
+TestGeneration_AcceptedTests | Number of unit tests suggested by Kiro and accepted by the user. This metric applies to unit tests generated through the /test command.  
+TestGeneration_EventCount | Number of times the user engaged with Kiro through the /test command.  
+TestGeneration_GeneratedLines | Lines of code suggested by Kiro. This metric applies to lines of code generated through the /test command.  
+TestGeneration_GeneratedTests | Number of unit tests suggested by Kiro. This metric applies to unit tests generated through the /test command.  
+Transformation_EventCount | Number of times the user engaged with Kiro through the /transform command, excluding the times when the user transformed code on the command line.  
+Transformation_LinesGenerated | Lines of code suggested by Kiro. This metric applies to code generated through the /transform command, excluding code transformed on the command line.  
+Transformation_LinesIngested | Lines of code provided to Kiro for transformation. This metric applies to code that is provided through the /transform command, excluding code provided for transformation on the command line, or for an SQL conversion.  
+Page updated: November 18, 2025
+[View usage (dashboard)](https://kiro.dev/docs/cli/enterprise/monitor-and-track/dashboard/)
+[Log user prompts](https://kiro.dev/docs/cli/enterprise/monitor-and-track/prompt-logging/)
+On this page
+  * [About the report](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#about-the-report)
+  * [Enable user activity reports](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#enable-user-activity-reports)
+  * [Prerequisite](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#prerequisite)
+  * [To enable user activity reports](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#to-enable-user-activity-reports)
+  * [User activity report metrics](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity/#user-activity-report-metrics)

package/.kiro/documentation/docs_cli_enterprise_settings.md

@@ -0,0 +1,15 @@
+# Settings
+An administrator can control the following settings in a [Kiro profile](https://kiro.dev/docs/cli/enterprise/concepts/#kiro-profile).
+Setting | Description  
+---|---  
+**Encryption key** | By default, Kiro uses an AWS managed key to encrypt your data at rest. For some features, instead of using an AWS managed key, you can use your own key. This is known as a _customer-managed key_. To specify a customer-managed key, enable **Encryption key** and use the available UI to specify a new or existing key. For details about which features' data can be encrypted with a customer managed key, see [Encryption at rest](https://kiro.dev/docs/cli/privacy-and-security/data-protection#encryption-at-rest).  
+**Include suggestions with code references** | Kiro learns, in part, from open-source projects. Sometimes, Kiro suggests code that is similar to publicly available code. When you enable **Include suggestions with code references** , Kiro will include information about the source used to generate a suggestion.  
+**Kiro usage dashboard** | Enable **Kiro usage dashboard** to display a dashboard on the Kiro console's main page. For more information about the dashboard, see [Viewing Kiro usage on the dashboard](https://kiro.dev/docs/cli/enterprise/monitor-and-track/dashboard).  
+**Kiro user activity report** | Enable **Kiro user activity report** to allow Kiro to collect user activity telemetry of individual Kiro subscribers in your organization and present that information in a report. For more information, see [Viewing per-user activity](https://kiro.dev/docs/cli/enterprise/monitor-and-track/user-activity).  
+**Prompt logging** | Enable **Logging** to allow Kiro to record all inline suggestions and chat conversations that users have in the Kiro IDE. For more information, see [Logging users' prompts](https://kiro.dev/docs/cli/enterprise/monitor-and-track/prompt-logging).  
+**Member account subscriptions** | If you are a management account administrator within an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html), you can configure Kiro to display Kiro subscriptions from both _management_ and _member_ accounts in a single, unified list on the **Subscriptions** page of the Amazon Q console (_not_ the Kiro console) while signed in to your management account. This organization-wide visibility eliminates the need to sign in to multiple accounts to track your subscriptions. To have all Kiro subscriptions be displayed in the Amazon Q console, enable the **Member account subscriptions** setting. This setting is only visible when signed in to the AWS console as a management account administrator.  
+**Model Context Protocol (MCP)** | Enable the **Model Context Protocol (MCP)** setting to allow Kiro subscribers to use MCP servers.  
+**Overages** | Enable **Overages** to allow Kiro subscribers to continue working when they exceed their plan limits. For more information see [Enabling overages for Kiro users](https://kiro.dev/docs/cli/enterprise/subscription-management#enabling-overages-for-kiro-users).  
+Page updated: November 16, 2025
+[Log user prompts](https://kiro.dev/docs/cli/enterprise/monitor-and-track/prompt-logging/)
+[Billing](https://kiro.dev/docs/cli/enterprise/billing/)

package/.kiro/documentation/docs_cli_enterprise_subscribe.md

@@ -0,0 +1,36 @@
+# Subscribing your team to Kiro
+## Prerequisites[](https://kiro.dev/docs/cli/enterprise/subscribe/#prerequisites)
+Before you begin, make sure you have the following:
+  * **An AWS account** - You can [create an AWS account](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-creating.html) if you do not have one already.
+  * **AWS permissions** - As a Kiro admin, you must have the permissions to access the Kiro console in AWS in order to subscribe and manage Kiro users. The minimum permissions you'll need are described in [Policy: Allow administrators to configure Kiro and subscribe users](https://kiro.dev/docs/cli/enterprise/iam/#policy-allow-administrators-to-configure-kiro-and-subscribe-users).
+  * **AWS IAM Identity Center** - You must have an instance of IAM Identity Center set up in your AWS account, with the identities of the users you want to subscribe to Kiro. Your IAM Identity Center instance must be in [a supported AWS Region](https://kiro.dev/docs/cli/enterprise/supported-regions).
+  * **Users and groups** - You can add users and groups to IAM Identity Center's built-in directory, or to an external identity provider (IdP) that is connected to IAM Identity Center. For more information, see [Getting started with IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/getting-started.html).
+
+
+## Create the Kiro profile[](https://kiro.dev/docs/cli/enterprise/subscribe/#create-the-kiro-profile)
+  1. Sign in to the AWS Management Console.
+  2. Switch to the Kiro console.
+  3. Make sure you are in your preferred [supported AWS Region](https://kiro.dev/docs/cli/enterprise/supported-regions) to create the [Kiro profile](https://kiro.dev/docs/cli/enterprise/concepts/#kiro-profile) and store user data.
+  4. Choose the **Sign up for Kiro** button.
+  5. Review the contents of the **Create Kiro profile** dialog box then choose **Enable**. The Kiro profile is created.
+  6. _(Optional) Edit the profile with a different name or description as needed in the**Settings** page._
+
+
+## Subscribe your team to Kiro[](https://kiro.dev/docs/cli/enterprise/subscribe/#subscribe-your-team-to-kiro)
+  1. Switch to the Kiro console if you're not there yet.
+  2. Make sure you're in the AWS Region where you created the [Kiro profile](https://kiro.dev/docs/cli/enterprise/concepts/#kiro-profile).
+  3. In the **Users & Groups** page, choose the **Users** or **Groups** tab.
+  4. Choose the **Add user** or **Add group** button. A dialog box appears where you can select the [Kiro subscription tier](https://kiro.dev/docs/cli/enterprise/concepts/#kiro-subscription-tier) (Pro, Pro+, Power) with details about each tier.
+  5. Choose the desired subscription tier and choose **Continue**.
+  6. In the search bar, search for a group or a user you want to subscribe to the selected tier, or select one from the drop down.
+  7. The group or user will auto-populate with what is available in the IAM Identity Center.
+  8. Select them and choose **Assign**. Users or groups are now subscribed.
+
+
+Page updated: December 12, 2025
+[Onboarding quickstart](https://kiro.dev/docs/cli/enterprise/getting-started/)
+[Manage subscriptions](https://kiro.dev/docs/cli/enterprise/subscription-management/)
+On this page
+  * [Prerequisites](https://kiro.dev/docs/cli/enterprise/subscribe/#prerequisites)
+  * [Create the Kiro profile](https://kiro.dev/docs/cli/enterprise/subscribe/#create-the-kiro-profile)
+  * [Subscribe your team to Kiro](https://kiro.dev/docs/cli/enterprise/subscribe/#subscribe-your-team-to-kiro)

package/.kiro/documentation/docs_cli_enterprise_subscription-management.md

@@ -0,0 +1,55 @@
+# Managing Kiro subscriptions
+## Change Kiro subscription plans[](https://kiro.dev/docs/cli/enterprise/subscription-management/#change-kiro-subscription-plans)
+  1. Sign in to the AWS Management Console.
+  2. Switch to the Kiro console. If you don't see it, you might be in the wrong AWS Region.
+  3. In the **Users & Groups** page, choose the **Users** or **Groups** tab.
+  4. Choose the user or group whose subscriptions you want to upgrade or downgrade.
+  5. Choose **Change plan** then choose the new plan. Select **Continue** to finish.
+  6. If it is a higher tier plan, changes will happen immediately. If it is a lower tier plan, changes happen at the beginning of the following month.
+
+
+**Info**
+To learn about what's offered at each subscription tier, see [Enterprise billing](https://kiro.dev/docs/cli/enterprise/billing).
+## Unsubscribe Kiro users[](https://kiro.dev/docs/cli/enterprise/subscription-management/#unsubscribe-kiro-users)
+  1. Sign in to the AWS Management Console.
+  2. Switch to the Kiro console. If you don't see it, you might be in the wrong AWS Region.
+  3. In the **Users & Groups** page, choose the **Users** or **Groups** tab.
+  4. Choose the user or group whose subscriptions you want to cancel.
+  5. Choose **Deactivate plan**. Review the contents of the **Unsubscribee** dialog box then choose **Unsubscribe**.
+
+
+**Info**
+After unsubscribing users, their subscriptions are marked as **Canceled**. They will have until the end of the month to use credits from the current plan. Starting the following month, they can no longer access paid Kiro features.
+## Enable overages for Kiro users[](https://kiro.dev/docs/cli/enterprise/subscription-management/#enable-overages-for-kiro-users)
+You might want to enable overages to give users the ability to continue working when they exceed their plan limits. Enabling overages has the following advantages:
+  * **Uninterrupted productivity** – When a user exceeds their plan's quota, they can continue working without disruption. The productivity benefits of continued access might outweigh the additional costs.
+  * **Better usage pattern insights** – Users get more accurate data about their actual usage, which helps in right-sizing future subscription needs.
+
+
+By default, overages are _disabled_. Once enabled, overages become available to all users and groups in the profile. To enable overages:
+  1. Sign in to the AWS Management Console.
+  2. Switch to the Kiro console. If you don't see it, you might be in the wrong AWS Region.
+  3. Choose **Settings**.
+  4. Find the **Kiro settings** section.
+  5. Turn on **Overages**.
+
+
+**Info**
+Setting custom caps for overages is not yet supported (coming soon).
+## Subscription statuses[](https://kiro.dev/docs/cli/enterprise/subscription-management/#subscription-statuses)
+You can view the status of your users' subscriptions on the **Subscriptions** page of the Kiro console. The statuses on the **User** tab are:
+  * **Active** – The user is subscribed to Kiro. You will be charged for active user subscriptions in the group.
+  * **Canceled** – The user subscription was canceled by an administrator. Unsubscribed users in the group can no longer access paid Kiro features. For more information, see [Unsubscribe Kiro users](https://kiro.dev/docs/cli/enterprise/subscription-management/#unsubscribe-kiro-users).
+  * **Pending** – The user is subscribed but has not activated their subscription. You are not being charged for this subscription and there will be no data under _Last active_ column.
+
+
+**Info**
+There are no statuses on the **Groups** tab since subscriptions are assigned to users, not groups.
+Page updated: November 16, 2025
+[Subscribe your team](https://kiro.dev/docs/cli/enterprise/subscribe/)
+[Supported regions](https://kiro.dev/docs/cli/enterprise/supported-regions/)
+On this page
+  * [Change Kiro subscription plans](https://kiro.dev/docs/cli/enterprise/subscription-management/#change-kiro-subscription-plans)
+  * [Unsubscribe Kiro users](https://kiro.dev/docs/cli/enterprise/subscription-management/#unsubscribe-kiro-users)
+  * [Enable overages for Kiro users](https://kiro.dev/docs/cli/enterprise/subscription-management/#enable-overages-for-kiro-users)
+  * [Subscription statuses](https://kiro.dev/docs/cli/enterprise/subscription-management/#subscription-statuses)

package/.kiro/documentation/docs_cli_enterprise_supported-regions.md

@@ -0,0 +1,39 @@
+# Supported regions
+There are two AWS Regions relevant to Kiro administrators:
+  * The Region where your IAM Identity Center instance is enabled. This is where user identities are managed, and where subscriptions are stored.
+  * The Region where your Kiro profile is created. This is where [data is stored](https://kiro.dev/docs/cli/privacy-and-security/data-protection#data-storage) and [inference is done](https://kiro.dev/docs/cli/privacy-and-security/data-protection#cross-region-processing), and might be different from your IAM Identity Center instance's Region.
+
+
+## Supported Kiro console and Kiro profile regions[](https://kiro.dev/docs/cli/enterprise/supported-regions/#supported-kiro-console-and-kiro-profile-regions)
+The **Kiro** **console** and **Kiro profile** are supported in the following Regions:
+  * US East (N. Virginia)
+  * Europe (Frankfurt)
+
+
+## IAM identity center regions supported by Kiro[](https://kiro.dev/docs/cli/enterprise/supported-regions/#iam-identity-center-regions-supported-by-kiro)
+The users that you want to subscribe to Kiro must have identities in an IAM Identity Center instance (or a connected identity provider) in one of the following Regions:
+  * US East (Ohio)
+  * US East (N. Virginia)
+  * US West (N. California)
+  * US West (Oregon)
+  * Asia Pacific (Mumbai)
+  * Asia Pacific (Osaka)
+  * Asia Pacific (Seoul)
+  * Asia Pacific (Singapore)
+  * Asia Pacific (Sydney)
+  * Asia Pacific (Tokyo)
+  * Canada (Central)
+  * Europe (Frankfurt)
+  * Europe (Ireland)
+  * Europe (London)
+  * Europe (Paris)
+  * Europe (Stockholm)
+  * South America (São Paulo)
+
+
+Page updated: November 16, 2025
+[Manage subscriptions](https://kiro.dev/docs/cli/enterprise/subscription-management/)
+[Monitor and track](https://kiro.dev/docs/cli/enterprise/monitor-and-track/)
+On this page
+  * [Supported Kiro console and Kiro profile regions](https://kiro.dev/docs/cli/enterprise/supported-regions/#supported-kiro-console-and-kiro-profile-regions)
+  * [IAM identity center regions supported by Kiro](https://kiro.dev/docs/cli/enterprise/supported-regions/#iam-identity-center-regions-supported-by-kiro)

package/.kiro/documentation/docs_cli_experimental.md

@@ -0,0 +1,282 @@
+# Experimental features
+Kiro CLI includes experimental features that provide advanced functionality. These features are in active development and can be toggled on/off using the `/experiment` command.
+**Warning**
+These features may change or be removed at any time. The experience might not be perfect. Use at your own discretion in production workflows.
+These features are provided to gather feedback and test new capabilities. Please report issues through the `kiro issue` command.
+## Managing experiments[](https://kiro.dev/docs/cli/experimental/#managing-experiments)
+Use the `/experiment` command to toggle experimental features:
+bash
+```
+
+/experiment
+
+
+```
+
+This shows an interactive menu where you can:
+  * See current status of each experiment (ON/OFF)
+  * Toggle experiments by selecting them
+  * View descriptions of what each experiment does
+
+
+## Available experiments[](https://kiro.dev/docs/cli/experimental/#available-experiments)
+### Knowledge management[](https://kiro.dev/docs/cli/experimental/#knowledge-management)
+**Command:** `/knowledge`
+Enables persistent context storage and retrieval across chat sessions with semantic search capabilities.
+**Features:**
+  * Store and search through files, directories, and text content
+  * Semantic search for better context retrieval
+  * Persistent knowledge base across sessions
+  * Agent-specific knowledge isolation
+
+
+**Enable:**
+bash
+```
+
+kiro-cli settings chat.enableKnowledge true
+
+
+```
+
+[Learn more about Knowledge Management →](https://kiro.dev/docs/cli/experimental/knowledge-management)
+### Tangent mode[](https://kiro.dev/docs/cli/experimental/#tangent-mode)
+**Command:** `/tangent` or **Ctrl+T**
+Create conversation checkpoints to explore side topics without disrupting your main conversation flow.
+**Features:**
+  * Create conversation checkpoints
+  * Explore tangential topics
+  * Return to main conversation thread
+  * Preserve conversation context
+
+
+**Enable:**
+bash
+```
+
+kiro-cli settings chat.enableTangentMode true
+
+
+```
+
+[Learn more about Tangent Mode →](https://kiro.dev/docs/cli/experimental/tangent-mode)
+### TODO lists[](https://kiro.dev/docs/cli/experimental/#todo-lists)
+**Tool:** `todo` | **Command:** `/todo`
+Enables Kiro to create and modify TODO lists automatically, with commands for you to view and manage them.
+**Features:**
+  * Kiro automatically creates TODO lists when appropriate
+  * View, manage, and delete TODOs
+  * Resume existing TODO lists
+  * Persisted across chat sessions
+
+
+**Enable:**
+bash
+```
+
+kiro-cli settings chat.enableTodoList true
+
+
+```
+
+[Learn more about TODO Lists →](https://kiro.dev/docs/cli/experimental/todo-lists)
+### Thinking tool[](https://kiro.dev/docs/cli/experimental/#thinking-tool)
+Shows AI reasoning process for complex problems with step-by-step thought processes.
+**Features:**
+  * Transparent decision-making process
+  * Step-by-step reasoning display
+  * Useful for debugging and learning
+  * Better understanding of conclusions
+
+
+**Enable:**
+bash
+```
+
+kiro-cli settings chat.enableThinking true
+
+
+```
+
+[Learn more about Thinking Tool →](https://kiro.dev/docs/cli/experimental/thinking)
+### Checkpointing[](https://kiro.dev/docs/cli/experimental/#checkpointing)
+**Command:** `/checkpoint`
+Enables session-scoped checkpoints for tracking file changes using Git-like commands.
+**Features:**
+  * Snapshots file changes into shadow git repo
+  * List, expand, diff, and restore checkpoints
+  * Conversation history unwinds when restoring
+  * Auto-enables in git repositories
+  * Manual initialization for non-git directories
+
+
+**Enable:**
+bash
+```
+
+kiro-cli settings chat.enableCheckpoint true
+
+
+```
+
+**Basic Usage:**
+bash
+```
+
+/checkpoint list                    # Show checkpoints
+/checkpoint expand <tag>            # Show detailed checkpoint info
+/checkpoint diff <tag1> [tag2]      # Compare checkpoints
+/checkpoint restore [<tag>]         # Restore to checkpoint
+/checkpoint clean                   # Delete session shadow repo
+
+
+```
+
+[Learn more about Checkpointing →](https://kiro.dev/docs/cli/experimental/checkpointing)
+### Context usage percentage[](https://kiro.dev/docs/cli/experimental/#context-usage-percentage)
+Shows context window usage as a percentage in the chat prompt with color-coded indicators.
+**Features:**
+  * Displays percentage in prompt (e.g., "[rust-agent] 6% >")
+  * Color-coded indicators: 
+    * Green: Less than 50% usage
+    * Yellow: 50-89% usage
+    * Red: 90-100% usage
+  * Helps monitor context consumption
+
+
+**Enable:**
+bash
+```
+
+kiro-cli settings chat.enableContextUsageIndicator true
+
+
+```
+
+### Delegate[](https://kiro.dev/docs/cli/experimental/#delegate)
+Launch and manage asynchronous task processes, running Kiro chat sessions with specific agents in parallel.
+**Features:**
+  * Launch background tasks using natural language
+  * Run parallel chat sessions with specific agents
+  * Monitor task progress independently
+  * Agent approval flow for security
+
+
+**Enable:**
+bash
+```
+
+kiro-cli settings chat.enableDelegate true
+
+
+```
+
+**Usage:** Use natural language to ask Kiro to launch a background task:
+```
+
+Can you create a background task to analyze the performance of our API endpoints?
+
+
+```
+
+Then check on results:
+```
+
+Check the status of my API analysis task
+Show me the results from the background analysis
+
+
+```
+
+[Learn more about Delegate →](https://kiro.dev/docs/cli/experimental/delegate)
+## Settings integration[](https://kiro.dev/docs/cli/experimental/#settings-integration)
+Experiments are stored as settings and persist across sessions:
+bash
+```
+
+# View all experimental settings
+kiro-cli settings list | grep -i enable
+
+# Enable/disable specific experiments
+kiro-cli settings chat.enableKnowledge true
+kiro-cli settings chat.enableTangentMode true
+kiro-cli settings chat.enableTodoList true
+kiro-cli settings chat.enableThinking true
+kiro-cli settings chat.enableCheckpoint true
+kiro-cli settings chat.enableContextUsageIndicator true
+kiro-cli settings chat.enableDelegate true
+
+
+```
+
+## Fuzzy search support[](https://kiro.dev/docs/cli/experimental/#fuzzy-search-support)
+All experimental commands are available in fuzzy search (Ctrl+S):
+  * `/experiment` - Manage experimental features
+  * `/knowledge` - Knowledge base commands (when enabled)
+  * `/todo` - TODO list commands (when enabled)
+  * `/tangent` - Tangent mode toggle (when enabled)
+  * `/checkpoint` - Checkpoint commands (when enabled)
+
+
+## Best practices[](https://kiro.dev/docs/cli/experimental/#best-practices)
+  1. **Test in safe environments** : Try experimental features on non-critical projects first
+  2. **Provide feedback** : Report issues and suggestions using `kiro issue`
+  3. **Stay updated** : Check release notes for changes to experimental features
+  4. **Understand limitations** : Read individual feature documentation for known issues
+  5. **Have backups** : Some features modify files (checkpointing, TODO lists)
+
+
+## Troubleshooting[](https://kiro.dev/docs/cli/experimental/#troubleshooting)
+### Feature not working[](https://kiro.dev/docs/cli/experimental/#feature-not-working)
+  1. Verify feature is enabled:
+bash
+```
+
+kiro-cli settings list | grep -i enable
+
+
+```
+
+  2. Check for error messages in chat
+  3. Try disabling and re-enabling:
+bash
+```
+
+kiro-cli settings chat.enableFeatureName false
+kiro-cli settings chat.enableFeatureName true
+
+
+```
+
+  4. Restart Kiro CLI
+
+
+### Commands not available[](https://kiro.dev/docs/cli/experimental/#commands-not-available)
+Ensure the feature is enabled before using its commands. For example, `/knowledge` only works when knowledge management is enabled.
+## Next steps[](https://kiro.dev/docs/cli/experimental/#next-steps)
+  * [Knowledge Management](https://kiro.dev/docs/cli/experimental/knowledge-management)
+  * [Tangent Mode](https://kiro.dev/docs/cli/experimental/tangent-mode)
+  * [TODO Lists](https://kiro.dev/docs/cli/experimental/todo-lists)
+  * [Settings Configuration](https://kiro.dev/docs/cli/settings)
+
+
+Page updated: December 18, 2025
+[Steering](https://kiro.dev/docs/cli/steering/)
+[Knowledge management](https://kiro.dev/docs/cli/experimental/knowledge-management/)
+On this page
+  * [Managing experiments](https://kiro.dev/docs/cli/experimental/#managing-experiments)
+  * [Available experiments](https://kiro.dev/docs/cli/experimental/#available-experiments)
+  * [Knowledge management](https://kiro.dev/docs/cli/experimental/#knowledge-management)
+  * [Tangent mode](https://kiro.dev/docs/cli/experimental/#tangent-mode)
+  * [TODO lists](https://kiro.dev/docs/cli/experimental/#todo-lists)
+  * [Thinking tool](https://kiro.dev/docs/cli/experimental/#thinking-tool)
+  * [Checkpointing](https://kiro.dev/docs/cli/experimental/#checkpointing)
+  * [Context usage percentage](https://kiro.dev/docs/cli/experimental/#context-usage-percentage)
+  * [Delegate](https://kiro.dev/docs/cli/experimental/#delegate)
+  * [Settings integration](https://kiro.dev/docs/cli/experimental/#settings-integration)
+  * [Fuzzy search support](https://kiro.dev/docs/cli/experimental/#fuzzy-search-support)
+  * [Best practices](https://kiro.dev/docs/cli/experimental/#best-practices)
+  * [Troubleshooting](https://kiro.dev/docs/cli/experimental/#troubleshooting)
+  * [Feature not working](https://kiro.dev/docs/cli/experimental/#feature-not-working)
+  * [Commands not available](https://kiro.dev/docs/cli/experimental/#commands-not-available)
+  * [Next steps](https://kiro.dev/docs/cli/experimental/#next-steps)