Ë ÿ`gjÁ3ãóT—dZddlmZddlZddlmZddlmZdd„Z d d„Z y) a-``hermes gateway`` and ``hermes proxy`` subcommand parsers. Extracted verbatim from ``hermes_cli/main.py:main()`` (god-file Phase 2). Both parsers are built together because they shared one inline block (the ``gateway`` section also defined ``proxy``). Handlers injected to avoid importing ``main``. é)Ú annotationsN)ÚCallable)Úadd_accept_hooks_flagcóH—|jddtj¬«y)a{Accept stale `gateway --platform X` docs without advertising it. Gateway service lifecycle commands operate on the gateway process, not a single messaging adapter. Photon briefly printed a per-platform start command during setup; keep that command parseable so users following the old hint don't get blocked by argparse before the gateway can start. z --platformÚplatform©ÚdestÚhelpN)Ú add_argumentÚargparseÚSUPPRESS)Úparsers úQ/root/.hermes/venv/lib/python3.12/site-packages/hermes_cli/subcommands/gateway.pyÚ_add_compat_platform_flagrs&€ð ×ÑØØ Ü × Ñ ðõócóþ—|jddd¬«}|jd¬«}|jdd¬ «}|jd d d d d¬«|jdddd¬«|jddd¬«|jddd¬«|jddd¬«|jddd¬«t|«t|«|jdd¬ «}|jddd ¬«|jd!dd"¬«t |«|jd#d$¬ «}|jddd ¬«|jd!dd%¬«|jd&d'¬ «} | jddd ¬«| jd!dd(¬«t | «|jd)d*¬ «} | jd+dd,¬«| jd-d.dd/¬«| jddd ¬«t | «|jd0d1¬ «} | jddd2¬«| jddd3¬«| jd4d5d6¬7«| jd8d9dd:d;¬<«| jd=d9d>d?¬@«| jdAdBdd:dC¬<«| jdDdBd>dE¬@«| jdFdGdt j ¬@«|jdHdI¬ «} | jddd ¬«|jdJdK¬ «|jdLdM¬ «|jdNdOdP¬«} | jdQdRddS¬@«| jdTdUdVddW¬@«|jdXdYdZ¬«}|jd[d:d\¬]«|jd^d_d:d`¬a«|jdbdcd:dd¬a«|jdedfd:dg¬a«|j|¬h«|jdidjdk¬«}|jdl¬«}|jddm¬ «}|jdndodp¬]«|jdqd:dr¬]«|jdstd:dt¬u«|jd)dv¬ «|jdwdx¬ «|j|¬h«|j|¬h«y:)yzCAttach the ``gateway`` and ``proxy`` subcommands to ``subparsers``.ÚgatewayzMessaging gateway managementzLManage the messaging gateway (Telegram, Discord, WhatsApp, Weixin, and more))r Ú descriptionÚgateway_command)r Úrunz?Run gateway in foreground (recommended for WSL, Docker, Termux))r z-vz --verboseÚcountrz2Increase stderr log verbosity (-v=INFO, -vv=DEBUG))ÚactionÚdefaultr z-qz--quietÚ store_truezSuppress all stderr log output)rr z --replacez:Replace any existing gateway instance (useful for systemd)z--forcezÝStart a foreground gateway even when a systemd/launchd/s6 service already supervises this profile. Without --force, the command refuses because a second dispatcher escapes the service and can corrupt shared gateway state.z--no-supervisea¯Inside the s6-overlay Docker image, normally `gateway run` is automatically redirected to the supervised s6 service (so the gateway gets auto-restart on crash, plus a supervised dashboard if HERMES_DASHBOARD is set). Pass --no-supervise to opt out and get the historical pre-s6 foreground behavior: the gateway is the container's main process and the container exits with the gateway's exit code. No effect outside an s6 container.z--external-supervisorzøDeclare that an external process manager owns this foreground gateway. In-chat restarts and updates exit back to that manager instead of spawning a detached replacement. Use this when a launchd/systemd wrapper strips its native environment markers.Ústartz6Start the installed systemd/launchd background servicez--systemz-Target the Linux system-level gateway servicez--allzDKill ALL stale gateway processes across all profiles before startingÚstopzStop gateway servicez.Stop ALL gateway processes across all profilesÚrestartzRestart gateway servicez@Kill ALL gateway processes across all profiles before restartingÚstatuszShow gateway statusz--deepzDeep status checkz-lz--fullz9Show full, untruncated service/log output where supportedÚinstallz7Install gateway as a systemd/launchd background servicezForce reinstallz8Install as a Linux system-level service (starts at boot)z --run-as-userÚ run_as_userz3User account the Linux system service should run asrz --start-nowÚ start_nowNz6Start the gateway service immediately after installing)r rrr z--no-start-nowÚ store_falsez1Do not start the gateway service after installing)r rr z--start-on-loginÚstart_on_loginz7Enable the service to start automatically on login/bootz--no-start-on-loginz0Do not enable the service to start on login/bootz--elevated-handoffÚelevated_handoffÚ uninstallzUninstall gateway serviceÚlistz*List all profiles and their gateway statusÚsetupzConfigure messaging platformszmigrate-legacyz;Remove legacy hermes.service units from pre-rename installszÖStop, disable, and remove legacy Hermes gateway unit files (e.g. hermes.service) left over from older installs. Profile units (hermes-gateway-.service) and unrelated third-party services are never touched.z --dry-runÚdry_runz+List what would be removed without doing itz-yz--yesÚyeszSkip the confirmation promptÚenrollzLEnroll this gateway with a relay connector (writes relay auth creds to .env)a–Redeem a single-use enrollment token with a relay connector. Authenticates as your Nous Portal account (the connector derives the authoritative tenant from it), mints this gateway's per-gateway secret and per-tenant delivery key, and writes GATEWAY_RELAY_ID / GATEWAY_RELAY_SECRET / GATEWAY_RELAY_DELIVERY_KEY into ~/.hermes/.env. Requires being logged in (hermes setup). Not available in managed installs.z--tokenz†The single-use enrollment token from the connector (delivered with your gateway config). Also settable via GATEWAY_RELAY_ENROLL_TOKEN.)rr z--connector-urlÚ connector_urlz®The connector base/relay URL, e.g. wss://connector.example.com/relay or https://connector.example.com. Also settable via GATEWAY_RELAY_URL / gateway.relay_url in config.yaml.)r rr z --gateway-idÚ gateway_idz[A stable id for this gateway instance (kill-switch granularity). Defaults to gw-.z --wake-urlÚwake_urluaPhase 5 §5.2 wake URL: a reachable URL the connector pokes (payload-free GET) to wake this gateway when buffered work arrives while it's idle/suspended, so it reconnects and drains. Persisted as GATEWAY_RELAY_WAKE_URL in ~/.hermes/.env and forwarded at provision. Optional — without it the gateway still drains whenever it next reconnects on its own.)ÚfuncÚproxyz0Local OpenAI-compatible proxy to OAuth providerszÝRun a local HTTP server that forwards OpenAI-compatible requests to an OAuth-authenticated provider (e.g. Nous Portal). External apps can point at the proxy with any bearer token; the proxy attaches your real credentials.Ú proxy_commandzRun the proxy in the foregroundz --providerÚnouszMUpstream provider: nous or xai (default: nous). See `hermes proxy providers`.z--hostz@Bind address (default: 127.0.0.1). Use 0.0.0.0 to expose on LAN.z--portzBind port (default: 8645))Útyperr z$Show which proxy upstreams are readyÚ providersz'List available proxy upstream providers) Ú add_parserÚadd_subparsersr rrr r Ú set_defaultsÚint)Ú subparsersÚ cmd_gatewayÚ cmd_proxyÚcmd_gateway_enrollÚgateway_parserÚgateway_subparsersÚ gateway_runÚ gateway_startÚ gateway_stopÚgateway_restartÚgateway_statusÚgateway_installÚgateway_uninstallÚgateway_migrate_legacyÚgateway_enrollÚ proxy_parserÚproxy_subparsersÚ proxy_starts rÚbuild_gateway_parserrJ ss€ð ×*Ñ*ØØ +Øbð+ó€Nð (×6Ñ6ÐTÐ0ÓU€LØ×ÑØØØ <ðôð ×ÑØØØ =ðôð)×3Ñ3ØÐ1ð4ó€Oð× Ñ ØØØ <ð!ôð × Ñ ØØØ Oð!ôô ˜oÔ.ð(×2Ñ2°8ÐBWÐ2ÓX€NØ×Ñ °ÐDWÐÔXØ×ÑØ ØØØ Hð  ôð ×ÑØØØ <ð ôô ˜nÔ-ð)×3Ñ3ØÐQð4ó€Oð× Ñ  °<ÐFWÐ ÔXØ× Ñ ØØØ Gð!ôð × Ñ ØØ Ø Bð!ôð × Ñ ØØ ØØØ Eð !ôð× Ñ ØØ ØØ @ð !ôð × Ñ ØØ ØØØ Fð !ôð× Ñ ØØ ØØ ?ð !ôð × Ñ ØØ ØÜ × Ñ ð !ôð+×5Ñ5ØÐ5ð6óÐð×"Ñ"ØØØ <ð#ôð×!Ñ! &Ð/[Ð!Ô\ð×!Ñ! 'Ð0OÐ!ÔPð0×:Ñ:ØØ Jð 6ð ;ó Ðð×'Ñ'ØØ ØØ :ð (ôð ×'Ñ'Ø ØØ ØØ +ð (ôð(×2Ñ2ØØ [ð Zð 3ó €Nð×ÑØØð Rð  ôð×ÑØØ Øð 2ð  ô ð×ÑØØ Øð )ð  ôð×ÑØØ Øð %ð  ô ð×ÑÐ%7ÐÔ8ð×(Ñ(ØØ ?ð .ð )ó €Lð$×2Ñ2¸Ð2ÓHÐà"×-Ñ-ØÐ7ð.ó€Kð×ÑØØØ \ðôð ×ÑØØØ Oðôð ×ÑØÜ ØØ (ð ôð×ÑØÐ=ð ôð×ÑØÐCð ôð×Ñ 9ÐÔ-Ø×Ñ [ÐÕ1r)rzargparse.ArgumentParserÚreturnÚNone)r9rr:rr;rrKrL) Ú__doc__Ú __future__rr ÚtypingrÚhermes_cli.subcommands._sharedrrrJ©rrúrRsGðñõ#ãÝå@ó ðC2Ø (ðC2Ø5=ðC2ØS[ðC2à ôC2r