Kiro honors model config but doesn't advertise it via GetConfigSpec

[illegalcall]

Context (shared across all harnesses)

AO stores a per-role model in agentConfig.model (backend/internal/domain/agentconfig.go:27), resolved and forwarded to every adapter as cfg.Config.Model. Adapters that honor the model are also expected to advertise it via GetConfigSpec — Claude does (claudecode/claudecode.go:104-106, exposing model + permission mode) and Codex's fix (#2869) added the same.

This issue tracks Kiro for completeness of the harness-model-config audit (sibling issues: #2883–#2901).

Situation — Kiro honors the model but does NOT advertise it

Good news first: Kiro already forwards the configured model. setKiroAgentDefaults writes model into Kiro's agent-config file when agentConfig.Model is non-blank (backend/internal/adapters/agent/kiro/hooks.go:268-272), and this is covered by tests (kiro/kiro_test.go:520 TestGetAgentHooksWritesConfiguredModel, plus a project-model preservation assertion at :167-208). So Kiro is not affected by the launch bug the sibling issues describe.

The gap: Kiro has no GetConfigSpec override (it inherits the empty agentbase.Base.GetConfigSpec, agentbase/agentbase.go:20-21). So while Kiro consumes agentConfig.model, it never declares that it supports the model field — inconsistent with Claude and Codex, and it means the field isn't discoverable/validated through the config-spec surface for Kiro.

Expected

Kiro should advertise the model config field it already honors, matching the Claude/Codex contract.

Suggested fix (small)

• Override GetConfigSpec in the Kiro adapter to report a model field (ports.ConfigFieldString), mirroring claudecode/claudecode.go:104-106 and codex/codex.go.
• Add/extend a GetConfigSpec test asserting the model field is reported (see the codex/claude spec tests for the pattern).

Notes

Low priority / consistency polish — Kiro's runtime behavior is already correct; this only aligns its declared config spec with the other model-aware adapters.

References

• Sibling audit issues: Cursor ignores role-specific model config on launch #2883–Agy (Antigravity): verify model-override support and honor role-specific model config #2901 · Original context: Codex ignores role-specific model config on launch #2769 · Reference pattern: fix: pass Codex model config to launch commands #2869
• Relevant files: backend/internal/adapters/agent/kiro/kiro.go, backend/internal/adapters/agent/kiro/hooks.go:268-272

[somewherelostt]

Thanks for contributing to Agent Orchestrator.

This issue is being picked up by the current external contributor on-call pair:

• @illegalcall
• @Pulkit7070

If someone is already working on this, please continue as usual.
The on-call pair is added for visibility, tracking, and support, not to take over the work.
If you need help with review, direction, reproduction, or next steps, please tag @illegalcall and @Pulkit7070 here.

For faster context or live questions, you can also join the AO Discord.

Join the session here:
https://discord.gg/H6ZDcUXmq

Come by if you want to see what is being built, ask questions, or just hang around with the community.