Repository navigation
chore(fork): bring the 2.1.1-fork.1 commits onto main - #2
Merged
Merged
Conversation
Some clients rewrite the assistant tool turn before answering it. Hermes Agent, for example, splits one `tool_call` batch call into one call per entry and gives the extra calls ids of its own. The results then answer every call the plugin announced, plus ids it never issued, and the resume failed with 400 "partial tool result resume". The client replays the same history on every retry, so the conversation could never continue. When the results cover every announced call of the parked run for the same credential and only add unknown ids, abort the parked run and fall back to a new agent built from the transcript, the same path that results with only unknown ids already take. Missing, duplicate, mixed and wrong-credential results still return 400 and keep the parked run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub no longer offers macos-14 runners. Fork-only commit; not part of the upstream PR. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
auth-cursor 2.1.1 + rewritten tool turn fix (UNICKCHENG#3)
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.
What was broken
The deployed
auth-cursor-v2.1.1-fork.1release was tagged on two commits that never landed onmain:2076671 fix(auth-cursor): rebuild the run when a client rewrites the tool turn(the Hermes fix, upstream fix(auth-cursor): rebuild the run when a client rewrites the tool turn UNICKCHENG/cliproxyapi-plugins#3)a2bdb49 ci(fork): skip the darwin/arm64 release buildA release from
mainwould drop the tool-turn fix. Releasing #1 frommainalso failed on the darwin/arm64 runner (The configuration 'macos-14-arm64-us-default' is not supported), and that run published nothing.What changed
This merges the
auth-cursor-v2.1.1-fork.1tag intomain. It merged with no conflicts.mainthen has the deployed code plus #1 (nousageon replies), and can be taggedauth-cursor-v2.1.1-fork.2.Testing
go vet ./...,gofmt -l .(clean),go test ./...pass on the merged tree. The tool-turn tests from2076671and the no-usagecheck from #1 both run.Not covered
The deployed check happens after release: CLIProxyAPI on
2.1.1-fork.2, with a Hermes tool loop through LiteLLM.🤖 Generated with Claude Code