Michi
道 (michi) — "path" or "the way" in Japanese. A companion to Kiro (岐路, "crossroads").
Michi is an extension for Kiro, VS Code, and VSCodium that manages Kiro configuration files — steering, skills, hooks, and MCP settings — by linking them from designated config stores into your global and workspace .kiro/ directories.
Michi is a local-only tool. It helps a user define, maintain, and version-control their own steering files across their global config and their workspaces.
Features
- Config Store discovery — point Michi at folders with a
michi.yml manifest and browse available configs in the sidebar
- One-click activation — link steering files, skills, and hooks into
.kiro/ with hard links (files) or junctions (folders)
- MCP server management — activate/deactivate MCP server definitions that get merged into
mcp.json
- Scope toggle — switch between Global (
~/.kiro/) and Workspace (.kiro/) targets
- Active Configs view — see what is currently linked at a glance
- Conflict detection — refuses to overwrite existing configs not managed by Michi
- Built-in store — ships with a steering file that teaches Kiro about Michi itself
Getting Started
- Create a config store folder with a
michi.yml manifest (see below).
- Open the Michi sidebar and click the Add Config Store button in the header.
- Browse items and click to activate them.
Config Store Layout
my-config-store/
michi.yml
steering/
python.md
git.md
hooks/
lint-on-save.json
mcp/
aws-docs.yml
michi.yml
name: "My Configs"
description: "Personal Kiro configurations"
version: "1.0.0"
items:
- path: steering/python.md
description: "Python coding standards"
tags: [python, standards]
- path: hooks/lint-on-save.json
description: "Runs linter on file save"
tags: [lint]
Commands
| Command |
Description |
| Michi: Add Config Store |
Browse for a store folder to register |
| Michi: Remove Config Store |
Unregister a configured store |
| Michi: Activate Config |
Pick items to activate via quick-pick |
| Michi: Deactivate Config... |
Pick active items to deactivate |
| Michi: Refresh Stores |
Re-read all store manifests |
| Michi: Toggle Scope |
Switch between Global and Workspace scope |
State and Git
Michi tracks active links in .kiro/michi.json. This file is machine-specific. Michi automatically adds it to .kiro/.gitignore when created.
Linked config files (steering, skills, hooks) are regular files on disk. They can and should be committed to your workspace repository. Other collaborators who clone the repo get copies of those files even if they do not use Michi.
Team Usage
If multiple people on a team use Michi, each user registers the appropriate config store on their machine. The store is version-controlled separately (for example, a shared GitLab repo). Users pull the store to get updates. Hard-linked files in the workspace reflect store changes immediately.
Requirements
- Kiro, VS Code, or VSCodium
- Windows, macOS, or Linux
