+ lHj0Rt^RIHt^RIHt^RIHt^RIHt^RI H t H t H t H t Ht^RIHtHt!RR] 4t!R R ] 4t!R R ] 4t!R R]4t!RR] 4t]!R]]RR7!RR]4t!RR] 4t!RR] 4t!RR] 4t!RR] 4t!RR] 4t!R R!] 4t!R"R#]4t!R$R%] 4t!R&R'] 4t !R(R)] 4t!!R*R+] 4t"!R,R-] 4t#!R.R/] 4t$!R0R1] 4t%!R2R3] 4t&]!R4]]&R5R7!R6R7]4t'!R8R9]4t(!R:R;] 4t)]!R<](])R=R7!R>R?]4t*!R@RA]4t+]!RB]+]RCR7!RDRE]4t,]!RF],]RGR7!RHRI]4t-]!RJ]-]RKR7!RLRM]4t.]!RN].]ROR7!RPRQ]4t/]!RR]/]RSR7!RTRU]4t0]!RV]0]RWR7]!RX]0]RYR7]!RZ]*]R[R7!R\R]]4t1]!R^]1]R_R7!R`Ra] 4t2!RbRc]4t3]!Rd]3]ReR7!RfRg]4t4!RhRi]4t5!RjRk]4t6!RlRm]4t7!RnRo] 4t8!RpRq] 4t9]!Rr]6]RsR7]!Rt]7]9RuR7!RvRw]4t:!RxRy] 4t;]!Rz];R{R|7R}#)~ugServer→client requests: the backend asks the renderer a question (``server_requests.send``). Every entry is one request method: the ``params`` the frame carries (``session_id`` is added by the transport and declared on the shared base) and the ``result`` the client answers with. The ``request.cancel`` event that withdraws an open request lives here too. ) annotations)Literal)Field) TourPreset) JsonValueParamsPayloadResultWireEnum)eventserver_requestc&]tRt^t$RtR]R&RtR#)ServerRequestParamszLEvery request frame's params start with the session the question belongs to.str session_idN__name__ __module__ __qualname____firstlineno____doc____annotations____static_attributes__rJ/home/ubuntu/.hermes/hermes-agent/tui_gateway/contracts/server_requests.pyrrs VOrrc&]tRt^t$RtR]R&RtR#) ValueResultztThe answer to any one-string prompt (sudo, secret, vault prompts, desktop bridges): ``''`` means skipped / declined.rvaluerNrrrrrrs( JrrcH]tRt^$t$R]R&R]R&RtR]R&RtR]R &R tR#) ClarifyQuestionrqidquestionNzlist[str] | NonechoicesFbool multi_selectr)rrrrrr#r%rrrrr r $s! HM $G $L$rr c4]tRt^+t$RtR]R&RtR]R&RtR#)ClarifyRequestParamsza``answers`` rides only on a reconnect replay (locks the server already accepted; null = skipped).zlist[ClarifyQuestion] questionsNdict[str, str | None] | Noneanswersr)rrrrrrr*rrrrr'r'+sk$$,0G )0rr'c8]tRt^2t$RtRtR]R&RtR]R&RtR#) ClarifyResulta``{answers}`` for the whole set (early locks go through the ``clarify.lock`` RPC); a response without ``answers`` is cancel-all. ``outcome`` (optional): how the viewer's own panel ended, as main's classic CLI reports it (``timed_out`` keeps the answers locked before its deadline).Nr)r*z5Literal['submitted', 'timed_out', 'cancelled'] | Noneoutcomer) rrrrrr*rr-rrrrr,r,2s c-1G )0EIG BIrr,clarifyz-The clarify tool: ask the user 1-5 questions.)paramsresultdocc2]tRt^CtRtRtRtRtRtRt Rt Rt R #) SetupBeatnamethemelayout connectorspluginstourbuildrN) rrrrr4r5r6r7r8r9r:rrrrr3r3Cs% D E FJG D Err3c,]tRt^Mt$R]R&R]R&RtR#) SetupOptionridlabelrNrrrrrrrrrr<r<Ms  G Jrr<c&]tRt^Rt$RtR]R&RtR#) SetupNameCardN str | None suggestedr)rrrrrCrrrrrrArARs  Iz rrAc"]tRt^Vt$R]R&RtR#)SetupThemeCardrpickerrNr?rrrrErEV KrrEc"]tRt^Zt$R]R&RtR#)SetupOptionsCardzlist[SetupOption]optionsrNr?rrrrIrIZs rrIc"]tRt^^t$R]R&RtR#)SetupConnectorsCard list[str]rCrNr?rrrrLrL^srrLc"]tRt^bt$R]R&RtR#)SetupPluginsCardrMr8rNr?rrrrOrObs rrOcL]tRt^ft$RtR]R&RtR]R&RtR]R&R]R &R tR#) SetupBeatRequestParamsa``card`` is the beat's data (``agent/onboarding_flow.py::BEATS``): name, theme, connectors and plugins have their own shape; layout, tour and build carry ``options``. ``tool_call_id`` is the setup_beat call the card belongs to: only that transcript row draws it.r3beatNrBr" tool_call_idzZSetupNameCard | SetupThemeCard | SetupOptionsCard | SetupConnectorsCard | SetupPluginsCardcardr) rrrrrrr"rSrrrrrQrQfs)O OHj#L*# ddrrQc"]tRt^qt$R]R&RtR#)SetupNameAnswerrr4rNr?rrrrVrVqs IrrVc4]tRt^ut$RtR]R&RtR]R&RtR#)SetupThemeAnswerNrBaccentmoder)rrrrrYrrZrrrrrXrXusFJD*rrXc"]tRt^zt$R]R&RtR#)SetupLayoutAnswerrr6rNr?rrrr\r\zrGrr\c>]tRt^~t$R]R&]!]R7tR]R&RtR#)SetupConnectorsAnswerrM connecteddefault_factorynewly_connectedrN) rrrrrrlistrbrrrrr^r^~s!&t!rrrrrrr>rrrrreresE:rrec0]tRt^t$R]R&RtR]R&RtR#)SetupTourAnswerrr9NrBr>rrgrrrriris IE:rric0]tRt^t$R]R&RtR]R&RtR#)SetupBuildAnswerrr:NrBr>rrgrrrrkrks JE:rrkcF]tRt^t$RtRtR]R&RtR]R&RtR]R &R t R#) SetupBeatResulta``answer`` holds the shown beat's picks; ids must be one of the card's options (the backend rejects any other answer). ``said`` is composer text typed while the name card waited: the name. ``wrote_instead``: the user sent a message instead of answering; the backend ends the turn and the client sends that message as the next one. A response with none of these, or none within 300 s, closes the card unanswered.NzSetupNameAnswer | SetupThemeAnswer | SetupLayoutAnswer | SetupConnectorsAnswer | SetupPluginsAnswer | SetupTourAnswer | SetupBuildAnswer | NoneanswerrBsaidFr$ wrote_insteadr) rrrrrrnrrorprrrrrmrms1#=A 9AD*M4rrm setup_beatzRThe onboarding chat's card for one beat; blocks setup_beat until answered (300 s).c&]tRt^tRtRtRtRtRtR#)ApprovalChoiceoncesessionalwaysdenyrN) rrrrrtrurvrwrrrrrsrss DG F Drrsc]tRt^t$RtR]R&RtR]R&RtR]R&]!] R7t R]R &R t R ]R &R t R ]R &R t R ]R&R tR]R&]!R RR7tR]R&]P"RR/,tRtR #)ApprovalRequestParamsu]``tui_gateway/server.py::_approval_request_payload`` — the command is redacted server-side.r request_idcommand descriptionr`zlist[ApprovalChoice]r#N bool | Noneallow_permanent allow_session smart_deniedrB tool_namegateway_session_id)defaultaliassession_id_hintextraallowr)rrrrrrr|r}rrcr#rrrrrr model_configrrrrryrysgOGSK$)$$?G !?#'O['!%M;% $L+$ Iz "'rsv#)>>+& &f1.1JFJy!5mBD& !F!Vv&ve0efv =F=  f v  f  |$:?giX</<"V z"7DF , + v/ @B1-1 x 3KMO2 $-Ek]_"5 !*Eksu0 |$:;LN0 '=kPR~&<[OQ}%7 RT '1 ' }%<[XZ