Repository navigation
Fix Agent Forge server after usage accounting (#62) - #70
Merged
Merged
Conversation
… execute options Exports emptyRunUsage() so hosts that synthesize an ExecutionResult do not hand-build the usage shape. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
After #62 the Agent Forge server no longer typechecked (
ExecutionResult.usageis aRunUsage;onLLMResponsegained a usage argument) and one server test asserted the old empty tool-execute options. ExportsemptyRunUsage()and updates the call sites.Verified: full local gate on main + this change, including Agent Forge typechecks (client and server), client suite and server suite (12/12 files).
The local merge gate now always runs the Agent Forge suites, not only for PRs that touch
apps/agent-forge.🤖 Generated with Claude Code