[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAMRFY4M8QJQ0D22PGM7YV":3,"skill-same:01M6CAMRFY4M8QJQ0D22PGM7YV":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6CAMRFY4M8QJQ0D22PGM7YV","hermes-agent",null,"Configure, extend, or contribute to Hermes Agent.","adnichols\u002Fai-configs","adnichols","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F493746?v=4","01M6C33VRY9WF6XWYPT1AFA7JJ","Aaron Nichols","01M6C33VWTNKGRM92E9G643V4W",5,"MIT","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fwriting\u002Fskills\u002Fautonomous-ai-agents\u002Fhermes-agent\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"hermes agent","hermes","code","opencode","multi-agent","contribute","configure","https","gateway","macos","development","setup","windows","codex","linux","github","cli","2026-11-10 10:12:30",false,"---\nname: hermes-agent\ndescription: \"Configure, extend, or contribute to Hermes Agent.\"\nversion: 2.1.0\nauthor: Hermes Agent + Teknium\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [hermes, setup, configuration, multi-agent, spawning, cli, gateway, development]\n    homepage: https:\u002F\u002Fgithub.com\u002FNousResearch\u002Fhermes-agent\n    related_skills: [claude-code, codex, opencode]\n---\n\n# Hermes Agent\n\nHermes Agent is an open-source AI agent framework by Nous Research that runs in your terminal, messaging platforms, and IDEs. It belongs to the same category as Claude Code (Anthropic), Codex (OpenAI), and OpenClaw — autonomous coding and task-execution agents that use tool calling to interact with your system. Hermes works with any LLM provider (OpenRouter, Anthropic, OpenAI, DeepSeek, local models, and 15+ others) and runs on Linux, macOS, and WSL.\n\nWhat makes Hermes different:\n\n- **Self-improving through skills** — Hermes learns from experience by saving reusable procedures as skills. When it solves a complex problem, discovers a workflow, or gets corrected, it can persist that knowledge as a skill document that loads into future sessions. Skills accumulate over time, making the agent better at your specific tasks and environment.\n- **Persistent memory across sessions** — remembers who you are, your preferences, environment details, and lessons learned. Pluggable memory backends (built-in, Honcho, Mem0, and more) let you choose how memory works.\n- **Multi-platform gateway** — the same agent runs on Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Email, and 10+ other platforms with full tool access, not just chat.\n- **Provider-agnostic** — swap models and providers mid-workflow without changing anything else. Credential pools rotate across multiple API keys automatically.\n- **Profiles** — run multiple independent Hermes instances with isolated configs, sessions, skills, and memory.\n- **Extensible** — plugins, MCP servers, custom tools, webhook triggers, cron scheduling, and the full Python ecosystem.\n\nPeople use Hermes for software development, research, system administration, data analysis, content creation, home automation, and anything else that benefits from an AI agent with persistent context and full system access.\n\n**This skill helps you work with Hermes Agent effectively** — setting it up, configuring features, spawning additional agent instances, troubleshooting issues, finding the right commands and settings, and understanding how the system works when you need to extend or contribute to it.\n\n**Docs:** https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002F\n\n## Quick Start\n\n```bash\n# Install\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002FNousResearch\u002Fhermes-agent\u002Fmain\u002Fscripts\u002Finstall.sh | bash\n\n# Interactive chat (default)\nhermes\n\n# Single query\nhermes chat -q \"What is the capital of France?\"\n\n# Setup wizard\nhermes setup\n\n# Change model\u002Fprovider\nhermes model\n\n# Check health\nhermes doctor\n```\n\n---\n\n## CLI Reference\n\n### Global Flags\n\n```\nhermes [flags] [command]\n\n  --version, -V             Show version\n  --resume, -r SESSION      Resume session by ID or title\n  --continue, -c [NAME]     Resume by name, or most recent session\n  --worktree, -w            Isolated git worktree mode (parallel agents)\n  --skills, -s SKILL        Preload skills (comma-separate or repeat)\n  --profile, -p NAME        Use a named profile\n  --yolo                    Skip dangerous command approval\n  --pass-session-id         Include session ID in system prompt\n```\n\nNo subcommand defaults to `chat`.\n\n### Chat\n\n```\nhermes chat [flags]\n  -q, --query TEXT          Single query, non-interactive\n  -m, --model MODEL         Model (e.g. anthropic\u002Fclaude-sonnet-4)\n  -t, --toolsets LIST       Comma-separated toolsets\n  --provider PROVIDER       Force provider (openrouter, anthropic, nous, etc.)\n  -v, --verbose             Verbose output\n  -Q, --quiet               Suppress banner, spinner, tool previews\n  --checkpoints             Enable filesystem checkpoints (\u002Frollback)\n  --source TAG              Session source tag (default: cli)\n```\n\n### Configuration\n\n```\nhermes setup [section]      Interactive wizard (model|terminal|gateway|tools|agent)\nhermes model                Interactive model\u002Fprovider picker\nhermes config               View current config\nhermes config edit          Open config.yaml in $EDITOR\nhermes config set KEY VAL   Set a config value\nhermes config path          Print config.yaml path\nhermes config env-path      Print .env path\nhermes config check         Check for missing\u002Foutdated config\nhermes config migrate       Update config with new options\nhermes auth                 Interactive credential manager\nhermes auth add PROVIDER    Add OAuth or API-key credential (e.g. nous, openai-codex, qwen-oauth)\nhermes auth list            List stored credentials\nhermes auth remove PROVIDER Remove a stored credential\nhermes doctor [--fix]       Check dependencies and config\nhermes status [--all]       Show component status\n```\n\n### Tools & Skills\n\n```\nhermes tools                Interactive tool enable\u002Fdisable (curses UI)\nhermes tools list           Show all tools and status\nhermes tools enable NAME    Enable a toolset\nhermes tools disable NAME   Disable a toolset\n\nhermes skills list          List installed skills\nhermes skills search QUERY  Search the skills hub\nhermes skills install ID    Install a skill (ID can be a hub identifier OR a direct https:\u002F\u002F…\u002FSKILL.md URL; pass --name to override when frontmatter has no name)\nhermes skills inspect ID    Preview without installing\nhermes skills config        Enable\u002Fdisable skills per platform\nhermes skills check         Check for updates\nhermes skills update        Update outdated skills\nhermes skills uninstall N   Remove a hub skill\nhermes skills publish PATH  Publish to registry\nhermes skills browse        Browse all available skills\nhermes skills tap add REPO  Add a GitHub repo as skill source\n```\n\n### MCP Servers\n\n```\nhermes mcp serve            Run Hermes as an MCP server\nhermes mcp add NAME         Add an MCP server (--url or --command)\nhermes mcp remove NAME      Remove an MCP server\nhermes mcp list             List configured servers\nhermes mcp test NAME        Test connection\nhermes mcp configure NAME   Toggle tool selection\n```\n\n### Gateway (Messaging Platforms)\n\n```\nhermes gateway run          Start gateway foreground\nhermes gateway install      Install as background service\nhermes gateway start\u002Fstop   Control the service\nhermes gateway restart      Restart the service\nhermes gateway status       Check status\nhermes gateway setup        Configure platforms\n```\n\nSupported platforms: Telegram, Discord, Slack, WhatsApp, Signal, Email, SMS, Matrix, Mattermost, Home Assistant, DingTalk, Feishu, WeCom, BlueBubbles (iMessage), Weixin (WeChat), API Server, Webhooks. Open WebUI connects via the API Server adapter.\n\nPlatform docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002F\n\n### Sessions\n\n```\nhermes sessions list        List recent sessions\nhermes sessions browse      Interactive picker\nhermes sessions export OUT  Export to JSONL\nhermes sessions rename ID T Rename a session\nhermes sessions delete ID   Delete a session\nhermes sessions prune       Clean up old sessions (--older-than N days)\nhermes sessions stats       Session store statistics\n```\n\n### Cron Jobs\n\n```\nhermes cron list            List jobs (--all for disabled)\nhermes cron create SCHED    Create: '30m', 'every 2h', '0 9 * * *'\nhermes cron edit ID         Edit schedule, prompt, delivery\nhermes cron pause\u002Fresume ID Control job state\nhermes cron run ID          Trigger on next tick\nhermes cron remove ID       Delete a job\nhermes cron status          Scheduler status\n```\n\n### Webhooks\n\n```\nhermes webhook subscribe N  Create route at \u002Fwebhooks\u002F\u003Cname>\nhermes webhook list         List subscriptions\nhermes webhook remove NAME  Remove a subscription\nhermes webhook test NAME    Send a test POST\n```\n\n### Profiles\n\n```\nhermes profile list         List all profiles\nhermes profile create NAME  Create (--clone, --clone-all, --clone-from)\nhermes profile use NAME     Set sticky default\nhermes profile delete NAME  Delete a profile\nhermes profile show NAME    Show details\nhermes profile alias NAME   Manage wrapper scripts\nhermes profile rename A B   Rename a profile\nhermes profile export NAME  Export to tar.gz\nhermes profile import FILE  Import from archive\n```\n\n### Credential Pools\n\n```\nhermes auth add             Interactive credential wizard\nhermes auth list [PROVIDER] List pooled credentials\nhermes auth remove P INDEX  Remove by provider + index\nhermes auth reset PROVIDER  Clear exhaustion status\n```\n\n### Other\n\n```\nhermes insights [--days N]  Usage analytics\nhermes update               Update to latest version\nhermes pairing list\u002Fapprove\u002Frevoke  DM authorization\nhermes plugins list\u002Finstall\u002Fremove  Plugin management\nhermes honcho setup\u002Fstatus  Honcho memory integration (requires honcho plugin)\nhermes memory setup\u002Fstatus\u002Foff  Memory provider config\nhermes completion bash|zsh  Shell completions\nhermes acp                  ACP server (IDE integration)\nhermes claw migrate         Migrate from OpenClaw\nhermes uninstall            Uninstall Hermes\n```\n\n---\n\n## Slash Commands (In-Session)\n\nType these during an interactive chat session. New commands land fairly\noften; if something below looks stale, run `\u002Fhelp` in-session for the\nauthoritative list or see the [live slash commands reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fslash-commands).\nThe registry of record is `hermes_cli\u002Fcommands.py` — every consumer\n(autocomplete, Telegram menu, Slack mapping, `\u002Fhelp`) derives from it.\n\n### Session Control\n```\n\u002Fnew (\u002Freset)        Fresh session\n\u002Fclear               Clear screen + new session (CLI)\n\u002Fretry               Resend last message\n\u002Fundo                Remove last exchange\n\u002Ftitle [name]        Name the session\n\u002Fcompress            Manually compress context\n\u002Fstop                Kill background processes\n\u002Frollback [N]        Restore filesystem checkpoint\n\u002Fsnapshot [sub]      Create or restore state snapshots of Hermes config\u002Fstate (CLI)\n\u002Fbackground \u003Cprompt> Run prompt in background\n\u002Fqueue \u003Cprompt>      Queue for next turn\n\u002Fsteer \u003Cprompt>      Inject a message after the next tool call without interrupting\n\u002Fagents (\u002Ftasks)     Show active agents and running tasks\n\u002Fresume [name]       Resume a named session\n\u002Fgoal [text|sub]     Set a standing goal Hermes works on across turns until achieved\n                     (subcommands: status, pause, resume, clear)\n\u002Fredraw              Force a full UI repaint (CLI)\n```\n\n### Configuration\n```\n\u002Fconfig              Show config (CLI)\n\u002Fmodel [name]        Show or change model\n\u002Fpersonality [name]  Set personality\n\u002Freasoning [level]   Set reasoning (none|minimal|low|medium|high|xhigh|show|hide)\n\u002Fverbose             Cycle: off → new → all → verbose\n\u002Fvoice [on|off|tts]  Voice mode\n\u002Fyolo                Toggle approval bypass\n\u002Fbusy [sub]          Control what Enter does while Hermes is working (CLI)\n                     (subcommands: queue, steer, interrupt, status)\n\u002Findicator [style]   Pick the TUI busy-indicator style (CLI)\n                     (styles: kaomoji, emoji, unicode, ascii)\n\u002Ffooter [on|off]     Toggle gateway runtime-metadata footer on final replies\n\u002Fskin [name]         Change theme (CLI)\n\u002Fstatusbar           Toggle status bar (CLI)\n```\n\n### Tools & Skills\n```\n\u002Ftools               Manage tools (CLI)\n\u002Ftoolsets            List toolsets (CLI)\n\u002Fskills              Search\u002Finstall skills (CLI)\n\u002Fskill \u003Cname>        Load a skill into session\n\u002Freload-skills       Re-scan ~\u002F.hermes\u002Fskills\u002F for added\u002Fremoved skills\n\u002Freload              Reload .env variables into the running session (CLI)\n\u002Freload-mcp          Reload MCP servers\n\u002Fcron                Manage cron jobs (CLI)\n\u002Fcurator [sub]       Background skill maintenance (status, run, pin, archive, …)\n\u002Fkanban [sub]        Multi-profile collaboration board (tasks, links, comments)\n\u002Fplugins             List plugins (CLI)\n```\n\n### Gateway\n```\n\u002Fapprove             Approve a pending command (gateway)\n\u002Fdeny                Deny a pending command (gateway)\n\u002Frestart             Restart gateway (gateway)\n\u002Fsethome             Set current chat as home channel (gateway)\n\u002Fupdate              Update Hermes to latest (gateway)\n\u002Ftopic [sub]         Enable or inspect Telegram DM topic sessions (gateway)\n\u002Fplatforms (\u002Fgateway) Show platform connection status (gateway)\n```\n\n### Utility\n```\n\u002Fbranch (\u002Ffork)      Branch the current session\n\u002Ffast                Toggle priority\u002Ffast processing\n\u002Fbrowser             Open CDP browser connection\n\u002Fhistory             Show conversation history (CLI)\n\u002Fsave                Save conversation to file (CLI)\n\u002Fcopy [N]            Copy the last assistant response to clipboard (CLI)\n\u002Fpaste               Attach clipboard image (CLI)\n\u002Fimage               Attach local image file (CLI)\n```\n\n### Info\n```\n\u002Fhelp                Show commands\n\u002Fcommands [page]     Browse all commands (gateway)\n\u002Fusage               Token usage\n\u002Finsights [days]     Usage analytics\n\u002Fgquota              Show Google Gemini Code Assist quota usage (CLI)\n\u002Fstatus              Session info (gateway)\n\u002Fprofile             Active profile info\n\u002Fdebug               Upload debug report (system info + logs) and get shareable links\n```\n\n### Exit\n```\n\u002Fquit (\u002Fexit, \u002Fq)    Exit CLI\n```\n\n---\n\n## Key Paths & Config\n\n```\n~\u002F.hermes\u002Fconfig.yaml       Main configuration\n~\u002F.hermes\u002F.env              API keys and secrets\n$HERMES_HOME\u002Fskills\u002F        Installed skills\n~\u002F.hermes\u002Fsessions\u002F         Gateway routing index, request dumps, *.jsonl transcripts (and optional per-session JSON snapshots when sessions.write_json_snapshots: true)\n~\u002F.hermes\u002Fstate.db          Canonical session store (SQLite + FTS5)\n~\u002F.hermes\u002Flogs\u002F             Gateway and error logs\n~\u002F.hermes\u002Fauth.json         OAuth tokens and credential pools\n~\u002F.hermes\u002Fhermes-agent\u002F     Source code (if git-installed)\n```\n\nProfiles use `~\u002F.hermes\u002Fprofiles\u002F\u003Cname>\u002F` with the same layout.\n\n### Config Sections\n\nEdit with `hermes config edit` or `hermes config set section.key value`.\n\n| Section | Key options |\n|---------|-------------|\n| `model` | `default`, `provider`, `base_url`, `api_key`, `context_length` |\n| `agent` | `max_turns` (90), `tool_use_enforcement` |\n| `terminal` | `backend` (local\u002Fdocker\u002Fssh\u002Fmodal), `cwd`, `timeout` (180) |\n| `compression` | `enabled`, `threshold` (0.50), `target_ratio` (0.20) |\n| `display` | `skin`, `tool_progress`, `show_reasoning`, `show_cost` |\n| `stt` | `enabled`, `provider` (local\u002Fgroq\u002Fopenai\u002Fmistral) |\n| `tts` | `provider` (edge\u002Felevenlabs\u002Fopenai\u002Fminimax\u002Fmistral\u002Fneutts) |\n| `memory` | `memory_enabled`, `user_profile_enabled`, `provider` |\n| `security` | `tirith_enabled`, `website_blocklist` |\n| `delegation` | `model`, `provider`, `base_url`, `api_key`, `max_iterations` (50), `reasoning_effort` |\n| `checkpoints` | `enabled`, `max_snapshots` (50) |\n\nFull config reference: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fconfiguration\n\n### Providers\n\n20+ providers supported. Set via `hermes model` or `hermes setup`.\n\n| Provider | Auth | Key env var |\n|----------|------|-------------|\n| OpenRouter | API key | `OPENROUTER_API_KEY` |\n| Anthropic | API key | `ANTHROPIC_API_KEY` |\n| Nous Portal | OAuth | `hermes auth` |\n| OpenAI Codex | OAuth | `hermes auth` |\n| GitHub Copilot | Token | `COPILOT_GITHUB_TOKEN` |\n| Google Gemini | API key | `GOOGLE_API_KEY` or `GEMINI_API_KEY` |\n| DeepSeek | API key | `DEEPSEEK_API_KEY` |\n| xAI \u002F Grok | API key | `XAI_API_KEY` |\n| Hugging Face | Token | `HF_TOKEN` |\n| Z.AI \u002F GLM | API key | `GLM_API_KEY` |\n| MiniMax | API key | `MINIMAX_API_KEY` |\n| MiniMax CN | API key | `MINIMAX_CN_API_KEY` |\n| Kimi \u002F Moonshot | API key | `KIMI_API_KEY` |\n| Alibaba \u002F DashScope | API key | `DASHSCOPE_API_KEY` |\n| Xiaomi MiMo | API key | `XIAOMI_API_KEY` |\n| Kilo Code | API key | `KILOCODE_API_KEY` |\n| OpenCode Zen | API key | `OPENCODE_ZEN_API_KEY` |\n| OpenCode Go | API key | `OPENCODE_GO_API_KEY` |\n| Qwen OAuth | OAuth | `hermes auth add qwen-oauth` |\n| Custom endpoint | Config | `model.base_url` + `model.api_key` in config.yaml |\n| GitHub Copilot ACP | External | `COPILOT_CLI_PATH` or Copilot CLI |\n\nFull provider docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fintegrations\u002Fproviders\n\n### Toolsets\n\nEnable\u002Fdisable via `hermes tools` (interactive) or `hermes tools enable\u002Fdisable NAME`.\n\n| Toolset | What it provides |\n|---------|-----------------|\n| `web` | Web search and content extraction |\n| `search` | Web search only (subset of `web`) |\n| `browser` | Browser automation (Browserbase, Camofox, or local Chromium) |\n| `terminal` | Shell commands and process management |\n| `file` | File read\u002Fwrite\u002Fsearch\u002Fpatch |\n| `code_execution` | Sandboxed Python execution |\n| `vision` | Image analysis |\n| `image_gen` | AI image generation |\n| `video` | Video analysis and generation |\n| `tts` | Text-to-speech |\n| `skills` | Skill browsing and management |\n| `memory` | Persistent cross-session memory |\n| `session_search` | Search past conversations |\n| `delegation` | Subagent task delegation |\n| `cronjob` | Scheduled task management |\n| `clarify` | Ask user clarifying questions |\n| `messaging` | Cross-platform message sending |\n| `todo` | In-session task planning and tracking |\n| `kanban` | Multi-agent work-queue tools (gated to workers) |\n| `debugging` | Extra introspection\u002Fdebug tools (off by default) |\n| `safe` | Minimal, low-risk toolset for locked-down sessions |\n| `spotify` | Spotify playback and playlist control |\n| `homeassistant` | Smart home control (off by default) |\n| `discord` | Discord integration tools |\n| `discord_admin` | Discord admin\u002Fmoderation tools |\n| `feishu_doc` | Feishu (Lark) document tools |\n| `feishu_drive` | Feishu (Lark) drive tools |\n| `yuanbao` | Yuanbao integration tools |\n| `rl` | Reinforcement learning tools (off by default) |\n| `moa` | Mixture of Agents (off by default) |\n\nFull enumeration lives in `toolsets.py` as the `TOOLSETS` dict; `_HERMES_CORE_TOOLS` is the default bundle most platforms inherit from.\n\nTool changes take effect on `\u002Freset` (new session). They do NOT apply mid-conversation to preserve prompt caching.\n\n---\n\n## Security & Privacy Toggles\n\nCommon \"why is Hermes doing X to my output \u002F tool calls \u002F commands?\" toggles — and the exact commands to change them. Most of these need a fresh session (`\u002Freset` in chat, or start a new `hermes` invocation) because they're read once at startup.\n\n### Secret redaction in tool output\n\nSecret redaction is **on by default** — tool output (terminal stdout, `read_file`, web content, subagent summaries, etc.) is scanned for strings that look like API keys, tokens, and secrets before it enters the conversation context and logs. Leave it enabled for normal use:\n\n```bash\nhermes config set security.redact_secrets true       # keep enabled globally\n```\n\n**Restart required.** `security.redact_secrets` is snapshotted at import time — toggling it mid-session (e.g. via `export HERMES_REDACT_SECRETS=false` from a tool call) will NOT take effect for the running process. Tell the user to change it in config from a terminal, then start a new session. This is deliberate — it prevents an LLM from flipping the toggle on itself mid-task.\n\nDisable only when you deliberately need raw credential-like strings for debugging or redactor development:\n```bash\nhermes config set security.redact_secrets false\n```\n\n### PII redaction in gateway messages\n\nSeparate from secret redaction. When enabled, the gateway hashes user IDs and strips phone numbers from the session context before it reaches the model:\n\n```bash\nhermes config set privacy.redact_pii true    # enable\nhermes config set privacy.redact_pii false   # disable (default)\n```\n\n### Command approval prompts\n\nBy default (`approvals.mode: manual`), Hermes prompts the user before running shell commands flagged as destructive (`rm -rf`, `git reset --hard`, etc.). The modes are:\n\n- `manual` — always prompt (default)\n- `smart` — use an auxiliary LLM to auto-approve low-risk commands, prompt on high-risk\n- `off` — skip all approval prompts (equivalent to `--yolo`)\n\n```bash\nhermes config set approvals.mode smart       # recommended middle ground\nhermes config set approvals.mode off         # bypass everything (not recommended)\n```\n\nPer-invocation bypass without changing config:\n- `hermes --yolo …`\n- `export HERMES_YOLO_MODE=1`\n\nNote: YOLO \u002F `approvals.mode: off` does NOT turn off secret redaction. They are independent.\n\n### Shell hooks allowlist\n\nSome shell-hook integrations require explicit allowlisting before they fire. Managed via `~\u002F.hermes\u002Fshell-hooks-allowlist.json` — prompted interactively the first time a hook wants to run.\n\n### Disabling the web\u002Fbrowser\u002Fimage-gen tools\n\nTo keep the model away from network or media tools entirely, open `hermes tools` and toggle per-platform. Takes effect on next session (`\u002Freset`). See the Tools & Skills section above.\n\n---\n\n## Voice & Transcription\n\n### STT (Voice → Text)\n\nVoice messages from messaging platforms are auto-transcribed.\n\nProvider priority (auto-detected):\n1. **Local faster-whisper** — free, no API key: `pip install faster-whisper`\n2. **Groq Whisper** — free tier: set `GROQ_API_KEY`\n3. **OpenAI Whisper** — paid: set `VOICE_TOOLS_OPENAI_KEY`\n4. **Mistral Voxtral** — set `MISTRAL_API_KEY`\n\nConfig:\n```yaml\nstt:\n  enabled: true\n  provider: local        # local, groq, openai, mistral\n  local:\n    model: base          # tiny, base, small, medium, large-v3\n```\n\n### TTS (Text → Voice)\n\n| Provider | Env var | Free? |\n|----------|---------|-------|\n| Edge TTS | None | Yes (default) |\n| ElevenLabs | `ELEVENLABS_API_KEY` | Free tier |\n| OpenAI | `VOICE_TOOLS_OPENAI_KEY` | Paid |\n| MiniMax | `MINIMAX_API_KEY` | Paid |\n| Mistral (Voxtral) | `MISTRAL_API_KEY` | Paid |\n| NeuTTS (local) | None (`pip install neutts[all]` + `espeak-ng`) | Free |\n\nVoice commands: `\u002Fvoice on` (voice-to-voice), `\u002Fvoice tts` (always voice), `\u002Fvoice off`.\n\n---\n\n## Spawning Additional Hermes Instances\n\nRun additional Hermes processes as fully independent subprocesses — separate sessions, tools, and environments.\n\n### When to Use This vs delegate_task\n\n| | `delegate_task` | Spawning `hermes` process |\n|-|-----------------|--------------------------|\n| Isolation | Separate conversation, shared process | Fully independent process |\n| Duration | Minutes (bounded by parent loop) | Hours\u002Fdays |\n| Tool access | Subset of parent's tools | Full tool access |\n| Interactive | No | Yes (PTY mode) |\n| Use case | Quick parallel subtasks | Long autonomous missions |\n\n### One-Shot Mode\n\n```\nterminal(command=\"hermes chat -q 'Research GRPO papers and write summary to ~\u002Fresearch\u002Fgrpo.md'\", timeout=300)\n\n# Background for long tasks:\nterminal(command=\"hermes chat -q 'Set up CI\u002FCD for ~\u002Fmyapp'\", background=true)\n```\n\n### Interactive PTY Mode (via tmux)\n\nHermes uses prompt_toolkit, which requires a real terminal. Use tmux for interactive spawning:\n\n```\n# Start\nterminal(command=\"tmux new-session -d -s agent1 -x 120 -y 40 'hermes'\", timeout=10)\n\n# Wait for startup, then send a message\nterminal(command=\"sleep 8 && tmux send-keys -t agent1 'Build a FastAPI auth service' Enter\", timeout=15)\n\n# Read output\nterminal(command=\"sleep 20 && tmux capture-pane -t agent1 -p\", timeout=5)\n\n# Send follow-up\nterminal(command=\"tmux send-keys -t agent1 'Add rate limiting middleware' Enter\", timeout=5)\n\n# Exit\nterminal(command=\"tmux send-keys -t agent1 '\u002Fexit' Enter && sleep 2 && tmux kill-session -t agent1\", timeout=10)\n```\n\n### Multi-Agent Coordination\n\n```\n# Agent A: backend\nterminal(command=\"tmux new-session -d -s backend -x 120 -y 40 'hermes -w'\", timeout=10)\nterminal(command=\"sleep 8 && tmux send-keys -t backend 'Build REST API for user management' Enter\", timeout=15)\n\n# Agent B: frontend\nterminal(command=\"tmux new-session -d -s frontend -x 120 -y 40 'hermes -w'\", timeout=10)\nterminal(command=\"sleep 8 && tmux send-keys -t frontend 'Build React dashboard for user management' Enter\", timeout=15)\n\n# Check progress, relay context between them\nterminal(command=\"tmux capture-pane -t backend -p | tail -30\", timeout=5)\nterminal(command=\"tmux send-keys -t frontend 'Here is the API schema from the backend agent: ...' Enter\", timeout=5)\n```\n\n### Session Resume\n\n```\n# Resume most recent session\nterminal(command=\"tmux new-session -d -s resumed 'hermes --continue'\", timeout=10)\n\n# Resume specific session\nterminal(command=\"tmux new-session -d -s resumed 'hermes --resume 20260225_143052_a1b2c3'\", timeout=10)\n```\n\n### Tips\n\n- **Prefer `delegate_task` for quick subtasks** — less overhead than spawning a full process\n- **Use `-w` (worktree mode)** when spawning agents that edit code — prevents git conflicts\n- **Set timeouts** for one-shot mode — complex tasks can take 5-10 minutes\n- **Use `hermes chat -q` for fire-and-forget** — no PTY needed\n- **Use tmux for interactive sessions** — raw PTY mode has `\\r` vs `\\n` issues with prompt_toolkit\n- **For scheduled tasks**, use the `cronjob` tool instead of spawning — handles delivery and retry\n\n---\n\n## Durable & Background Systems\n\nFour systems run alongside the main conversation loop. Quick reference\nhere; full developer notes live in `AGENTS.md`, user-facing docs under\n`website\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002F`.\n\n### Delegation (`delegate_task`)\n\nSynchronous subagent spawn — the parent waits for the child's summary\nbefore continuing its own loop. Isolated context + terminal session.\n\n- **Single:** `delegate_task(goal, context, toolsets)`.\n- **Batch:** `delegate_task(tasks=[{goal, ...}, ...])` runs children in\n  parallel, capped by `delegation.max_concurrent_children` (default 3).\n- **Roles:** `leaf` (default; cannot re-delegate) vs `orchestrator`\n  (can spawn its own workers, bounded by `delegation.max_spawn_depth`).\n- **Not durable.** If the parent is interrupted, the child is\n  cancelled. For work that must outlive the turn, use `cronjob` or\n  `terminal(background=True, notify_on_complete=True)`.\n\nConfig: `delegation.*` in `config.yaml`.\n\n### Cron (scheduled jobs)\n\nDurable scheduler — `cron\u002Fjobs.py` + `cron\u002Fscheduler.py`. Drive it via\nthe `cronjob` tool, the `hermes cron` CLI (`list`, `add`, `edit`,\n`pause`, `resume`, `run`, `remove`), or the `\u002Fcron` slash command.\n\n- **Schedules:** duration (`\"30m\"`, `\"2h\"`), \"every\" phrase\n  (`\"every monday 9am\"`), 5-field cron (`\"0 9 * * *\"`), or ISO timestamp.\n- **Per-job knobs:** `skills`, `model`\u002F`provider` override, `script`\n  (pre-run data collection; `no_agent=True` makes the script the whole\n  job), `context_from` (chain job A's output into job B), `workdir`\n  (run in a specific dir with its `AGENTS.md` \u002F `CLAUDE.md` loaded),\n  multi-platform delivery.\n- **Invariants:** 3-minute hard interrupt per run, `.tick.lock` file\n  prevents duplicate ticks across processes, cron sessions pass\n  `skip_memory=True` by default, and cron deliveries are framed with a\n  header\u002Ffooter instead of being mirrored into the target gateway\n  session (keeps role alternation intact).\n\nUser docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fcron\n\n### Curator (skill lifecycle)\n\nBackground maintenance for agent-created skills. Tracks usage, marks\nidle skills stale, archives stale ones, keeps a pre-run tar.gz backup\nso nothing is lost.\n\n- **CLI:** `hermes curator \u003Cverb>` — `status`, `run`, `pause`, `resume`,\n  `pin`, `unpin`, `archive`, `restore`, `prune`, `backup`, `rollback`.\n- **Slash:** `\u002Fcurator \u003Csubcommand>` mirrors the CLI.\n- **Scope:** only touches skills with `created_by: \"agent\"` provenance.\n  Bundled + hub-installed skills are off-limits. **Never deletes** —\n  max destructive action is archive. Pinned skills are exempt from\n  every auto-transition and every LLM review pass.\n- **Telemetry:** sidecar at `~\u002F.hermes\u002Fskills\u002F.usage.json` holds\n  per-skill `use_count`, `view_count`, `patch_count`,\n  `last_activity_at`, `state`, `pinned`.\n\nConfig: `curator.*` (`enabled`, `interval_hours`, `min_idle_hours`,\n`stale_after_days`, `archive_after_days`, `backup.*`).\nUser docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fcurator\n\n### Kanban (multi-agent work queue)\n\nDurable SQLite board for multi-profile \u002F multi-worker collaboration.\nUsers drive it via `hermes kanban \u003Cverb>`; dispatcher-spawned workers\nsee a focused `kanban_*` toolset gated by `HERMES_KANBAN_TASK`, and\norchestrator profiles can opt into the broader `kanban` toolset. Normal\nsessions still have zero `kanban_*` schema footprint unless configured.\n\n- **CLI verbs (common):** `init`, `create`, `list` (alias `ls`),\n  `show`, `assign`, `link`, `unlink`, `comment`, `complete`, `block`,\n  `unblock`, `archive`, `tail`. Less common: `watch`, `stats`, `runs`,\n  `log`, `dispatch`, `daemon`, `gc`.\n- **Worker\u002Forchestrator toolset:** `kanban_show`, `kanban_complete`,\n  `kanban_block`, `kanban_heartbeat`, `kanban_comment`, `kanban_create`,\n  `kanban_link`; profiles that explicitly enable the `kanban` toolset\n  outside a dispatcher-spawned task also get `kanban_list` and\n  `kanban_unblock` for board routing.\n- **Dispatcher** runs inside the gateway by default\n  (`kanban.dispatch_in_gateway: true`) — reclaims stale claims,\n  promotes ready tasks, atomically claims, spawns assigned profiles.\n  Auto-blocks a task after `failure_limit` consecutive spawn failures\n  (default 2; configurable via `kanban.failure_limit` or per-task\n  `max_retries`).\n- **Isolation:** board is the hard boundary (workers get\n  `HERMES_KANBAN_BOARD` pinned in env); tenant is a soft namespace\n  within a board for workspace-path + memory-key isolation.\n\nUser docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fkanban\n\n---\n\n## Windows-Specific Quirks\n\nHermes runs natively on Windows (PowerShell, cmd, Windows Terminal, git-bash\nmintty, VS Code integrated terminal). Most of it just works, but a handful\nof differences between Win32 and POSIX have bitten us — document new ones\nhere as you hit them so the next person (or the next session) doesn't\nrediscover them from scratch.\n\n### Input \u002F Keybindings\n\n**Alt+Enter doesn't insert a newline.** Windows Terminal intercepts Alt+Enter\nat the terminal layer to toggle fullscreen — the keystroke never reaches\nprompt_toolkit. Use **Ctrl+Enter** instead. Windows Terminal delivers\nCtrl+Enter as LF (`c-j`), distinct from plain Enter (`c-m` \u002F CR), and the\nCLI binds `c-j` to newline insertion on `win32` only (see\n`_bind_prompt_submit_keys` + the Windows-only `c-j` binding in `cli.py`).\nSide effect: the raw Ctrl+J keystroke also inserts a newline on Windows —\nunavoidable, because Windows Terminal collapses Ctrl+Enter and Ctrl+J to\nthe same keycode at the Win32 console API layer. No conflicting binding\nexisted for Ctrl+J on Windows, so this is a harmless side effect.\n\nmintty \u002F git-bash behaves the same (fullscreen on Alt+Enter) unless you\ndisable Alt+Fn shortcuts in Options → Keys. Easier to just use Ctrl+Enter.\n\n**Diagnosing keybindings.** Run `python scripts\u002Fkeystroke_diagnostic.py`\n(repo root) to see exactly how prompt_toolkit identifies each keystroke\nin the current terminal. Answers questions like \"does Shift+Enter come\nthrough as a distinct key?\" (almost never — most terminals collapse it\nto plain Enter) or \"what byte sequence is my terminal sending for\nCtrl+Enter?\" This is how the Ctrl+Enter = c-j fact was established.\n\n### Config \u002F Files\n\n**HTTP 400 \"No models provided\" on first run.** `config.yaml` was saved\nwith a UTF-8 BOM (common when Windows apps write it). Re-save as UTF-8\nwithout BOM. `hermes config edit` writes without BOM; manual edits in\nNotepad are the usual culprit.\n\n### `execute_code` \u002F Sandbox\n\n**WinError 10106** (\"The requested service provider could not be loaded\nor initialized\") from the sandbox child process — it can't create an\n`AF_INET` socket, so the loopback-TCP RPC fallback fails before\n`connect()`. Root cause is usually **not** a broken Winsock LSP; it's\nHermes's own env scrubber dropping `SYSTEMROOT` \u002F `WINDIR` \u002F `COMSPEC`\nfrom the child env. Python's `socket` module needs `SYSTEMROOT` to locate\n`mswsock.dll`. Fixed via the `_WINDOWS_ESSENTIAL_ENV_VARS` allowlist in\n`tools\u002Fcode_execution_tool.py`. If you still hit it, echo `os.environ`\ninside an `execute_code` block to confirm `SYSTEMROOT` is set. Full\ndiagnostic recipe in `references\u002Fexecute-code-sandbox-env-windows.md`.\n\n### Testing \u002F Contributing\n\n**`scripts\u002Frun_tests.sh` doesn't work as-is on Windows** — it looks for\nPOSIX venv layouts (`.venv\u002Fbin\u002Factivate`). The Hermes-installed venv at\n`venv\u002FScripts\u002F` has no pip or pytest either (stripped for install size).\nWorkaround: install `pytest + pytest-xdist + pyyaml` into a system Python\n3.11 user site, then invoke pytest directly with `PYTHONPATH` set:\n\n```bash\n\"\u002Fc\u002FProgram Files\u002FPython311\u002Fpython\" -m pip install --user pytest pytest-xdist pyyaml\nexport PYTHONPATH=\"$(pwd)\"\n\"\u002Fc\u002FProgram Files\u002FPython311\u002Fpython\" -m pytest tests\u002Ffoo\u002Ftest_bar.py -v --tb=short -n 0\n```\n\nUse `-n 0`, not `-n 4` — `pyproject.toml`'s default `addopts` already\nincludes `-n`, and the wrapper's CI-parity guarantees don't apply off POSIX.\n\n**POSIX-only tests need skip guards.** Common markers already in the codebase:\n- Symlinks — elevated privileges on Windows\n- `0o600` file modes — POSIX mode bits not enforced on NTFS by default\n- `signal.SIGALRM` — Unix-only (see `tests\u002Fconftest.py::_enforce_test_timeout`)\n- Winsock \u002F Windows-specific regressions — `@pytest.mark.skipif(sys.platform != \"win32\", ...)`\n\nUse the existing skip-pattern style (`sys.platform == \"win32\"` or\n`sys.platform.startswith(\"win\")`) to stay consistent with the rest of the\nsuite.\n\n### Path \u002F Filesystem\n\n**Line endings.** Git may warn `LF will be replaced by CRLF the next time\nGit touches it`. Cosmetic — the repo's `.gitattributes` normalizes. Don't\nlet editors auto-convert committed POSIX-newline files to CRLF.\n\n**Forward slashes work almost everywhere.** `C:\u002FUsers\u002F...` is accepted by\nevery Hermes tool and most Windows APIs. Prefer forward slashes in code\nand logs — avoids shell-escaping backslashes in bash.\n\n---\n\n## Troubleshooting\n\n### Voice not working\n1. Check `stt.enabled: true` in config.yaml\n2. Verify provider: `pip install faster-whisper` or set API key\n3. In gateway: `\u002Frestart`. In CLI: exit and relaunch.\n\n### Tool not available\n1. `hermes tools` — check if toolset is enabled for your platform\n2. Some tools need env vars (check `.env`)\n3. `\u002Freset` after enabling tools\n\n### Model\u002Fprovider issues\n1. `hermes doctor` — check config and dependencies\n2. `hermes auth` — re-authenticate OAuth providers (or `hermes auth add \u003Cprovider>`)\n3. Check `.env` has the right API key\n4. **Copilot 403**: `gh auth login` tokens do NOT work for Copilot API. You must use the Copilot-specific OAuth device code flow via `hermes model` → GitHub Copilot.\n\n### Changes not taking effect\n- **Tools\u002Fskills:** `\u002Freset` starts a new session with updated toolset\n- **Config changes:** In gateway: `\u002Frestart`. In CLI: exit and relaunch.\n- **Code changes:** Restart the CLI or gateway process\n\n### Skills not showing\n1. `hermes skills list` — verify installed\n2. `hermes skills config` — check platform enablement\n3. Load explicitly: `\u002Fskill name` or `hermes -s name`\n\n### Gateway issues\nCheck logs first:\n```bash\ngrep -i \"failed to send\\|error\" ~\u002F.hermes\u002Flogs\u002Fgateway.log | tail -20\n```\n\nCommon gateway problems:\n- **Gateway dies on SSH logout**: Enable linger: `sudo loginctl enable-linger $USER`\n- **Gateway dies on WSL2 close**: WSL2 requires `systemd=true` in `\u002Fetc\u002Fwsl.conf` for systemd services to work. Without it, gateway falls back to `nohup` (dies when session closes).\n- **Gateway crash loop**: Reset the failed state: `systemctl --user reset-failed hermes-gateway`\n\n### Platform-specific issues\n- **Discord bot silent**: Must enable **Message Content Intent** in Bot → Privileged Gateway Intents.\n- **Slack bot only works in DMs**: Must subscribe to `message.channels` event. Without it, the bot ignores public channels.\n- **Windows-specific issues** (`Alt+Enter` newline, WinError 10106, UTF-8 BOM config, test suite, line endings): see the dedicated **Windows-Specific Quirks** section above.\n\n### Auxiliary models not working\nIf `auxiliary` tasks (vision, compression, session_search) fail silently, the `auto` provider can't find a backend. Either set `OPENROUTER_API_KEY` or `GOOGLE_API_KEY`, or explicitly configure each auxiliary task's provider:\n```bash\nhermes config set auxiliary.vision.provider \u003Cyour_provider>\nhermes config set auxiliary.vision.model \u003Cmodel_name>\n```\n\n---\n\n---\n\n## Hermes Skill Authoring\n\n### In-Repo vs User-Local Skills\n- **User-local:** `~\u002F.hermes\u002Fskills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` — created via `skill_manage(action='create')`\n- **In-repo:** `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` — committed, shipped with the package. Use `write_file` + `git add`\n\n### Required Frontmatter\n```yaml\n---\nname: my-skill-name               # lowercase, hyphens, ≤64 chars\ndescription: Use when \u003Ctrigger>. \u003Cone-line behavior>.   # ≤1024 chars\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [short, descriptive, tags]\n    related_skills: [other-skill]\n---\n```\n\n### Size Limits\n- Description ≤ 1024 chars (enforced)\n- Full SKILL.md ≤ 100,000 chars (≈36k tokens)\n- Peer skills sit at 8–14k chars. Aim for that range.\n\n### Workflow\n1. Survey peers in the target category (`ls skills\u002F\u003Ccategory>\u002F`)\n2. Draft with `write_file` to `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md`\n3. Validate locally (YAML frontmatter, size limits)\n4. `git add && git commit`\n\n### Common Pitfalls\n- `skill_manage(action='create')` writes to `~\u002F.hermes\u002Fskills\u002F`, NOT the repo tree — use `write_file` for in-repo\n- Leading whitespace before `---` fails validation\n- Current session won't see the new skill until `\u002Freset`\n\n---\n\n## Hermes s6-overlay Container Supervision\n\n### When to Use\n- Adding\u002Fremoving static services in the Hermes Docker image\n- Diagnosing why a per-profile gateway isn't starting or surviving restart\n- Modifying `cont-init.d` boot scripts or per-profile gateway run-scripts\n\n### Architecture at a Glance\n```\n\u002Finit (s6-overlay v3)\n├── cont-init.d\n│   ├── 01-hermes-setup      ← docker\u002Fstage2-hook.sh\n│   └── 02-reconcile-profiles ← container_boot.py\n├── s6-rc.d (static services)\n│   ├── main-hermes\u002Frun      ← exec sleep infinity (no-op slot)\n│   └── dashboard\u002Frun        ← conditional\n└── \u002Frun\u002Fservice (per-profile gateways, tmpfs)\n    └── gateway-\u003Cname>\u002F\n        ├── run  ← s6-setuidgid hermes hermes -p \u003Cname> gateway run\n        └── log\u002Frun\n```\n\n### Why Architecture B (CMD as main program)\n1. `cont-init.d` scripts receive no CMD args\n2. s6 halt always exits 143 regardless of written exitcode\n\nSo main hermes runs as the CMD (`\u002Fopt\u002Fhermes\u002Fdocker\u002Fmain-wrapper.sh`), not as a supervised service. Per-profile gateways under `\u002Frun\u002Fservice\u002F` get full supervision.\n\n### Quick Recipes\n```bash\ndocker exec \u003Cc> \u002Fcommand\u002Fs6-svstat \u002Frun\u002Fservice\u002Fgateway-\u003Cname>   # Inspect\ndocker exec \u003Cc> \u002Fcommand\u002Fs6-svc -u \u002Frun\u002Fservice\u002Fgateway-\u003Cname>   # Up\ndocker exec \u003Cc> \u002Fcommand\u002Fs6-svc -d \u002Frun\u002Fservice\u002Fgateway-\u003Cname>   # Down\ndocker exec \u003Cc> tail -n 50 \u002Fopt\u002Fdata\u002Flogs\u002Fcontainer-boot.log     # Reconciler log\n```\n\n### Pitfalls\n- `docker exec` defaults to root; files under `$HERMES_HOME\u002Fprofiles\u002F` should be hermes-owned\n- Service slot on tmpfs → wiped on container restart; reconciler recreates it\n- Gateway starts then exits → profile likely unconfigured; fix config, supervisor will retry\n\n---\n\n## Debugging Hermes TUI Slash Commands\n\n### Architecture\n```\nPython backend (hermes_cli\u002Fcommands.py)     ← canonical COMMAND_REGISTRY\n       ↓\nTUI gateway (tui_gateway\u002Fserver.py)         ← slash.exec \u002F command.dispatch\n       ↓\nTUI frontend (ui-tui\u002Fsrc\u002Fapp\u002Fslash\u002F)        ← local handlers + fallthrough\n```\n\n### Fix: Missing Command Autocomplete\n1. Add `CommandDef` to `COMMAND_REGISTRY` in `hermes_cli\u002Fcommands.py`\n2. Ensure `subcommands` tuple matches TUI expectations\n3. Add handler in `cli.py::process_command()` for CLI-only\n4. Add handler in `gateway\u002Frun.py` for gateway-available\n\n### Common Issues\n1. **Shows in TUI but not autocomplete** → missing from `COMMAND_REGISTRY`\n2. **Shows in autocomplete but doesn't work** → missing frontend or gateway handler\n3. **Behavior differs between CLI and TUI** → divergent implementations\n4. **Config persists but UI doesn't update** → patch nanostore state immediately (`patchUiState`)\n\n### Debugging Tactics\n- Python side hangs → use `python-debugpy` to break inside `_SlashWorker.exec`\n- Ink side not reacting → use `node-inspect-debugger` to break in `app.tsx`\n- Registry mismatch → compare `COMMAND_REGISTRY` against TUI local command list\n\n### Verification\n1. Rebuild TUI: `npm --prefix ui-tui run build`\n2. Test autocomplete with `\u002F`\n3. Confirm behavior, persisted config, and live UI state\n\n\n| Looking for... | Location |\n|----------------|----------|\n| Config options | `hermes config edit` or [Configuration docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fconfiguration) |\n| Available tools | `hermes tools list` or [Tools reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Ftools-reference) |\n| Slash commands | `\u002Fhelp` in session or [Slash commands reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fslash-commands) |\n| Skills catalog | `hermes skills browse` or [Skills catalog](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fskills-catalog) |\n| Provider setup | `hermes model` or [Providers guide](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fintegrations\u002Fproviders) |\n| Platform setup | `hermes gateway setup` or [Messaging docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002F) |\n| MCP servers | `hermes mcp list` or [MCP guide](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fmcp) |\n| Profiles | `hermes profile list` or [Profiles docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fprofiles) |\n| Cron jobs | `hermes cron list` or [Cron docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fcron) |\n| Memory | `hermes memory status` or [Memory docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fmemory) |\n| Env variables | `hermes config env-path` or [Env vars reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fenvironment-variables) |\n| CLI commands | `hermes --help` or [CLI reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fcli-commands) |\n| Gateway logs | `~\u002F.hermes\u002Flogs\u002Fgateway.log` |\n| Session files | `hermes sessions browse` (reads state.db) |\n| Source code | `~\u002F.hermes\u002Fhermes-agent\u002F` |\n\n---\n\n## Contributor Quick Reference\n\nFor occasional contributors and PR authors. Full developer docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fdeveloper-guide\u002F\n\n### Project Layout\n\n```\nhermes-agent\u002F\n├── run_agent.py          # AIAgent — core conversation loop\n├── model_tools.py        # Tool discovery and dispatch\n├── toolsets.py           # Toolset definitions\n├── cli.py                # Interactive CLI (HermesCLI)\n├── hermes_state.py       # SQLite session store\n├── agent\u002F                # Prompt builder, context compression, memory, model routing, credential pooling, skill dispatch\n├── hermes_cli\u002F           # CLI subcommands, config, setup, commands\n│   ├── commands.py       # Slash command registry (CommandDef)\n│   ├── config.py         # DEFAULT_CONFIG, env var definitions\n│   └── main.py           # CLI entry point and argparse\n├── tools\u002F                # One file per tool\n│   └── registry.py       # Central tool registry\n├── gateway\u002F              # Messaging gateway\n│   └── platforms\u002F        # Platform adapters (telegram, discord, etc.)\n├── cron\u002F                 # Job scheduler\n├── tests\u002F                # ~3000 pytest tests\n└── website\u002F              # Docusaurus docs site\n```\n\nConfig: `~\u002F.hermes\u002Fconfig.yaml` (settings), `~\u002F.hermes\u002F.env` (API keys).\n\n### Adding a Tool (3 files)\n\n**1. Create `tools\u002Fyour_tool.py`:**\n```python\nimport json, os\nfrom tools.registry import registry\n\ndef check_requirements() -> bool:\n    return bool(os.getenv(\"EXAMPLE_API_KEY\"))\n\ndef example_tool(param: str, task_id: str = None) -> str:\n    return json.dumps({\"success\": True, \"data\": \"...\"})\n\nregistry.register(\n    name=\"example_tool\",\n    toolset=\"example\",\n    schema={\"name\": \"example_tool\", \"description\": \"...\", \"parameters\": {...}},\n    handler=lambda args, **kw: example_tool(\n        param=args.get(\"param\", \"\"), task_id=kw.get(\"task_id\")),\n    check_fn=check_requirements,\n    requires_env=[\"EXAMPLE_API_KEY\"],\n)\n```\n\n**2. Add to `toolsets.py`** → `_HERMES_CORE_TOOLS` list.\n\nAuto-discovery: any `tools\u002F*.py` file with a top-level `registry.register()` call is imported automatically — no manual list needed.\n\nAll handlers must return JSON strings. Use `get_hermes_home()` for paths, never hardcode `~\u002F.hermes`.\n\n### Adding a Slash Command\n\n1. Add `CommandDef` to `COMMAND_REGISTRY` in `hermes_cli\u002Fcommands.py`\n2. Add handler in `cli.py` → `process_command()`\n3. (Optional) Add gateway handler in `gateway\u002Frun.py`\n\nAll consumers (help text, autocomplete, Telegram menu, Slack mapping) derive from the central registry automatically.\n\n### Agent Loop (High Level)\n\n```\nrun_conversation():\n  1. Build system prompt\n  2. Loop while iterations \u003C max:\n     a. Call LLM (OpenAI-format messages + tool schemas)\n     b. If tool_calls → dispatch each via handle_function_call() → append results → continue\n     c. If text response → return\n  3. Context compression triggers automatically near token limit\n```\n\n### Testing\n\n```bash\npython -m pytest tests\u002F -o 'addopts=' -q   # Full suite\npython -m pytest tests\u002Ftools\u002F -q            # Specific area\n```\n\n- Tests auto-redirect `HERMES_HOME` to temp dirs — never touch real `~\u002F.hermes\u002F`\n- Run full suite before pushing any change\n- Use `-o 'addopts='` to clear any baked-in pytest flags\n\n**Windows contributors:** `scripts\u002Frun_tests.sh` currently looks for POSIX venvs (`.venv\u002Fbin\u002Factivate` \u002F `venv\u002Fbin\u002Factivate`) and will error out on Windows where the layout is `venv\u002FScripts\u002Factivate` + `python.exe`. The Hermes-installed venv at `venv\u002FScripts\u002F` also has no `pip` or `pytest` — it's stripped for end-user install size. Workaround: install pytest + pytest-xdist + pyyaml into a system Python 3.11 user site (`\u002Fc\u002FProgram Files\u002FPython311\u002Fpython -m pip install --user pytest pytest-xdist pyyaml`), then run tests directly:\n\n```bash\nexport PYTHONPATH=\"$(pwd)\"\n\"\u002Fc\u002FProgram Files\u002FPython311\u002Fpython\" -m pytest tests\u002Ftools\u002Ftest_foo.py -v --tb=short -n 0\n```\n\nUse `-n 0` (not `-n 4`) because `pyproject.toml`'s default `addopts` already includes `-n`, and the wrapper's CI-parity story doesn't apply off-POSIX.\n\n**Cross-platform test guards:** tests that use POSIX-only syscalls need a skip marker. Common ones already in the codebase:\n- Symlink creation → `@pytest.mark.skipif(sys.platform == \"win32\", reason=\"Symlinks require elevated privileges on Windows\")` (see `tests\u002Fcron\u002Ftest_cron_script.py`)\n- POSIX file modes (0o600, etc.) → `@pytest.mark.skipif(sys.platform.startswith(\"win\"), reason=\"POSIX mode bits not enforced on Windows\")` (see `tests\u002Fhermes_cli\u002Ftest_auth_toctou_file_modes.py`)\n- `signal.SIGALRM` → Unix-only (see `tests\u002Fconftest.py::_enforce_test_timeout`)\n- Live Winsock \u002F Windows-specific regression tests → `@pytest.mark.skipif(sys.platform != \"win32\", reason=\"Windows-specific regression\")`\n\n**Monkeypatching `sys.platform` is not enough** when the code under test also calls `platform.system()` \u002F `platform.release()` \u002F `platform.mac_ver()`. Those functions re-read the real OS independently, so a test that sets `sys.platform = \"linux\"` on a Windows runner will still see `platform.system() == \"Windows\"` and route through the Windows branch. Patch all three together:\n\n```python\nmonkeypatch.setattr(sys, \"platform\", \"linux\")\nmonkeypatch.setattr(platform, \"system\", lambda: \"Linux\")\nmonkeypatch.setattr(platform, \"release\", lambda: \"6.8.0-generic\")\n```\n\nSee `tests\u002Fagent\u002Ftest_prompt_builder.py::TestEnvironmentHints` for a worked example.\n\n### Extending the system prompt's execution-environment block\n\nFactual guidance about the host OS, user home, cwd, terminal backend, and shell (bash vs. PowerShell on Windows) is emitted from `agent\u002Fprompt_builder.py::build_environment_hints()`. This is also where the WSL hint and per-backend probe logic live. The convention:\n\n- **Local terminal backend** → emit host info (OS, `$HOME`, cwd) + Windows-specific notes (hostname ≠ username, `terminal` uses bash not PowerShell).\n- **Remote terminal backend** (anything in `_REMOTE_TERMINAL_BACKENDS`: `docker, singularity, modal, daytona, ssh, managed_modal`) → **suppress** host info entirely and describe only the backend. A live `uname`\u002F`whoami`\u002F`pwd` probe runs inside the backend via `tools.environments.get_environment(...).execute(...)`, cached per process in `_BACKEND_PROBE_CACHE`, with a static fallback if the probe times out.\n- **Key fact for prompt authoring:** when `TERMINAL_ENV != \"local\"`, *every* file tool (`read_file`, `write_file`, `patch`, `search_files`) runs inside the backend container, not on the host. The system prompt must never describe the host in that case — the agent can't touch it.\n\nFull design notes, the exact emitted strings, and testing pitfalls:\n`references\u002Fprompt-builder-environment-hints.md`.\n\n**Refactor-safety pattern (POSIX-equivalence guard):** when you extract inline logic into a helper that adds Windows\u002Fplatform-specific behavior, keep a `_legacy_\u003Cname>` oracle function in the test file that's a verbatim copy of the old code, then parametrize-diff against it. Example: `tests\u002Ftools\u002Ftest_code_execution_windows_env.py::TestPosixEquivalence`. This locks in the invariant that POSIX behavior is bit-for-bit identical and makes any future drift fail loudly with a clear diff.\n\n### Commit Conventions\n\n```\ntype: concise subject line\n\nOptional body.\n```\n\nTypes: `fix:`, `feat:`, `refactor:`, `docs:`, `chore:`\n\n### Key Rules\n\n- **Never break prompt caching** — don't change context, tools, or system prompt mid-conversation\n- **Message role alternation** — never two assistant or two user messages in a row\n- Use `get_hermes_home()` from `hermes_constants` for all paths (profile-safe)\n- Config values go in `config.yaml`, secrets go in `.env`\n- New tools need a `check_fn` so they only appear when requirements are met\n","# Hermes Agent\n\nHermes Agent is an open-source AI agent framework by Nous Research that runs in your terminal, messaging platforms, and IDEs. It belongs to the same category as Claude Code (Anthropic), Codex (OpenAI), and OpenClaw — autonomous coding and task-execution agents that use tool calling to interact with your system. Hermes works with any LLM provider (OpenRouter, Anthropic, OpenAI, DeepSeek, local models, and 15+ others) and runs on Linux, macOS, and WSL.\n\nWhat makes Hermes different:\n\n- **Self-improving through skills** — Hermes learns from experience by saving reusable procedures as skills. When it solves a complex problem, discovers a workflow, or gets corrected, it can persist that knowledge as a skill document that loads into future sessions. Skills accumulate over time, making the agent better at your specific tasks and environment.\n- **Persistent memory across sessions** — remembers who you are, your preferences, environment details, and lessons learned. Pluggable memory backends (built-in, Honcho, Mem0, and more) let you choose how memory works.\n- **Multi-platform gateway** — the same agent runs on Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Email, and 10+ other platforms with full tool access, not just chat.\n- **Provider-agnostic** — swap models and providers mid-workflow without changing anything else. Credential pools rotate across multiple API keys automatically.\n- **Profiles** — run multiple independent Hermes instances with isolated configs, sessions, skills, and memory.\n- **Extensible** — plugins, MCP servers, custom tools, webhook triggers, cron scheduling, and the full Python ecosystem.\n\nPeople use Hermes for software development, research, system administration, data analysis, content creation, home automation, and anything else that benefits from an AI agent with persistent context and full system access.\n\n**This skill helps you work with Hermes Agent effectively** — setting it up, configuring features, spawning additional agent instances, troubleshooting issues, finding the right commands and settings, and understanding how the system works when you need to extend or contribute to it.\n\n**Docs:** https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002F\n\n## Quick Start\n\n```bash\n# Install\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002FNousResearch\u002Fhermes-agent\u002Fmain\u002Fscripts\u002Finstall.sh | bash\n\n# Interactive chat (default)\nhermes\n\n# Single query\nhermes chat -q \"What is the capital of France?\"\n\n# Setup wizard\nhermes setup\n\n# Change model\u002Fprovider\nhermes model\n\n# Check health\nhermes doctor\n```\n\n---\n\n## CLI Reference\n\n### Global Flags\n\n```\nhermes [flags] [command]\n\n  --version, -V             Show version\n  --resume, -r SESSION      Resume session by ID or title\n  --continue, -c [NAME]     Resume by name, or most recent session\n  --worktree, -w            Isolated git worktree mode (parallel agents)\n  --skills, -s SKILL        Preload skills (comma-separate or repeat)\n  --profile, -p NAME        Use a named profile\n  --yolo                    Skip dangerous command approval\n  --pass-session-id         Include session ID in system prompt\n```\n\nNo subcommand defaults to `chat`.\n\n### Chat\n\n```\nhermes chat [flags]\n  -q, --query TEXT          Single query, non-interactive\n  -m, --model MODEL         Model (e.g. anthropic\u002Fclaude-sonnet-4)\n  -t, --toolsets LIST       Comma-separated toolsets\n  --provider PROVIDER       Force provider (openrouter, anthropic, nous, etc.)\n  -v, --verbose             Verbose output\n  -Q, --quiet               Suppress banner, spinner, tool previews\n  --checkpoints             Enable filesystem checkpoints (\u002Frollback)\n  --source TAG              Session source tag (default: cli)\n```\n\n### Configuration\n\n```\nhermes setup [section]      Interactive wizard (model|terminal|gateway|tools|agent)\nhermes model                Interactive model\u002Fprovider picker\nhermes config               View current config\nhermes config edit          Open config.yaml in $EDITOR\nhermes config set KEY VAL   Set a config value\nhermes config path          Print config.yaml path\nhermes config env-path      Print .env path\nhermes config check         Check for missing\u002Foutdated config\nhermes config migrate       Update config with new options\nhermes auth                 Interactive credential manager\nhermes auth add PROVIDER    Add OAuth or API-key credential (e.g. nous, openai-codex, qwen-oauth)\nhermes auth list            List stored credentials\nhermes auth remove PROVIDER Remove a stored credential\nhermes doctor [--fix]       Check dependencies and config\nhermes status [--all]       Show component status\n```\n\n### Tools & Skills\n\n```\nhermes tools                Interactive tool enable\u002Fdisable (curses UI)\nhermes tools list           Show all tools and status\nhermes tools enable NAME    Enable a toolset\nhermes tools disable NAME   Disable a toolset\n\nhermes skills list          List installed skills\nhermes skills search QUERY  Search the skills hub\nhermes skills install ID    Install a skill (ID can be a hub identifier OR a direct https:\u002F\u002F…\u002FSKILL.md URL; pass --name to override when frontmatter has no name)\nhermes skills inspect ID    Preview without installing\nhermes skills config        Enable\u002Fdisable skills per platform\nhermes skills check         Check for updates\nhermes skills update        Update outdated skills\nhermes skills uninstall N   Remove a hub skill\nhermes skills publish PATH  Publish to registry\nhermes skills browse        Browse all available skills\nhermes skills tap add REPO  Add a GitHub repo as skill source\n```\n\n### MCP Servers\n\n```\nhermes mcp serve            Run Hermes as an MCP server\nhermes mcp add NAME         Add an MCP server (--url or --command)\nhermes mcp remove NAME      Remove an MCP server\nhermes mcp list             List configured servers\nhermes mcp test NAME        Test connection\nhermes mcp configure NAME   Toggle tool selection\n```\n\n### Gateway (Messaging Platforms)\n\n```\nhermes gateway run          Start gateway foreground\nhermes gateway install      Install as background service\nhermes gateway start\u002Fstop   Control the service\nhermes gateway restart      Restart the service\nhermes gateway status       Check status\nhermes gateway setup        Configure platforms\n```\n\nSupported platforms: Telegram, Discord, Slack, WhatsApp, Signal, Email, SMS, Matrix, Mattermost, Home Assistant, DingTalk, Feishu, WeCom, BlueBubbles (iMessage), Weixin (WeChat), API Server, Webhooks. Open WebUI connects via the API Server adapter.\n\nPlatform docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002F\n\n### Sessions\n\n```\nhermes sessions list        List recent sessions\nhermes sessions browse      Interactive picker\nhermes sessions export OUT  Export to JSONL\nhermes sessions rename ID T Rename a session\nhermes sessions delete ID   Delete a session\nhermes sessions prune       Clean up old sessions (--older-than N days)\nhermes sessions stats       Session store statistics\n```\n\n### Cron Jobs\n\n```\nhermes cron list            List jobs (--all for disabled)\nhermes cron create SCHED    Create: '30m', 'every 2h', '0 9 * * *'\nhermes cron edit ID         Edit schedule, prompt, delivery\nhermes cron pause\u002Fresume ID Control job state\nhermes cron run ID          Trigger on next tick\nhermes cron remove ID       Delete a job\nhermes cron status          Scheduler status\n```\n\n### Webhooks\n\n```\nhermes webhook subscribe N  Create route at \u002Fwebhooks\u002F\u003Cname>\nhermes webhook list         List subscriptions\nhermes webhook remove NAME  Remove a subscription\nhermes webhook test NAME    Send a test POST\n```\n\n### Profiles\n\n```\nhermes profile list         List all profiles\nhermes profile create NAME  Create (--clone, --clone-all, --clone-from)\nhermes profile use NAME     Set sticky default\nhermes profile delete NAME  Delete a profile\nhermes profile show NAME    Show details\nhermes profile alias NAME   Manage wrapper scripts\nhermes profile rename A B   Rename a profile\nhermes profile export NAME  Export to tar.gz\nhermes profile import FILE  Import from archive\n```\n\n### Credential Pools\n\n```\nhermes auth add             Interactive credential wizard\nhermes auth list [PROVIDER] List pooled credentials\nhermes auth remove P INDEX  Remove by provider + index\nhermes auth reset PROVIDER  Clear exhaustion status\n```\n\n### Other\n\n```\nhermes insights [--days N]  Usage analytics\nhermes update               Update to latest version\nhermes pairing list\u002Fapprove\u002Frevoke  DM authorization\nhermes plugins list\u002Finstall\u002Fremove  Plugin management\nhermes honcho setup\u002Fstatus  Honcho memory integration (requires honcho plugin)\nhermes memory setup\u002Fstatus\u002Foff  Memory provider config\nhermes completion bash|zsh  Shell completions\nhermes acp                  ACP server (IDE integration)\nhermes claw migrate         Migrate from OpenClaw\nhermes uninstall            Uninstall Hermes\n```\n\n---\n\n## Slash Commands (In-Session)\n\nType these during an interactive chat session. New commands land fairly\noften; if something below looks stale, run `\u002Fhelp` in-session for the\nauthoritative list or see the [live slash commands reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fslash-commands).\nThe registry of record is `hermes_cli\u002Fcommands.py` — every consumer\n(autocomplete, Telegram menu, Slack mapping, `\u002Fhelp`) derives from it.\n\n### Session Control\n```\n\u002Fnew (\u002Freset)        Fresh session\n\u002Fclear               Clear screen + new session (CLI)\n\u002Fretry               Resend last message\n\u002Fundo                Remove last exchange\n\u002Ftitle [name]        Name the session\n\u002Fcompress            Manually compress context\n\u002Fstop                Kill background processes\n\u002Frollback [N]        Restore filesystem checkpoint\n\u002Fsnapshot [sub]      Create or restore state snapshots of Hermes config\u002Fstate (CLI)\n\u002Fbackground \u003Cprompt> Run prompt in background\n\u002Fqueue \u003Cprompt>      Queue for next turn\n\u002Fsteer \u003Cprompt>      Inject a message after the next tool call without interrupting\n\u002Fagents (\u002Ftasks)     Show active agents and running tasks\n\u002Fresume [name]       Resume a named session\n\u002Fgoal [text|sub]     Set a standing goal Hermes works on across turns until achieved\n                     (subcommands: status, pause, resume, clear)\n\u002Fredraw              Force a full UI repaint (CLI)\n```\n\n### Configuration\n```\n\u002Fconfig              Show config (CLI)\n\u002Fmodel [name]        Show or change model\n\u002Fpersonality [name]  Set personality\n\u002Freasoning [level]   Set reasoning (none|minimal|low|medium|high|xhigh|show|hide)\n\u002Fverbose             Cycle: off → new → all → verbose\n\u002Fvoice [on|off|tts]  Voice mode\n\u002Fyolo                Toggle approval bypass\n\u002Fbusy [sub]          Control what Enter does while Hermes is working (CLI)\n                     (subcommands: queue, steer, interrupt, status)\n\u002Findicator [style]   Pick the TUI busy-indicator style (CLI)\n                     (styles: kaomoji, emoji, unicode, ascii)\n\u002Ffooter [on|off]     Toggle gateway runtime-metadata footer on final replies\n\u002Fskin [name]         Change theme (CLI)\n\u002Fstatusbar           Toggle status bar (CLI)\n```\n\n### Tools & Skills\n```\n\u002Ftools               Manage tools (CLI)\n\u002Ftoolsets            List toolsets (CLI)\n\u002Fskills              Search\u002Finstall skills (CLI)\n\u002Fskill \u003Cname>        Load a skill into session\n\u002Freload-skills       Re-scan ~\u002F.hermes\u002Fskills\u002F for added\u002Fremoved skills\n\u002Freload              Reload .env variables into the running session (CLI)\n\u002Freload-mcp          Reload MCP servers\n\u002Fcron                Manage cron jobs (CLI)\n\u002Fcurator [sub]       Background skill maintenance (status, run, pin, archive, …)\n\u002Fkanban [sub]        Multi-profile collaboration board (tasks, links, comments)\n\u002Fplugins             List plugins (CLI)\n```\n\n### Gateway\n```\n\u002Fapprove             Approve a pending command (gateway)\n\u002Fdeny                Deny a pending command (gateway)\n\u002Frestart             Restart gateway (gateway)\n\u002Fsethome             Set current chat as home channel (gateway)\n\u002Fupdate              Update Hermes to latest (gateway)\n\u002Ftopic [sub]         Enable or inspect Telegram DM topic sessions (gateway)\n\u002Fplatforms (\u002Fgateway) Show platform connection status (gateway)\n```\n\n### Utility\n```\n\u002Fbranch (\u002Ffork)      Branch the current session\n\u002Ffast                Toggle priority\u002Ffast processing\n\u002Fbrowser             Open CDP browser connection\n\u002Fhistory             Show conversation history (CLI)\n\u002Fsave                Save conversation to file (CLI)\n\u002Fcopy [N]            Copy the last assistant response to clipboard (CLI)\n\u002Fpaste               Attach clipboard image (CLI)\n\u002Fimage               Attach local image file (CLI)\n```\n\n### Info\n```\n\u002Fhelp                Show commands\n\u002Fcommands [page]     Browse all commands (gateway)\n\u002Fusage               Token usage\n\u002Finsights [days]     Usage analytics\n\u002Fgquota              Show Google Gemini Code Assist quota usage (CLI)\n\u002Fstatus              Session info (gateway)\n\u002Fprofile             Active profile info\n\u002Fdebug               Upload debug report (system info + logs) and get shareable links\n```\n\n### Exit\n```\n\u002Fquit (\u002Fexit, \u002Fq)    Exit CLI\n```\n\n---\n\n## Key Paths & Config\n\n```\n~\u002F.hermes\u002Fconfig.yaml       Main configuration\n~\u002F.hermes\u002F.env              API keys and secrets\n$HERMES_HOME\u002Fskills\u002F        Installed skills\n~\u002F.hermes\u002Fsessions\u002F         Gateway routing index, request dumps, *.jsonl transcripts (and optional per-session JSON snapshots when sessions.write_json_snapshots: true)\n~\u002F.hermes\u002Fstate.db          Canonical session store (SQLite + FTS5)\n~\u002F.hermes\u002Flogs\u002F             Gateway and error logs\n~\u002F.hermes\u002Fauth.json         OAuth tokens and credential pools\n~\u002F.hermes\u002Fhermes-agent\u002F     Source code (if git-installed)\n```\n\nProfiles use `~\u002F.hermes\u002Fprofiles\u002F\u003Cname>\u002F` with the same layout.\n\n### Config Sections\n\nEdit with `hermes config edit` or `hermes config set section.key value`.\n\n| Section | Key options |\n|---------|-------------|\n| `model` | `default`, `provider`, `base_url`, `api_key`, `context_length` |\n| `agent` | `max_turns` (90), `tool_use_enforcement` |\n| `terminal` | `backend` (local\u002Fdocker\u002Fssh\u002Fmodal), `cwd`, `timeout` (180) |\n| `compression` | `enabled`, `threshold` (0.50), `target_ratio` (0.20) |\n| `display` | `skin`, `tool_progress`, `show_reasoning`, `show_cost` |\n| `stt` | `enabled`, `provider` (local\u002Fgroq\u002Fopenai\u002Fmistral) |\n| `tts` | `provider` (edge\u002Felevenlabs\u002Fopenai\u002Fminimax\u002Fmistral\u002Fneutts) |\n| `memory` | `memory_enabled`, `user_profile_enabled`, `provider` |\n| `security` | `tirith_enabled`, `website_blocklist` |\n| `delegation` | `model`, `provider`, `base_url`, `api_key`, `max_iterations` (50), `reasoning_effort` |\n| `checkpoints` | `enabled`, `max_snapshots` (50) |\n\nFull config reference: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fconfiguration\n\n### Providers\n\n20+ providers supported. Set via `hermes model` or `hermes setup`.\n\n| Provider | Auth | Key env var |\n|----------|------|-------------|\n| OpenRouter | API key | `OPENROUTER_API_KEY` |\n| Anthropic | API key | `ANTHROPIC_API_KEY` |\n| Nous Portal | OAuth | `hermes auth` |\n| OpenAI Codex | OAuth | `hermes auth` |\n| GitHub Copilot | Token | `COPILOT_GITHUB_TOKEN` |\n| Google Gemini | API key | `GOOGLE_API_KEY` or `GEMINI_API_KEY` |\n| DeepSeek | API key | `DEEPSEEK_API_KEY` |\n| xAI \u002F Grok | API key | `XAI_API_KEY` |\n| Hugging Face | Token | `HF_TOKEN` |\n| Z.AI \u002F GLM | API key | `GLM_API_KEY` |\n| MiniMax | API key | `MINIMAX_API_KEY` |\n| MiniMax CN | API key | `MINIMAX_CN_API_KEY` |\n| Kimi \u002F Moonshot | API key | `KIMI_API_KEY` |\n| Alibaba \u002F DashScope | API key | `DASHSCOPE_API_KEY` |\n| Xiaomi MiMo | API key | `XIAOMI_API_KEY` |\n| Kilo Code | API key | `KILOCODE_API_KEY` |\n| OpenCode Zen | API key | `OPENCODE_ZEN_API_KEY` |\n| OpenCode Go | API key | `OPENCODE_GO_API_KEY` |\n| Qwen OAuth | OAuth | `hermes auth add qwen-oauth` |\n| Custom endpoint | Config | `model.base_url` + `model.api_key` in config.yaml |\n| GitHub Copilot ACP | External | `COPILOT_CLI_PATH` or Copilot CLI |\n\nFull provider docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fintegrations\u002Fproviders\n\n### Toolsets\n\nEnable\u002Fdisable via `hermes tools` (interactive) or `hermes tools enable\u002Fdisable NAME`.\n\n| Toolset | What it provides |\n|---------|-----------------|\n| `web` | Web search and content extraction |\n| `search` | Web search only (subset of `web`) |\n| `browser` | Browser automation (Browserbase, Camofox, or local Chromium) |\n| `terminal` | Shell commands and process management |\n| `file` | File read\u002Fwrite\u002Fsearch\u002Fpatch |\n| `code_execution` | Sandboxed Python execution |\n| `vision` | Image analysis |\n| `image_gen` | AI image generation |\n| `video` | Video analysis and generation |\n| `tts` | Text-to-speech |\n| `skills` | Skill browsing and management |\n| `memory` | Persistent cross-session memory |\n| `session_search` | Search past conversations |\n| `delegation` | Subagent task delegation |\n| `cronjob` | Scheduled task management |\n| `clarify` | Ask user clarifying questions |\n| `messaging` | Cross-platform message sending |\n| `todo` | In-session task planning and tracking |\n| `kanban` | Multi-agent work-queue tools (gated to workers) |\n| `debugging` | Extra introspection\u002Fdebug tools (off by default) |\n| `safe` | Minimal, low-risk toolset for locked-down sessions |\n| `spotify` | Spotify playback and playlist control |\n| `homeassistant` | Smart home control (off by default) |\n| `discord` | Discord integration tools |\n| `discord_admin` | Discord admin\u002Fmoderation tools |\n| `feishu_doc` | Feishu (Lark) document tools |\n| `feishu_drive` | Feishu (Lark) drive tools |\n| `yuanbao` | Yuanbao integration tools |\n| `rl` | Reinforcement learning tools (off by default) |\n| `moa` | Mixture of Agents (off by default) |\n\nFull enumeration lives in `toolsets.py` as the `TOOLSETS` dict; `_HERMES_CORE_TOOLS` is the default bundle most platforms inherit from.\n\nTool changes take effect on `\u002Freset` (new session). They do NOT apply mid-conversation to preserve prompt caching.\n\n---\n\n## Security & Privacy Toggles\n\nCommon \"why is Hermes doing X to my output \u002F tool calls \u002F commands?\" toggles — and the exact commands to change them. Most of these need a fresh session (`\u002Freset` in chat, or start a new `hermes` invocation) because they're read once at startup.\n\n### Secret redaction in tool output\n\nSecret redaction is **on by default** — tool output (terminal stdout, `read_file`, web content, subagent summaries, etc.) is scanned for strings that look like API keys, tokens, and secrets before it enters the conversation context and logs. Leave it enabled for normal use:\n\n```bash\nhermes config set security.redact_secrets true       # keep enabled globally\n```\n\n**Restart required.** `security.redact_secrets` is snapshotted at import time — toggling it mid-session (e.g. via `export HERMES_REDACT_SECRETS=false` from a tool call) will NOT take effect for the running process. Tell the user to change it in config from a terminal, then start a new session. This is deliberate — it prevents an LLM from flipping the toggle on itself mid-task.\n\nDisable only when you deliberately need raw credential-like strings for debugging or redactor development:\n```bash\nhermes config set security.redact_secrets false\n```\n\n### PII redaction in gateway messages\n\nSeparate from secret redaction. When enabled, the gateway hashes user IDs and strips phone numbers from the session context before it reaches the model:\n\n```bash\nhermes config set privacy.redact_pii true    # enable\nhermes config set privacy.redact_pii false   # disable (default)\n```\n\n### Command approval prompts\n\nBy default (`approvals.mode: manual`), Hermes prompts the user before running shell commands flagged as destructive (`rm -rf`, `git reset --hard`, etc.). The modes are:\n\n- `manual` — always prompt (default)\n- `smart` — use an auxiliary LLM to auto-approve low-risk commands, prompt on high-risk\n- `off` — skip all approval prompts (equivalent to `--yolo`)\n\n```bash\nhermes config set approvals.mode smart       # recommended middle ground\nhermes config set approvals.mode off         # bypass everything (not recommended)\n```\n\nPer-invocation bypass without changing config:\n- `hermes --yolo …`\n- `export HERMES_YOLO_MODE=1`\n\nNote: YOLO \u002F `approvals.mode: off` does NOT turn off secret redaction. They are independent.\n\n### Shell hooks allowlist\n\nSome shell-hook integrations require explicit allowlisting before they fire. Managed via `~\u002F.hermes\u002Fshell-hooks-allowlist.json` — prompted interactively the first time a hook wants to run.\n\n### Disabling the web\u002Fbrowser\u002Fimage-gen tools\n\nTo keep the model away from network or media tools entirely, open `hermes tools` and toggle per-platform. Takes effect on next session (`\u002Freset`). See the Tools & Skills section above.\n\n---\n\n## Voice & Transcription\n\n### STT (Voice → Text)\n\nVoice messages from messaging platforms are auto-transcribed.\n\nProvider priority (auto-detected):\n1. **Local faster-whisper** — free, no API key: `pip install faster-whisper`\n2. **Groq Whisper** — free tier: set `GROQ_API_KEY`\n3. **OpenAI Whisper** — paid: set `VOICE_TOOLS_OPENAI_KEY`\n4. **Mistral Voxtral** — set `MISTRAL_API_KEY`\n\nConfig:\n```yaml\nstt:\n  enabled: true\n  provider: local        # local, groq, openai, mistral\n  local:\n    model: base          # tiny, base, small, medium, large-v3\n```\n\n### TTS (Text → Voice)\n\n| Provider | Env var | Free? |\n|----------|---------|-------|\n| Edge TTS | None | Yes (default) |\n| ElevenLabs | `ELEVENLABS_API_KEY` | Free tier |\n| OpenAI | `VOICE_TOOLS_OPENAI_KEY` | Paid |\n| MiniMax | `MINIMAX_API_KEY` | Paid |\n| Mistral (Voxtral) | `MISTRAL_API_KEY` | Paid |\n| NeuTTS (local) | None (`pip install neutts[all]` + `espeak-ng`) | Free |\n\nVoice commands: `\u002Fvoice on` (voice-to-voice), `\u002Fvoice tts` (always voice), `\u002Fvoice off`.\n\n---\n\n## Spawning Additional Hermes Instances\n\nRun additional Hermes processes as fully independent subprocesses — separate sessions, tools, and environments.\n\n### When to Use This vs delegate_task\n\n| | `delegate_task` | Spawning `hermes` process |\n|-|-----------------|--------------------------|\n| Isolation | Separate conversation, shared process | Fully independent process |\n| Duration | Minutes (bounded by parent loop) | Hours\u002Fdays |\n| Tool access | Subset of parent's tools | Full tool access |\n| Interactive | No | Yes (PTY mode) |\n| Use case | Quick parallel subtasks | Long autonomous missions |\n\n### One-Shot Mode\n\n```\nterminal(command=\"hermes chat -q 'Research GRPO papers and write summary to ~\u002Fresearch\u002Fgrpo.md'\", timeout=300)\n\n# Background for long tasks:\nterminal(command=\"hermes chat -q 'Set up CI\u002FCD for ~\u002Fmyapp'\", background=true)\n```\n\n### Interactive PTY Mode (via tmux)\n\nHermes uses prompt_toolkit, which requires a real terminal. Use tmux for interactive spawning:\n\n```\n# Start\nterminal(command=\"tmux new-session -d -s agent1 -x 120 -y 40 'hermes'\", timeout=10)\n\n# Wait for startup, then send a message\nterminal(command=\"sleep 8 && tmux send-keys -t agent1 'Build a FastAPI auth service' Enter\", timeout=15)\n\n# Read output\nterminal(command=\"sleep 20 && tmux capture-pane -t agent1 -p\", timeout=5)\n\n# Send follow-up\nterminal(command=\"tmux send-keys -t agent1 'Add rate limiting middleware' Enter\", timeout=5)\n\n# Exit\nterminal(command=\"tmux send-keys -t agent1 '\u002Fexit' Enter && sleep 2 && tmux kill-session -t agent1\", timeout=10)\n```\n\n### Multi-Agent Coordination\n\n```\n# Agent A: backend\nterminal(command=\"tmux new-session -d -s backend -x 120 -y 40 'hermes -w'\", timeout=10)\nterminal(command=\"sleep 8 && tmux send-keys -t backend 'Build REST API for user management' Enter\", timeout=15)\n\n# Agent B: frontend\nterminal(command=\"tmux new-session -d -s frontend -x 120 -y 40 'hermes -w'\", timeout=10)\nterminal(command=\"sleep 8 && tmux send-keys -t frontend 'Build React dashboard for user management' Enter\", timeout=15)\n\n# Check progress, relay context between them\nterminal(command=\"tmux capture-pane -t backend -p | tail -30\", timeout=5)\nterminal(command=\"tmux send-keys -t frontend 'Here is the API schema from the backend agent: ...' Enter\", timeout=5)\n```\n\n### Session Resume\n\n```\n# Resume most recent session\nterminal(command=\"tmux new-session -d -s resumed 'hermes --continue'\", timeout=10)\n\n# Resume specific session\nterminal(command=\"tmux new-session -d -s resumed 'hermes --resume 20260225_143052_a1b2c3'\", timeout=10)\n```\n\n### Tips\n\n- **Prefer `delegate_task` for quick subtasks** — less overhead than spawning a full process\n- **Use `-w` (worktree mode)** when spawning agents that edit code — prevents git conflicts\n- **Set timeouts** for one-shot mode — complex tasks can take 5-10 minutes\n- **Use `hermes chat -q` for fire-and-forget** — no PTY needed\n- **Use tmux for interactive sessions** — raw PTY mode has `\\r` vs `\\n` issues with prompt_toolkit\n- **For scheduled tasks**, use the `cronjob` tool instead of spawning — handles delivery and retry\n\n---\n\n## Durable & Background Systems\n\nFour systems run alongside the main conversation loop. Quick reference\nhere; full developer notes live in `AGENTS.md`, user-facing docs under\n`website\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002F`.\n\n### Delegation (`delegate_task`)\n\nSynchronous subagent spawn — the parent waits for the child's summary\nbefore continuing its own loop. Isolated context + terminal session.\n\n- **Single:** `delegate_task(goal, context, toolsets)`.\n- **Batch:** `delegate_task(tasks=[{goal, ...}, ...])` runs children in\n  parallel, capped by `delegation.max_concurrent_children` (default 3).\n- **Roles:** `leaf` (default; cannot re-delegate) vs `orchestrator`\n  (can spawn its own workers, bounded by `delegation.max_spawn_depth`).\n- **Not durable.** If the parent is interrupted, the child is\n  cancelled. For work that must outlive the turn, use `cronjob` or\n  `terminal(background=True, notify_on_complete=True)`.\n\nConfig: `delegation.*` in `config.yaml`.\n\n### Cron (scheduled jobs)\n\nDurable scheduler — `cron\u002Fjobs.py` + `cron\u002Fscheduler.py`. Drive it via\nthe `cronjob` tool, the `hermes cron` CLI (`list`, `add`, `edit`,\n`pause`, `resume`, `run`, `remove`), or the `\u002Fcron` slash command.\n\n- **Schedules:** duration (`\"30m\"`, `\"2h\"`), \"every\" phrase\n  (`\"every monday 9am\"`), 5-field cron (`\"0 9 * * *\"`), or ISO timestamp.\n- **Per-job knobs:** `skills`, `model`\u002F`provider` override, `script`\n  (pre-run data collection; `no_agent=True` makes the script the whole\n  job), `context_from` (chain job A's output into job B), `workdir`\n  (run in a specific dir with its `AGENTS.md` \u002F `CLAUDE.md` loaded),\n  multi-platform delivery.\n- **Invariants:** 3-minute hard interrupt per run, `.tick.lock` file\n  prevents duplicate ticks across processes, cron sessions pass\n  `skip_memory=True` by default, and cron deliveries are framed with a\n  header\u002Ffooter instead of being mirrored into the target gateway\n  session (keeps role alternation intact).\n\nUser docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fcron\n\n### Curator (skill lifecycle)\n\nBackground maintenance for agent-created skills. Tracks usage, marks\nidle skills stale, archives stale ones, keeps a pre-run tar.gz backup\nso nothing is lost.\n\n- **CLI:** `hermes curator \u003Cverb>` — `status`, `run`, `pause`, `resume`,\n  `pin`, `unpin`, `archive`, `restore`, `prune`, `backup`, `rollback`.\n- **Slash:** `\u002Fcurator \u003Csubcommand>` mirrors the CLI.\n- **Scope:** only touches skills with `created_by: \"agent\"` provenance.\n  Bundled + hub-installed skills are off-limits. **Never deletes** —\n  max destructive action is archive. Pinned skills are exempt from\n  every auto-transition and every LLM review pass.\n- **Telemetry:** sidecar at `~\u002F.hermes\u002Fskills\u002F.usage.json` holds\n  per-skill `use_count`, `view_count`, `patch_count`,\n  `last_activity_at`, `state`, `pinned`.\n\nConfig: `curator.*` (`enabled`, `interval_hours`, `min_idle_hours`,\n`stale_after_days`, `archive_after_days`, `backup.*`).\nUser docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fcurator\n\n### Kanban (multi-agent work queue)\n\nDurable SQLite board for multi-profile \u002F multi-worker collaboration.\nUsers drive it via `hermes kanban \u003Cverb>`; dispatcher-spawned workers\nsee a focused `kanban_*` toolset gated by `HERMES_KANBAN_TASK`, and\norchestrator profiles can opt into the broader `kanban` toolset. Normal\nsessions still have zero `kanban_*` schema footprint unless configured.\n\n- **CLI verbs (common):** `init`, `create`, `list` (alias `ls`),\n  `show`, `assign`, `link`, `unlink`, `comment`, `complete`, `block`,\n  `unblock`, `archive`, `tail`. Less common: `watch`, `stats`, `runs`,\n  `log`, `dispatch`, `daemon`, `gc`.\n- **Worker\u002Forchestrator toolset:** `kanban_show`, `kanban_complete`,\n  `kanban_block`, `kanban_heartbeat`, `kanban_comment`, `kanban_create`,\n  `kanban_link`; profiles that explicitly enable the `kanban` toolset\n  outside a dispatcher-spawned task also get `kanban_list` and\n  `kanban_unblock` for board routing.\n- **Dispatcher** runs inside the gateway by default\n  (`kanban.dispatch_in_gateway: true`) — reclaims stale claims,\n  promotes ready tasks, atomically claims, spawns assigned profiles.\n  Auto-blocks a task after `failure_limit` consecutive spawn failures\n  (default 2; configurable via `kanban.failure_limit` or per-task\n  `max_retries`).\n- **Isolation:** board is the hard boundary (workers get\n  `HERMES_KANBAN_BOARD` pinned in env); tenant is a soft namespace\n  within a board for workspace-path + memory-key isolation.\n\nUser docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fkanban\n\n---\n\n## Windows-Specific Quirks\n\nHermes runs natively on Windows (PowerShell, cmd, Windows Terminal, git-bash\nmintty, VS Code integrated terminal). Most of it just works, but a handful\nof differences between Win32 and POSIX have bitten us — document new ones\nhere as you hit them so the next person (or the next session) doesn't\nrediscover them from scratch.\n\n### Input \u002F Keybindings\n\n**Alt+Enter doesn't insert a newline.** Windows Terminal intercepts Alt+Enter\nat the terminal layer to toggle fullscreen — the keystroke never reaches\nprompt_toolkit. Use **Ctrl+Enter** instead. Windows Terminal delivers\nCtrl+Enter as LF (`c-j`), distinct from plain Enter (`c-m` \u002F CR), and the\nCLI binds `c-j` to newline insertion on `win32` only (see\n`_bind_prompt_submit_keys` + the Windows-only `c-j` binding in `cli.py`).\nSide effect: the raw Ctrl+J keystroke also inserts a newline on Windows —\nunavoidable, because Windows Terminal collapses Ctrl+Enter and Ctrl+J to\nthe same keycode at the Win32 console API layer. No conflicting binding\nexisted for Ctrl+J on Windows, so this is a harmless side effect.\n\nmintty \u002F git-bash behaves the same (fullscreen on Alt+Enter) unless you\ndisable Alt+Fn shortcuts in Options → Keys. Easier to just use Ctrl+Enter.\n\n**Diagnosing keybindings.** Run `python scripts\u002Fkeystroke_diagnostic.py`\n(repo root) to see exactly how prompt_toolkit identifies each keystroke\nin the current terminal. Answers questions like \"does Shift+Enter come\nthrough as a distinct key?\" (almost never — most terminals collapse it\nto plain Enter) or \"what byte sequence is my terminal sending for\nCtrl+Enter?\" This is how the Ctrl+Enter = c-j fact was established.\n\n### Config \u002F Files\n\n**HTTP 400 \"No models provided\" on first run.** `config.yaml` was saved\nwith a UTF-8 BOM (common when Windows apps write it). Re-save as UTF-8\nwithout BOM. `hermes config edit` writes without BOM; manual edits in\nNotepad are the usual culprit.\n\n### `execute_code` \u002F Sandbox\n\n**WinError 10106** (\"The requested service provider could not be loaded\nor initialized\") from the sandbox child process — it can't create an\n`AF_INET` socket, so the loopback-TCP RPC fallback fails before\n`connect()`. Root cause is usually **not** a broken Winsock LSP; it's\nHermes's own env scrubber dropping `SYSTEMROOT` \u002F `WINDIR` \u002F `COMSPEC`\nfrom the child env. Python's `socket` module needs `SYSTEMROOT` to locate\n`mswsock.dll`. Fixed via the `_WINDOWS_ESSENTIAL_ENV_VARS` allowlist in\n`tools\u002Fcode_execution_tool.py`. If you still hit it, echo `os.environ`\ninside an `execute_code` block to confirm `SYSTEMROOT` is set. Full\ndiagnostic recipe in `references\u002Fexecute-code-sandbox-env-windows.md`.\n\n### Testing \u002F Contributing\n\n**`scripts\u002Frun_tests.sh` doesn't work as-is on Windows** — it looks for\nPOSIX venv layouts (`.venv\u002Fbin\u002Factivate`). The Hermes-installed venv at\n`venv\u002FScripts\u002F` has no pip or pytest either (stripped for install size).\nWorkaround: install `pytest + pytest-xdist + pyyaml` into a system Python\n3.11 user site, then invoke pytest directly with `PYTHONPATH` set:\n\n```bash\n\"\u002Fc\u002FProgram Files\u002FPython311\u002Fpython\" -m pip install --user pytest pytest-xdist pyyaml\nexport PYTHONPATH=\"$(pwd)\"\n\"\u002Fc\u002FProgram Files\u002FPython311\u002Fpython\" -m pytest tests\u002Ffoo\u002Ftest_bar.py -v --tb=short -n 0\n```\n\nUse `-n 0`, not `-n 4` — `pyproject.toml`'s default `addopts` already\nincludes `-n`, and the wrapper's CI-parity guarantees don't apply off POSIX.\n\n**POSIX-only tests need skip guards.** Common markers already in the codebase:\n- Symlinks — elevated privileges on Windows\n- `0o600` file modes — POSIX mode bits not enforced on NTFS by default\n- `signal.SIGALRM` — Unix-only (see `tests\u002Fconftest.py::_enforce_test_timeout`)\n- Winsock \u002F Windows-specific regressions — `@pytest.mark.skipif(sys.platform != \"win32\", ...)`\n\nUse the existing skip-pattern style (`sys.platform == \"win32\"` or\n`sys.platform.startswith(\"win\")`) to stay consistent with the rest of the\nsuite.\n\n### Path \u002F Filesystem\n\n**Line endings.** Git may warn `LF will be replaced by CRLF the next time\nGit touches it`. Cosmetic — the repo's `.gitattributes` normalizes. Don't\nlet editors auto-convert committed POSIX-newline files to CRLF.\n\n**Forward slashes work almost everywhere.** `C:\u002FUsers\u002F...` is accepted by\nevery Hermes tool and most Windows APIs. Prefer forward slashes in code\nand logs — avoids shell-escaping backslashes in bash.\n\n---\n\n## Troubleshooting\n\n### Voice not working\n1. Check `stt.enabled: true` in config.yaml\n2. Verify provider: `pip install faster-whisper` or set API key\n3. In gateway: `\u002Frestart`. In CLI: exit and relaunch.\n\n### Tool not available\n1. `hermes tools` — check if toolset is enabled for your platform\n2. Some tools need env vars (check `.env`)\n3. `\u002Freset` after enabling tools\n\n### Model\u002Fprovider issues\n1. `hermes doctor` — check config and dependencies\n2. `hermes auth` — re-authenticate OAuth providers (or `hermes auth add \u003Cprovider>`)\n3. Check `.env` has the right API key\n4. **Copilot 403**: `gh auth login` tokens do NOT work for Copilot API. You must use the Copilot-specific OAuth device code flow via `hermes model` → GitHub Copilot.\n\n### Changes not taking effect\n- **Tools\u002Fskills:** `\u002Freset` starts a new session with updated toolset\n- **Config changes:** In gateway: `\u002Frestart`. In CLI: exit and relaunch.\n- **Code changes:** Restart the CLI or gateway process\n\n### Skills not showing\n1. `hermes skills list` — verify installed\n2. `hermes skills config` — check platform enablement\n3. Load explicitly: `\u002Fskill name` or `hermes -s name`\n\n### Gateway issues\nCheck logs first:\n```bash\ngrep -i \"failed to send\\|error\" ~\u002F.hermes\u002Flogs\u002Fgateway.log | tail -20\n```\n\nCommon gateway problems:\n- **Gateway dies on SSH logout**: Enable linger: `sudo loginctl enable-linger $USER`\n- **Gateway dies on WSL2 close**: WSL2 requires `systemd=true` in `\u002Fetc\u002Fwsl.conf` for systemd services to work. Without it, gateway falls back to `nohup` (dies when session closes).\n- **Gateway crash loop**: Reset the failed state: `systemctl --user reset-failed hermes-gateway`\n\n### Platform-specific issues\n- **Discord bot silent**: Must enable **Message Content Intent** in Bot → Privileged Gateway Intents.\n- **Slack bot only works in DMs**: Must subscribe to `message.channels` event. Without it, the bot ignores public channels.\n- **Windows-specific issues** (`Alt+Enter` newline, WinError 10106, UTF-8 BOM config, test suite, line endings): see the dedicated **Windows-Specific Quirks** section above.\n\n### Auxiliary models not working\nIf `auxiliary` tasks (vision, compression, session_search) fail silently, the `auto` provider can't find a backend. Either set `OPENROUTER_API_KEY` or `GOOGLE_API_KEY`, or explicitly configure each auxiliary task's provider:\n```bash\nhermes config set auxiliary.vision.provider \u003Cyour_provider>\nhermes config set auxiliary.vision.model \u003Cmodel_name>\n```\n\n---\n\n---\n\n## Hermes Skill Authoring\n\n### In-Repo vs User-Local Skills\n- **User-local:** `~\u002F.hermes\u002Fskills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` — created via `skill_manage(action='create')`\n- **In-repo:** `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` — committed, shipped with the package. Use `write_file` + `git add`\n\n### Required Frontmatter\n```yaml\n---\nname: my-skill-name               # lowercase, hyphens, ≤64 chars\ndescription: Use when \u003Ctrigger>. \u003Cone-line behavior>.   # ≤1024 chars\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [short, descriptive, tags]\n    related_skills: [other-skill]\n---\n```\n\n### Size Limits\n- Description ≤ 1024 chars (enforced)\n- Full SKILL.md ≤ 100,000 chars (≈36k tokens)\n- Peer skills sit at 8–14k chars. Aim for that range.\n\n### Workflow\n1. Survey peers in the target category (`ls skills\u002F\u003Ccategory>\u002F`)\n2. Draft with `write_file` to `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md`\n3. Validate locally (YAML frontmatter, size limits)\n4. `git add && git commit`\n\n### Common Pitfalls\n- `skill_manage(action='create')` writes to `~\u002F.hermes\u002Fskills\u002F`, NOT the repo tree — use `write_file` for in-repo\n- Leading whitespace before `---` fails validation\n- Current session won't see the new skill until `\u002Freset`\n\n---\n\n## Hermes s6-overlay Container Supervision\n\n### When to Use\n- Adding\u002Fremoving static services in the Hermes Docker image\n- Diagnosing why a per-profile gateway isn't starting or surviving restart\n- Modifying `cont-init.d` boot scripts or per-profile gateway run-scripts\n\n### Architecture at a Glance\n```\n\u002Finit (s6-overlay v3)\n├── cont-init.d\n│   ├── 01-hermes-setup      ← docker\u002Fstage2-hook.sh\n│   └── 02-reconcile-profiles ← container_boot.py\n├── s6-rc.d (static services)\n│   ├── main-hermes\u002Frun      ← exec sleep infinity (no-op slot)\n│   └── dashboard\u002Frun        ← conditional\n└── \u002Frun\u002Fservice (per-profile gateways, tmpfs)\n    └── gateway-\u003Cname>\u002F\n        ├── run  ← s6-setuidgid hermes hermes -p \u003Cname> gateway run\n        └── log\u002Frun\n```\n\n### Why Architecture B (CMD as main program)\n1. `cont-init.d` scripts receive no CMD args\n2. s6 halt always exits 143 regardless of written exitcode\n\nSo main hermes runs as the CMD (`\u002Fopt\u002Fhermes\u002Fdocker\u002Fmain-wrapper.sh`), not as a supervised service. Per-profile gateways under `\u002Frun\u002Fservice\u002F` get full supervision.\n\n### Quick Recipes\n```bash\ndocker exec \u003Cc> \u002Fcommand\u002Fs6-svstat \u002Frun\u002Fservice\u002Fgateway-\u003Cname>   # Inspect\ndocker exec \u003Cc> \u002Fcommand\u002Fs6-svc -u \u002Frun\u002Fservice\u002Fgateway-\u003Cname>   # Up\ndocker exec \u003Cc> \u002Fcommand\u002Fs6-svc -d \u002Frun\u002Fservice\u002Fgateway-\u003Cname>   # Down\ndocker exec \u003Cc> tail -n 50 \u002Fopt\u002Fdata\u002Flogs\u002Fcontainer-boot.log     # Reconciler log\n```\n\n### Pitfalls\n- `docker exec` defaults to root; files under `$HERMES_HOME\u002Fprofiles\u002F` should be hermes-owned\n- Service slot on tmpfs → wiped on container restart; reconciler recreates it\n- Gateway starts then exits → profile likely unconfigured; fix config, supervisor will retry\n\n---\n\n## Debugging Hermes TUI Slash Commands\n\n### Architecture\n```\nPython backend (hermes_cli\u002Fcommands.py)     ← canonical COMMAND_REGISTRY\n       ↓\nTUI gateway (tui_gateway\u002Fserver.py)         ← slash.exec \u002F command.dispatch\n       ↓\nTUI frontend (ui-tui\u002Fsrc\u002Fapp\u002Fslash\u002F)        ← local handlers + fallthrough\n```\n\n### Fix: Missing Command Autocomplete\n1. Add `CommandDef` to `COMMAND_REGISTRY` in `hermes_cli\u002Fcommands.py`\n2. Ensure `subcommands` tuple matches TUI expectations\n3. Add handler in `cli.py::process_command()` for CLI-only\n4. Add handler in `gateway\u002Frun.py` for gateway-available\n\n### Common Issues\n1. **Shows in TUI but not autocomplete** → missing from `COMMAND_REGISTRY`\n2. **Shows in autocomplete but doesn't work** → missing frontend or gateway handler\n3. **Behavior differs between CLI and TUI** → divergent implementations\n4. **Config persists but UI doesn't update** → patch nanostore state immediately (`patchUiState`)\n\n### Debugging Tactics\n- Python side hangs → use `python-debugpy` to break inside `_SlashWorker.exec`\n- Ink side not reacting → use `node-inspect-debugger` to break in `app.tsx`\n- Registry mismatch → compare `COMMAND_REGISTRY` against TUI local command list\n\n### Verification\n1. Rebuild TUI: `npm --prefix ui-tui run build`\n2. Test autocomplete with `\u002F`\n3. Confirm behavior, persisted config, and live UI state\n\n\n| Looking for... | Location |\n|----------------|----------|\n| Config options | `hermes config edit` or [Configuration docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fconfiguration) |\n| Available tools | `hermes tools list` or [Tools reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Ftools-reference) |\n| Slash commands | `\u002Fhelp` in session or [Slash commands reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fslash-commands) |\n| Skills catalog | `hermes skills browse` or [Skills catalog](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fskills-catalog) |\n| Provider setup | `hermes model` or [Providers guide](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fintegrations\u002Fproviders) |\n| Platform setup | `hermes gateway setup` or [Messaging docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002F) |\n| MCP servers | `hermes mcp list` or [MCP guide](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fmcp) |\n| Profiles | `hermes profile list` or [Profiles docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fprofiles) |\n| Cron jobs | `hermes cron list` or [Cron docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fcron) |\n| Memory | `hermes memory status` or [Memory docs](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fmemory) |\n| Env variables | `hermes config env-path` or [Env vars reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fenvironment-variables) |\n| CLI commands | `hermes --help` or [CLI reference](https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Freference\u002Fcli-commands) |\n| Gateway logs | `~\u002F.hermes\u002Flogs\u002Fgateway.log` |\n| Session files | `hermes sessions browse` (reads state.db) |\n| Source code | `~\u002F.hermes\u002Fhermes-agent\u002F` |\n\n---\n\n## Contributor Quick Reference\n\nFor occasional contributors and PR authors. Full developer docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fdeveloper-guide\u002F\n\n### Project Layout\n\n```\nhermes-agent\u002F\n├── run_agent.py          # AIAgent — core conversation loop\n├── model_tools.py        # Tool discovery and dispatch\n├── toolsets.py           # Toolset definitions\n├── cli.py                # Interactive CLI (HermesCLI)\n├── hermes_state.py       # SQLite session store\n├── agent\u002F                # Prompt builder, context compression, memory, model routing, credential pooling, skill dispatch\n├── hermes_cli\u002F           # CLI subcommands, config, setup, commands\n│   ├── commands.py       # Slash command registry (CommandDef)\n│   ├── config.py         # DEFAULT_CONFIG, env var definitions\n│   └── main.py           # CLI entry point and argparse\n├── tools\u002F                # One file per tool\n│   └── registry.py       # Central tool registry\n├── gateway\u002F              # Messaging gateway\n│   └── platforms\u002F        # Platform adapters (telegram, discord, etc.)\n├── cron\u002F                 # Job scheduler\n├── tests\u002F                # ~3000 pytest tests\n└── website\u002F              # Docusaurus docs site\n```\n\nConfig: `~\u002F.hermes\u002Fconfig.yaml` (settings), `~\u002F.hermes\u002F.env` (API keys).\n\n### Adding a Tool (3 files)\n\n**1. Create `tools\u002Fyour_tool.py`:**\n```python\nimport json, os\nfrom tools.registry import registry\n\ndef check_requirements() -> bool:\n    return bool(os.getenv(\"EXAMPLE_API_KEY\"))\n\ndef example_tool(param: str, task_id: str = None) -> str:\n    return json.dumps({\"success\": True, \"data\": \"...\"})\n\nregistry.register(\n    name=\"example_tool\",\n    toolset=\"example\",\n    schema={\"name\": \"example_tool\", \"description\": \"...\", \"parameters\": {...}},\n    handler=lambda args, **kw: example_tool(\n        param=args.get(\"param\", \"\"), task_id=kw.get(\"task_id\")),\n    check_fn=check_requirements,\n    requires_env=[\"EXAMPLE_API_KEY\"],\n)\n```\n\n**2. Add to `toolsets.py`** → `_HERMES_CORE_TOOLS` list.\n\nAuto-discovery: any `tools\u002F*.py` file with a top-level `registry.register()` call is imported automatically — no manual list needed.\n\nAll handlers must return JSON strings. Use `get_hermes_home()` for paths, never hardcode `~\u002F.hermes`.\n\n### Adding a Slash Command\n\n1. Add `CommandDef` to `COMMAND_REGISTRY` in `hermes_cli\u002Fcommands.py`\n2. Add handler in `cli.py` → `process_command()`\n3. (Optional) Add gateway handler in `gateway\u002Frun.py`\n\nAll consumers (help text, autocomplete, Telegram menu, Slack mapping) derive from the central registry automatically.\n\n### Agent Loop (High Level)\n\n```\nrun_conversation():\n  1. Build system prompt\n  2. Loop while iterations \u003C max:\n     a. Call LLM (OpenAI-format messages + tool schemas)\n     b. If tool_calls → dispatch each via handle_function_call() → append results → continue\n     c. If text response → return\n  3. Context compression triggers automatically near token limit\n```\n\n### Testing\n\n```bash\npython -m pytest tests\u002F -o 'addopts=' -q   # Full suite\npython -m pytest tests\u002Ftools\u002F -q            # Specific area\n```\n\n- Tests auto-redirect `HERMES_HOME` to temp dirs — never touch real `~\u002F.hermes\u002F`\n- Run full suite before pushing any change\n- Use `-o 'addopts='` to clear any baked-in pytest flags\n\n**Windows contributors:** `scripts\u002Frun_tests.sh` currently looks for POSIX venvs (`.venv\u002Fbin\u002Factivate` \u002F `venv\u002Fbin\u002Factivate`) and will error out on Windows where the layout is `venv\u002FScripts\u002Factivate` + `python.exe`. The Hermes-installed venv at `venv\u002FScripts\u002F` also has no `pip` or `pytest` — it's stripped for end-user install size. Workaround: install pytest + pytest-xdist + pyyaml into a system Python 3.11 user site (`\u002Fc\u002FProgram Files\u002FPython311\u002Fpython -m pip install --user pytest pytest-xdist pyyaml`), then run tests directly:\n\n```bash\nexport PYTHONPATH=\"$(pwd)\"\n\"\u002Fc\u002FProgram Files\u002FPython311\u002Fpython\" -m pytest tests\u002Ftools\u002Ftest_foo.py -v --tb=short -n 0\n```\n\nUse `-n 0` (not `-n 4`) because `pyproject.toml`'s default `addopts` already includes `-n`, and the wrapper's CI-parity story doesn't apply off-POSIX.\n\n**Cross-platform test guards:** tests that use POSIX-only syscalls need a skip marker. Common ones already in the codebase:\n- Symlink creation → `@pytest.mark.skipif(sys.platform == \"win32\", reason=\"Symlinks require elevated privileges on Windows\")` (see `tests\u002Fcron\u002Ftest_cron_script.py`)\n- POSIX file modes (0o600, etc.) → `@pytest.mark.skipif(sys.platform.startswith(\"win\"), reason=\"POSIX mode bits not enforced on Windows\")` (see `tests\u002Fhermes_cli\u002Ftest_auth_toctou_file_modes.py`)\n- `signal.SIGALRM` → Unix-only (see `tests\u002Fconftest.py::_enforce_test_timeout`)\n- Live Winsock \u002F Windows-specific regression tests → `@pytest.mark.skipif(sys.platform != \"win32\", reason=\"Windows-specific regression\")`\n\n**Monkeypatching `sys.platform` is not enough** when the code under test also calls `platform.system()` \u002F `platform.release()` \u002F `platform.mac_ver()`. Those functions re-read the real OS independently, so a test that sets `sys.platform = \"linux\"` on a Windows runner will still see `platform.system() == \"Windows\"` and route through the Windows branch. Patch all three together:\n\n```python\nmonkeypatch.setattr(sys, \"platform\", \"linux\")\nmonkeypatch.setattr(platform, \"system\", lambda: \"Linux\")\nmonkeypatch.setattr(platform, \"release\", lambda: \"6.8.0-generic\")\n```\n\nSee `tests\u002Fagent\u002Ftest_prompt_builder.py::TestEnvironmentHints` for a worked example.\n\n### Extending the system prompt's execution-environment block\n\nFactual guidance about the host OS, user home, cwd, terminal backend, and shell (bash vs. PowerShell on Windows) is emitted from `agent\u002Fprompt_builder.py::build_environment_hints()`. This is also where the WSL hint and per-backend probe logic live. The convention:\n\n- **Local terminal backend** → emit host info (OS, `$HOME`, cwd) + Windows-specific notes (hostname ≠ username, `terminal` uses bash not PowerShell).\n- **Remote terminal backend** (anything in `_REMOTE_TERMINAL_BACKENDS`: `docker, singularity, modal, daytona, ssh, managed_modal`) → **suppress** host info entirely and describe only the backend. A live `uname`\u002F`whoami`\u002F`pwd` probe runs inside the backend via `tools.environments.get_environment(...).execute(...)`, cached per process in `_BACKEND_PROBE_CACHE`, with a static fallback if the probe times out.\n- **Key fact for prompt authoring:** when `TERMINAL_ENV != \"local\"`, *every* file tool (`read_file`, `write_file`, `patch`, `search_files`) runs inside the backend container, not on the host. The system prompt must never describe the host in that case — the agent can't touch it.\n\nFull design notes, the exact emitted strings, and testing pitfalls:\n`references\u002Fprompt-builder-environment-hints.md`.\n\n**Refactor-safety pattern (POSIX-equivalence guard):** when you extract inline logic into a helper that adds Windows\u002Fplatform-specific behavior, keep a `_legacy_\u003Cname>` oracle function in the test file that's a verbatim copy of the old code, then parametrize-diff against it. Example: `tests\u002Ftools\u002Ftest_code_execution_windows_env.py::TestPosixEquivalence`. This locks in the invariant that POSIX behavior is bit-for-bit identical and makes any future drift fail loudly with a clear diff.\n\n### Commit Conventions\n\n```\ntype: concise subject line\n\nOptional body.\n```\n\nTypes: `fix:`, `feat:`, `refactor:`, `docs:`, `chore:`\n\n### Key Rules\n\n- **Never break prompt caching** — don't change context, tools, or system prompt mid-conversation\n- **Message role alternation** — never two assistant or two user messages in a row\n- Use `get_hermes_home()` from `hermes_constants` for all paths (profile-safe)\n- Config values go in `config.yaml`, secrets go in `.env`\n- New tools need a `check_fn` so they only appear when requirements are met\n",{"name":5,"author":46,"license":15,"version":47,"metadata":48,"platforms":56,"description":7},"Hermes Agent + Teknium","2.1.0",{"hermes":49},{"tags":50,"homepage":53,"related_skills":54},[25,35,51,28,52,40,32,34],"configuration","spawning","https:\u002F\u002Fgithub.com\u002FNousResearch\u002Fhermes-agent",[55,37,27],"claude-code",[38,33,36],"main","64e2fc9afa7bb3da1138eb73399144d0e7e73e9d","_hermes\u002Fdefault\u002Fprofiles\u002Fwriting\u002Fskills\u002Fautonomous-ai-agents\u002Fhermes-agent",4,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs","https:\u002F\u002Fgithub.com\u002Fadnichols","2026-11-06 00:28:38",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add adnichols\u002Fai-configs --skill hermes-agent",{"tool":70,"command":71},"bunx","bunx skills add adnichols\u002Fai-configs --skill hermes-agent",{"tool":73,"command":74},"pnpm","pnpm dlx skills add adnichols\u002Fai-configs --skill hermes-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fwriting\u002Fskills\u002Fautonomous-ai-agents\u002Fhermes-agent\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi_reference.md","REFERENCE","参考文档",16384,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fmetabolomics-workbench-database\u002Freferences\u002Fapi_reference.md",[85,102,131,155,166,182],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":41},"01M6CB7RN791P5RRRCJWWC7DAR","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[92,93,94,95,96,97,98,24,25,99,100,36,101,38,33],"recovery","page","blocked page recovery","bot","fallback","use","fetch","Citations","waf","research",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":117,"publishedAt":41},"01M6CB7NQY2VVYCQJ1QBXACQF4","writing-plans","Use when creating or updating executable software plans. Keep plans as local files unless the user explicitly asks to register them in Doct.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[108,111,112],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[118,119,120,121,122,123,124,34,125,126,127,128,97,129,24,25,130],"writing","writing plans","documentation","test","workflow","design","user","planning","files","implementation","html","ops","plan",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":146,"publishedAt":41},"01M6CB7JME246KZQHP73Z2STDF","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[137,140,143],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":144,"categoryName":145,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000037","律师与法务",[121,34,147,148,149,24,25,150,130,151,26,152,33,153,38,154,36],"test driven development","red-green-refactor","superpowers","quality","refactor","debugging","tdd","testing",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":41},"01M6CB7FQ407KQTD4Z9VAWKY54","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[161],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[152,163,34,149,24,25,164,130,165,36,121,38,33],"systematic debugging","troubleshooting","investigation",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":41},"01M6CB7D57MK88HE5YPZHKH68Q","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[168,36,176,177,101,178,38,33,179,180,181,24,25,130,125],"validate","experiments","prototype","feasibility","sketch","experiment",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":192,"publishedAt":41},"01M6CB7APAQ37YE5YE1MAAFT42","simplify-code","Parallel 3-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[188,189],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":190,"categoryName":191,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000030","开发工程师",[193,194,26,195,24,25,196,130,151,197,198,199,34,36,121,38,200,33],"simplify code","simplify","subagent","parallel","code-review","delegation","cleanup","review"]