+ „WÝjT ãó.€Rt^RIHt^RIHtRRltR#)z#``hermes tools`` subcommand parser.)Ú annotations)ÚCallablecó €V^8„dQhRRRR/#)éÚ cmd_toolsrÚreturnÚNone©)Úformats"ÚPC:\Users\johnn\AppData\Local\hermes\hermes-agent\hermes_cli\subcommands\tools.pyÚ __annotate__r s€÷*.ñ*.°ð*.¸dñ*.ócó,€VPRRRR7pVPRRRR7VPR R 7pVPR R R 7pVPRRRR7VPRRR 7pVPRRRRR7VPRRRR7VPRRR 7pVPRRRRR7VPRRRR7VPRRRR7pVPR R!R"R#7VPVR$7R%#)&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)ÚdestÚlistz0Show all tools and their enabled/disabled status)rz --platformÚclizPlatform to show (default: cli))ÚdefaultrÚdisablezDisable toolsets or MCP toolsÚnamesÚ+ÚNAMEz7Toolset name (e.g. web) or MCP tool in server:tool form)ÚnargsÚmetavarrz#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)u†Run 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, xAI, Codex). Stable, non-interactive target the dashboard spawns to drive backend setup. Keys: agent_browser, camofox, cua_driver, kittentts, piper, ddgs, xai_grok, openai_codex.Úpost_setup_keyÚKEYzr2sðÙ)å"å÷*.r