yj%:dZddlmZddlZddlmZd dZd d ZdS)u``hermes dashboard`` / ``hermes serve`` subcommand parsers. ``dashboard`` is the browser web UI; ``serve`` is the same gateway, headless — what the desktop app and remote backends run. ``serve`` also skips the web UI build (``headless_backend=True``): pure JSON-RPC/WS clients never load the SPA. Both share one handler (``cmd_dashboard`` → ``start_server``). Extracted from ``hermes_cli/main.py:main()`` (god-file Phase 2); handler injected to avoid importing ``main``. ) annotationsN)CallablereturnNonec|dtdd|ddd|d d d |d d d |dd d |dddtj|dd d |dd d dS)uAttach the runtime flags shared by ``dashboard`` and ``serve``. Both subcommands boot the *same* ``web_server.start_server`` (the JSON-RPC/WebSocket gateway). ``dashboard`` opens a browser UI on top of it; ``serve`` is the headless backend the desktop app and remote clients connect to. The shared server logic lives in one place — only the browser-opening behavior and help framing differ. z--porti#z,Port (default 9119, 0 for auto-assign by OS))typedefaulthelpz--hostz 127.0.0.1zHost (default 127.0.0.1)r r z --insecure store_trueuDEPRECATED / NO-OP. Formerly bypassed auth on a non-loopback bind. As of the June 2026 hardening it no longer disables authentication — a public bind always requires an auth provider (password or OAuth). Bind 127.0.0.1 + tunnel to keep it local.actionr z --skip-buildzSkip the web UI build step and serve the existing dist directly. Useful for non-interactive contexts (Windows Scheduled Tasks, CI) where npm may not be available. Pre-build with: cd web && npm run buildz --isolatedzWhen launched from a named profile, run a dedicated server scoped to that profile instead of routing to the machine-level server. Default behavior is unified: profile launches attach to (or start) ONE machine-level server and preselect the profile.z--open-profile open_profiledestr r z--stopz5Stop all running Hermes web server processes and exitz--statusz1List running Hermes web server processes and exitN) add_argumentintargparseSUPPRESS)parsers F/home/ragecks/.hermes/hermes-agent/hermes_cli/subcommands/dashboard.py_add_server_runtime_argsrs[ sD/] +,F  M      V   B           D   @ cmd_dashboardrcmd_dashboard_registerc:|ddd}t||ddd|d dtj|| |d d d }t||ddtj|ddddd|ddddd||dd|d}|ddd}|ddd !|d"d#dd$%|d&d'dd(%|| dS))uAttach the ``dashboard`` and ``serve`` subcommands. Both share the same backend (``cmd_dashboard`` → ``start_server``). ``dashboard`` is the browser UI; ``serve`` is the headless backend used by the desktop app and remote clients. They are independent surfaces — neither "launches" the other — so the desktop app spawns ``serve``, never ``dashboard``. dashboardzStart the web UI dashboardzQLaunch the Hermes Agent web dashboard for managing config, API keys, and sessions)r descriptionz --no-openr z Don't open browser automaticallyr z--tui)funcservezVStart the Hermes backend server (headless; powers the desktop app and remote backends)uRun the Hermes backend server — the JSON-RPC/WebSocket gateway the desktop app and remote clients connect to. Headless: it never opens a browser UI.z--ssh-session-token-filessh_session_token_filePATHNz3Read a one-shot Desktop SSH session token from PATH)rmetavarr r z--ssh-owner-noncessh_owner_nonceNONCEz,Identify a Desktop-owned SSH backend processT)r no_openheadless_backenddashboard_subcommand)rregisterzVRegister a self-hosted dashboard with Nous Portal (writes the OAuth client ID to .env)zRegister this install as a self-hosted dashboard with your Nous Portal account. Creates an OAuth client, writes HERMES_DASHBOARD_OAUTH_CLIENT_ID into ~/.hermes/.env, and prints how to engage the login gate. Requires being logged in (hermes setup).z--namezHHuman-readable label for the dashboard (default: an auto-generated name)r z--redirect-uri redirect_urizOptional public HTTPS OAuth redirect URI for the dashboard, e.g. https://hermes.example.com/auth/callback. Omit for localhost-only use.rz --portal-url portal_urlzOverride the Nous Portal base URL for registration (default: the portal you logged into). The access token must be valid at this portal. Also settable via HERMES_DASHBOARD_PORTAL_URL. Mainly for testing against a staging/preview portal.) add_parserrrrr set_defaultsadd_subparsers) subparsersrrdashboard_parser serve_parserdashboard_subparsersdashboard_register_parsers rbuild_dashboard_parserr5Wsi",, )g- -...!!L/Q"!!  " !!}!555(( e  )L\***Lx/@" % B   ; =$QUVVV ,:: #;!5 ? ? e U !@ ! !** W+ **  U +**  8 +   **0F*GGGGGr)rr)rrrrrr)__doc__ __future__rrtypingrrr5rrr:s#"""""CCCCLHHHHHHr