Skip to content

fix(cli): clarify Explore execution limits - #13759

Merged
marius-kilocode merged 1 commit into
mainfrom
fix-explore-execution-limits
Sep 3, 2026
Merged

marius-kilocode merged 1 commit into
mainfrom
fix-explore-execution-limits

Conversation

@marius-kilocode

Copy link
Copy Markdown
Collaborator

What Problem This Solves

Task lists agent names and descriptions, but Explore did not advertise its restrictive Bash allowlist. Read-only investigation can still require scripts, tests, or binary-analysis commands that Explore cannot execute.

Why This Change Was Made

Append a short capability clarification to the built-in Explore description. Direct execution-dependent work outside the allowlist to an available agent whose permissions allow it, while retaining the requested no-change scope. Keep the existing search guidance and explicit custom description overrides.

User Impact

Parents receive accurate capability guidance when selecting Explore. This is a description-only fix: permissions, models, worker prompts, routing, and Swarm behavior are unchanged. No benchmark or cost improvement is claimed.

Evidence

  • 87 focused tests pass across the Kilo metadata, Task catalog, agent configuration, and plan/subagent permission suites.
  • CLI typecheck, changed-file oxlint, annotation guard, and diff whitespace checks pass.
  • Live self-test with two isolated worktree-source backends: /agent and /experimental/tool expose the new default guidance and preserve an explicit custom Explore description exactly. No LLM requests or real credentials were used; both backends were stopped.
  • Includes a patch changeset for @kilocode/cli.

@kilo-code-bot

This comment has been minimized.

@marius-kilocode
marius-kilocode merged commit 5d4c699 into main Sep 3, 2026
32 checks passed
@marius-kilocode
marius-kilocode deleted the fix-explore-execution-limits branch September 3, 2026 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants