rtk-ai/rtk

Feature Request: Add support for Kiro

Open

#1,970 opened on May 19, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Rust (2,914 forks)batch import
area:clienhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Summary

RTK currently supports a wide range of AI coding tools (Claude Code, Cursor, Gemini CLI, Codex, Windsurf, Cline, etc.), but Kiro is not yet supported.

Kiro (https://kiro.dev/) is an agentic AI-powered IDE and CLI introduced by AWS. It is gaining rapid traction in the developer community and is built on top of advanced foundation models (like Claude Sonnet and Opus) with a robust agentic architecture.

Why This Matters

  • Kiro features a powerful hook-based architecture (using smart hooks for event-driven automations), making RTK integration highly feasible
  • Kiro is seeing increasing adoption among developers globally
  • Users of Kiro would benefit greatly from RTK's token reduction capabilities (60–90% savings), especially when working within large codebases

Technical Details

Kiro uses project-level steering and hook files (typically stored in a .kiro directory, analogous to CLAUDE.md) for instructions and automated workflows. Its tool invocation lifecycle includes pre- and post-command hooks, which aligns closely with how RTK intercepts calls for Claude Code.

Based on the existing Claude Code integration:

rtk init -g   # generates ~/.claude/settings.json with PreToolUse hook

Contributor guide

Research direction
Examine how RTK integrates with Claude Code via hooks and replicate similar hook based integration for Kiro using .kiro directory structure.
Tech stack
rust
Domain
clideveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60