kiro-buddy

Never lose your Kiro context again.

kiro-buddy is a CLI + MCP tool that manages persistent feature contexts across Kiro sessions. When your context window fills up and you start a new session, kiro-buddy reloads everything so you can pick up right where you left off.

The Problem

Kiro's context window has limits. When it fills up, you lose all the context about what you were building — requirements, decisions, progress, what's done, what's next. Starting a new session means re-explaining everything from scratch.

How It Works

Each feature you're working on gets a dedicated folder with structured markdown files:

~/.kiro-buddy/features/user-auth/
├── requirements.md   # what you're building
├── progress.md       # what's done, what's left
├── notes.md          # decisions, gotchas, freeform notes
├── sessions.md       # timestamped session history
├── dependencies.md   # blocked-by / blocks
├── steering.md       # auto-generated context for Kiro
└── snapshots/        # progress checkpoints

When you start a new Kiro session, kiro-buddy detects your active feature (via git branch or explicit selection) and feeds the context back to Kiro automatically.

Installation

npm install -g kiro-buddy --registry https://registry.npmjs.org

Quick Start

# Create a new feature
kiro-buddy new "user-auth" --desc "Add login and signup endpoints"

# Check current status
kiro-buddy status

# Switch between features
kiro-buddy switch "user-auth"

# Log progress during a session
kiro-buddy log "Added JWT validation middleware"

# Save a snapshot at a milestone
kiro-buddy snapshot "login endpoint working"

# End a session with a summary
kiro-buddy end "Added login endpoint, JWT validation pending"

Commands

| Command | Description | |---|---| | kiro-buddy new <name> | Create a new feature with scaffolded context files | | kiro-buddy list | List all features (active one marked with ▶) | | kiro-buddy switch <name> | Switch active feature | | kiro-buddy status | Show active feature's steering context and progress | | kiro-buddy log <entry> | Add a timestamped entry to session history | | kiro-buddy snapshot <label> | Save a checkpoint of current progress | | kiro-buddy end <summary> | End session, log summary, update steering file | | kiro-buddy template <type> | Show a prompt template (api-endpoint, bug-fix, refactor) |

MCP Integration

kiro-buddy also runs as an MCP server, so Kiro can call it directly as a tool. Add this to your Kiro MCP config:

{
  "mcpServers": {
    "kiro-buddy": {
      "command": "kiro-buddy",
      "args": ["mcp"]
    }
  }
}

This lets Kiro automatically log progress, update files, and end sessions without you running CLI commands manually.

Auto-Detection

kiro-buddy tries to detect your active feature automatically:

1. Git branch — if you're on feat/user-auth or feature/user-auth, it maps to the user-auth feature
2. Local marker — falls back to a .kiro-buddy-active file in your working directory

Prompt Templates

Kickstart common feature types with structured prompts:

kiro-buddy template api-endpoint   # API endpoint scaffold
kiro-buddy template bug-fix        # Bug investigation template
kiro-buddy template refactor       # Refactor planning template

License

MIT