+ iHjl7Rt^RIHt^RIt^RIt^RIHtHtHtH t ^t ^dt Rt ^t ^tRtR t]!0R!m4tRRltRR ltR R ltR R ltRRltRRR^RRRRR] R] R]/RRlltRRltRRltRRltR#)"ub Send-path image eviction policy shared by both stateless outbound passes. Two passes retire old tool-result images from the per-request copy of the conversation: ``agent.context_compressor.evict_stale_outbound_tool_images`` on the OpenAI-shaped list and ``agent.anthropic_message_convert._evict_old_screenshots`` on the Anthropic wire list. Both run from scratch on a fresh clone every request, so they must agree on one policy or the second pass re-evicts on a different frontier than the first (#113517). This module is stdlib-only so the wire converter, a leaf, can import it without dragging in the compaction stack. Why the trigger is a provider limit, not a keep-newest count: retiring an image edits a message the provider has already cached, and Anthropic matches its prompt cache on an exact byte prefix. A keep-newest-N window retires one more message on every new image, so every turn is a full-prefix miss. Holding images until the request would cross a real API limit and then retiring a batch costs one slower turn per batch and nothing below the limit. 20 is the documented threshold at which Anthropic applies a stricter per-image dimension cap (2000 px) to EVERY image in the request, counting images nested in tool_result content. Crossing it costs nothing by itself: it only matters when some image actually exceeds 2000 px on a side. Hermes already shrinks its own tool images far below that before they enter history (``vision_analyze`` and browser screenshots embed at 1568 px, ``computer_use`` at 1456 px by default), so the 21st screenshot of a run trips no provider constraint and a batch retire there buys a full prefix rewrite for nothing — and, on the preserved-thinking models, invalidates every later thinking block. Anthropic's own computer-use guidance now says to keep screenshots at or under 2000 px and NOT to prune them client-side for exactly that reason. So the block ceiling is CONDITIONAL on the request's actual dimensions: the strict 20 applies only when some image exceeds ``MANY_IMAGE_DIMENSION_LIMIT``, when the stricter per-side cap is live and the retire genuinely protects the request; otherwise the ceiling is the hard count ``OUTBOUND_IMAGE_HARD_LIMIT``. The hard ceilings above 20 are real but distant (100 images per request on 200K-context models, 600 otherwise) and the 32 MB request-size limit usually binds first, which the byte budget guards with headroom for text. Classification reads image HEADERS only — never a full decode of every base64 payload per request — and treats unreadable or unknown dimensions as unsafe, so a payload this module cannot measure keeps today's strict trigger. ) annotationsN)AnyIterableOptionalSequencei6nic V^8dQhRRRR/#)rawbytesreturnzOptional[tuple[int, int]])formats"@/home/ubuntu/.hermes/hermes-agent/agent/image_eviction_policy.py __annotate__r?sU/HcVPR4'dG\V4^8d7\P!RVR,4wr\ V4\ V43#VPR4'EdV\V4^8EdE^pV^ ,\V48Ed+W,^8wd V^, pK0W^,,V^,r4V^8Xd#V\V48dW,V^,r4K)VR9dKyV^8XgV^,\V48dR#\P WV^,R4pV^8gW5,\V48dR#V\ 9dTV^8dM\P W^,V^,R4\P W^,V^,R43#W5, pEKBR#)z(width, height) for PNG / JPEG bytes, or None when unreadable. PNG: IHDR. JPEG: walk segments (skipping 0xFF fill bytes) to the first SOF marker; stop at SOS. Lives here so both the send-path passes and the tool layer share one header-only reader.sPNG  z>II:NsbigN>) startswithlenstructunpackint from_bytes_JPEG_SOF_MARKERS)r widthheightimarker segment_lens& rimage_dimensions_from_bytesr#?sv ~~*++CB eSZ8 5z3v;&& ~~k""s3x!| !ec#hv~QE AEAD.QS\FAE%~QS!1  ..q1uu=KQ!/CH"< **{a/?~~ca%A&6>sWXSXYZ]^Y^O_af@ggg A rc V^8dQhRRRR/#)rdata Optional[str]r Optional[int]r )r s"rrr\s33=3]3rcV'gR#TpVPR4'd8VPR4wr#pV'dRVRVPR49dR#VP4pVR\pVR\ V4\ V4^,, pV'gR#\ P!VRR7p\T4pTe \T4#R# \\3dR#i;i)aLongest side (px) of a data-URL / bare-base64 image, or None when it cannot be read. Decodes only the leading base64 prefix (``_DIMENSION_PROBE_CHARS``), so classifying a request with dozens of images costs a few header reads, not a full decode of every payload. Accepts both ``data:image/...;base64,....`` and a bare base64 string; anything else (a remote URL, an unrecognized container) yields None. Nzdata:,z;base64F)validate) r partitionindexstrip_DIMENSION_PROBE_CHARSrbase64 b64decode ValueError TypeErrorr#max)r%payload_ separatorprefixr dimss& rimage_max_side_from_datar9\s G'"" ' 1 1# 6gIT2B4::c?-CCmmoG ,, -F 5c&kS[1_5 6F v6 's +D(3t92d2  "s$CC-,C-c V^8dQhRRRR/#)rr%r&r boolr )r s"rrrxsII I$IrcB\V4pVRJ;'d V\8*#)aTrue only when the image's longest side is known and within ``MANY_IMAGE_DIMENSION_LIMIT``. Unknown dimensions are NOT safe: the stricter per-request cap would still be live, so the caller keeps the strict trigger. See :func:`images_all_within_many_image_limit`. N)r9MANY_IMAGE_DIMENSION_LIMIT)r%longests& rimage_within_many_image_limitr?xs' 't,G $  H H7.H#HHrc V^8dQhRRRR/#)rdataszIterable[Optional[str]]r r;r )r s"rrrs  .E $ rc@VFp\V4'dKR# R#)anTrue when EVERY image in the request is a readable image within the many-image limit. The Anthropic rule is per request: one oversized image holds every image in the request to the stricter cap, so a single unreadable or over-limit image must keep the strict block ceiling. Short-circuits on the first offender, which is what keeps this cheap on image-heavy turns. FT)r?)rAr%s& r"images_all_within_many_image_limitrCs!,T22 rc V^8dQhRRRR/#)rmany_image_safer;r rr )r s"rrrsRRRRrc*V'd\#\#)z[Block ceiling for a request: the strict 20 unless every image is within the many-image cap.)OUTBOUND_IMAGE_HARD_LIMITOUTBOUND_IMAGE_LIMIT)rEs&routbound_image_block_limitrIs(7 $Q=QQrcarrier_bytes_newest_firstreserved_bytesrEFlimitbudgetbatchfloorc@V^8dQhRRRRRRRRRR R R R RR RRRRR/ #)rcarrier_blocks_newest_first Sequence[int]reserved_blocksrrJOptional[Sequence[int]]rKrEr;rLr'rMrNrOr r )r s"rrrsl::!.::!8 :  :  : : : : : :rc aaaaaaaa a Sf \V4o\S4o Vo \VVVVVVVV V 3 Rl\^S ^,44^R7#)u3How many of the OLDEST image-bearing tool results to retire. ``carrier_blocks_newest_first`` is the image-block count per image-bearing tool result, newest first; ``reserved_blocks`` counts images the pass must never rewrite (user uploads). The byte dimension is active only when ``carrier_bytes_newest_first`` is given. ``limit`` defaults to :func:`outbound_image_block_limit` of ``many_image_safe``, so both passes pick the same ceiling from the same per-request classification. The retire count must be a STEP FUNCTION of the overshoot, because the pass is recomputed on every request: an exact ``count - limit`` target moves the frontier on every new image, and a fixed one-batch retire stops enforcing the limit after the first batch. So the count advances in quanta until the request fits. The quantum is ``batch`` capped at ``window - floor``, where ``window`` is how many newest carriers fit under the ceiling. A quantum wider than that would step past the newest frames on every advance; cutting each step back to exactly ``total - floor`` instead makes the retire count track ``total`` again — the per-image frontier this policy exists to avoid, visible whenever a tool result carries several images or uploads fill most of the ceiling. Holding for ``window - floor`` turns per advance is the most the floor allows. The floor is a SATISFIABILITY floor: it shelters the newest frames only when reserved uploads alone breach the block ceiling (no retirement can fix that), and never under byte pressure — the request-size limit is hard and the provider answers 413. Even then the count stays a step function: it retires whole quanta down toward the floor (keeping ``floor`` to ``floor + batch - 1`` carriers, fewer when the byte budget binds), so the cached prefix is rewritten once per quantum rather than on every new image. c 3|< "TF1p\SS V, RSS fRM S S V, RSSSSS4xK3 R#5iN)_retire_count_for_request) .0mrNrMrQrOrLrSrKsizestotals & r .outbound_image_retire_count..sZ ) &+EAIJ7 5+<  )s9<)default)rIrr3range) rQrSrJrKrErLrMrNrOr[r\s ff$d$dddd@@routbound_image_retire_countrasWN }*?; + ,E &E  1eai(  rc V^8dQhRRRR/#)ragentrr zset[str]r )r s"rrrs  c h rc\VRR4p\VRR4pVeV^,V8wdV\43pW nV^,#)a The session's latched set of tool-call ids whose images the send path has retired. Keyed on ``agent.session_id`` so a new session (or a compaction rotation, which rewrites the prefix anyway) starts clean and a reused provider call id cannot retire a fresh screenshot. session_idN_outbound_retired_image_ids)getattrsetrf)rcrehelds& routbound_retired_image_idsrjsL  d3J 57 >D |tAw*,CE",0) 7Nrc(V^8dQhRRRRRRRR/#)rretirercarrier_ids_newest_firstzSequence[Optional[str]] retired_idszOptional[set[str]]r r )r s"rrrs, +BQcrcVfV#\V4p\V4UUu.uFwrEV'gKWR9gKVNK pppV'd\WV^,, 4MTpVPRWV, R44V#uuppi)aWiden ``retire`` so every carrier up to the newest previously retired one stays retired, then record the carriers being retired into ``retired_ids``. The per-request decision cannot see history: a request that drops an upload (once it leaves the replay window) relaxes the ceiling, and re-deciding from scratch would restore screenshots an earlier request already retired, rewriting the cached prefix back. Nc38"TFq'gK VxK R#5irWr )rYcids& rr]'latched_retire_count..sW&OsSVss&Os  )r enumerater3update)rlrmrnr\nrqlatcheds&&& rlatched_retire_countrws ( )E()ABaBVQcqcN`qqBGa07S+ ,VFW&>v~&OWW Mbs BBBc<V^8dQhRRRRRRRRRRR RR RR RR R/ #) rrQrRrSrr[rTrKrLrMrNrOr r )r s"rrrsb..!... #. .  .  . . . .rcaaaaaaaaa\V4p^.V^,,o^.V^,,o\V4FJp SV ,W ,,SV ^,&SV ,Se SV ,M^,SV ^,&KL RVVVV3RlloRVVVV3RlloS!V4'd^#\\V^4V4pS!^4'gnS!V4'd`\V3Rl\Wx^,444p \^\WjV, ^,44p W, p WV ,, #S!^4'd&\V3Rl\V^,444M^p \^\WmV, 44p ^pW8d,\W,V4pS!W, 4'gK.V#V#)zSRetire count for one request in isolation; see :func:`outbound_image_retire_count`.c V^8dQhRRRR/#rkeptrr r;r )r s"rr/_retire_count_for_request..__annotate__sLLLLrcB<SRJ;'gSSV,,S8*#rWr )r|rM bytes_keptrKr[s&r _bytes_fit-_retire_count_for_request.._bytes_fits$}KKD1A AV KKrc V^8dQhRRRR/#r{r )r s"rrr}sQQCQDQrcJ<SSV,,S8*;'d S!V4#rWr )r|r blocks_keptrLrSs&r_fits(_retire_count_for_request.._fitss%T!22e;PP 4@PPrc3H<"TFpS!V4'gKVxK R#5irWr )rYkrs& rr],_retire_count_for_request..sN%< 1 !!%<" "c3H<"TFpS!V4'gKVxK R#5irWr )rYrrs& rr]rs9,qa,r)rr`minr3)rQrSr[rKrLrMrNrOr\r byte_windowquantumexcesswindowrlrrrrs&fffff&& @@@@rrXrXs} + ,E##K "J 5\(^.I.LL AE&qM9JU1XPQR 1q5LLQQ U|| E1 u %E 88 5)) NU5!)%<NN aU%$7!$;<=(((=B1XXS9E%!),9 91F!S/0G F .V%u-   M6Mri> )__doc__ __future__rr/rtypingrrrrrHrGOUTBOUND_IMAGE_BUDGET_BYTESIMAGE_EVICTION_BATCHOUTBOUND_IMAGE_FLOORr=r. frozensetrr#r9r?rCrIrarjrwrXr rrrs!F# 44  ("#lm:38I R :;? :  : " : :.:&:&:| $.r