sjdZddlZddlmZddlmZddlmZmZddl m Z dZ dde d e d e fd Z dde d e fd Zd efd ZddddddddddddddgddZejddededdS)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"``. Lives in the ``desktop_ui`` toolset (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 ?/home/agent/.hermes/hermes-agent/tools/react_to_message_tool.py_open_session_dbrsG******y{{ tts   emoji session_keyreturnc|stdS|}d}|Qtdt|pd}||d|}|t|rd|dndSn'||t|}|pd} ||t||pdd } n)#t $r} td | cYd} ~ Sd} ~ wwxYw| td |d S tjdt|| |dn#t $rYnwxYwtj dt|| ddS)AAttach (or with an empty ``emoji`` retract) the agent's reaction.>No active session — reactions need a persisted conversation.userNr)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) rmaxintlatest_message_row_idget_message_roleset_message_reactionr remitjsondumps) rmessage_row_id messages_backdbrr target_rolebackrowrexcs r _react_to_message_with_dbr-"s \Z[[[ FK ~ 1c-,1--..))+F4)PP >9=e55555Ce   !!+s6{{;;mV @++ VemtG,   @@@>>>????????@OVOOOPPP   6{{K P P           :CKKiHHW\   s0(B:: C CC C 9&D D-,D-c|pd}tddptdd}|stdSt}|tdS t ||||| |S#t $rYSwxYw# |w#t $rYwwxYwxYw)rHERMES_SESSION_KEYHERMES_SESSION_IDrNzSession storage is unavailable.)r(r)striprrrr-closer )rr&r'rr(s r react_to_message_toolr4Zs  [b   ! !E!"6;;R@@K \Z[[[   B z;<<< (   #      HHJJJJ    D   HHJJJJ    D sB(B!<B BB!C#B87C8 CCCCc ddlm}|d}n#t$rYdSwxYwt |t o"t |ddS)uOpt-in feature flag — surface eligibility is the toolset's job. ``desktop_ui`` already restricts this to GUI sessions. What's left is the user's own toggle (Settings → Appearance), which the desktop mirrors into ``display.message_reactions`` on the CONNECTED gateway's config — so this reads the right config whether that gateway is local, SSH, URL, or cloud. r)load_config_readonlydisplayFmessage_reactions)hermes_cli.configr6getr isinstancedictbool)r6r7s r check_react_requirementsr>ws::::::&&((,,Y77 uu gt $ $ Vgkk:Mu.U.U)V)VVs #& 44react_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')rB propertiesrequired)namerC parametersrc t|dd|d|dS)Nrr/r&r'rE)r4r:)argskws r rMsF4hhw##xx 011hh//   u💛)rHtoolsetschemahandlercheck_fnr)NN)__doc__r$gateway.session_contextrtoolsrtools.registryrrutilsrrstrr-r4r=r>REACT_TO_MESSAGE_SCHEMAregisterrNr r\s   333333////////!!!!!!55 5  5 5555pRU:W$WWWW$  !6"S"F  0I5++\   "   &       rN