yjUdZddlmZddlZddlmZddlmZmZej e Z eddZ de d <ed d hZddZddZddZdddddZdS) u Ambient session-accounting context for auxiliary LLM calls. Auxiliary calls (vision, compression, title generation, web_extract, session_search, ...) funnel through ``agent.auxiliary_client`` which has no session handle — so their token usage was historically discarded, leaving dashboard analytics blind to aux model spend (issue #23270). Instead of threading ``session_db``/``session_id`` parameters through every aux call site, the agent loop publishes them here (mirroring the Nous Portal conversation context in ``agent.portal_tags``) and the auxiliary client records usage at its single response-validation chokepoint. ContextVar semantics give us the right isolation for free: * concurrent agents in one process (gateway sessions, delegate subagents) never see each other's accounting context; * worker threads spawned via ``tools.thread_context.propagate_context_to_thread`` (MoA fan-out, background review) inherit the parent turn's context; * asyncio tasks inherit the context of the code that created them. MoA reference/aggregator slots are explicitly EXCLUDED from recording: ``agent/conversation_loop.py`` already folds MoA advisor usage and cost into the main loop's ``update_token_counts`` delta, so recording them here would double-count (see ``_EXCLUDED_TASKS``). ) annotationsN) ContextVar)AnyOptionalaux_accounting_context)defaultzContextVar[Optional[tuple]] _accounting moa_referencemoa_aggregator session_dbr session_id Optional[str]cv||stdSt||fS)a(Publish the active session's accounting handles for aux usage recording. Called by the agent loop at turn entry. Returns the ContextVar token so callers can ``reset_accounting_context(token)`` on turn exit. Publishing ``None`` handles (no DB / no session id) clears the context. N)r set)r r s :/home/ragecks/.hermes/hermes-agent/agent/aux_accounting.pyset_accounting_contextr.s8t$$$ ??J 3 4 44returnNonec t|dS#t$rtdYdSwxYw)z@Restore the previous accounting context (pair with ``set_...``).N)r reset Exceptionr)tokens rreset_accounting_contextr:sW%     s$AAOptional[tuple]c4tS)zEReturn ``(session_db, session_id)`` for the active turn, or ``None``.)r getrrget_accounting_contextrBs ??  rproviderbase_urlresponsetaskr!r"c  |r |tvrdSt}|dS|\}}t|dd}|dSddlm}m} | ||} | js| js| j s| j s | j sdStt|ddpdpd} d} || | || } | j t| j } n,#t$rt d d YnwxYw|||| ||| j| j| j | j | j | dS#t$r t dd YdSwxYw)uRecord an auxiliary response's token usage against the ambient session. Called from the auxiliary client's response-validation chokepoint. Strictly best-effort: any failure is swallowed (accounting must never break an aux call). No-ops when: * no accounting context is published (call is outside any agent turn), * the task is main-loop-accounted (MoA slots — see ``_EXCLUDED_TASKS``), * the response carries no usage object. The model is read from ``response.model`` (accurate even after the aux client's provider-fallback chains); *provider*/*base_url* reflect the originally-resolved route and are best-effort. Nusager)estimate_usage_costnormalize_usage)r!modelunknownr z Aux usage cost estimation failedT)exc_info) r)billing_providerbilling_base_url input_tokens output_tokenscache_read_tokenscache_write_tokensreasoning_tokensestimated_cost_usdz&Aux usage recording failed (non-fatal))_EXCLUDED_TASKSr rgetattragent.usage_pricingr'r(r/r0r1r2r3str amount_usdfloatrloggerdebugrecord_auxiliary_usage)r#r$r!r"ctxr r raw_usager'r(r&r)estimated_costcosts rrecord_aux_usagerBGs*.N t.. Foo ; F!$ JHgt44   FLLLLLLLL H===   "'"5 & */*B %  FGHgr228b99FY L&&ux(D*!&t!7!7 L L L LL;dL K K K K K L ))  %%+-#5$7"3- *  NNN = MMMMMMNsK D7D7D78D7$D7%*CD7&C96D78C99rLs14#"""""""""""  8 $ $,6:d,,, )_.>?@@ 5 5 5 5#" CNCNCNCNCNCNCNCNr