Release Notes: v0.12.0¶

Release Date: 2026-03-08

Highlights¶

This release improves the developer experience for Kiro CLI deployments with post-generation install instructions and prevents a common misconfiguration that caused duplicate directory nesting.

Post-generation install instructions — After running assistantkit generate, the CLI now prints platform-specific commands to install agents to Kiro CLI (~/.kiro/) or Claude Code (.claude/)
Output path validation — Rejects deployment output paths ending in agents/, steering/, etc. with an actionable error message

Added¶

Post-Generation Install Instructions¶

After generating plugins, the CLI now prints install commands:

Generated targets:
  - local-kiro: plugins/kiro

To install:

  Kiro CLI:
    cp plugins/kiro/agents/*.json ~/.kiro/agents/
    cp plugins/kiro/steering/*.md ~/.kiro/steering/

  Tip: Set output to ~/.kiro or .claude in your deployment file to install directly.

If you configure "output": "~/.kiro" in your deployment, it shows:

  Kiro CLI: ✓ Already installed to ~/.kiro

Improved Help Text¶

The generate --help now documents deployment output path requirements:

Deployment output paths:
  The output path in your deployment target should be the plugin ROOT directory.
  The generator creates subdirectories (agents/, steering/, etc.) automatically.

  For distribution:  "output": "plugins/kiro"    -> plugins/kiro/agents/*.json
  For local install: "output": "~/.kiro"         -> ~/.kiro/agents/*.json

  Do NOT include subdirectories in output paths (e.g., "plugins/kiro/agents").

Fixed¶

Output Path Validation¶

Previously, specifying "output": "plugins/kiro/agents" in a deployment file would create duplicate nesting:

plugins/kiro/agents/agents/coordinator.json   # Wrong!

Now, the generator rejects paths ending in generated subdirectory names (agents, steering, skills, commands) with a clear error:

output path "plugins/kiro/agents" should be the plugin root directory,
not a subdirectory (use "plugins/kiro" instead)

Documentation¶

Kiro CLI Deployment Guide¶

Significantly expanded documentation at docs/deployments/kiro-cli.md:

New Installation section with two approaches:
Option A: Generate then copy (for distribution)
Option B: Direct install via "output": "~/.kiro" (for personal use)
Project vs User-Level Agents comparison table explaining why Kiro requires user-level installation while Claude Code supports project-level agents
Steering files workaround for project-level context in Kiro CLI

Platform Comparison¶

Aspect	Claude Code	Kiro CLI
Project agents	`.claude/agents/*.md` ✅	Not supported ❌
User agents	`~/.claude/agents/*.md`	`~/.kiro/agents/*.json`
Project context	`CLAUDE.md`	`.kiro/steering/*.md`
Auto-discovery	Yes (scans project)	No (user dir only)
Namespacing	Directory-based	Prefix-based

Tests¶

Added TestGeneratePlatformPlugin_RejectsSubdirectoryPaths covering validation of output paths

Installation¶

go get github.com/plexusone/assistantkit@v0.12.0

CLI Installation¶

go install github.com/plexusone/assistantkit/cmd/assistantkit@v0.12.0