+ lHjRt^RIt^RIt^RIHt^RIHt^RIHtH t Rt RRRllt RR lt R R R R RRRRRRRR R/RRRR R/RRRR R//RR.//t ]P!R R] R] RR7R#) a`Agent emoji reaction in the Hermes desktop app: the counterpart to the user's tapback (same store, one-per-author, ``author="agent"``). Lives in the ``desktop_ui`` toolset so it costs nothing elsewhere (adapters expose reactions via ``send_message(action="react")``); defaults to the triggering message and emits ``message.reaction`` for live painting.N)get_session_env) desktop_ui)registry tool_errorcB^RIHpV!4# \dR#i;i)zAOpen the SessionDB for the profile owning this turn, or ``None``.acquireN)hermes_state_registryr Exceptionrs @/home/ubuntu/.hermes/hermes-agent/tools/react_to_message_tool.py_open_session_dbr s$1y s  c0V^8dQhR\R\/#)emojireturn)str)formats"r __annotate__rs#!#!#!RU#!c T;'gRP4p\RR4;'g \RR4pV'g \R4#\4pVf \R4#TRreVf\ ^\ T;'g^44pVP VRVR7pVfS\V'dR V R 2MR 4\P!\4;_uu_4^R I H pV!V4RRR4#M%VPV\ V44;'gRpTPT\ V4T;'gRR R7p T fI\RT R24\P!\4;_uu_4^R I H pT!T4RRR4#\P!\4;_uu_4\P!RR\ T4RT RT/4RRR4\ P"!RRR\ T4RT /RR7\P!\4;_uu_4^R I H pT!T4RRR4# +'gi#;i \dep \RT 24uRp ? \P!\4;_uu_4^R I H pT!T4RRR4# +'gi#;iRp ? ii;i +'gi#;i +'giEL ;i +'gi#;i \P!\4;_uu_4^R I H pT!T4RRR4i +'gii;i;i)zAAttach (or with an empty ``emoji`` retract) the agent's reaction.HERMES_SESSION_IDHERMES_SESSION_KEYu>No active session — reactions need a persisted conversation.NzSession storage is unavailable.user)roleoffsetzNo user message found z back.z No user message to react to yet.)release_or_closeagent)authorzFailed to set the reaction: zMessage z" is not part of this conversation.zmessage.reactionrow_id reactionsrsuccessTF) ensure_ascii)striprrr maxintlatest_message_row_id contextlibsuppressr r rget_message_roleset_message_reactionremitjsondumps) rmessage_row_id messages_back session_keydbr target_rolebackrr excs &&& r react_to_message_toolr5s [[b   !E!"5r:ggoNbdf>gK Z[[  B z;<<!,f >q#m00q12D--kt-TF~!4$:4&"GUwx  + + > R , +!--k3v;GQQ6K D// S[%--SW`g/hI  0RST  + + > R , +   + + OO.3v; U^`fhs0t u,zz9dHc&k;PYZino   + + > R , + + + D R , + + + D, + , + +, +Z  + + > R , + + +s(L;L I8"LLI> IL;K "L5'K.L,K0 I  K" K/K0LJ.. J> KL K  K- ' L0 L #M&L> 5 M> M Mc$V^8dQhR\/#)rr)bool)rs"r rr>sGG$Grc2\P!RRR7#)uXOpt-in flag (Settings → Appearance); ``desktop_ui`` already restricts to GUI sessions.message_reactionsF)default)r user_enabledrr check_react_requirementsr=>s  " "#6 FFrnamereact_to_message descriptionuReact to a message with a single emoji, the way you'd tapback in iMessage. Reach for it when a reaction is what a person would do: something funny gets a 😂, warmth gets a ❤️, a plan you're on board with gets a 👍 — then just carry on with whatever the message actually needs. If a reaction says it all, it can BE the reply (skip the redundant 'sounds good!' turn). Use it like a person would: occasionally, when felt — not on every message, and never as a status signal. NEVER narrate or explain a reaction ('I reacted with...', 'Reacting now') — the emoji appearing on the bubble is the whole point, and commentary kills it. Defaults to the user's most recent message. One reaction per message: a different emoji replaces yours, an empty string retracts it. parameterstypeobject propertiesrstringufThe emoji to react with (e.g. '❤️', '😂', '👍'). Pass an empty string to remove your reaction.r.integerz}Optional. The specific message to react to. Omit to react to the user's latest message, which is almost always what you want.r/uOptional. React to an EARLIER user message: 1 = the one before the latest, 2 = two before, and so on. For when something lands late — the joke you only got after answering.requiredrc z\VPRR4VPR4VPR4R7#)rrr.r/)rr.r/)r5get)argskws&,r rLss04hhw#DHH=M4Nhh/ 1ru💛)r>toolsetschemahandlercheck_fnr)NN)__doc__r'r,gateway.session_contextrtoolsrtools.registryrrr r5r=REACT_TO_MESSAGE_SCHEMAregisterr<rr rWsX  3/#!LG    6  S  F 0 WI5+\  \:Q 1&V r