Kiro (kiro)

• Rules: steering files must start with their YAML frontmatter. Rules without globs use inclusion: always. Rules with globs use fileMatch with fileMatchPattern, a string for one pattern and a list for several. Rules with globs need the Kiro IDE or Kiro CLI V3. CLI V1 and V2 load only always files. Sync never writes Kiro's auto and manual modes.
• AGENTS.md: Kiro includes it in default resources. When Codex or another tool that copies rules into AGENTS.md adds the ## Rules block, always-on rules normally get no steering file. fileMatch rules keep theirs. Custom agents inherit default resources alongside their own list unless chat.disableInheritingDefaultResources is on. Setting x-kiro.resources on an agent does not change this. If you turn that setting on, add file://AGENTS.md to each agent's x-kiro.resources. agnostic-ai lint warns (LINT029) when an agent with resources leaves it out. See target behavior.
• Memory: with builtins: [memory], .kiro/steering/kiro-memory-index.md includes .agnostic-ai/memory/MEMORY.md and .agnostic-ai/local/memory/MEMORY.md with #[[file:...]], so Kiro loads both shared memory lists every session. No other tool gets the file, and sync --global leaves it out. Kiro resolves each path from the workspace root and shows a marker for a list that does not exist yet. It applies its file read permissions and ignore rules to a reference, so a list they block does not load. With memory.personal: repo, the file includes only the project list. The shared policy tells Kiro to find personal memory with agnostic-ai memory path.
• Skills: native at .kiro/skills/<name>/SKILL.md, read by the skill picker. The file (name and description frontmatter) is identical to the shared .agents/skills/ one. Bundled scripts/, references/, and assets/ are copied with it.
• Agents: native custom agents in YAML-frontmatter Markdown, read by the agent picker. description (default: the agent name) and model are copied as written. The spec name stays the file name. x-kiro.name sets Kiro's optional display name and survives import.
• Settings: the settings model goes to chat.defaultModel in .kiro/settings/cli.json, as written, and every other key in the file stays. Kiro CLI uses a workspace value over the global one in ~/.kiro/settings/cli.json in its terminal UI sessions. Kiro ids use dots (claude-sonnet-4.6), so set model: {default: ..., kiro: claude-sonnet-4.6} when the shared value is a Claude Code id. A Claude alias such as sonnet raises a note and writes nothing. permissions raise a note, because the file has no allow, deny, or ask list. Sync replaces a chat.defaultModel you set by hand while a settings spec sets model, and removing the model later deletes the key without restoring your earlier value; set model: {claude: ...} to keep Kiro out. x-kiro in a settings spec raises a note and is not written, because cli.json takes flat dotted keys. Sync rewrites the file in its own two-space format, and comments in it are not kept.
• Agent MCP servers: each server an agent names in mcpServers is written in full under the agent's mcpServers, the only form Kiro takes. An agent-only server stays out of .kiro/settings/mcp.json. x-kiro.mcpServers replaces the list.

Commands

Kiro CLI 2.27.0 and newer shows workspace prompts as /name commands in V3. Sync writes the command body to .kiro/prompts/<name>.md, with a generated-file header and no frontmatter.

Kiro expands $ARGUMENTS, ${1} through ${10}, and ${@}. Sync keeps these tokens as they are. Use a ::target kiro fence for Kiro-specific templates. Bare $1 and $ARGUMENTS[0] still get the unsupported-syntax checks.

outputs.kiro.commands-dir changes the prompt folder. Otherwise, outputs.kiro.dir puts prompts under <dir>/prompts. Import reads the same folder into sources.commands.

Kiro also has a global prompt folder. sync --global does not write commands.

Kiro's agent schema also carries tools, mcpServers, permissions, hooks, keyboardShortcut (CLI 2.x only), welcomeMessage, excludedTools, includeMcpJson, and includePowers. tools is translated from the portable can or tools field. Kiro's mcpServers holds inline definitions, not names, so set x-kiro.mcpServers. Set the rest, and any other key, under x-kiro.

Kiro groups agent tools into read, write, shell, web, and subagent. The configuration reference and tools page list the same categories. It also accepts @server_name, @server_name/tool_name, @mcp, @builtin, and *.

Built-in tools such as knowledge use their exact tool IDs. Sync translates four of the categories, plus named MCP servers and tools:

