Amazon Kiro: Waitlist-Only Agentic IDE - August 2025 Latest Status and Complete Usage Guide¶

⚠️ Important Notice as of August 2025

New Access: Waitlist registration required (restricted due to "unprecedented demand")
Pricing Plans: Initially announced pricing structure withdrawn, new plan announcement expected mid-August
Performance: Response delays reported, infrastructure enhancement in progress
Language Support: Currently English only, Japanese support timeline TBD

Key Points¶

Spec-Driven Development
Automatic generation from natural language specifications to technical design, data flow diagrams, and API design
Agent Hook Automation
Like experienced developers, automatically executes code quality checks, test updates, and document synchronization in the background
Prototype → Production
Seamless transition from "casual coding" to production-quality systems
Multi-Agent Collaboration
Integrated management combining Amazon AI and third-party AI agents for everything from code generation to documentation

📖 Overview¶

Announced by Amazon Web Services (AWS) on July 14, 2025, "Kiro" is a revolutionary Agentic IDE featuring Spec-Driven Development.

Current Status (August 2025): Due to "unprecedented demand," new users require waitlist registration, and existing users face daily usage limits. The initially announced pricing plans have been withdrawn, with new plan announcement scheduled for mid-August.

Kiro goes beyond traditional code completion to realize automation of the entire development process driven by specifications. It's gaining attention as a groundbreaking tool that supports everything from prototyping to production-quality systems through AI agents.

🚀 Kiro's Revolutionary Features¶

1. Spec-Driven Development¶

The biggest difference from conventional AI coding tools is the development process centered on specifications (Specs).

Why is it revolutionary?¶

Conventional AI tools: Prompt → Code generation (simple conversion)

Kiro: Prompt → Requirements analysis → Design documents → Implementation tasks → Code generation (automation of the entire development process)

This isn't just "advanced code generation" but a transformation of software engineering methodology itself.

Automatic Design from Natural Language¶

Input example: "Add product review system"

Kiro automatically generates:
✓ User stories
✓ Edge case analysis (using EARS notation)
✓ Acceptance criteria
✓ Data flow diagrams
✓ API design
✓ Database schema

Rigorous Specifications with EARS Notation¶

Utilizes EARS (Easy Approach to Requirements Syntax)
Automatic generation of technical specifications that eliminate ambiguity
Demonstrates power in refactoring and complex feature design

2. Agent Hooks¶

Automation system like having experienced developers constantly watching over

Decisive Difference from Conventional Tools¶

Conventional: Developer writes code → Manually create tests → Manually update documentation

Kiro: Developer writes code → Automatic test updates, document sync, quality checks

This automates important tasks often "postponed because they're tedious", preventing technical debt accumulation.

Automatic Quality Management¶

On file save: Automatic test file updates
On API changes: Automatic README and documentation sync
Before commit: Security scan and credential leak checks
On code modifications: Standards compliance checks and optimization suggestions

Event-Driven Background Processing¶

React component save
  ↓
Hook auto-execution
  ↓
Corresponding test file update
  ↓
Type definition check
  ↓
Documentation sync

3. Living Documentation¶

Fundamental Solution to Traditional Issues¶

Problem: Documentation-code divergence has been an eternal challenge in software development.

Kiro's Solution: - Bidirectional sync: Code changes ⇄ Specifications automatically sync - Always current: "Outdated documentation" problem structurally impossible - Design consistency: Original design philosophy preserved through implementation

4. Multi-Agent Collaboration¶

Integrated AI Agent Management¶

Amazon AI: Main development support agent
Third-party AI: Specialized agent integration
MCP (Model Context Protocol): External tool integration
Steering Rules: AI behavior control across the entire project

💼 Actual Development Flow¶

Prototype Stage¶

1. Describe functionality in natural language
   "Want to create a Todo app with user authentication"

2. Kiro automatically generates specifications
   - User stories
   - Technical requirements
   - Security considerations

3. Begin code generation
   - Simultaneous frontend and backend generation
   - Type definitions and API design

Production Transition¶

4. Quality enhancement process
   - Automatic testing via agent hooks
   - Security scanning
   - Performance optimization

5. Documentation preparation
   - Automatic API documentation generation
   - Operations manual creation
   - Deployment procedure updates

🔧 Technical Specifications & Supported Environments¶

Foundation Technology¶

Code OSS: Full VS Code settings and extension compatibility
Open VSX: Existing plugins usable as-is
Multi-language Support: English only (additional language support planned)

Integration Features¶

MCP Support: Standard protocol integration with specialized tools
Multimodal: Text, diagram, and file input support
Context Providers: File, URL, and document referencing

💰 Pricing Plans (August 2025 Latest Information)¶

Current Status (Preview Period)¶

Free Access: Free usage within "reasonable limits"
Waitlist: New users require waitlist registration
Usage Limits: Daily usage limits for existing users too
High Demand: Access restricted due to "unprecedented demand"

