Skip to content

feat(user-agent): Attribute the Kiro IDE agent - #10584

Open
seshubaws wants to merge 1 commit into
aws:v2from
seshubaws:feature/kiro-ide-user-agent
Open

feat(user-agent): Attribute the Kiro IDE agent#10584
seshubaws wants to merge 1 commit into
aws:v2from
seshubaws:feature/kiro-ide-user-agent

Conversation

@seshubaws

@seshubaws seshubaws commented Aug 19, 2026

Copy link
Copy Markdown

The Kiro IDE and Kiro CLI are separate products with separate app bundles. Only the CLI exports KIRO_SESSION_ID, so commands driven by the IDE's agent were reported as ordinary human-run commands and its traffic was unattributed.

Add AGENTIC_CALLER_KIRO_IDE (AX), keyed on KIRO_AGENT. The variable is scoped to agent activity rather than to the editor being open, following CURSOR_AGENT and ANTIGRAVITY_AGENT.

Something like TERM_PROGRAM=kiro was rejected since the IDE's integrated terminal is also human-driven, so it would attribute a person's typing as agentic and make the metric non-comparable with the other AGENTIC_CALLER_* rows. Kiro service must export KIRO_AGENT for this to report, matching how Cursor behaves today. Setting this up for when it does.

Also expose is_agentic_caller() so callers that adapt behavior for agents (for example, suppressing interactive prompts) use the same signals the User-Agent already reports instead of reimplementing the table.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The Kiro IDE and Kiro CLI are separate products with separate app
bundles. Only the CLI exports KIRO_SESSION_ID, so commands driven by the
IDE's agent were reported as ordinary human-run commands and its traffic
was unattributed.

Add AGENTIC_CALLER_KIRO_IDE (AX), keyed on KIRO_AGENT. The variable is
scoped to agent activity rather than to the editor being open, following
CURSOR_AGENT and ANTIGRAVITY_AGENT. An editor-presence signal such as
TERM_PROGRAM=kiro was rejected: the IDE's integrated terminal is also
human-driven, so it would attribute a person's typing as agentic and make
the metric non-comparable with the other AGENTIC_CALLER_* rows. Kiro must
export KIRO_AGENT for this to report, matching how Cursor behaves today.

Also expose is_agentic_caller() so callers that adapt behavior for agents
(for example, suppressing interactive prompts) use the same signals the
User-Agent already reports instead of reimplementing the table.
@seshubaws
seshubaws requested a review from a team as a code owner August 19, 2026 02:56
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.

1 participant