fix(kiro): attribute sessions by agent id#1505
Merged
Haz3-jolt merged 1 commit intoJun 23, 2026
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Co-authored-by: Hemalatha Madeswaran <HemalathaMadeswaran18@users.noreply.github.com>
9c9add1 to
1bffb2a
Compare
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.
Purpose / Description
Fix Kiro session attribution so each pulled agent carries its Observal UUID in its own hook command. This avoids cwd-based guessing and prevents sessions from being assigned to the wrong agent when multiple agents exist.
Fixes
No issue linked.
Approach
Kiro hooks now use
OBSERVAL_AGENT_ID=<uuid>instead of agent name. Session push resolves that UUID through~/.observal/lockfile.jsonand sends the lockfile id/version. If the UUID is missing or not found, Kiro sessions stay unattributed instead of falling back to cwd.doctor patchno longer rewrites Kiro agent files with generic hooks because Kiro attribution must be installed per pulled agent.How Has This Been Tested?
Ran:
Manual smoke:
Result:
Learning (optional, can help others)
Kiro JSONL files do not include a reliable top-level active agent identity. The reliable source is the per-agent Kiro hook configuration, so the hook must carry the Observal agent UUID.
Checklist
No UI changes.
AI Assistance
Was generative AI tooling used to co-author this PR?