Duplicates are merged. A Kiro category covers more than one tool, so access widens: write also covers delete_file, and web covers fetch and search. Sync prints a note naming the extra access, such as kiro: .agnostic-ai/agents/writer.md: edit becomes Kiro's write category, which also allows delete_file. on-unsupported: error fails when access widens, including for a Claude Code alias such as Edit. Scoped values, such as shell(git diff *) and read(src/**), are dropped with a sync note. The rest are still written. x-kiro.tools takes Kiro's own names and always wins.

Hooks are native: one JSON file per spec, {"version": "v1", "hooks": [{name, trigger, matcher, action, timeout, enabled, description}]}.

• Portable on: before-tool maps to PreToolUse, with anchored lists of documented built-in IDs for shell, read, web, and edit, and @<server>/* for mcp:<server>. Built-in kinds exclude MCP tools and need an updated mapping for new IDs. The tool wildcard keeps server names such as mcp distinct from source selectors. Other portable events and decision: stdout have no Kiro mapping. See portable hooks.
• event becomes trigger, as written. validate flags AgentSpawn and agentSpawn, Kiro V3's compatibility aliases, and suggests SessionStart.
• Each command (string or list) becomes an action: {"type": "command", "command": ...} entry in the same file. The name gets a -2, -3, ... suffix to stay unique.
• disabled: true writes "enabled": false. description is written to the file as documentation only.
• timeout: 0 disables the timeout; omitting it keeps Kiro's 60-second default.
• x-kiro keys are copied to each entry. That is the only way to set confirm (ask before a Stop command hook runs, with question, options of id/label/run, and optional confirmCommand).
• x-kiro.action takes {type: agent, prompt: ...} or {type: command, command: ...}. A valid one needs no portable command and replaces the whole list with one action. An invalid one fails sync.
• .agnostic-ai/scripts/<name> references are copied to .kiro/scripts/<name>, outside .kiro/hooks/ where Kiro reads hook files, and the command is rewritten. See shared hook scripts.
• agnostic-ai hook run runs a UserPromptSubmit or Stop hook, or a tool hook with --payload, on an assumed sh -c, before a session does.

Use your home hook specs in every workspace with Kiro CLI V3:

agnostic-ai sync --global --only kiro --dry-run
agnostic-ai sync --global --only kiro
agnostic-ai sync --global --only kiro --check

Sync writes ~/.kiro/hooks/<name>.json and copies shared scripts to ~/.kiro/scripts/. Set KIRO_HOME to a valid absolute profile directory to change where agnostic-ai writes these folders and Kiro's other global files. Like Kiro CLI, sync uses ~/.kiro when the value is relative, a filesystem root, your home directory, or one of its ancestors. Global hooks and workspace hooks both run.

Sync removes only recorded files after their specs are removed. A conflicting or edited file stops sync.

agnostic-ai import --global kiro imports hook files that one spec can reproduce at the same filename. Files with mixed triggers, names that differ from their filename, or other content the spec cannot preserve are skipped with a warning. Existing specs stay. After importing, run the sync and check commands above.

MCP servers go to .kiro/settings/mcp.json under mcpServers, Kiro's workspace-level config. Local servers have command plus optional args and env. Remote ones have url plus optional headers and env. Kiro expands a ${NAME} reference only after you approve the variable under Mcp Approved Env Vars in its settings. See environment references. disabled is copied as written (default false). Kiro also accepts autoApprove (tools approved without prompting, "*" for all) and disabledTools (tools hidden from the agent). A remote server can add oauth ({clientId, clientSecret, redirectUri, clientMetadataUrl, oauthScopes}) and a top-level oauthScopes fallback; oauth.oauthScopes wins. An empty oauthScopes: [] is written as is, which is Kiro's documented fix for scope errors. Kiro's oauth differs from Claude Code's, so each tool maps only its own sub-keys. See disabled support by target.

Ignore specs are joined into the project .kiroignore in gitignore syntax (Kiro ignore); override with outputs.kiro.ignore-file. The IDE honors the file only when it is listed in kiroAgent.agentIgnoreFiles (Kiro suggests [".gitignore", ".kiroignore"]). CLI V3 honors workspace .kiroignore, ~/.kiro/settings/kiroignore, and Git's global ignore file (core.excludesfile, only in Git repositories). Matching files are blocked from direct reads and hidden from content and filename search.