fix(runner): preserve structured tool results in events - #117
Merged
Merged
Conversation
Carry typed tool result metadata through RunTaskObserver so downstream adapters can consume structured evidence without parsing text. Co-authored-by: Cursor <cursoragent@cursor.com>
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
divo12 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
codeant-ai
Bot
added
the
size:M
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
| tool=ev.name, | ||
| is_error=ev.is_error, | ||
| content=ev.content, | ||
| structured=dict(ev.structured) if ev.structured is not None else None, |
There was a problem hiding this comment.
Suggestion: The real Session translation constructs ToolUseResult without structured, and the engine's ToolExecutionCompleted event does not carry it, so this line receives None for production tool calls even when the underlying ToolResult contains structured data. Propagate the structured payload through the engine event and session translation layers before copying it here. [api mismatch]
Severity Level: Major ⚠️
- ❌ Structured payloads disappear from production role tool observers.
- ⚠️ Chorus adapters receive only textual tool-result content.
- ⚠️ Built-in structured tools lose machine-readable observer data.
Prompt for AI Agent 🤖
This is a comment left during a code review.
**Path:** src/dream/runner/role.py
**Line:** 249:249
**Comment:**
*Api Mismatch: The real `Session` translation constructs `ToolUseResult` without `structured`, and the engine's `ToolExecutionCompleted` event does not carry it, so this line receives `None` for production tool calls even when the underlying `ToolResult` contains structured data. Propagate the structured payload through the engine event and session translation layers before copying it here.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix
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.
User description
Summary
structured: Mapping[str, object] | NonetoRoleToolResultToolUseResult.structuredinto the observer eventThis closes the typed observer contract required by Chorus's merged Dream adapter.
Test plan
uv run pytest tests/test_runner/test_role_tool_structured.py -vMade with Cursor
CodeAnt-AI Description
Preserve structured tool results for downstream observers
What Changed
Impact
✅ Structured tool evidence available to downstream adapters✅ Reliable observer event data✅ Backward-compatible tool results without metadata💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.