Future Pricing Structure (Under Consideration)¶

⚠️ Important: Initially announced pricing plans have been withdrawn.

Old Plans (Withdrawn): Free( $0/50 uses), Pro($ 19/1000 uses), Pro+($39/3000 uses)
New Plans: Announcement expected mid-August
Free Tier: Continued provision planned
Free Trial: 2-week free trial when paid plans announced

🤝 Kiro × Claude Code: The Ultimate Combination¶

Ideal Role Division¶

In actual development scenarios, combining Kiro's design capabilities with Claude Code's implementation power can achieve phenomenal development efficiency:

Phase	Kiro	Claude Code
Requirements Definition	◎ Detailed dialogue clarification	△ Weak with ambiguous requirements
Design	◎ High-quality document generation	○ Implementation policy decisions possible
Implementation	△ Slow speed	◎ Very fast
Development Environment	○ Basic functionality	◎ Rich features like MCP, hooks, custom commands

Practical Workflow¶

# 1. Create design documents with Kiro
# Use Spec mode for requirements definition, design, task decomposition

# 2. Pass design to Claude Code for implementation
claude Implement based on documents in .kiro/specs/feature-name. No operation verification needed. --dangerously-skip-permissions

Real Usage Example: Solar System Simulation Development¶

From developer real experience: 1. Kiro: Generated detailed requirements, design, and task documents 2. Claude Code: High-speed implementation based on generated documents 3. Result: Achieved high-quality development at high speed as expected

"Combining Kiro's requirements definition and design functions with Claude Code's implementation speed enables high-speed development based on detailed design documents that meet expectations" - Voice of developer who actually used both tools

🆚 Why is Kiro "Amazing"? Technical Breakthroughs¶

1. Paradigm Shift: From Code Generation to Development Process Management¶

While other AI tools compete on "better code completion," Kiro changed the competition field itself.

Conventional: Competition on "AI code writing speed/accuracy"
Kiro: Realizing "AI's ability to manage the entire development process"

Innovation in Design Specialization¶

Kiro's greatest strength is specializing as "AI that performs requirements definition and design":

Rigorous specification definition using EARS notation
Systematic 3-tier document structure:
requirements.md: User stories including acceptance criteria
design.md: Architecture and implementation policy
tasks.md: Specific execution procedures
Requirements clarification through dialogue

While AI tools have traditionally been "generating code somehow from vague instructions," Kiro realized "reliable implementation from clear design" - the royal road of software engineering.

2. Enterprise Ready: From Individual to Team Development¶

Individual developer focused: Cursor, Windsurf, GitHub Copilot
Team/enterprise focused: Kiro

Kiro is designed from the beginning with team development consistency and quality management in mind.

3. Structural Solution to Technical Debt¶

Agent hooks make the following structurally impossible: - Code without tests - APIs without documentation - Neglected security holes - Coding standard violations

4. Deep Integration with AWS Ecosystem¶

Being developed by Amazon, future native integration with AWS services is expected: - Automatic Lambda function deployment - Automatic DynamoDB schema management - CloudFormation template generation

🔍 Competitive Comparison: Kiro vs Existing AI Tools¶

Feature	Kiro	Cursor	Windsurf	GitHub Copilot
Approach	Spec-driven	Code completion focused	Agent-type	Inline completion
Pricing	TBD (August announcement)	$20	$15	$10
Access	Waitlist only	Immediate	Immediate	Immediate
Key Features	Automatic specification generation	Checkpoints	Unlimited free plan	VS Code integration
Automation Level	Entire process	Code change time	Agent execution	Completion & suggestions
Production Ready	★★★★★	★★★☆☆	★★★☆☆	★★☆☆☆

Kiro's Differentiation Points¶

Specifications First: Clarify design philosophy before code
Production Quality: Bridge from prototype to full system
Agent Integration: Collaborative work of multiple AI agents
AWS Ecosystem: Native integration with cloud services

📥 Installation Guide¶

System Requirements¶

OS: Windows 10+, macOS 10.15+, Linux (Ubuntu 20.04+ recommended)
Memory: 8GB+ recommended
Disk: 2GB+ free space
Internet: Required (AI processing runs in cloud)

Access Method (August 2025 Latest)¶

Current Status: Access Restricted¶

⚠️ Important Change: Kiro is implementing access restrictions due to "unprecedented demand."

Current Status:
✓ Existing users: Can continue with daily usage limits
✗ New users: Waitlist registration required

Waitlist registration procedure:
1. Access kiro.dev
2. Click "Join Waitlist" button
3. Account registration (GitHub, Google, AWS Builder ID, etc.)
4. Wait for signup code email notification

Access Start Timeline¶

From next week: Invitation starts for waitlist registrants
Sequential invitations: Signup codes sent by email in registration order
Infrastructure enhancement: System expansion in progress for demand response

2. Download¶

