Skip to content

KAS 0.66.43 (kiro-cli 2.32.0) drops custom-agent prompts; no floor or notice #23561

Open

Description

@iamwhatever

On kiro-cli 2.32.0 (KAS engine 0.66.43), KAS registers a custom agent sent in _meta.kiro.customAgents and accepts session/set_mode, but the model does not get the agent's prompt. This was measured live in both JSON and markdown form. On kiro-cli 2.33.1 (KAS 0.66.58) the prompt is applied (test/fixtures/acp_frames/kas/markdown-agent-live.jsonl, worker-kit-live.jsonl, #23534).

Crew does not refuse or warn on 0.66.43:

  • The KAS floor is a help probe (kas_floor_wait.py), not a version number.
  • The backend card shows markdown_agents as available on KAS.
  • A crewmate worker (ACP_BACKENDS_MATE_WORKER_KIT) on 0.66.43 would run without its prompt addition. Its tool limits still apply, because they ride tools / excludedTools.
  • The opt-in bundle route pins KAS 0.66.33 (acp/kas_pin.py). Whether 0.66.33 applies the prompt is not measured.

An owner should decide whether to add a version floor or a notice for custom-agent prompts on KAS, and whether the bundle pin should move.

Activity

  1. added
    tier:T1Bug: behaviour does not match intent; fix keeps the design
    on Oct 23, 2026
  2. buluoray commented on Oct 24, 2026

    @buluoray
    Contributor

    🤖 Kiro Crew Auto-Pipeline [operator: buluoray#ce473fca]: This needs an owner decision, so no automated fix. Checked on main (5d7a22df70): the KAS floor is the help probe in src/kiro_crew/agent_sdk/kas_floor_wait.py, not a version check; markdown_agents on the backend card is gated only by ACP_BACKENDS_MARKDOWN_AGENT_SPECS (src/kiro_crew/agent_sdk/backend_cards.py:328); and the bundle pin is KAS_PIN_VERSION = "0.66.33" (src/kiro_crew/acp/kas_pin.py:41). The 0.66.58 captures from #23534 are the only measured "prompt applied" evidence.

    Decision: what Crew does when a KAS engine older than the first version known to apply custom-agent prompts runs a custom agent.

    1. Refuse: add a version floor for custom agents on KAS. Users on 0.66.43 get a clear "update kiro-cli" error instead of an agent that silently lacks its prompt. Plain sessions keep working.
    2. Warn: run the agent, but show a notice on the backend card and at session start that the prompt may be ignored on this engine. Nothing stops working; the user can see why the agent behaves generically.
    3. Leave it: document the minimum version only.

    Recommended: 2 now (makes the silent failure visible, removes nothing), with 1 for the crewmate worker kit only once the floor version is measured. Separately, the bundle pin (0.66.33) should be measured with the same capture before deciding whether to move it to 0.66.58.

  3. added
    needs-humanPR flagged for human review by drive-to-green pipeline
    and removed
    needs-triageAwaiting automated triage
    on Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

needs-humanPR flagged for human review by drive-to-green pipelinetier:T1Bug: behaviour does not match intent; fix keeps the design

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions