`gj (dZddlmZddlmZddZy)z``hermes tools`` subcommand parser. Extracted from ``hermes_cli/main.py:main()`` (god-file Phase 2 follow-up). Handler injected to avoid importing ``main``. ) annotations)Callablec*|jddd}|jddd|jd }|jd d }|jddd|jdd }|jdddd|jddd|jdd }|jdddd|jddd|jddd}|jd d!d"#|j|$y%)&z2Attach the ``tools`` subcommand to ``subparsers``.toolsz.Configure which tools are enabled per platformaEnable, disable, or list tools for CLI, Telegram, Discord, etc. Built-in toolsets use plain names (e.g. web, memory). MCP tools use server:tool notation (e.g. github:create_issue). Run 'hermes tools' with no subcommand for the interactive configuration UI.)help descriptionz --summary store_truez6Print a summary of enabled tools per platform and exit)actionr tools_action)destlistz0Show all tools and their enabled/disabled status)rz --platformclizPlatform to show (default: cli))defaultrdisablezDisable toolsets or MCP toolsnames+NAMEz7Toolset name (e.g. web) or MCP tool in server:tool form)nargsmetavarrz#Platform to apply to (default: cli)enablezEnable toolsets or MCP toolsz,Toolset name or MCP tool in server:tool formz post-setupz9Run a provider's post-setup install hook (npm/pip/binary)uRun the install/bootstrap hook a tool backend declares — the same step `hermes tools` runs after you pick a provider that needs extra dependencies (browser Chromium, Camofox, cua-driver, KittenTTS/Piper, ddgs, Spotify, Langfuse, xAI). Stable, non-interactive target the dashboard spawns to drive backend setup. Keys: agent_browser, camofox, cua_driver, kittentts, piper, ddgs, spotify, langfuse, xai_grok.post_setup_keyKEYzr/s #S.r(