Repository navigation
Tell which agent turn asked for a decision in cloudfall why - #78
Merged
Merged
Conversation
An investigation step now keeps the turn that made its call, and why reads the investigation records beside the decisions: a decision an agent asked for is told with the model, the endpoint, the alert, the turn, and that turn's reasoning with the endpoint's response and request ids. The record could already say what the model thought, but only by reading two files by hand. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01APTdZZw8Jw9PQF4TD55wMv
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
romamo
added a commit
that referenced
this pull request
Oct 12, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01APTdZZw8Jw9PQF4TD55wMv
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
1 participant
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.
cloudfall whyanswered what happened to a decision, but not what the agent was thinking when it asked for it. That lived in the investigation record, and the two were joined only by reading both by hand.turnthat made its call (optional inagent-investigation.schema.json; older records have none)why --investigations DIR(defaultinvestigations, bound for MCP clients the same way asdecisions) adds to the story the model, the endpoint, the alert, the turn, and that turn's reasoning with the response and request ids. The answer carries them asagentwhywithRECORD_INVALID(why_investigation_invalid)Checked on a live Nemotron 3 Super replay run. The
shop-logrotatestory now reads "The agent nvidia/nemotron-3-super-120b-a12b at https://api.tokenfactory.nebius.com/v1/ asked for it in turn 2 of investigation …", then its reasoning, quoted with the Token Factory ids.Full suite: 520 passed. ruff check and mypy are clean.
Next: the hosted demo shows this after a run (a separate PR once this is on main, since the demo pins Cloudfall by git rev).
🤖 Generated with Claude Code
https://claude.ai/code/session_01APTdZZw8Jw9PQF4TD55wMv