kiro-agent-team 1.0.0

package/.kiro/documentation/docs_cli_autocomplete.md

@@ -0,0 +1,132 @@
+# Completions & autocomplete
+Kiro CLI provides two AI-powered assistance features to help you work more efficiently in your terminal:
+  * **Autocomplete Dropdown Menu** : A graphical menu showing available command options
+  * **Inline Suggestions** : Gray "ghost text" that appears as you type
+
+
+These features work independently and support hundreds of popular command line tools including `git`, `npm`, `docker`, and `aws`.
+## Autocomplete dropdown menu[](https://kiro.dev/docs/cli/autocomplete/#autocomplete-dropdown-menu)
+The autocomplete dropdown appears to the right of your cursor when typing commands, showing available options, subcommands, and arguments that you can select using arrow keys.
+### Using autocomplete[](https://kiro.dev/docs/cli/autocomplete/#using-autocomplete)
+The autocomplete dropdown is automatically enabled after you install Kiro CLI:
+  1. Open your terminal or command prompt
+  2. Start typing a command
+  3. A graphical menu will appear showing available options
+  4. Use arrow keys to navigate suggestions
+  5. Press **Tab** or **Enter** to select an option
+
+
+### Configuration[](https://kiro.dev/docs/cli/autocomplete/#configuration)
+Customize the autocomplete behavior:
+bash
+```
+
+# Enable/disable autocomplete
+kiro-cli settings autocomplete.disable false  # enable
+kiro-cli settings autocomplete.disable true   # disable
+
+# Change theme
+kiro-cli theme dark
+kiro-cli theme light  
+kiro-cli theme system
+
+# View current theme
+kiro-cli theme
+
+# List available themes
+kiro-cli theme --list
+
+
+```
+
+## Inline suggestions[](https://kiro.dev/docs/cli/autocomplete/#inline-suggestions)
+Inline suggestions appear as gray "ghost text" directly on your command line as you type. This feature works independently from the dropdown menu.
+### Using inline suggestions[](https://kiro.dev/docs/cli/autocomplete/#using-inline-suggestions)
+Inline suggestions are enabled by default:
+  1. Start typing a command
+  2. Gray ghost text will appear showing potential completions
+  3. Press the **right arrow key** or **Tab** to accept
+  4. Continue typing to ignore the suggestion
+
+
+### Managing inline suggestions[](https://kiro.dev/docs/cli/autocomplete/#managing-inline-suggestions)
+Control inline suggestions with the `kiro-cli inline` command:
+bash
+```
+
+# Enable inline suggestions
+kiro-cli inline enable
+
+# Disable inline suggestions  
+kiro-cli inline disable
+
+# Check current status
+kiro-cli inline status
+
+# Set customization
+kiro-cli inline set-customization [ARN]
+
+# Show available customizations
+kiro-cli inline show-customizations
+
+
+```
+
+## Supported tools[](https://kiro.dev/docs/cli/autocomplete/#supported-tools)
+The autocomplete system supports hundreds of command line tools:
+### Popular tools[](https://kiro.dev/docs/cli/autocomplete/#popular-tools)
+  * **Git** : Branch names, commit hashes, file paths
+  * **Docker** : Container names, image tags, commands
+  * **npm/yarn** : Package names, scripts, dependencies
+  * **kubectl** : Resources, namespaces, contexts
+  * **terraform** : Resources, providers, variables
+  * **aws** : Services, regions, resource names
+
+
+### Language tools[](https://kiro.dev/docs/cli/autocomplete/#language-tools)
+  * **Python** : `pip`, `poetry`, `conda`
+  * **Node.js** : `npm`, `yarn`, `pnpm`
+  * **Ruby** : `gem`, `bundle`
+  * **Go** : `go mod`, `go build`
+
+
+### System tools[](https://kiro.dev/docs/cli/autocomplete/#system-tools)
+  * Standard Unix/Linux commands
+  * Package managers (`apt`, `brew`, `yum`)
+  * File operations (`ls`, `find`, `grep`)
+
+
+## Troubleshooting[](https://kiro.dev/docs/cli/autocomplete/#troubleshooting)
+### Autocomplete not working[](https://kiro.dev/docs/cli/autocomplete/#autocomplete-not-working)
+If autocomplete isn't appearing:
+  1. Verify installation: `kiro-cli --version`
+  2. Check if disabled: `kiro-cli settings autocomplete.disable`
+  3. Restart your terminal
+  4. Try a different shell (bash, zsh, fish)
+
+
+### Inline suggestions issues[](https://kiro.dev/docs/cli/autocomplete/#inline-suggestions-issues)
+If inline suggestions aren't working:
+  1. Check status: `kiro-cli inline status`
+  2. Enable if disabled: `kiro-cli inline enable`
+  3. Verify shell compatibility
+  4. Check terminal emulator support
+
+
+Page updated: November 16, 2025
+[Hooks](https://kiro.dev/docs/cli/hooks/)
+[Code Intelligence](https://kiro.dev/docs/cli/code-intelligence/)
+On this page
+  * [Autocomplete dropdown menu](https://kiro.dev/docs/cli/autocomplete/#autocomplete-dropdown-menu)
+  * [Using autocomplete](https://kiro.dev/docs/cli/autocomplete/#using-autocomplete)
+  * [Configuration](https://kiro.dev/docs/cli/autocomplete/#configuration)
+  * [Inline suggestions](https://kiro.dev/docs/cli/autocomplete/#inline-suggestions)
+  * [Using inline suggestions](https://kiro.dev/docs/cli/autocomplete/#using-inline-suggestions)
+  * [Managing inline suggestions](https://kiro.dev/docs/cli/autocomplete/#managing-inline-suggestions)
+  * [Supported tools](https://kiro.dev/docs/cli/autocomplete/#supported-tools)
+  * [Popular tools](https://kiro.dev/docs/cli/autocomplete/#popular-tools)
+  * [Language tools](https://kiro.dev/docs/cli/autocomplete/#language-tools)
+  * [System tools](https://kiro.dev/docs/cli/autocomplete/#system-tools)
+  * [Troubleshooting](https://kiro.dev/docs/cli/autocomplete/#troubleshooting)
+  * [Autocomplete not working](https://kiro.dev/docs/cli/autocomplete/#autocomplete-not-working)
+  * [Inline suggestions issues](https://kiro.dev/docs/cli/autocomplete/#inline-suggestions-issues)

package/.kiro/documentation/docs_cli_billing.md

@@ -0,0 +1,31 @@
+# Billing for individuals
+Kiro offers four distinct service tiers designed to meet different development needs: **Kiro Free** , **Kiro Pro** , **Kiro Pro+** , and **Kiro Power**. Each tier provides progressively more capabilities.
+New Kiro users are automatically enrolled in a 30 day free trial. The free trial is a temporary enhancement to the perpetual **Kiro Free** tier that allows you to test Pro features by providing 500 credits to use over a 30 day trial period. After your trial, you'll need to choose one of Kiro's paid tiers or switch to the perpetual **Kiro Free** tier, and any unused credits will expire.
+**Info**
+If you upgrade tiers during the 30 day trial, you'll keep the 500 credits, but any unused trial credits will expire after the 30 days are complete. For example, if you upgrade to the Pro tier within 30 days, you'll have 1,500 credits (1,000 Pro + 500 Trial). After 30 days, unused trial credit expires, leaving you with the Pro tier credits.
+Credits are consumed fractionally based on each request. Simple edits and shorter prompts will use fewer credits than complex, lengthy tasks. This means that fractional credits allow you to get more value from your credit allocation.
+## Tier comparison[](https://kiro.dev/docs/cli/billing/#tier-comparison)
+Tier | Credits | Overage  
+---|---|---  
+Trial | 500 | Not available  
+Free | 50 | Not available  
+Pro | 1,000 | Opt-in  
+Pro+ | 2,000 | Opt-in  
+Power | 10,000 | Opt-in  
+## Billing practices[](https://kiro.dev/docs/cli/billing/#billing-practices)
+Note the following billing practices when you subscribe, downgrade, unsubscribe, and incur overages:
+  * If you are on the **Kiro Free** tier, have never upgraded before, and **upgrade** to the Pro, Pro+, or Power tier mid-month, you are charged a prorated fee, but immediately get access to your new plan's full credit limits. For example, if you subscribe to Pro on April 15th, you'll be charged half the subscription fee and be able to use all of the credits for that tier. Additionally, if you decide to **upgrade** again on April 20th to Pro+, you'll get backdated prorated fees and access to the full credit limits of that tier, as if you directly upgraded to Pro+ on April 15th. After that, you'll be charged the full amount.
+  * If you are on any paid tier, such as the Pro, Pro+, or Power tier, and **upgrade** to another paid tier, you are charged a retroactive fee for the entire month based on the price difference. For example, if you upgrade from a Pro to a Pro+ tier, you'll be charged the difference in the subscription fee and at the end of the month, Kiro will recalculate the entire month's usage under the new tier's credits. In this case, if you used 1,010 credits, that would be 10 credits over the Pro cap, however since you upgrade to the Pro+ tier, you avoided paying an overage fee.
+**Info**
+If you're on a paid tier, switch to the **Kiro Free** tier, and then switch back to a paid tier, the payment behavior will be the same as above. Note that downgrades take effect in the following month and upgrades are effective immediately.
+  * If you **downgrade** from Pro+ to Pro tier mid-month, you are charged the full fee for that month. For example, if you downgrade on June 2nd, you'll be charged the full Pro+ subscription fee for the month of June. From July onward, you will be charged the Pro fee.
+  * If you **incur overages** , you are charged the total overage fees for the month at the end of the current billing cycle.
+  * For all tiers, your **usage cap** renews at the beginning of the next billing cycle.
+
+
+Page updated: November 15, 2025
+[Code Intelligence](https://kiro.dev/docs/cli/code-intelligence/)
+[Managing your Kiro CLI subscription](https://kiro.dev/docs/cli/billing/subscription-portal/)
+On this page
+  * [Tier comparison](https://kiro.dev/docs/cli/billing/#tier-comparison)
+  * [Billing practices](https://kiro.dev/docs/cli/billing/#billing-practices)

package/.kiro/documentation/docs_cli_billing_contact-support.md

@@ -0,0 +1,43 @@
+# Contacting billing support
+If you need assistance with billing questions, payment issues, subscription changes, or other account-related concerns, you can contact our billing support team directly.
+## When to contact billing support[](https://kiro.dev/docs/cli/billing/contact-support/#when-to-contact-billing-support)
+Contact billing support for help with:
+  * **Payment issues** - Failed payments, updating payment methods, or billing errors
+  * **Subscription questions** - Plan changes, upgrade/downgrade assistance, or billing cycle inquiries
+  * **Account access** - Issues accessing your account or billing dashboard
+  * **Refund requests** - Questions about refunds or billing disputes
+  * **Usage clarification** - Understanding your usage charges or tier limits
+  * **Invoice questions** - Requesting copies of invoices or clarifying charges
+
+
+## How to contact support[](https://kiro.dev/docs/cli/billing/contact-support/#how-to-contact-support)
+You can contact billing support in two ways:
+### Option 1: Command line[](https://kiro.dev/docs/cli/billing/contact-support/#option-1-command-line)
+Use the Kiro CLI issue reporting command:
+bash
+```
+
+kiro-cli issue
+
+
+```
+
+### Option 2: From within chat[](https://kiro.dev/docs/cli/billing/contact-support/#option-2-from-within-chat)
+If you're already in a Kiro CLI chat session, you can use the built-in issue reporting tool to create a GitHub issue with pre-filled context. Just tell Kiro in natural language about the issue that you want to report, and it will help you create the issue on GitHub.
+Both methods will help you create a support request that gets routed to our billing team.
+## What information you'll need[](https://kiro.dev/docs/cli/billing/contact-support/#what-information-youll-need)
+When creating your support request, include:
+  * **Issue title** - Brief description of your billing concern
+  * **Detailed description** - Specific information about your billing question or issue
+  * **Account details** - Your Kiro account email and subscription information
+  * **Context** - Any relevant error messages or circumstances
+
+
+## Tips for effective support requests[](https://kiro.dev/docs/cli/billing/contact-support/#tips-for-effective-support-requests)
+To help us resolve your issue quickly:
+  * **Be specific** - Clearly describe the billing problem you're experiencing
+  * **Include relevant details** - Account email, subscription tier, approximate dates of issues
+  * **Mention previous attempts** - Let us know if you've tried any troubleshooting steps
+
+
+**Info**

package/.kiro/documentation/docs_cli_billing_managing-taxes.md

@@ -0,0 +1,67 @@
+# Managing your taxes
+This section provides answers to tax collection, VAT, and billing address questions for Kiro.
+## Why do I see information for Amazon web services, inc. For my Kiro purchase?[](https://kiro.dev/docs/cli/billing/managing-taxes/#why-do-i-see-information-for-amazon-web-services-inc-for-my-kiro-purchase)
+Amazon Web Services, Inc. is the service provider for Kiro. Amazon Web Services, Inc. ("AWSI") is established and operates in the United States. AWSI is registered for Sales Tax in the states shown [here](https://aws.amazon.com/tax-help/united-states/). AWSI is also registered for VAT in countries where indirect tax laws require foreign providers of Electronically Supplied Services ("ESS") to register and collect local VAT. AWSI treats Kiro as Downloaded Software in the USA and as ESS outside of the USA. If required by your country's Indirect Tax laws, AWS will collect Indirect Taxes from you, issue a tax invoice, and remit it to the tax authority in AWS's name. In some countries, AWS is not required to collect Indirect Taxes from you and remit it to the tax authority in AWS's name if you have a valid tax registration number ("TRN") in that country. You need to add your TRN to your Stripe Account Customer Profile, and you may be required to self-assess VAT depending on local regulations.
+Please see below jurisdictions where tax will be charged on Kiro purchases:
+Country Name | Tax Collected From | Tax Rate  
+---|---|---  
+AUSTRALIA | B2C | 10%  
+AUSTRIA | B2B/B2C | 20%  
+BANGLADESH | B2B | 15%  
+BELGIUM | B2B/B2C | 21%  
+BULGARIA | B2C | 20%  
+CANADA | B2B/B2C | Varies by Province  
+CHILE | B2C | 19%  
+CZECH REPUBLIC | B2B/B2C | 21%  
+FRANCE | B2C | 20%  
+GERMANY | B2C | 19%  
+INDIA | B2C | 18%  
+INDONESIA | B2B/B2C | 11%  
+ISRAEL | N/A | 18%  
+ITALY | B2C | 22%  
+JAPAN | B2B/B2C | 10%  
+KOREA (REPUBLIC OF KOREA) | B2C | 10%  
+MALAYSIA | B2B/B2C | 8%  
+NEPAL | B2B | 13%  
+NETHERLANDS | B2C | 21%  
+NEW ZEALAND | B2C | 15%  
+NORWAY | B2B/B2C | 25%  
+POLAND | B2C | 23%  
+PORTUGAL | B2B/B2C | 23%  
+ROMANIA | B2C | 19%  
+SINGAPORE | B2C | 9%  
+SOUTH AFRICA | B2B/B2C | 15%  
+SPAIN | B2C | 21%  
+SWEDEN | B2B/B2C | 25%  
+SWITZERLAND | B2B/B2C | 8.1%  
+TAIWAN | B2C | 5%  
+THAILAND | B2C | 7%  
+UK | B2C | 20%  
+UNITED ARAB EMIRATES | B2B/B2C | 5%  
+UNITED STATES (US) | B2B/B2C | Varies by state  
+## How does AWS determine my location to determine the applicable taxes for my account(s)?[](https://kiro.dev/docs/cli/billing/managing-taxes/#how-does-aws-determine-my-location-to-determine-the-applicable-taxes-for-my-accounts)
+AWS will use your customer billing address you provide when purchasing Kiro. If the billing address entered is invalid, you will get a customer_tax_location_invalid error.
+## I am a B2B (business) customer, my company's tax registration number (TRN) is on our stripe/AWS accounts, so why are we being charged VAT rather than using reverse charge and self-assessing VAT?[](https://kiro.dev/docs/cli/billing/managing-taxes/#i-am-a-b2b-business-customer-my-companys-tax-registration-number-trn-is-on-our-stripeaws-accounts-so-why-are-we-being-charged-vat-rather-than-using-reverse-charge-and-self-assessing-vat)
+Kiro is billed using a different platform (not the AWS Console). If you are a B2B customer who has provided its TRN in your AWS Account, you will need to also include for your Kiro account through your customer portal. In addition, certain jurisdictions require AWS to charge and collect tax on both B2B and B2C purchases, in these jurisdictions AWS is responsible, and you will not be able to Self-Assess.
+## If I update my tax, account, or billing address mid-month, how is VAT calculated?[](https://kiro.dev/docs/cli/billing/managing-taxes/#if-i-update-my-tax-account-or-billing-address-mid-month-how-is-vat-calculated)
+AWS will use your billing address at the time of your purchase, or changes to your subscription such as upgrades or renewals.
+## I receive special status/relief from paying VAT. How do I check that I am not charged VAT?[](https://kiro.dev/docs/cli/billing/managing-taxes/#i-receive-special-statusrelief-from-paying-vat-how-do-i-check-that-i-am-not-charged-vat)
+Special status/relief status from paying VAT is coming soon.
+## What payment currencies and payment methods are supported by AWS inc. For Kiro purchases?[](https://kiro.dev/docs/cli/billing/managing-taxes/#what-payment-currencies-and-payment-methods-are-supported-by-aws-inc-for-kiro-purchases)
+We accept all major credit cards. Kiro usage is invoiced in USD.
+## My VAT invoice, and/or AWS seller appears incorrectly.[](https://kiro.dev/docs/cli/billing/managing-taxes/#my-vat-invoice-andor-aws-seller-appears-incorrectly)
+Please contact [Kiro billing support](https://support.aws.amazon.com/#/contacts/kiro).
+## What tax registration numbers (trns) and formats are accepted?[](https://kiro.dev/docs/cli/billing/managing-taxes/#what-tax-registration-numbers-trns-and-formats-are-accepted)
+Kiro will accept TRNs based on the requirements set forth by the country in which the customer is located. When a customer adds a TRN, Kiro will check that the formatting is correct.
+Page updated: November 16, 2025
+[Managing your Kiro CLI subscription](https://kiro.dev/docs/cli/billing/subscription-portal/)
+[Related questions](https://kiro.dev/docs/cli/billing/related-questions/)
+On this page
+  * [Why do I see information for Amazon web services, inc. For my Kiro purchase?](https://kiro.dev/docs/cli/billing/managing-taxes/#why-do-i-see-information-for-amazon-web-services-inc-for-my-kiro-purchase)
+  * [How does AWS determine my location to determine the applicable taxes for my account(s)?](https://kiro.dev/docs/cli/billing/managing-taxes/#how-does-aws-determine-my-location-to-determine-the-applicable-taxes-for-my-accounts)
+  * [I am a B2B (business) customer, my company's tax registration number (TRN) is on our stripe/AWS accounts, so why are we being charged VAT rather than using reverse charge and self-assessing VAT?](https://kiro.dev/docs/cli/billing/managing-taxes/#i-am-a-b2b-business-customer-my-companys-tax-registration-number-trn-is-on-our-stripeaws-accounts-so-why-are-we-being-charged-vat-rather-than-using-reverse-charge-and-self-assessing-vat)
+  * [If I update my tax, account, or billing address mid-month, how is VAT calculated?](https://kiro.dev/docs/cli/billing/managing-taxes/#if-i-update-my-tax-account-or-billing-address-mid-month-how-is-vat-calculated)
+  * [I receive special status/relief from paying VAT. How do I check that I am not charged VAT?](https://kiro.dev/docs/cli/billing/managing-taxes/#i-receive-special-statusrelief-from-paying-vat-how-do-i-check-that-i-am-not-charged-vat)
+  * [What payment currencies and payment methods are supported by AWS inc. For Kiro purchases?](https://kiro.dev/docs/cli/billing/managing-taxes/#what-payment-currencies-and-payment-methods-are-supported-by-aws-inc-for-kiro-purchases)
+  * [My VAT invoice, and/or AWS seller appears incorrectly.](https://kiro.dev/docs/cli/billing/managing-taxes/#my-vat-invoice-andor-aws-seller-appears-incorrectly)
+  * [What tax registration numbers (trns) and formats are accepted?](https://kiro.dev/docs/cli/billing/managing-taxes/#what-tax-registration-numbers-trns-and-formats-are-accepted)

package/.kiro/documentation/docs_cli_billing_related-questions.md

@@ -0,0 +1,49 @@
+# Related questions
+This section provides answers to billing, subscriptions, and payment questions for Kiro.
+## Which countries or regions are supported for paid plans?[](https://kiro.dev/docs/cli/billing/related-questions/#which-countries-or-regions-are-supported-for-paid-plans)
+Currently, you can purchase a Kiro paid plan with a billing address in Afghanistan, Algeria, Angola, Antigua and Barbuda, Argentina, Armenia, Aruba, Australia, Austria, Azerbaijan, Bangladesh, Belgium, Belize, Bermuda, Bhutan, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, Brunei, Bulgaria, Burkina Faso, Burundi, Cambodia, Canada, Cape Verde, Cayman Islands, Central African Republic, Chad, Chile, China, Colombia, Comoros, Congo, Cook Islands, Costa Rica, Croatia, Curacao, Cyprus, Czech Republic, Democratic Republic of the Congo, Denmark, Djibouti, Dominica, Dominican Republic, East Timor, Ecuador, El Salvador, Equatorial Guinea, Eritrea, Estonia, Ethiopia, Falkland Islands, Fiji, Finland, France, French Guiana, Gabon, Gambia, Germany, Gibraltar, Greece, Greenland, Grenada, Guatemala, Guinea, Guinea-Bissau, Guyana, Haiti, Honduras, Hong Kong SAR, Hungary, India, Indonesia, Iraq, Ireland, Israel, Italy, Jamaica, Japan, Jordan, Kiribati, Kosovo, Latvia, Lebanon, Lesotho, Liberia, Libya, Lithuania, Luxembourg, Macao, Macedonia, Madagascar, Malawi, Malaysia, Maldives, Mali, Malta, Mauritania, Mexico, Mongolia, Montenegro, Morocco, Mozambique, Myanmar, Namibia, Nauru, Nepal, Netherlands, New Zealand, Nicaragua, Niger, Norway, Palestinian Territories, Panama, Papua New Guinea, Paraguay, Philippines, Poland, Portugal, Qatar, Romania, Rwanda, Saint Kitts and Nevis, Saint Lucia, Saint Vincent and the Grenadines, Samoa, San Marino, Seychelles, Sierra Leone, Singapore, Slovakia, Slovenia, Solomon Islands, Somalia, South Africa, South Korea, South Sudan, Spain, Sri Lanka, Swaziland, Sweden, Switzerland, Tajikistan, Tanzania, Thailand, Togo, Tonga, Trinidad and Tobago, Tunisia, Turkmenistan, Tuvalu, United Arab Emirates, United Kingdom, United States of America, Uruguay, Uzbekistan, Vanuatu, Vatican City State, Venezuela, and Yemen. More countries or regions will be added soon.
+## What is a credit?[](https://kiro.dev/docs/cli/billing/related-questions/#what-is-a-credit)
+A credit is a unit of work in response to user prompts. Simple prompts can consume less than 1 credit. More complex prompts, such as executing a spec task, typically cost more than 1 credit. Additionally, different models consume credits at different rates, with a prompt executed via Sonnet 4 costing more credits than executing it with Auto. For example, a given task that consumes X credits to execute in Auto, will cost you 1.3X credits to execute via Sonnet 4. Credits are metered to the second decimal point, so the least number of credits a task can consume is 0.01 credits.
+## What paid plan should I choose if I'm not sure about my future usage?[](https://kiro.dev/docs/cli/billing/related-questions/#what-paid-plan-should-i-choose-if-im-not-sure-about-my-future-usage)
+Many customers are still exploring agentic development, and we expect that learning curve to continue beyond the first month. We don’t want you to have to predict your future usage or “time” upgrades to get a fair deal—we want you focused on building. A good path is to start on Pro and, if needed, enable overage so you can continue working without friction. If you later decide you need more, upgrade when you’re ready. In your first paid month we’ll discount for what you already paid and charge a single prorated amount for the higher plan back to the day you first became paid, so you won’t pay more than if you had upgraded earlier. For example, in a 30-day month if you start Pro on day 15 ($10 for the rest of the month) and later switch to Pro+ the same month, we discount for the $10 and charge $20—net $10—so you finish the month on Pro+ with one prorated allowance. From Month 2 onward, upgrades charge the full price difference and we re-rate the whole month under the higher plan’s limits, which also prevents overpaying.
+## What paid plan should I choose once my Kiro usage is stable?[](https://kiro.dev/docs/cli/billing/related-questions/#what-paid-plan-should-i-choose-once-my-kiro-usage-is-stable)
+Our intent with Kiro’s pricing is to let most developers work comfortably without micromanaging usage or worrying about surprises. Once your usage settles into a pattern, choose the smallest subscription plan that reliably covers a typical month, with a little headroom. That reflects our goal of making your default experience predictable: if you prefer a fixed bill, leave overage off and your usage will pause at the cap; if you prefer continuity during occasional spikes, keep overage on. If those spikes become frequent, or your month-end overage spend starts to approach the price difference to the next tier, moving up will usually lower your total cost while keeping things simple.
+## What happens when I reach the monthly limit of my plan?[](https://kiro.dev/docs/cli/billing/related-questions/#what-happens-when-i-reach-the-monthly-limit-of-my-plan)
+If you hit the limit, requests pause until your limits reset at the start of the next month.
+The **Kiro Free** tier has fixed monthly limits and does not allow overage. If you hit a Free limit, you can upgrade to a paid plan for immediate additional capacity.
+On paid plans, you can enable overage to continue working uninterrupted beyond your included limits. You can also upgrade to a higher plan at any time, and the higher usage limits immediately apply.
+## I'm near month-end. Should I upgrade now or rely on overage?[](https://kiro.dev/docs/cli/billing/related-questions/#im-near-month-end-should-i-upgrade-now-or-rely-on-overage)
+If you're on a paid plan and only have a few days left, turning on overage is often the simplest way to finish the month unless your month-to-date overage cost is approaching the price difference to the next tier. When that "breakeven" point is reached, upgrading will usually lower your total bill and raise your limits immediately. In your first paid month, if you do upgrade late, we apply a discount for what you've already paid and charge a single prorated amount for the higher plan back to the day you first became paid, so you don't overpay for waiting a bit. From Month 2 onward, mid-month upgrades charge the full price difference and we re-rate the whole month under the higher plan.
+## What happens to my bonus credits if I upgrade early?[](https://kiro.dev/docs/cli/billing/related-questions/#what-happens-to-my-bonus-credits-if-i-upgrade-early)
+If you are within the 30 day trial period for the bonus credits, those credits will carry over for the remainder of the 30 day trial period, independent of the plan you upgrade to.
+## How does proration work during the initial month that I upgrade from the free trial or Kiro free tier to paying?[](https://kiro.dev/docs/cli/billing/related-questions/#how-does-proration-work-during-the-initial-month-that-i-upgrade-from-the-free-trial-or-kiro-free-tier-to-paying)
+During the month that you first upgrade to a paid plan, the plan charges are pro-rated by days remaining in the month. For example, in a 30-day month, if you upgrade to Pro ($20) with 10 days left (i.e., on day 21), you pay $6.67 (10/30 of $20) and receive access to Pro credit limits immediately. Informally, because you’re on Pro for one-third of the month, you pay one-third of the price, but get the full monthly quota of your new plan immediately.
+If you later upgrade to Pro+ ($40) in that same first paid month, we discount the $6.67 you already paid for Pro and charge $13.33 (10⁄30 of $40), so your net extra payment is $6.66 at the time of upgrade. On your invoice, this appears as a discount line for the earlier Pro charge and a prorated charge line for Pro+.
+## How does proration work after the first upgrade?[](https://kiro.dev/docs/cli/billing/related-questions/#how-does-proration-work-after-the-first-upgrade)
+Prorated pay only applies to the first upgrade. After the first upgrade, any future upgrade, at any day of the month, will be charged in full and users will receive full plan limits.
+## What happens to my existing overage if I upgrade during the middle of the month?[](https://kiro.dev/docs/cli/billing/related-questions/#what-happens-to-my-existing-overage-if-i-upgrade-during-the-middle-of-the-month)
+Our intent is that you shouldn’t have to “time” an upgrade or pay twice for the same usage. When you upgrade to a higher subscription plan mid-month, we re-evaluate your month-to-date usage under the higher plan, so you get the benefit of its larger limits.
+## When does Kiro bill me?[](https://kiro.dev/docs/cli/billing/related-questions/#when-does-kiro-bill-me)
+Kiro bills on a calendar month. Your billing month starts at 12:00 a.m. (UTC) on the first day of the month and ends at 11:59 p.m. (UTC) on the last day. The exact timing of your monthly charge will depend on your local timezone. If you upgrade mid-month, we will bill you immediately for the cost of the new plan discounted by the cost of the prior plan. Overage is included as separate line items on your month’s bill.
+## Why might a single action span more than one credit?[](https://kiro.dev/docs/cli/billing/related-questions/#why-might-a-single-action-span-more-than-one-credit)
+Some actions require much more context or generate more output than average, such as working across a large codebase or executing a highly complex build. When that happens, the total token usage can exceed the limit for a single request, and Kiro will count it as more than one credit. You’ll see the count right after the interaction finishes.
+## How does Kiro help optimize my costs?[](https://kiro.dev/docs/cli/billing/related-questions/#how-does-kiro-help-optimize-my-costs)
+Kiro is engineered to minimize redundant LLM work. We reuse context where possible and apply provider‑level efficiencies, such as token‑efficient tool use and prompt caching when available, to cut underlying token spend without adding friction to your workflow. You pay by request, not by token, and we pass efficiency gains through Kiro's pricing plan design rather than asking you to micromanage prompts.
+Page updated: December 17, 2025
+[Managing your taxes](https://kiro.dev/docs/cli/billing/managing-taxes/)
+[Contacting billing support](https://kiro.dev/docs/cli/billing/contact-support/)
+On this page
+  * [Which countries or regions are supported for paid plans?](https://kiro.dev/docs/cli/billing/related-questions/#which-countries-or-regions-are-supported-for-paid-plans)
+  * [What is a credit?](https://kiro.dev/docs/cli/billing/related-questions/#what-is-a-credit)
+  * [What paid plan should I choose if I'm not sure about my future usage?](https://kiro.dev/docs/cli/billing/related-questions/#what-paid-plan-should-i-choose-if-im-not-sure-about-my-future-usage)
+  * [What paid plan should I choose once my Kiro usage is stable?](https://kiro.dev/docs/cli/billing/related-questions/#what-paid-plan-should-i-choose-once-my-kiro-usage-is-stable)
+  * [What happens when I reach the monthly limit of my plan?](https://kiro.dev/docs/cli/billing/related-questions/#what-happens-when-i-reach-the-monthly-limit-of-my-plan)
+  * [I'm near month-end. Should I upgrade now or rely on overage?](https://kiro.dev/docs/cli/billing/related-questions/#im-near-month-end-should-i-upgrade-now-or-rely-on-overage)
+  * [What happens to my bonus credits if I upgrade early?](https://kiro.dev/docs/cli/billing/related-questions/#what-happens-to-my-bonus-credits-if-i-upgrade-early)
+  * [How does proration work during the initial month that I upgrade from the free trial or Kiro free tier to paying?](https://kiro.dev/docs/cli/billing/related-questions/#how-does-proration-work-during-the-initial-month-that-i-upgrade-from-the-free-trial-or-kiro-free-tier-to-paying)
+  * [How does proration work after the first upgrade?](https://kiro.dev/docs/cli/billing/related-questions/#how-does-proration-work-after-the-first-upgrade)
+  * [What happens to my existing overage if I upgrade during the middle of the month?](https://kiro.dev/docs/cli/billing/related-questions/#what-happens-to-my-existing-overage-if-i-upgrade-during-the-middle-of-the-month)
+  * [When does Kiro bill me?](https://kiro.dev/docs/cli/billing/related-questions/#when-does-kiro-bill-me)
+  * [Why might a single action span more than one credit?](https://kiro.dev/docs/cli/billing/related-questions/#why-might-a-single-action-span-more-than-one-credit)
+  * [How does Kiro help optimize my costs?](https://kiro.dev/docs/cli/billing/related-questions/#how-does-kiro-help-optimize-my-costs)
+  * [How can I retrieve my User ID?](https://kiro.dev/docs/cli/billing/related-questions/#how-can-i-retrieve-my-user-id)

package/.kiro/documentation/docs_cli_billing_subscription-portal.md

@@ -0,0 +1,31 @@
+# Managing Your Kiro Subscription
+Your Kiro subscription gives you access to powerful AI-powered development tools. You can manage your subscription, view usage, and update billing information through the subscription portal.
+## Accessing the subscription portal[](https://kiro.dev/docs/cli/billing/subscription-portal/#accessing-the-subscription-portal)
+Follow [this link](https://app.kiro.dev/account/usage) to the portal.
+You can also use the `/usage` command to remind you of the URL.
+## What you can do in the portal[](https://kiro.dev/docs/cli/billing/subscription-portal/#what-you-can-do-in-the-portal)
+Once you're in the subscription portal, you can:
+  * **View current plan** and usage statistics
+  * **Upgrade or downgrade** your subscription
+  * **Update payment methods** and billing information
+  * **Download invoices** and billing history
+  * **Manage team members** (for team plans)
+  * **Cancel your subscription** if needed
+
+
+![Kiro Web Portal](https://kiro.dev/images/kiro-web-portal.png?h=5c73d685)
+## Need help?[](https://kiro.dev/docs/cli/billing/subscription-portal/#need-help)
+If you need assistance with your subscription, you can:
+  * Visit our [billing support page](https://kiro.dev/billing/contact-support)
+  * Email us at billing@kiro.dev
+  * Use the help chat in the subscription portal
+
+
+Page updated: November 16, 2025
+[Billing for individuals](https://kiro.dev/docs/cli/billing/)
+[Managing your taxes](https://kiro.dev/docs/cli/billing/managing-taxes/)
+On this page
+  * [Accessing the subscription portal](https://kiro.dev/docs/cli/billing/subscription-portal/#accessing-the-subscription-portal)
+  * [From the IDE](https://kiro.dev/docs/cli/billing/subscription-portal/#from-the-ide)
+  * [What you can do in the portal](https://kiro.dev/docs/cli/billing/subscription-portal/#what-you-can-do-in-the-portal)
+  * [Need help?](https://kiro.dev/docs/cli/billing/subscription-portal/#need-help)

package/.kiro/documentation/docs_cli_chat.md

@@ -0,0 +1,84 @@
+# Chat
+The Kiro CLI provides an interactive chat mode that lets you have natural conversations with AI directly in your terminal. This feature brings the power of conversational AI to your command-line workflow.
+## Starting a session[](https://kiro.dev/docs/cli/chat/#starting-a-session)
+To start a chat session
+bash
+```
+
+kiro-cli
+
+
+```
+
+Or start a chat with a specific context:
+bash
+```
+
+kiro-cli --agent myagent
+
+
+```
+
+## Entering multi-line statements[](https://kiro.dev/docs/cli/chat/#entering-multi-line-statements)
+To enter multi-line statements, use the `/editor` command or type `Ctrl(^) + J` to insert new-line for multi-line prompt
+bash
+```
+
+/editor
+
+
+```
+
+This opens your default editor (defaults to vi) where you can compose longer, multi-line prompts. After you save and close the editor, the content will be sent as your message to Kiro.
+You can also:
+  * Use the [`/reply`](https://kiro.dev/docs/cli/chat/responding) command to open your editor with the most recent assistant message quoted for reply, which is useful for multi-line responses to previous messages.
+
+
+## Conversation persistence[](https://kiro.dev/docs/cli/chat/#conversation-persistence)
+Kiro can remember your conversations based on the folder where you started them. When you start a session where you previously chatted with Kiro, you can tell Kiro to automatically load that conversation history, allowing you to seamlessly continue your discussion.
+### Directory-based persistence[](https://kiro.dev/docs/cli/chat/#directory-based-persistence)
+If it's your first time chatting in that directory, Kiro will start a new conversation (taking into consideration any designated context).
+To explicitly resume a conversation in the current directory, use:
+bash
+```
+
+$ kiro-cli chat --resume
+
+
+```
+
+### Manually saving and loading conversations[](https://kiro.dev/docs/cli/chat/#manually-saving-and-loading-conversations)
+You can also manually save and load conversations using the following commands while in a chat session:
+bash
+```
+
+    /save [path] – Saves your current conversation to a JSON file.
+
+        Add -f or --force to overwrite an existing file
+
+        Examples:
+
+        /save ./my-project-conversation -f
+
+        /save /home/user/project/my-project-conversation.json
+
+        You cannot use ~ to denote your home directory.
+
+    /load [path] – Loads a conversation from a previously saved JSON file
+
+        Example: /load ./my-project-conversation.json
+
+
+```
+
+**Info**
+The `/save` and `/load` commands operate independently of the directory where the conversation was originally created. When loading a conversation, be mindful that it will replace your current conversation regardless of which directory it was saved from.
+Page updated: November 16, 2025
+[Authentication](https://kiro.dev/docs/cli/authentication/)
+[Model selection](https://kiro.dev/docs/cli/chat/model-selection/)
+On this page
+  * [Starting a session](https://kiro.dev/docs/cli/chat/#starting-a-session)
+  * [Entering multi-line statements](https://kiro.dev/docs/cli/chat/#entering-multi-line-statements)
+  * [Conversation persistence](https://kiro.dev/docs/cli/chat/#conversation-persistence)
+  * [Directory-based persistence](https://kiro.dev/docs/cli/chat/#directory-based-persistence)
+  * [Manually saving and loading conversations](https://kiro.dev/docs/cli/chat/#manually-saving-and-loading-conversations)

package/.kiro/documentation/docs_cli_chat_configuration.md

@@ -0,0 +1,40 @@
+# Configuration
+### Configuration file paths[](https://kiro.dev/docs/cli/chat/configuration/#configuration-file-paths)
+You can configure Kiro CLI to match your development preferences and team standards. You can set configuration in one of three scopes:
+  1. **Global** - Configuration that is applied across all the projects where Kiro is used - `<user-home>/.kiro/`
+  2. **Project** - Configuration specific to a project - `<project-root>/.kiro`
+  3. **Agent** - Configuration defined in the agent configuration file - `<user-home | project-root>/.kiro/agents`
+
+Configuration | Global Scope | Project Scope  
+---|---|---  
+MCP servers | `~/.kiro/settings/mcp.json` | `.kiro/settings/mcp.json`  
+Prompts | `~/.kiro/prompts` | `.kiro/prompts`  
+Custom agents | `~/.kiro/agents` | `.kiro/agents`  
+Steering | `~/.kiro/steering` | `.kiro/steering`  
+Settings | `~/.kiro/settings/cli.json` |   
+### What can you configure at these scopes[](https://kiro.dev/docs/cli/chat/configuration/#what-can-you-configure-at-these-scopes)
+Configuration | User Scope | Project Scope | Agent Scope  
+---|---|---|---  
+MCP servers | Yes | Yes | Yes  
+Prompts | Yes | Yes | No  
+Custom agents | Yes | Yes | N/A  
+Steering | Yes | Yes | Yes  
+Settings | Yes | N/A | N/A  
+### Resolving configuration conflicts[](https://kiro.dev/docs/cli/chat/configuration/#resolving-configuration-conflicts)
+Configuration conflicts are resolved by selecting the configuration that is closest to where you are interacting with Kiro CLI. For example, if you have a MCP configuration in both global and project `mcp.json` files, when you are chatting with Kiro in the project folder, the MCP configuration from the project folder will be applied.
+Since you can also define a custom agents at a global and project scope, if there is a conflict between at the same level with the agent configuration, then Kiro CLI will choose the configuration from the agent.
+Here's the priority order of how configuration is rationalized:
+Configuration | Priority  
+---|---  
+MCP servers | Agent > Project > Global  
+Prompts | Project > Global  
+Custom agents | Project > Global  
+Steering | Project > Global  
+Since MCP servers can be configured in three scopes and there is a `includeMcpJson` setting in an agent configuration, MCP servers are handled slightly differently. Refer [MCP server loading priority](https://kiro.dev/docs/cli/mcp/#mcp-server-loading-priority)
+Page updated: December 10, 2025
+[Security considerations](https://kiro.dev/docs/cli/chat/security/)
+[Custom agents](https://kiro.dev/docs/cli/custom-agents/)
+On this page
+  * [Configuration file paths](https://kiro.dev/docs/cli/chat/configuration/#configuration-file-paths)
+  * [What can you configure at these scopes](https://kiro.dev/docs/cli/chat/configuration/#what-can-you-configure-at-these-scopes)
+  * [Resolving configuration conflicts](https://kiro.dev/docs/cli/chat/configuration/#resolving-configuration-conflicts)