feat(python): expose escalation mode to Python - #3
Merged
Conversation
escalation(judge_target, efficient_target, capable_target, *, prompt, confirmations, recent_turn_window, window_message_chars, max_output_tokens): each efficient answer is judged and a confirmed streak of escalate verdicts latches the session to the capable target. Sessions ride request metadata (session-id header); a latched session serves capable directly without further judge calls. Version 0.2.0+gumloop.0.2.0. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: rbehal <rahulbehal01@hotmail.com> Co-authored-by: Cursor <cursoragent@cursor.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.
What
Binds
LlmClassifierConfig::Escalationto Python aslibsy.escalation(judge_target, efficient_target, capable_target, *, prompt, confirmations, recent_turn_window, window_message_chars, max_output_tokens), with type stubs and binding tests. Bumps the dist to0.2.0+gumloop.0.2.0(wheels for this version are already in the Artifact Registry).Why
The backend's Chew mid-run step layer (escalation variant) runs libsy's escalation algorithm per agent step: each efficient answer is judged, and a confirmed streak of escalate verdicts latches the run's session onto the capable tier. The capability existed in the Rust core but had no Python door.
Notes
session-idheader); a latched session serves the capable target directly with no further judge calls — covered intests/test_libsy_escalation.py(streak below confirmations, latch, session isolation, judge fail-open, validation).custom_classifierbinding; no changes to existing bindings.gumloop-mainthat was force-reset; thegumloop-v0.2.0+gumloop.0.2.0tag was removed and should be re-pushed on the merge commit.Made with Cursor