kiro-agent-team 1.0.0

package/.kiro/documentation/docs_cli_custom-agents_creating.md

@@ -0,0 +1,93 @@
+# Creating custom agents
+Custom agents allow you to tailor Kiro CLI behavior for specific tasks by defining which tools are available, what permissions are granted, and what context is automatically included.
+## Quick start[](https://kiro.dev/docs/cli/custom-agents/creating/#quick-start)
+You can create an agent configuration using a slash command from within a Kiro CLI chat session. It will guide you through the process of configuring the agent:
+```
+
+> /agent generate
+
+✔ Enter agent name:  · backend-specialist
+✔ Enter agent description:  · You are specialist in backend coding practices 
+✔ Agent scope · Local (current workspace)
+Select MCP servers (use Space to toggle, Enter to confirm): markdown-downloader (node), code-analysis (uv)
+
+✓ Agent 'backend-specialist' has been created and saved successfully!
+
+
+```
+
+Alternatively, you can also use the CLI command to create a new custom agent:
+bash
+```
+
+kiro-cli agent create --name my-agent
+
+
+```
+
+This will guide you through the setup process and create a configuration file at `~/.kiro/agents/my-agent.json`.
+## Agent configuration file[](https://kiro.dev/docs/cli/custom-agents/creating/#agent-configuration-file)
+Custom agents are defined using JSON configuration files. Here's a basic example:
+json
+```
+
+{
+  "name": "my-agent",
+  "description": "A custom agent for my workflow",
+  "tools": ["read","write"],
+  "allowedTools": ["read"],
+  "resources": ["file://README.md", "file://.kiro/steering/**/*.md"],
+  "prompt": "You are a helpful coding assistant",
+  "model": "claude-sonnet-4"
+}
+
+
+```
+
+## Using your custom agent[](https://kiro.dev/docs/cli/custom-agents/creating/#using-your-custom-agent)
+Start a new chat session - which uses the default agent ("kiro_default") and swap to an agent using the agent slash command
+bash
+```
+
+> /agent swap
+
+ Choose one of the following agents 
+❯ rust-developer-agent
+  kiro_default
+  backend-specialist
+
+
+```
+
+After selecting an agent, you will see the following:
+bash
+```
+
+✔ Choose one of the following agents · backend-specialist
+
+[backend-specialist] > 
+
+
+```
+
+Alternatively, start a chat session with your custom agent:
+bash
+```
+
+kiro-cli --agent my-agent
+
+
+```
+
+## Next steps[](https://kiro.dev/docs/cli/custom-agents/creating/#next-steps)
+  * Explore [Agent Configuration](https://kiro.dev/docs/cli/custom-agents/configuration-reference) options in detail
+
+
+Page updated: November 18, 2025
+[Custom agents](https://kiro.dev/docs/cli/custom-agents/)
+[Configuration reference](https://kiro.dev/docs/cli/custom-agents/configuration-reference/)
+On this page
+  * [Quick start](https://kiro.dev/docs/cli/custom-agents/creating/#quick-start)
+  * [Agent configuration file](https://kiro.dev/docs/cli/custom-agents/creating/#agent-configuration-file)
+  * [Using your custom agent](https://kiro.dev/docs/cli/custom-agents/creating/#using-your-custom-agent)
+  * [Next steps](https://kiro.dev/docs/cli/custom-agents/creating/#next-steps)

package/.kiro/documentation/docs_cli_custom-agents_examples.md

@@ -0,0 +1,360 @@
+# Agent Examples
+This page provides practical examples of custom agents you can use as starting points for your own workflows.
+## AWS Specialist Agent[](https://kiro.dev/docs/cli/custom-agents/examples/#aws-specialist-agent)
+This custom agent is optimized for AWS infrastructure management and development tasks. It provides pre-approved access to AWS tools while including relevant documentation.
+json
+```
+
+{
+  "name": "aws-specialist-agent",
+  "description": "Specialized custom agent for AWS infrastructure and development tasks",
+  "prompt": "You are an expert AWS infrastructure specialist with deep knowledge of cloud architecture and best practices",
+  "tools": [
+    "read",
+    "write",
+    "shell",
+    "aws"
+  ],
+  "allowedTools": [
+    "read",
+    "aws"
+  ],
+  "toolsSettings": {
+    "aws": {
+      "allowedServices": [
+        "s3",
+        "lambda",
+        "cloudformation",
+        "ec2",
+        "iam",
+        "logs"
+      ]
+    },
+    "write": {
+      "allowedPaths": [
+        "infrastructure/**",
+        "scripts/**",
+        "*.yaml",
+        "*.yml",
+        "*.json"
+      ]
+    }
+  },
+  "resources": [
+    "file://README.md",
+    "file://infrastructure/**/*.yaml",
+    "file://infrastructure/**/*.yml",
+    "file://docs/aws-setup.md",
+    "file://scripts/deploy.sh"
+  ],
+  "hooks": {
+    "agentSpawn": [
+      {
+        "command": "aws sts get-caller-identity",
+        "timeout_ms": 10000,
+        "cache_ttl_seconds": 300
+      }
+    ]
+  },
+  "model": "claude-sonnet-4"
+}
+
+
+```
+
+Use cases:
+  * Deploying CloudFormation stacks
+  * Managing S3 buckets and Lambda functions
+  * Troubleshooting AWS service issues
+  * Reviewing and updating infrastructure as code
+
+
+## Development Workflow Agent[](https://kiro.dev/docs/cli/custom-agents/examples/#development-workflow-agent)
+This custom agent is designed for general software development tasks, including code review, testing, and Git operations.
+json
+```
+
+{
+  "name": "development-workflow-agent",
+  "description": "General development workflow custom agent with Git integration",
+  "prompt": "You are a software development assistant with expertise in Git workflows and code management",
+  "mcpServers": {
+    "git": {
+      "command": "git-mcp-server",
+      "args": [],
+      "timeout": 30000
+    }
+  },
+  "tools": [
+    "read",
+    "write",
+    "shell",
+    "@git"
+  ],
+  "allowedTools": [
+    "read",
+    "@git/git_status",
+    "@git/git_log",
+    "@git/git_diff"
+  ],
+  "toolAliases": {
+    "@git/git_status": "status",
+    "@git/git_log": "log",
+    "@git/git_diff": "diff"
+  },
+  "toolsSettings": {
+    "write": {
+      "allowedPaths": [
+        "src/**",
+        "tests/**",
+        "docs/**",
+        "*.md",
+        "*.json",
+        "package.json",
+        "requirements.txt"
+      ]
+    }
+  },
+  "resources": [
+    "file://README.md",
+    "file://CONTRIBUTING.md",
+    "file://docs/**/*.md",
+    "file://package.json",
+    "file://requirements.txt"
+  ],
+  "hooks": {
+    "agentSpawn": [
+      {
+        "command": "git status --porcelain",
+        "timeout_ms": 5000
+      },
+      {
+        "command": "git branch --show-current",
+        "timeout_ms": 3000
+      }
+    ]
+  }
+}
+
+
+```
+
+Use cases:
+  * Code review and analysis
+  * Writing and updating tests
+  * Git workflow management
+  * Documentation updates
+  * Dependency management
+
+
+## Code Review Agent[](https://kiro.dev/docs/cli/custom-agents/examples/#code-review-agent)
+This custom agent focuses specifically on code review tasks, with tools and context optimized for analyzing code quality, security, and best practices.
+json
+```
+
+{
+  "name": "code-review-agent",
+  "description": "Specialized custom agent for code review and quality analysis",
+  "prompt": "You are a code review specialist focused on quality, security, and best practices",
+  "tools": [
+    "read",
+    "shell"
+  ],
+  "allowedTools": [
+    "read",
+    "shell"
+  ],
+  "toolsSettings": {
+    "shell": {
+      "allowedCommands": [
+        "grep",
+        "find",
+        "wc",
+        "head",
+        "tail",
+        "cat",
+        "diff",
+        "git diff",
+        "git log",
+        "eslint",
+        "pylint",
+        "rubocop"
+      ]
+    }
+  },
+  "resources": [
+    "file://CONTRIBUTING.md",
+    "file://docs/coding-standards.md",
+    "file://docs/security-guidelines.md",
+    "file://.eslintrc.json",
+    "file://.pylintrc",
+    "file://pyproject.toml"
+  ],
+  "hooks": {
+    "agentSpawn": [
+      {
+        "command": "git diff --name-only HEAD~1",
+        "timeout_ms": 5000,
+        "max_output_size": 2048
+      }
+    ],
+    "userPromptSubmit": [
+      {
+        "command": "find . -name '*.py' -o -name '*.js' -o -name '*.ts' | wc -l",
+        "timeout_ms": 3000,
+        "cache_ttl_seconds": 60
+      }
+    ]
+  }
+}
+
+
+```
+
+Use cases:
+  * Reviewing pull requests for code quality
+  * Identifying security vulnerabilities
+  * Checking adherence to coding standards
+  * Analyzing code complexity and maintainability
+  * Suggesting improvements and refactoring opportunities
+
+
+## Project-Specific Agent[](https://kiro.dev/docs/cli/custom-agents/examples/#project-specific-agent)
+This example shows how to create a custom agent tailored to a specific project, including project-specific tools, documentation, and build processes.
+json
+```
+
+{
+  "name": "mobile-app-agent",
+  "description": "Custom agent for the mobile app backend project",
+  "prompt": "You are a backend development specialist for mobile applications with expertise in Docker and database management",
+  "mcpServers": {
+    "docker": {
+      "command": "docker-mcp-server",
+      "args": ["--socket", "/var/run/docker.sock"]
+    },
+    "database": {
+      "command": "postgres-mcp-server",
+      "args": ["--connection", "postgresql://localhost:5432/myapp"],
+      "env": {
+        "PGPASSWORD": "$DATABASE_PASSWORD"
+      }
+    }
+  },
+  "tools": [
+    "read",
+    "write",
+    "shell",
+    "@docker",
+    "@database"
+  ],
+  "allowedTools": [
+    "read",
+    "@docker/docker_ps",
+    "@docker/docker_logs",
+    "@database/query_read_only"
+  ],
+  "toolAliases": {
+    "@docker/docker_ps": "containers",
+    "@docker/docker_logs": "logs",
+    "@database/query_read_only": "query"
+  },
+  "toolsSettings": {
+    "write": {
+      "allowedPaths": [
+        "src/**",
+        "tests/**",
+        "migrations/**",
+        "docker-compose.yml",
+        "Dockerfile",
+        "requirements.txt"
+      ]
+    },
+    "shell": {
+      "allowedCommands": [
+        "npm test",
+        "npm run build",
+        "python manage.py test",
+        "docker-compose up",
+        "docker-compose down"
+      ]
+    }
+  },
+  "resources": [
+    "file://README.md",
+    "file://docs/api-documentation.md",
+    "file://docs/database-schema.md",
+    "file://docker-compose.yml",
+    "file://requirements.txt",
+    "file://src/config/settings.py"
+  ],
+  "hooks": {
+    "agentSpawn": [
+      {
+        "command": "docker-compose ps",
+        "timeout_ms": 10000,
+        "cache_ttl_seconds": 30
+      },
+      {
+        "command": "git status --porcelain",
+        "timeout_ms": 5000
+      }
+    ]
+  }
+}
+
+
+```
+
+Use cases:
+  * Managing Docker containers and services
+  * Running database queries and migrations
+  * Building and testing the application
+  * Debugging production issues
+  * Updating API documentation
+
+
+## Tips for Creating Effective Custom Agents[](https://kiro.dev/docs/cli/custom-agents/examples/#tips-for-creating-effective-custom-agents)
+  * **Start simple** - Begin with basic tool configurations and add complexity as needed
+  * **Use descriptive names** - Choose custom agent names that clearly indicate their purpose
+  * **Include relevant context** - Add project documentation and configuration files to resources
+  * **Pre-approve safe tools** - Include frequently used, low-risk tools in allowedTools
+  * **Use hooks for dynamic context** - Include current system state through command hooks
+  * **Limit tool scope** - Use toolsSettings to restrict tool access to relevant paths and services
+  * **Test thoroughly** - Verify that your custom agent configuration works as expected
+  * **Document your custom agents** - Use clear descriptions to help team members understand custom agent purposes
+
+
+## Remote MCP Server Integration[](https://kiro.dev/docs/cli/custom-agents/examples/#remote-mcp-server-integration)
+This example shows an agent configured to use a remote MCP server:
+json
+```
+
+{
+  "name": "domain-finder",
+  "description": "Agent with access to domain search capabilities",
+  "prompt": "You help users find and research domain names using the find-a-domain service.",
+  "mcpServers": {
+    "find-a-domain": {
+      "type": "http",
+      "url": "https://api.findadomain.dev/mcp"
+    }
+  },
+  "tools": ["@find-a-domain"],
+  "allowedTools": ["@find-a-domain"]
+}
+
+
+```
+
+This agent provides access to domain search tools through a remote MCP server. If the server requires OAuth authentication, use the `/mcp` command to authenticate when prompted.
+Page updated: November 18, 2025
+[Configuration reference](https://kiro.dev/docs/cli/custom-agents/configuration-reference/)
+[Troubleshooting](https://kiro.dev/docs/cli/custom-agents/troubleshooting/)
+On this page
+  * [AWS Specialist Agent](https://kiro.dev/docs/cli/custom-agents/examples/#aws-specialist-agent)
+  * [Development Workflow Agent](https://kiro.dev/docs/cli/custom-agents/examples/#development-workflow-agent)
+  * [Code Review Agent](https://kiro.dev/docs/cli/custom-agents/examples/#code-review-agent)
+  * [Project-Specific Agent](https://kiro.dev/docs/cli/custom-agents/examples/#project-specific-agent)
+  * [Tips for Creating Effective Custom Agents](https://kiro.dev/docs/cli/custom-agents/examples/#tips-for-creating-effective-custom-agents)
+  * [Remote MCP Server Integration](https://kiro.dev/docs/cli/custom-agents/examples/#remote-mcp-server-integration)

package/.kiro/documentation/docs_cli_custom-agents_troubleshooting.md

@@ -0,0 +1,180 @@
+# Troubleshooting custom agents
+## Overview[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#overview)
+This guide helps you diagnose and resolve common issues when creating and using custom agents in Kiro CLI.
+### Configuration errors[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#configuration-errors)
+#### Invalid JSON syntax[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#invalid-json-syntax)
+**Problem** : Custom agent fails to load with JSON parsing errors.
+**Symptoms** :
+  * Error messages mentioning "invalid JSON" or "syntax error"
+  * Custom agent not appearing in /agent list
+  * Fallback to default agent behavior
+
+
+**Solutions** :
+  * Validate your JSON using a JSON validator or linter
+  * Check for common JSON errors: 
+    * Missing commas between array elements or object properties
+    * Trailing commas after the last element
+    * Unmatched brackets or braces
+    * Unescaped quotes in string values
+  * Use `/agent schema` to verify your configuration structure
+
+
+#### Schema validation errors[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#schema-validation-errors)
+**Problem** : Custom agent configuration doesn't match the expected schema.
+**Symptoms** :
+  * Warnings about unknown configuration fields
+  * Custom agent behavior not matching configuration
+  * Missing required fields errors
+
+
+**Solutions** :
+  * Compare your configuration against the schema using /agent schema
+  * Check field names for typos (e.g., allowedTools vs allowedTool)
+  * Verify data types match schema requirements (arrays vs strings, booleans vs strings)
+
+
+### Custom agent loading issues[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#custom-agent-loading-issues)
+#### Custom agent not found[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#custom-agent-not-found)
+**Problem** : Custom agent doesn't appear in the list or can't be used.
+**Symptoms** :
+  * `/agent list` doesn't show your custom agent
+  * Fallback to default agent without warning
+
+
+**Solutions** :
+  * Verify the custom agent file is in the correct location: 
+    * Global: `~/.kiro/agents/[name].json`
+    * Workspace: `.kiro/agents/[name].json`
+  * Check file permissions - ensure the file is readable
+  * Verify the filename matches the custom agent name you're trying to use
+  * Ensure the file has a .json extension
+
+
+#### Wrong custom agent version loading[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#wrong-custom-agent-version-loading)
+**Problem** : A different version of your custom agent is loading than expected.
+**Symptoms** :
+  * Custom agent behavior doesn't match your recent configuration changes
+  * Warning message about custom agent conflicts
+  * Unexpected tool availability or permissions
+
+
+**Solutions** :
+  * Check for custom agent name conflicts between local and global directories
+  * Remember that local custom agents take precedence over global custom agents
+  * Use /agent list to see which version is being loaded
+  * Remove or rename conflicting custom agent files if necessary
+
+
+### Tool permission problems[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#tool-permission-problems)
+### Tool not available[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#tool-not-available)
+**Problem** : Custom agent can't access a tool you've configured.
+**Symptoms** :
+  * Error messages about unknown or unavailable tools
+  * Custom agent asking for permission for tools in allowedTools
+  * MCP server tools not working
+
+
+**Solutions** :
+  * Verify tool names are spelled correctly in the tools array
+  * For MCP tools, ensure the server is properly configured in mcpServers
+  * Check that MCP servers are running and accessible
+  * Use correct syntax for MCP tools: @server_name/tool_name
+  * Verify built-in tool names against the built-in tools documentation
+
+
+#### /tools command returns empty list[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#tools-command-returns-empty-list)
+**Problem** : The /tools command shows no available tools or fewer tools than expected.
+**Symptoms** :
+  * `/tools` returns an empty list
+  * Expected tools are missing from the tools list
+  * Custom agent appears to have no capabilities
+
+
+**Common causes** :
+  * Empty tools array in the custom agent configuration
+  * Typos in tool names within the tools array
+  * Incorrect MCP server tool names (missing server prefix)
+  * MCP server configuration issues preventing tool loading
+
+
+**Solutions** :
+  * Check that your custom agent configuration includes a tools array with valid tool names
+  * Verify tool names are spelled correctly (case-sensitive)
+  * For MCP tools, ensure you're using the correct server-prefixed format: `@server-name___tool-name`
+  * Test with the default agent to confirm tools are available `/tools`
+  * Check MCP server status if using external tools
+
+
+#### Unexpected permission prompts[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#unexpected-permission-prompts)
+**Problem** : Custom agent prompts for permission for tools you thought were pre-approved.
+**Symptoms** :
+  * Permission prompts for tools listed in `allowedTools`
+  * Workflow interruptions despite custom agent configuration
+
+
+**Solutions** :
+  * Ensure tools are listed in both tools and allowedTools arrays
+  * Check for typos in tool names between the two arrays
+  * For MCP tools, use the full server-prefixed name in`allowedTools`
+  * Verify that toolAliases are correctly applied
+
+
+### Debugging custom agent behavior[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#debugging-custom-agent-behavior)
+#### Missing context or resources[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#missing-context-or-resources)
+**Problem** : Custom agent doesn't seem to have access to expected files or context.
+**Solutions** :
+  * Verify file paths in the resources array are correct and files exist
+  * Check that glob patterns in resources are matching the intended files
+  * Ensure hook commands are executing successfully and producing output
+  * Test hook commands manually to verify they work in your environment
+  * Check hook timeout settings if commands are being cut off
+
+
+#### MCP server issues[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#mcp-server-issues)
+**Problem** : MCP servers aren't working or tools aren't available.
+**Solutions** :
+  * Verify MCP server commands are correct and executables are in your PATH
+  * Check that required environment variables are set
+  * Test MCP servers independently to ensure they're working
+  * Review MCP server logs for error messages
+  * Increase timeout values if servers are slow to start
+
+
+#### Testing custom agent configurations[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#testing-custom-agent-configurations)
+To systematically test your custom agent configuration:
+  * Validate JSON syntax using a JSON validator
+  * Check configuration against schema using /agent schema
+  * Test custom agent loading with `/agent list`
+  * Switch to the custom agent with `/agent swap [name]`
+  * Test each tool individually to verify access and permissions
+  * Verify that resources and hooks are providing expected context
+  * Test common workflows to ensure the custom agent behaves as expected
+
+
+## Next steps[](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#next-steps)
+  * Review the [Configuration reference](https://kiro.dev/docs/cli/custom-agents/configuration-reference) for detailed options
+  * Check [Examples](https://kiro.dev/docs/cli/custom-agents/examples) for working configurations
+  * Learn about [Creating custom agents](https://kiro.dev/docs/cli/custom-agents/creating)
+
+
+Page updated: November 16, 2025
+[Examples](https://kiro.dev/docs/cli/custom-agents/examples/)
+[MCP](https://kiro.dev/docs/cli/mcp/)
+On this page
+  * [Overview](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#overview)
+  * [Configuration errors](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#configuration-errors)
+  * [Invalid JSON syntax](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#invalid-json-syntax)
+  * [Schema validation errors](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#schema-validation-errors)
+  * [Custom agent loading issues](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#custom-agent-loading-issues)
+  * [Custom agent not found](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#custom-agent-not-found)
+  * [Wrong custom agent version loading](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#wrong-custom-agent-version-loading)
+  * [Tool permission problems](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#tool-permission-problems)
+  * [Tool not available](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#tool-not-available)
+  * [/tools command returns empty list](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#tools-command-returns-empty-list)
+  * [Unexpected permission prompts](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#unexpected-permission-prompts)
+  * [Debugging custom agent behavior](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#debugging-custom-agent-behavior)
+  * [Missing context or resources](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#missing-context-or-resources)
+  * [MCP server issues](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#mcp-server-issues)
+  * [Testing custom agent configurations](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#testing-custom-agent-configurations)
+  * [Next steps](https://kiro.dev/docs/cli/custom-agents/troubleshooting/#next-steps)

package/.kiro/documentation/docs_cli_enterprise_billing.md

@@ -0,0 +1,33 @@
+# Enterprise billing
+When you subscribe your team to Kiro, you can choose from the following service tiers: **Kiro Pro** , **Kiro Pro+** , and **Kiro Power**. Depending on usage patterns, higher level tiers will give users more credits to use with Kiro.
+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 will give you more value from your credit allocation.
+## Tier comparison[](https://kiro.dev/docs/cli/enterprise/billing/#tier-comparison)
+Tier | Credits | Overage  
+---|---|---  
+Pro | 1,000 | Opt-in  
+Pro+ | 2,000 | Opt-in  
+Power | 10,000 | Opt-in  
+You are billed monthly for each user that you subscribe to Kiro. For more information, see [Kiro pricing](https://kiro.dev/pricing/).
+## I've subscribed a user twice. Will I be double-billed?[](https://kiro.dev/docs/cli/enterprise/billing/#ive-subscribed-a-user-twice-will-i-be-double-billed)
+It depends.
+If a user is subscribed twice _under the same Kiro profile_ (for example, in two different groups), then you will _not_ be charged twice. Instead, you will pay the subscription price of the highest tier assigned to the user. Example: If Alice is subscribed at the Pro tier in group A, and the Pro+ tier in group B, then you will pay the Pro+ tier price for Alice.
+If a user is subscribed twice under _different Kiro profiles_ (for example, in two different AWS Regions), then you will be charged twice. Example: If Bob is subscribed in Profile A in Europe (Frankfurt) and Profile B in US East (N. Virginia), then you will be charged twice for Bob.
+## Proration considerations[](https://kiro.dev/docs/cli/enterprise/billing/#proration-considerations)
+  * If you **unsubscribe** a user mid-month, you will pay for the last month in full. The cancellation takes effect at the beginning of the following month.
+  * If you **upgrade** a subscription mid-month, you will be refunded for the lower-tier subscription, and you will be charged in full for the higher-tier subscription.
+  * If you **downgrade** a subscription mid-month, you will pay in full for the higher-tier subscription, and you will be charged for the lower-tier subscription starting the following month.
+
+
+## Viewing your bill[](https://kiro.dev/docs/cli/enterprise/billing/#viewing-your-bill)
+  * You can view your bill in the AWS console's Billing and Cost Management service. The Kiro expenses are listed on the **Charges by service** tab, under **Kiro**. For more information about the Billing and Cost Management service, see [What is AWS Billing and Cost Management?](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-what-is.html) in the _AWS Billing User Guide_.
+  * You can identify the cost of Kiro subscriptions for specific users with resource IDs through AWS Billing and Cost Management. To do so, in the Billing and Cost Management console, under [Data Exports](https://console.aws.amazon.com/costmanagement/home#/bcm-data-exports), create either a standard data export or a legacy CUR export with the **Include resource IDs** option selected. To learn more, refer to [Creating data exports](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-create.html?icmpid=docs_costmanagement_hp-dataexports-export-type) in the _AWS Data Exports User Guide_.
+
+
+Page updated: November 16, 2025
+[Settings](https://kiro.dev/docs/cli/enterprise/settings/)
+[IAM](https://kiro.dev/docs/cli/enterprise/iam/)
+On this page
+  * [Tier comparison](https://kiro.dev/docs/cli/enterprise/billing/#tier-comparison)
+  * [I've subscribed a user twice. Will I be double-billed?](https://kiro.dev/docs/cli/enterprise/billing/#ive-subscribed-a-user-twice-will-i-be-double-billed)
+  * [Proration considerations](https://kiro.dev/docs/cli/enterprise/billing/#proration-considerations)
+  * [Viewing your bill](https://kiro.dev/docs/cli/enterprise/billing/#viewing-your-bill)