After waitlist approval, download the installer for your OS from kiro.dev:

Windows: KiroSetup-x.x.x.exe
macOS Intel: Kiro-x.x.x-mac-x64.dmg
macOS Apple Silicon: Kiro-x.x.x-mac-arm64.dmg
Linux: kiro-x.x.x-linux-x64.AppImage or .deb/.rpm

3. Installation¶

Windows:

1. Run downloaded .exe file
2. Follow installation wizard
3. Desktop shortcut created

macOS:

1. Double-click .dmg file
2. Drag Kiro icon to Applications folder
3. On first launch, "Cannot verify developer" may appear,
   Allow from System Preferences > Security & Privacy

Linux (AppImage):

chmod +x kiro-x.x.x-linux-x64.AppImage
./kiro-x.x.x-linux-x64.AppImage

Linux (deb/Ubuntu):

sudo dpkg -i kiro_x.x.x_amd64.deb

4. Initial Setup¶

Login:
Sign in with GitHub, Google, or email
AWS account not required
Import VS Code Settings (Optional):
```
File > Import VS Code Settings
```
Can import existing VS Code settings, extensions, key bindings
Tutorial:
Complete interactive tutorial shown on first launch (~10 minutes)
Learn basics of spec-driven development

5. Basic Usage¶

Starting New Project:

1. File > New Project
2. Specify project name and location
3. Select framework (React, Vue, Node.js, etc.)

Creating First Spec:

1. Open "Specs" panel in sidebar
2. Click "New Spec"
3. Describe functionality in natural language (e.g., "Create user authentication system")
4. Kiro automatically generates requirements definition and design documents

Setting Agent Hooks:

1. Settings > Agent Hooks
2. Select from presets or create custom hooks
3. For team sharing, commit .kiro/hooks.json to Git

Troubleshooting¶

If it won't start: - Check firewall/proxy settings - Update to latest version - Check log files (~/.kiro/logs/)

If performance is slow: - Check memory usage (minimum 8GB recommended) - Check for extension conflicts - Adjust in Settings > Performance

💡 Best Practices¶

Effective Usage Methods¶

Large-scale Refactoring: Demonstrates power in projects where upfront design is important
New Feature Development: End-to-end from specification to implementation
Team Development: Ensure design consistency through specification sharing
Technical Debt Resolution: Understanding existing system structure and improvement suggestions

Recommended Use Cases¶

Serious enterprise development projects
Multi-person team development
Systems with long-term operation premise
Development in AWS environment

⚠️ Cautions & Limitations¶

Current Limitations (August 2025)¶

Access Restrictions: New users need waitlist registration
Usage Limits: Even existing users have daily usage count restrictions
Performance Issues: Response delays reported
Language Support: English only (Japanese support TBD)
Pricing Structure: Existing plans withdrawn, new plans announced mid-August
Preview Stage: Possible feature/specification changes

Considerations (August 2025)¶

Access Availability: Waitlist length and waiting period
Performance: Currently reported delay issues
Pricing Unknown: New pricing structure details not announced
Migration cost from existing tools
Difficulty verifying team-wide adoption effects
AWS environment compatibility (future integration planned)

🎯 Real Usage Scenarios: Where Kiro Shows True Value¶

Scenario 1: MVP Development at Startup¶

Situation: 3-person team building EC site with payment functionality in 2 weeks

Without Kiro: - Specification misunderstandings cause rework - Additional week for test/documentation creation - Security holes discovered later

With Kiro: - Everyone develops referencing same specs - Tests/documentation auto-generated - Security checks auto-executed before commit - Result: Production-ready quality achieved in 2 weeks

Scenario 2: Legacy System Refactoring¶

Situation: Converting 5-year-maintained monolithic app to microservices

Kiro's Value: - Reverse-generate design documents from existing code - Visualize dependencies and create refactoring plan - Manage gradual migration with specs - Visualize progress across entire team

🔮 Future Prospects¶

Amazon's Strategy¶

Kiro aims not just to be a coding tool, but digital transformation of the entire software development process.

Design consistency assurance
Requirements conflict resolution
Technical debt elimination
Knowledge inheritance automation

Market Impact¶

While Cursor, Windsurf, and GitHub Copilot compete on "code generation," Kiro presented a new competitive axis of "entire development process optimization."

This change is expected to evolve the AI development tool market from "supplementary tools" to "development partners."

📊 Developer Evaluations¶

Positive Evaluations¶

"Combining Kiro's requirements definition and design functions with Claude Code's implementation speed enables high-speed development based on detailed design documents that meet expectations"
"Thanks to Kiro, I can clarify requirements when commanding AI, and thanks to Claude Code, high-speed development according to those requirements becomes possible"
"Using Kiro to organize documentation and having Claude Code write code" is an effective approach

Future Usage Policy¶

Many developers express that they will "continue development with the Kiro × Claude Code combination," and complementary usage leveraging both tools' strengths is recommended.