Loading image...Kiro
  • CLI
  • Enterprise
  • Pricing
DOWNLOADS
Loading image...Kiro
  1. Docs
  2. CLI
  3. Custom Agents
  4. Creating

Creating custom agents

On this page
  • Quick start
  • Agent configuration file
  • Configuration options
  • Basic information
  • Tool management
  • Context configuration
  • Using your custom agent
  • Best practices
  • Next steps

Loading image...Kiro
Product
  • About Kiro
  • CLI
  • Pricing
  • Downloads
For
  • Enterprise
  • Startups
Resources
  • Documentation
  • Blog
  • Changelog
  • FAQs
  • Report a bug
  • Suggest an idea
  • Billing support
Social
Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences

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

Create a new custom agent using the interactive command:

bash
kiro-cli --agent create my-agent

This will guide you through the setup process and create a configuration file at ~/.kiro/agents/my-agent.json.

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": { "allowed": ["readFile", "writeFile", "executeBash"], "autoApprove": ["readFile"] }, "context": { "files": ["README.md", "package.json"], "systemPrompt": "You are a helpful coding assistant." } }

Configuration options

Basic information

  • name: Unique identifier for your agent
  • description: Brief explanation of the agent's purpose

Tool management

  • tools.allowed: Array of tool names the agent can access
  • tools.autoApprove: Tools that don't require user confirmation
  • tools.denied: Explicitly blocked tools (optional)

Context configuration

  • context.files: Files to automatically load into context
  • context.systemPrompt: Custom instructions for the agent
  • context.environment: Environment variables to include

Using your custom agent

Start a chat session with your custom agent:

bash
kiro-cli --agent my-agent

Best practices

  1. Start restrictive: Begin with minimal tool access and expand as needed
  2. Name clearly: Use descriptive names that indicate the agent's purpose
  3. Document usage: Add clear descriptions to help team members understand the agent
  4. Version control: Store agent configurations in your project repository
  5. Test thoroughly: Verify tool permissions work as expected before sharing

Next steps

  • Explore Agent Configuration options in detail
Page updated: November 16, 2025
Custom agents
Configuration reference