feat(kiro-cli): support global scope for commands and subagents#2102
Merged
Conversation
Kiro CLI reads user-wide prompts from ~/.kiro/prompts/ and agent configs from ~/.kiro/agents/ (local takes precedence), but the kiro-cli commands and subagents adapters ignored the --global flag entirely, so global dry-runs reported the features as unsupported. Flip supportsGlobal to true for kiro-cli in the commands and subagents processor metadata; the underlying KiroCommand/KiroSubagent getSettablePaths already resolve the same relative path for both scopes (the home-directory root is applied by the generate pipeline), matching the pattern already used for kiro-cli skills. The v3 Early Access surfaces (permissions.yaml, standalone hooks, Markdown agents) referenced in the original issue remain explicitly deferred per maintainer triage and are not touched here. The legacy frozen kiro alias is also untouched. Fixes part of #2034 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jul 1, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up for issue #2034. That issue's headline ask (Kiro CLI v3 Early Access support — permissions.yaml, standalone hooks, Markdown agents) remains explicitly DEFERRED per the maintainer's own triage comment ("Deferring until v3 stabilizes out of Early Access"). This PR implements only the separate, actionable v2 gap called out in a later maintainer comment: the current stable
kiro-clitarget is missing global scope for commands and subagents.Changes
Kiro CLI reads user-wide prompts (
~/.kiro/prompts/) and agent configs (~/.kiro/agents/) at the user level, but thekiro-clicommands/subagents adapters ignored--globalentirely (supportsGlobal: false). The underlying path-resolution logic inKiroCommand/KiroSubagentalready handled both scopes correctly (same relative path, home-dir root swap happens upstream in the generate pipeline) — the only gap was the processor gating flags.commands-processor.ts/subagents-processor.ts: flippedkiro-climetasupportsGlobaltotrue.kiro-clito the Tool × Feature global-mode happy-path matrices ine2e-commands.spec.ts/e2e-subagents.spec.ts.The legacy frozen
kiroalias is untouched (verified via diff).Verification
pnpm cicheckfully green: 301 test files, 6705 tests; sync-skill-docs, gitignore, supported-tools, cspell, secretlint all pass.References
Refs #2034 (v3 Early Access surface remains deferred/open)