Pmj dZddlZddlmZddlmZddlmZmZddl m Z dZ dde d e fd Z d efd Zd d ddddddddddddgddZejd dededdS)uLet the agent react to a message with an emoji in the Hermes desktop app. The conversational counterpart to the user's tapback: the same reaction store, the same one-per-author semantics, just written with ``author="agent"``. Gated on ``HERMES_DESKTOP`` (like the other GUI affordances) so it costs nothing on every other surface — the platform adapters already expose reactions through ``send_message(action="react")``, and this is the desktop's equivalent. Defaults to the message that triggered this turn (the photon precedent: the model shouldn't have to thread row ids through tool calls), and emits ``message.reaction`` so the renderer paints it without waiting for a resume. N)get_session_env) desktop_ui)registry tool_error)env_var_enabledcF ddlm}|S#t$rYdSwxYw)zAOpen the SessionDB for the profile owning this turn, or ``None``.r SessionDBN) hermes_stater Exceptionr s A/home/thesage/.hermes/hermes-agent/tools/react_to_message_tool.py_open_session_dbrsG******y{{ tts   emojireturncX|pd}tddptdd}|stdSt}|tdS|}d}|Qt dt |pd}||d| }|t|rd |d nd Sn'||t |}|pd} ||t ||pdd } n)#t$r} td| cYd} ~ Sd} ~ wwxYw| td|dS tj dt || |dn#t$rYnwxYwtj dt || ddS)zAAttach (or with an empty ``emoji`` retract) the agent's reaction.HERMES_SESSION_KEYHERMES_SESSION_IDu>No active session — reactions need a persisted conversation.NzSession storage is unavailable.userr)roleoffsetzNo user message found z back.z No user message to react to yet.agent)authorzFailed to set the reaction: zMessage z" is not part of this conversation.zmessage.reaction)row_id reactionsrT)successrrF) ensure_ascii)striprrrmaxintlatest_message_row_idget_message_roleset_message_reactionr remitjsondumps) rmessage_row_id messages_back session_keydbr target_rolebackrowrexcs r react_to_message_toolr/"sD [b   ! !E!"6;;R@@K \Z[[[   B z;<<< FK ~ 1c-,1--..))+F4)PP >9=e55555Ce   !!+s6{{;;mV @++ VemtG,   @@@>>>????????@OVOOOPPP   6{{K P P           :CKKiHHW\   s0&(D D5D0*D50D5&E55 FFctdsdS ddlm}|d}n#t$rYdSwxYwt |t o"t|ddS)uDesktop GUI only, and opt-in. HERMES_DESKTOP is set on the gateway the app spawns; the feature itself is off by default and enabled from Settings → Appearance (the desktop mirrors the toggle into ``display.message_reactions``). HERMES_DESKTOPFr)load_config_readonlydisplaymessage_reactions)rhermes_cli.configr2getr isinstancedictbool)r2r3s r check_react_requirementsr:\s + , ,u::::::&&((,,Y77 uu gt $ $ Vgkk:Mu.U.U)V)VVs#7 AAreact_to_messageuReact 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.objectstringufThe emoji to react with (e.g. '❤️', '😂', '👍'). Pass an empty string to remove your reaction.)type descriptionintegerz}Optional. The specific message to react to. Omit to react to the user's latest message, which is almost always what you want.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.rr'r()r> propertiesrequired)namer? parametersterminalc t|dd|d|dS)Nrrr'r(rA)r/r6)argskws r rJsF4hhw##xx 011hh//   u💛)rDtoolsetschemahandlercheck_fnr)NN)__doc__r%gateway.session_contextrtoolsrtools.registryrrutilsrrstrr/r9r:REACT_TO_MESSAGE_SCHEMAregisterrKr rYsy   333333////////!!!!!!777RU7777tW$WWWW&  !6"S"F  0I5++\   "   &       rK