Hermes Agent backup - 2026-06-04 04:48:07

logs/agent.log

@@ -1404,3 +1404,39 @@
 2026-06-04 04:46:13,803 INFO run_agent: OpenAI client closed (stream_request_complete, shared=False, tcp_force_closed=1) thread=Thread-11 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
 2026-06-04 04:46:13,806 WARNING [probe-6ad57775] agent.conversation_loop: API call failed (attempt 3/3) error_type=RateLimitError thread=hermes-bridge-run-2579986f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
 2026-06-04 04:46:13,808 ERROR [probe-6ad57775] agent.conversation_loop: API call failed after 3 retries. HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'} | provider=nvidia model=deepseek-ai/deepseek-v4-pro msgs=2 tokens=~5,031
+2026-06-04 04:47:14,770 INFO agent.credential_pool: credential pool: no available entries (all exhausted or empty)
+2026-06-04 04:47:14,839 INFO run_agent: OpenAI client created (agent_init, shared=True) thread=MainThread:140471116309312 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:14,878 INFO [test-37d05524] agent.conversation_loop: conversation turn: session=test-37d05524 model=deepseek-ai/deepseek-v4-pro provider=nvidia platform=cli history=0 msg='Hello! Reply with just OK.'
+2026-06-04 04:47:14,936 INFO run_agent: OpenAI client created (chat_completion_stream_request, shared=False) thread=Thread-12 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:14,984 INFO agent.chat_completion_helpers: Streaming failed before delivery: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:14,984 INFO run_agent: OpenAI client closed (stream_request_complete, shared=False, tcp_force_closed=1) thread=Thread-12 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:14,985 WARNING [test-37d05524] agent.conversation_loop: API call failed (attempt 1/3) error_type=RateLimitError thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:14,987 WARNING [test-37d05524] agent.conversation_loop: Retrying API call in 2.033048465459741s (attempt 1/3) thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:17,223 INFO run_agent: OpenAI client created (chat_completion_stream_request, shared=False) thread=Thread-13 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:17,273 INFO agent.chat_completion_helpers: Streaming failed before delivery: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:17,274 INFO run_agent: OpenAI client closed (stream_request_complete, shared=False, tcp_force_closed=1) thread=Thread-13 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:17,275 WARNING [test-37d05524] agent.conversation_loop: API call failed (attempt 2/3) error_type=RateLimitError thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:17,276 WARNING [test-37d05524] agent.conversation_loop: Retrying API call in 5.177516703146319s (attempt 2/3) thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:22,508 INFO run_agent: OpenAI client created (chat_completion_stream_request, shared=False) thread=Thread-14 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:22,547 INFO agent.chat_completion_helpers: Streaming failed before delivery: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:22,550 INFO run_agent: OpenAI client closed (stream_request_complete, shared=False, tcp_force_closed=1) thread=Thread-14 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:22,552 WARNING [test-37d05524] agent.conversation_loop: API call failed (attempt 3/3) error_type=RateLimitError thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:22,555 ERROR [test-37d05524] agent.conversation_loop: API call failed after 3 retries. HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'} | provider=nvidia model=deepseek-ai/deepseek-v4-pro msgs=2 tokens=~5,036
+2026-06-04 04:47:28,295 INFO agent.credential_pool: credential pool: no available entries (all exhausted or empty)
+2026-06-04 04:47:28,375 INFO run_agent: OpenAI client created (agent_init, shared=True) thread=MainThread:140471116309312 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:28,462 INFO [test-1eafe5ef] agent.conversation_loop: conversation turn: session=test-1eafe5ef model=deepseek-ai/deepseek-v4-pro provider=nvidia platform=cli history=0 msg='What is 2+2? Just the number.'
+2026-06-04 04:47:28,510 INFO run_agent: OpenAI client created (chat_completion_stream_request, shared=False) thread=Thread-15 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:28,558 INFO agent.chat_completion_helpers: Streaming failed before delivery: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:28,559 INFO run_agent: OpenAI client closed (stream_request_complete, shared=False, tcp_force_closed=1) thread=Thread-15 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:28,560 WARNING [test-1eafe5ef] agent.conversation_loop: API call failed (attempt 1/3) error_type=RateLimitError thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:28,561 WARNING [test-1eafe5ef] agent.conversation_loop: Retrying API call in 2.089400643709097s (attempt 1/3) thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:30,787 INFO run_agent: OpenAI client created (chat_completion_stream_request, shared=False) thread=Thread-16 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:30,837 INFO agent.chat_completion_helpers: Streaming failed before delivery: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:30,838 INFO run_agent: OpenAI client closed (stream_request_complete, shared=False, tcp_force_closed=1) thread=Thread-16 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:30,841 WARNING [test-1eafe5ef] agent.conversation_loop: API call failed (attempt 2/3) error_type=RateLimitError thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:30,841 WARNING [test-1eafe5ef] agent.conversation_loop: Retrying API call in 4.353413098019788s (attempt 2/3) thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:35,262 INFO run_agent: OpenAI client created (chat_completion_stream_request, shared=False) thread=Thread-17 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:35,302 INFO agent.chat_completion_helpers: Streaming failed before delivery: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:35,303 INFO run_agent: OpenAI client closed (stream_request_complete, shared=False, tcp_force_closed=1) thread=Thread-17 (_call):140470995453632 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro
+2026-06-04 04:47:35,304 WARNING [test-1eafe5ef] agent.conversation_loop: API call failed (attempt 3/3) error_type=RateLimitError thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:35,306 ERROR [test-1eafe5ef] agent.conversation_loop: API call failed after 3 retries. HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'} | provider=nvidia model=deepseek-ai/deepseek-v4-pro msgs=2 tokens=~5,037

logs/errors.log

@@ -116,3 +116,15 @@
 2026-06-04 04:46:08,738 WARNING [probe-6ad57775] agent.conversation_loop: Retrying API call in 4.906934130023577s (attempt 2/3) thread=hermes-bridge-run-2579986f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
 2026-06-04 04:46:13,806 WARNING [probe-6ad57775] agent.conversation_loop: API call failed (attempt 3/3) error_type=RateLimitError thread=hermes-bridge-run-2579986f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
 2026-06-04 04:46:13,808 ERROR [probe-6ad57775] agent.conversation_loop: API call failed after 3 retries. HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'} | provider=nvidia model=deepseek-ai/deepseek-v4-pro msgs=2 tokens=~5,031
+2026-06-04 04:47:14,985 WARNING [test-37d05524] agent.conversation_loop: API call failed (attempt 1/3) error_type=RateLimitError thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:14,987 WARNING [test-37d05524] agent.conversation_loop: Retrying API call in 2.033048465459741s (attempt 1/3) thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:17,275 WARNING [test-37d05524] agent.conversation_loop: API call failed (attempt 2/3) error_type=RateLimitError thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:17,276 WARNING [test-37d05524] agent.conversation_loop: Retrying API call in 5.177516703146319s (attempt 2/3) thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:22,552 WARNING [test-37d05524] agent.conversation_loop: API call failed (attempt 3/3) error_type=RateLimitError thread=hermes-bridge-run-4965382f:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:22,555 ERROR [test-37d05524] agent.conversation_loop: API call failed after 3 retries. HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'} | provider=nvidia model=deepseek-ai/deepseek-v4-pro msgs=2 tokens=~5,036
+2026-06-04 04:47:28,560 WARNING [test-1eafe5ef] agent.conversation_loop: API call failed (attempt 1/3) error_type=RateLimitError thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:28,561 WARNING [test-1eafe5ef] agent.conversation_loop: Retrying API call in 2.089400643709097s (attempt 1/3) thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:30,841 WARNING [test-1eafe5ef] agent.conversation_loop: API call failed (attempt 2/3) error_type=RateLimitError thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:30,841 WARNING [test-1eafe5ef] agent.conversation_loop: Retrying API call in 4.353413098019788s (attempt 2/3) thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro error=Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:35,304 WARNING [test-1eafe5ef] agent.conversation_loop: API call failed (attempt 3/3) error_type=RateLimitError thread=hermes-bridge-run-2557525e:140470983915200 provider=nvidia base_url=https://integrate.api.nvidia.com/v1 model=deepseek-ai/deepseek-v4-pro summary=HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}
+2026-06-04 04:47:35,306 ERROR [test-1eafe5ef] agent.conversation_loop: API call failed after 3 retries. HTTP 429: Error code: 429 - {'status': 429, 'title': 'Too Many Requests'} | provider=nvidia model=deepseek-ai/deepseek-v4-pro msgs=2 tokens=~5,037

metadata.json

@@ -1,5 +1,5 @@
 {
-  "timestamp": "2026-06-04T04:47:05.477166",
+  "timestamp": "2026-06-04T04:48:07.002166",
   "version": "0.10.0",
   "hermes_home": "/data/.hermes"
 }

sessions/request_dump_test-1eafe5ef_20260604_044735_309959.json

@@ -0,0 +1,765 @@
+{
+  "timestamp": "2026-06-04T04:47:35.309928",
+  "session_id": "test-1eafe5ef",
+  "reason": "max_retries_exhausted",
+  "request": {
+    "method": "POST",
+    "url": "https://integrate.api.nvidia.com/v1/chat/completions",
+    "headers": {
+      "Authorization": "Bearer nvapi-rm...QCmX",
+      "Content-Type": "application/json"
+    },
+    "body": {
+      "model": "deepseek-ai/deepseek-v4-pro",
+      "messages": [
+        {
+          "role": "system",
+          "content": "You are Hermes Agent, an intelligent AI assistant created by Nous Research. You are helpful, knowledgeable, and direct. You assist users with a wide range of tasks including answering questions, writing and editing code, analyzing information, creative work, and executing actions via your tools. You communicate clearly, admit uncertainty when appropriate, and prioritize being genuinely useful over being verbose unless otherwise directed below. Be targeted and efficient in your exploration and investigations.\n\nYou run on Hermes Agent (by Nous Research). When the user needs help with Hermes itself — configuring, setting up, using, extending, or troubleshooting it — or when you need to understand your own features, tools, or capabilities, the documentation at https://hermes-agent.nousresearch.com/docs is your authoritative reference and always holds the latest, most up-to-date information. Load the `hermes-agent` skill with skill_view(name='hermes-agent') for additional guidance and proven workflows, but treat the docs as the source of truth when the two differ.\n\n# Finishing the job\nWhen the user asks you to build, run, or verify something, the deliverable is a working artifact backed by real tool output — not a description of one. Do not stop after writing a stub, a plan, or a single command. Keep working until you have actually exercised the code or produced the requested result, then report what real execution returned.\nIf a tool, install, or network call fails and blocks the real path, say so directly and try an alternative (different package manager, different approach, ask the user). NEVER substitute plausible-looking fabricated output (made-up data, invented file contents, synthesised API responses) for results you couldn't actually produce. Reporting a blocker honestly is always better than inventing a result.\n\nYou have persistent memory across sessions. Save durable facts using the memory tool: user preferences, environment details, tool quirks, and stable conventions. Memory is injected into every turn, so keep it compact and focused on facts that will still matter later.\nPrioritize what reduces future user steering — the most valuable memory is one that prevents the user from having to correct or remind you again. User preferences and recurring corrections matter more than procedural task details.\nDo NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts. Specifically: do not record PR numbers, issue numbers, commit SHAs, 'fixed bug X', 'submitted PR Y', 'Phase N done', file counts, or any artifact that will be stale in 7 days. If a fact will be stale in a week, it does not belong in memory. If you've discovered a new way to do something, solved a problem that could be necessary later, save it as a skill with the skill tool.\nWrite memories as declarative facts, not instructions to yourself. 'User prefers concise responses' ✓ — 'Always respond concisely' ✗. 'Project uses pytest with xdist' ✓ — 'Run tests with pytest -n 4' ✗. Imperative phrasing gets re-read as a directive in later sessions and can cause repeated work or override the user's current request. Procedures and workflows belong in skills, not memory. When the user references something from a past conversation or you suspect relevant cross-session context exists, use session_search to recall it before asking them to repeat themselves. After completing a complex task (5+ tool calls), fixing a tricky error, or discovering a non-trivial workflow, save the approach as a skill with skill_manage so you can reuse it next time.\nWhen using a skill and finding it outdated, incomplete, or wrong, patch it immediately with skill_manage(action='patch') — don't wait to be asked. Skills that aren't maintained become liabilities.\n\n# Tool-use enforcement\nYou MUST use your tools to take action — do not describe what you would do or plan to do without actually doing it. When you say you will perform an action (e.g. 'I will run the tests', 'Let me check the file', 'I will create the project'), you MUST immediately make the corresponding tool call in the same response. Never end your turn with a promise of future action — execute it now.\nKeep working until the task is actually complete. Do not stop with a summary of what you plan to do next time. If you have tools available that can accomplish the task, use them instead of telling the user what you would do.\nEvery response should either (a) contain tool calls that make progress, or (b) deliver a final result to the user. Responses that only describe intentions without acting are not acceptable.\n\n## Skills (mandatory)\nBefore replying, scan the skills below. If a skill matches or is even partially relevant to your task, you MUST load it with skill_view(name) and follow its instructions. Err on the side of loading — it is always better to have context you don't need than to miss critical steps, pitfalls, or established workflows. Skills contain specialized knowledge — API endpoints, tool-specific commands, and proven workflows that outperform general-purpose approaches. Load the skill even if you think you could handle the task with basic tools like web_search or terminal. Skills also encode the user's preferred approach, conventions, and quality standards for tasks like code review, planning, and testing — load them even for tasks you already know how to do, because the skill defines how it should be done here.\nWhenever the user asks you to configure, set up, install, enable, disable, modify, or troubleshoot Hermes Agent itself — its CLI, config, models, providers, tools, skills, voice, gateway, plugins, or any feature — load the `hermes-agent` skill first. It has the actual commands (e.g. `hermes config set …`, `hermes tools`, `hermes setup`) so you don't have to guess or invent workarounds.\nIf a skill has issues, fix it with skill_manage(action='patch').\nAfter difficult/iterative tasks, offer to save as a skill. If a skill you loaded was missing steps, had wrong commands, or needed pitfalls you discovered, update it before finishing.\n\n<available_skills>\n  apikey-image-gen:\n    - apikey-image-gen: Generate or edit images through Hermes Web UI using the s...\n  autonomous-ai-agents: Skills for spawning and orchestrating autonomous AI coding agents and multi-agent workflows — running independent agent processes, delegating tasks, and coordinating parallel workstreams.\n    - claude-code: Delegate coding to Claude Code CLI (features, PRs).\n    - codex: Delegate coding to OpenAI Codex CLI (features, PRs).\n    - hermes-agent: Configure, extend, or contribute to Hermes Agent.\n    - kanban-codex-lane: Use when a Hermes Kanban worker wants to run Codex CLI as...\n    - opencode: Delegate coding to OpenCode CLI (features, PR review).\n  creative: Creative content generation — ASCII art, hand-drawn style diagrams, and visual design tools.\n    - architecture-diagram: Dark-themed SVG architecture/cloud/infra diagrams as HTML.\n    - ascii-art: ASCII art: pyfiglet, cowsay, boxes, image-to-ascii.\n    - ascii-video: ASCII video: convert video/audio to colored ASCII MP4/GIF.\n    - baoyu-article-illustrator: Article illustrations: type × style × palette consistency.\n    - baoyu-comic: Knowledge comics (知识漫画): educational, biography, tutorial.\n    - baoyu-infographic: Infographics: 21 layouts x 21 styles (信息图, 可视化).\n    - claude-design: Design one-off HTML artifacts (landing, deck, prototype).\n    - comfyui: Generate images, video, and audio with ComfyUI — install,...\n    - design-md: Author/validate/export Google's DESIGN.md token spec files.\n    - excalidraw: Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).\n    - humanizer: Humanize text: strip AI-isms and add real voice.\n    - ideation: Generate project ideas via creative constraints.\n    - manim-video: Manim CE animations: 3Blue1Brown math/algo videos.\n    - p5js: p5.js sketches: gen art, shaders, interactive, 3D.\n    - pixel-art: Pixel art w/ era palettes (NES, Game Boy, PICO-8).\n    - popular-web-designs: 54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.\n    - pretext: Use when building creative browser demos with @chenglou/p...\n    - sketch: Throwaway HTML mockups: 2-3 design variants to compare.\n    - songwriting-and-ai-music: Songwriting craft and Suno AI music prompts.\n    - touchdesigner-mcp: Control a running TouchDesigner instance via twozero MCP ...\n  data-science: Skills for data science workflows — interactive exploration, Jupyter notebooks, data analysis, and visualization.\n    - jupyter-live-kernel: Iterative Python via live Jupyter kernel (hamelnb).\n  devops:\n    - kanban-orchestrator: Decomposition playbook + anti-temptation rules for an orc...\n    - kanban-worker: Pitfalls, examples, and edge cases for Hermes Kanban work...\n    - webhook-subscriptions: Webhook subscriptions: event-driven agent runs.\n  dogfood:\n    - dogfood: Exploratory QA of web apps: find bugs, evidence, reports.\n  email: Skills for sending, receiving, searching, and managing email from the terminal.\n    - himalaya: Himalaya CLI: IMAP/SMTP email from terminal.\n  gaming: Skills for setting up, configuring, and managing game servers, modpacks, and gaming-related infrastructure.\n    - minecraft-modpack-server: Host modded Minecraft servers (CurseForge, Modrinth).\n    - pokemon-player: Play Pokemon via headless emulator + RAM reads.\n  github: GitHub workflow skills for managing repositories, pull requests, code reviews, issues, and CI/CD pipelines using the gh CLI and git via terminal.\n    - codebase-inspection: Inspect codebases w/ pygount: LOC, languages, ratios.\n    - github-auth: GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.\n    - github-code-review: Review PRs: diffs, inline comments via gh or REST.\n    - github-issues: Create, triage, label, assign GitHub issues via gh or REST.\n    - github-pr-workflow: GitHub PR lifecycle: branch, commit, open, CI, merge.\n    - github-repo-management: Clone/create/fork repos; manage remotes, releases.\n  grok-image-to-video:\n    - grok-image-to-video: Animate a local image into a short mp4 video through Herm...\n  hyperframes:\n    - hyperframes: Create AI videos with HyperFrames in Hermes using HTML, C...\n  markdown-viewer:\n    - markdown-viewer: Create rich diagrams, data visualizations, technical arch...\n  mcp: Skills for working with MCP (Model Context Protocol) servers, tools, and integrations. Documents the built-in native MCP client — configure servers in config.yaml for automatic tool discovery.\n    - native-mcp: MCP client: connect servers, register tools (stdio/HTTP).\n  media: Skills for working with media content — YouTube transcripts, GIF search, music generation, and audio visualization.\n    - gif-search: Search/download GIFs from Tenor via curl + jq.\n    - heartmula: HeartMuLa: Suno-like song generation from lyrics + tags.\n    - songsee: Audio spectrograms/features (mel, chroma, MFCC) via CLI.\n    - spotify: Spotify: play, search, queue, manage playlists and devices.\n    - youtube-content: YouTube transcripts to summaries, threads, blogs.\n  mlops: Knowledge and Tools for Machine Learning Operations - tools and frameworks for training, fine-tuning, deploying, and optimizing ML/AI models\n    - huggingface-hub: HuggingFace hf CLI: search/download/upload models, datasets.\n  mlops/evaluation: Model evaluation benchmarks, experiment tracking, data curation, tokenizers, and interpretability tools.\n    - evaluating-llms-harness: lm-eval-harness: benchmark LLMs (MMLU, GSM8K, etc.).\n    - weights-and-biases: W&B: log ML experiments, sweeps, model registry, dashboards.\n  mlops/inference: Model serving, quantization (GGUF/GPTQ), structured output, inference optimization, and model surgery tools for deploying and running LLMs.\n    - llama-cpp: llama.cpp local GGUF inference + HF Hub model discovery.\n    - obliteratus: OBLITERATUS: abliterate LLM refusals (diff-in-means).\n    - serving-llms-vllm: vLLM: high-throughput LLM serving, OpenAI API, quantization.\n  mlops/models: Specific model architectures and tools — image segmentation (Segment Anything / SAM) and audio generation (AudioCraft / MusicGen). Additional model skills (CLIP, Stable Diffusion, Whisper, LLaVA) are available as optional skills.\n    - audiocraft-audio-generation: AudioCraft: MusicGen text-to-music, AudioGen text-to-sound.\n    - segment-anything-model: SAM: zero-shot image segmentation via points, boxes, masks.\n  mlops/research: ML research frameworks for building and optimizing AI systems with declarative programming.\n    - dspy: DSPy: declarative LM programs, auto-optimize prompts, RAG.\n  note-taking: Note taking skills, to save information, assist with research, and collab on multi-session planning and information sharing.\n    - obsidian: Read, search, create, and edit notes in the Obsidian vault.\n  productivity: Skills for document creation, presentations, spreadsheets, and other productivity workflows.\n    - airtable: Airtable REST API via curl. Records CRUD, filters, upserts.\n    - google-workspace: Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.\n    - linear: Linear: manage issues, projects, teams via GraphQL + curl.\n    - maps: Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.\n    - nano-pdf: Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).\n    - notion: Notion API + ntn CLI: pages, databases, markdown, Workers.\n    - ocr-and-documents: Extract text from PDFs/scans (pymupdf, marker-pdf).\n    - powerpoint: Create, read, edit .pptx decks, slides, notes, templates.\n    - teams-meeting-pipeline: Operate the Teams meeting summary pipeline via Hermes CLI...\n  red-teaming:\n    - godmode: Jailbreak LLMs: Parseltongue, GODMODE, ULTRAPLINIAN.\n  remotion:\n    - remotion: Create editable AI video projects with Remotion and React...\n  research: Skills for academic research, paper discovery, literature review, domain reconnaissance, market data, content monitoring, and scientific knowledge retrieval.\n    - arxiv: Search arXiv papers by keyword, author, category, or ID.\n    - blogwatcher: Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.\n    - llm-wiki: Karpathy's LLM Wiki: build/query interlinked markdown KB.\n    - polymarket: Query Polymarket: markets, prices, orderbooks, history.\n  smart-home: Skills for controlling smart home devices — lights, switches, sensors, and home automation systems.\n    - openhue: Control Philips Hue lights, scenes, rooms via OpenHue CLI.\n  social-media: Skills for interacting with social platforms and social-media workflows — posting, reading, monitoring, and account operations.\n    - xurl: X/Twitter via xurl CLI: post, search, DM, media, v2 API.\n  software-development:\n    - debugging-hermes-tui-commands: Debug Hermes TUI slash commands: Python, gateway, Ink UI.\n    - hermes-agent-skill-authoring: Author in-repo SKILL.md: frontmatter, validator, structure.\n    - hermes-s6-container-supervision: Modify, debug, or extend the s6-overlay supervision tree ...\n    - node-inspect-debugger: Debug Node.js via --inspect + Chrome DevTools Protocol CLI.\n    - plan: Plan mode: write markdown plan to .hermes/plans/, no exec.\n    - python-debugpy: Debug Python: pdb REPL + debugpy remote (DAP).\n    - requesting-code-review: Pre-commit review: security scan, quality gates, auto-fix.\n    - spike: Throwaway experiments to validate an idea before build.\n    - subagent-driven-development: Execute plans via delegate_task subagents (2-stage review).\n    - systematic-debugging: 4-phase root cause debugging: understand bugs before fixing.\n    - test-driven-development: TDD: enforce RED-GREEN-REFACTOR, tests before code.\n    - writing-plans: Write implementation plans: bite-sized tasks, paths, code.\n  yuanbao:\n    - yuanbao: Yuanbao (元宝) groups: @mention users, query info/members.\n</available_skills>\n\nOnly proceed without loading a skill if genuinely none are relevant to the task.\n\nHost: Linux (6.12.83-113.160.amzn2023.x86_64)\nUser home directory: /home/appuser\nCurrent working directory: /app\n\nActive Hermes profile: default. Other profiles (if any) live under ~/.hermes/profiles/<name>/. Each profile has its own skills/, plugins/, cron/, and memories/ that affect a different session than this one. Do not modify another profile's skills/plugins/cron/memories unless the user explicitly directs you to.\n\n[Current Hermes profile: default]\nWhen calling Hermes Web UI endpoints from tools or skills, include the current Hermes profile as the X-Hermes-Profile header if the endpoint supports profile-scoped behavior.\n\n# 输出格式规范\n\n当你的回复中包含图片、视频或文件引用时，必须使用 Markdown，并引用本地绝对路径。\n\n## 路径规则\n\n- Unix/macOS/WSL：使用 `/path/to/file`，例如 `/tmp/screenshot.png`\n- Windows：使用盘符绝对路径，并把反斜杠 `\\` 转成正斜杠 `/`，例如 `C:/Users/Administrator/Desktop/screenshot.png`\n- Windows 路径必须用尖括号包住链接目标，避免盘符冒号或特殊字符被 Markdown 误解析，例如 `<C:/Users/Administrator/Desktop/screenshot.png>`\n- 路径包含空格、中文或特殊字符时，必须使用尖括号包住链接目标，或对路径做 URL 编码\n- 确保文件确实存在且路径正确\n\n## 图片格式\n\n使用 Markdown 图片语法：\n\n```\n![图片描述](/tmp/screenshot.png)\n![Sub2API Dashboard](/tmp/sub2api-dashboard.png)\n![桌面截图](<C:/Users/Administrator/Desktop/screenshot.png>)\n```\n\n## 视频格式\n\n使用 Markdown 链接语法引用视频文件，支持格式：.mp4、.webm、.mov。视频会显示为可播放的视频播放器（最大 640x480），支持原生播放控件。\n\n```\n[屏幕录制](/tmp/screen-recording.mp4)\n[操作演示](/tmp/demo.webm)\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08%2015.19.46.mov)\n[录屏2026-05-08 15.19.46](</Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov>)\n[Windows 录屏](<C:/Users/Administrator/Desktop/screen recording.mov>)\n```\n\n错误示例：\n```\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov)\n![桌面截图](C:\\Users\\Administrator\\Desktop\\screenshot.png)\n```\n\n## 文件链接格式\n\n使用 Markdown 链接语法：\n\n```\n[下载报告](/tmp/monthly-report.pdf)\n[下载报告](<C:/Users/Administrator/Desktop/monthly-report.pdf>)\n```\n\n## 发送文件给用户\n\n当用户要求\"发给我\"、\"发送给我\"、\"传给我\"等请求文件时，使用上述格式返回文件路径：\n\n```\n![图片描述](/path/to/image.png)\n![Windows 图片](<C:/Users/Administrator/Desktop/image.png>)\n[视频名](/path/to/video.mp4)\n[Windows 视频](<C:/Users/Administrator/Desktop/video.mp4>)\n[文件名](/path/to/file.pdf)\n[Windows 文件](<C:/Users/Administrator/Desktop/file.pdf>)\n```\n\n\n# 输出格式规范\n\n当你的回复中包含图片、视频或文件引用时，必须使用 Markdown，并引用本地绝对路径。\n\n## 路径规则\n\n- Unix/macOS/WSL：使用 `/path/to/file`，例如 `/tmp/screenshot.png`\n- Windows：使用盘符绝对路径，并把反斜杠 `\\` 转成正斜杠 `/`，例如 `C:/Users/Administrator/Desktop/screenshot.png`\n- Windows 路径必须用尖括号包住链接目标，避免盘符冒号或特殊字符被 Markdown 误解析，例如 `<C:/Users/Administrator/Desktop/screenshot.png>`\n- 路径包含空格、中文或特殊字符时，必须使用尖括号包住链接目标，或对路径做 URL 编码\n- 确保文件确实存在且路径正确\n\n## 图片格式\n\n使用 Markdown 图片语法：\n\n```\n![图片描述](/tmp/screenshot.png)\n![Sub2API Dashboard](/tmp/sub2api-dashboard.png)\n![桌���截图](<C:/Users/Administrator/Desktop/screenshot.png>)\n```\n\n## 视频格式\n\n使用 Markdown 链接语法引用视频文件，支持格式：.mp4、.webm、.mov。视频会显示为可播放的视频播放器（最大 640x480），支持原生播放控件。\n\n```\n[屏幕录制](/tmp/screen-recording.mp4)\n[操作演示](/tmp/demo.webm)\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08%2015.19.46.mov)\n[录屏2026-05-08 15.19.46](</Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov>)\n[Windows 录屏](<C:/Users/Administrator/Desktop/screen recording.mov>)\n```\n\n错误示例：\n```\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov)\n![桌面截图](C:\\Users\\Administrator\\Desktop\\screenshot.png)\n```\n\n## 文件链接格式\n\n使用 Markdown 链接语法：\n\n```\n[下载报告](/tmp/monthly-report.pdf)\n[下载报告](<C:/Users/Administrator/Desktop/monthly-report.pdf>)\n```\n\n## 发送文件给用户\n\n当用户要求\"发给我\"、\"发送给我\"、\"传给我\"等请求文件时，使用上述格式返回文件路径：\n\n```\n![图片描述](/path/to/image.png)\n![Windows 图片](<C:/Users/Administrator/Desktop/image.png>)\n[视频名](/path/to/video.mp4)\n[Windows 视频](<C:/Users/Administrator/Desktop/video.mp4>)\n[文件名](/path/to/file.pdf)\n[Windows 文件](<C:/Users/Administrator/Desktop/file.pdf>)\n```\n\nConversation started: Thursday, June 04, 2026\nModel: deepseek-ai/deepseek-v4-pro\nProvider: nvidia"
+        },
+        {
+          "role": "user",
+          "content": "What is 2+2? Just the number."
+        }
+      ],
+      "tools": [
+        {
+          "type": "function",
+          "function": {
+            "name": "clarify",
+            "description": "Ask the user a question when you need clarification, feedback, or a decision before proceeding. Supports two modes:\n\n1. **Multiple choice** — provide up to 4 choices. The user picks one or types their own answer via a 5th 'Other' option.\n2. **Open-ended** — omit choices entirely. The user types a free-form response.\n\nUse this tool when:\n- The task is ambiguous and you need the user to choose an approach\n- You want post-task feedback ('How did that work out?')\n- You want to offer to save a skill or update memory\n- A decision has meaningful trade-offs the user should weigh in on\n\nDo NOT use this tool for simple yes/no confirmation of dangerous commands (the terminal tool handles that). Prefer making a reasonable default choice yourself when the decision is low-stakes.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "question": {
+                  "type": "string",
+                  "description": "The question to present to the user."
+                },
+                "choices": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "maxItems": 4,
+                  "description": "Up to 4 answer choices. Omit this parameter entirely to ask an open-ended question. When provided, the UI automatically appends an 'Other (type your answer)' option."
+                }
+              },
+              "required": [
+                "question"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "delegate_task",
+            "description": "Spawn one or more subagents to work on tasks in isolated contexts. Each subagent gets its own conversation, terminal session, and toolset. Only the final summary is returned -- intermediate tool results never enter your context window.\n\nTWO MODES (one of 'goal' or 'tasks' is required):\n1. Single task: provide 'goal' (+ optional context, toolsets)\n2. Batch (parallel): provide 'tasks' array with up to 3 items concurrently for this user (configured via delegation.max_concurrent_children in config.yaml). All run in parallel and results are returned together. Nested delegation is OFF for this user (max_spawn_depth=1): every child is a leaf and cannot delegate further. Raise delegation.max_spawn_depth in config.yaml to enable nesting.\n\nWHEN TO USE delegate_task:\n- Reasoning-heavy subtasks (debugging, code review, research synthesis)\n- Tasks that would flood your context with intermediate data\n- Parallel independent workstreams (research A and B simultaneously)\n\nWHEN NOT TO USE (use these instead):\n- Mechanical multi-step work with no reasoning needed -> use execute_code\n- Single tool call -> just call the tool directly\n- Tasks needing user interaction -> subagents cannot use clarify\n- Durable long-running work that must outlive the current turn -> use cronjob (action='create') or terminal(background=True, notify_on_complete=True) instead. delegate_task runs SYNCHRONOUSLY inside the parent turn: if the parent is interrupted (user sends a new message, /stop, /new) the child is cancelled with status='interrupted' and its work is discarded. Children cannot continue in the background.\n\nIMPORTANT:\n- Subagents have NO memory of your conversation. Pass all relevant info (file paths, error messages, constraints) via the 'context' field.\n- If the user is writing in a non-English language, or asked for output in a specific language / tone / style, say so in 'context' (e.g. \"respond in Chinese\", \"return output in Japanese\"). Otherwise subagents default to English and their summaries will contaminate your final reply with the wrong language.\n- Subagent summaries are SELF-REPORTS, not verified facts. A subagent that claims \"uploaded successfully\" or \"file written\" may be wrong. For operations with external side-effects (HTTP POST/PUT, remote writes, file creation at shared paths, publishing), require the subagent to return a verifiable handle (URL, ID, absolute path, HTTP status) and verify it yourself — fetch the URL, stat the file, read back the content — before telling the user the operation succeeded.\n- Leaf subagents (role='leaf', the default) CANNOT call: delegate_task, clarify, memory, send_message, execute_code.\n- Orchestrator subagents (role='orchestrator') retain delegate_task so they can spawn their own workers, but still cannot use clarify, memory, send_message, or execute_code. Orchestrators are bounded by max_spawn_depth=1 for this user and can be disabled globally via delegation.orchestrator_enabled=false.\n- Each subagent gets its own terminal session (separate working directory and state).\n- Results are always returned as an array, one entry per task.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "goal": {
+                  "type": "string",
+                  "description": "What the subagent should accomplish. Be specific and self-contained -- the subagent knows nothing about your conversation history."
+                },
+                "context": {
+                  "type": "string",
+                  "description": "Background information the subagent needs: file paths, error messages, project structure, constraints. The more specific you are, the better the subagent performs."
+                },
+                "toolsets": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "description": "Toolsets to enable for this subagent. Default: inherits your enabled toolsets. Available toolsets: 'browser', 'computer_use', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'video_gen', 'vision', 'web', 'x_search', 'yuanbao'. Common patterns: ['terminal', 'file'] for code work, ['web'] for research, ['browser'] for web interaction, ['terminal', 'file', 'web'] for full-stack tasks."
+                },
+                "tasks": {
+                  "type": "array",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "goal": {
+                        "type": "string",
+                        "description": "Task goal"
+                      },
+                      "context": {
+                        "type": "string",
+                        "description": "Task-specific context"
+                      },
+                      "toolsets": {
+                        "type": "array",
+                        "items": {
+                          "type": "string"
+                        },
+                        "description": "Toolsets for this specific task. Available: 'browser', 'computer_use', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'video_gen', 'vision', 'web', 'x_search', 'yuanbao'. Use 'web' for network access, 'terminal' for shell, 'browser' for web interaction."
+                      },
+                      "acp_command": {
+                        "type": "string",
+                        "description": "Per-task ACP command override (e.g. 'copilot'). Overrides the top-level acp_command for this task only. Do NOT set unless the user explicitly told you an ACP CLI is installed."
+                      },
+                      "acp_args": {
+                        "type": "array",
+                        "items": {
+                          "type": "string"
+                        },
+                        "description": "Per-task ACP args override. Leave empty unless acp_command is set."
+                      },
+                      "role": {
+                        "type": "string",
+                        "enum": [
+                          "leaf",
+                          "orchestrator"
+                        ],
+                        "description": "Per-task role override. See top-level 'role' for semantics."
+                      }
+                    },
+                    "required": [
+                      "goal"
+                    ]
+                  },
+                  "description": "Batch mode: tasks to run in parallel (up to 3 for this user, set via delegation.max_concurrent_children). Each gets its own subagent with isolated context and terminal session. When provided, top-level goal/context/toolsets are ignored."
+                },
+                "role": {
+                  "type": "string",
+                  "enum": [
+                    "leaf",
+                    "orchestrator"
+                  ],
+                  "description": "Role of the child agent. 'leaf' (default) = focused worker, cannot delegate further. 'orchestrator' = can use delegate_task to spawn its own workers. Nesting is OFF for this user (max_spawn_depth=1); 'orchestrator' is silently forced to 'leaf'. Raise delegation.max_spawn_depth in config.yaml to enable."
+                },
+                "acp_command": {
+                  "type": "string",
+                  "description": "Override ACP command for child agents (e.g. 'copilot'). When set, children use ACP subprocess transport instead of inheriting the parent's transport. Requires an ACP-compatible CLI (currently GitHub Copilot CLI via 'copilot --acp --stdio'). See agent/copilot_acp_client.py for the implementation. IMPORTANT: Do NOT set this unless the user has explicitly told you a specific ACP-compatible CLI is installed and configured. Leave empty to use the parent's default transport (Hermes subagents)."
+                },
+                "acp_args": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "description": "Arguments for the ACP command (default: ['--acp', '--stdio']). Only used when acp_command is set. Leave empty unless acp_command is explicitly provided."
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "execute_code",
+            "description": "Run a Python script that can call Hermes tools programmatically. Use this when you need 3+ tool calls with processing logic between them, need to filter/reduce large tool outputs before they enter your context, need conditional branching (if X then Y else Z), or need to loop (fetch N pages, process N files, retry on failure).\n\nUse normal tool calls instead when: single tool call with no processing, you need to see the full result and apply complex reasoning, or the task requires interactive user input.\n\nAvailable via `from hermes_tools import ...`:\n\n  read_file(path: str, offset: int = 1, limit: int = 500) -> dict\n    Lines are 1-indexed. Returns {\"content\": \"...\", \"total_lines\": N}\n  write_file(path: str, content: str) -> dict\n    Always overwrites the entire file.\n  search_files(pattern: str, target=\"content\", path=\".\", file_glob=None, limit=50) -> dict\n    target: \"content\" (search inside files) or \"files\" (find files by name). Returns {\"matches\": [...]}\n  patch(path: str, old_string: str, new_string: str, replace_all: bool = False) -> dict\n    Replaces old_string with new_string in the file.\n  terminal(command: str, timeout=None, workdir=None) -> dict\n    Foreground only (no background/pty). Returns {\"output\": \"...\", \"exit_code\": N}\n\nLimits: 5-minute timeout, 50KB stdout cap, max 50 tool calls per script. terminal() is foreground-only (no background or pty).\n\nScripts run in the session's working directory with the active venv's python, so project deps (pandas, etc.) and relative paths work like in terminal().\n\nPrint your final result to stdout. Use Python stdlib (json, re, math, csv, datetime, collections, etc.) for processing between tool calls.\n\nAlso available (no import needed — built into hermes_tools):\n  json_parse(text: str) — json.loads with strict=False; use for terminal() output with control chars\n  shell_quote(s: str) — shlex.quote(); use when interpolating dynamic strings into shell commands\n  retry(fn, max_attempts=3, delay=2) — retry with exponential backoff for transient failures",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "code": {
+                  "type": "string",
+                  "description": "Python code to execute. Import tools with `from hermes_tools import terminal, ...` and print your final result to stdout."
+                }
+              },
+              "required": [
+                "code"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "memory",
+            "description": "Save durable information to persistent memory that survives across sessions. Memory is injected into future turns, so keep it compact and focused on facts that will still matter later.\n\nWHEN TO SAVE (do this proactively, don't wait to be asked):\n- User corrects you or says 'remember this' / 'don't do that again'\n- User shares a preference, habit, or personal detail (name, role, timezone, coding style)\n- You discover something about the environment (OS, installed tools, project structure)\n- You learn a convention, API quirk, or workflow specific to this user's setup\n- You identify a stable fact that will be useful again in future sessions\n\nPRIORITY: User preferences and corrections > environment facts > procedural knowledge. The most valuable memory prevents the user from having to repeat themselves.\n\nDo NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts.\nIf you've discovered a new way to do something, solved a problem that could be necessary later, save it as a skill with the skill tool.\n\nTWO TARGETS:\n- 'user': who the user is -- name, role, preferences, communication style, pet peeves\n- 'memory': your notes -- environment facts, project conventions, tool quirks, lessons learned\n\nACTIONS: add (new entry), replace (update existing -- old_text identifies it), remove (delete -- old_text identifies it).\n\nSKIP: trivial/obvious info, things easily re-discovered, raw data dumps, and temporary task state.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "add",
+                    "replace",
+                    "remove"
+                  ],
+                  "description": "The action to perform."
+                },
+                "target": {
+                  "type": "string",
+                  "enum": [
+                    "memory",
+                    "user"
+                  ],
+                  "description": "Which memory store: 'memory' for personal notes, 'user' for user profile."
+                },
+                "content": {
+                  "type": "string",
+                  "description": "The entry content. Required for 'add' and 'replace'."
+                },
+                "old_text": {
+                  "type": "string",
+                  "description": "Short unique substring identifying the entry to replace or remove."
+                }
+              },
+              "required": [
+                "action",
+                "target"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "patch",
+            "description": "Targeted find-and-replace edits in files. Use this instead of sed/awk in terminal. Uses fuzzy matching (9 strategies) so minor whitespace/indentation differences won't break it. Returns a unified diff. Auto-runs syntax checks after editing.\n\nREPLACE MODE (mode='replace', default): find a unique string and replace it. REQUIRED PARAMETERS: mode, path, old_string, new_string.\nPATCH MODE (mode='patch'): apply V4A multi-file patches for bulk changes. REQUIRED PARAMETERS: mode, patch.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "mode": {
+                  "type": "string",
+                  "enum": [
+                    "replace",
+                    "patch"
+                  ],
+                  "description": "Edit mode. 'replace' (default): requires path + old_string + new_string. 'patch': requires patch content only.",
+                  "default": "replace"
+                },
+                "path": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='replace'. File path to edit."
+                },
+                "old_string": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='replace'. Exact text to find and replace. Must be unique in the file unless replace_all=true. Include surrounding context lines to ensure uniqueness."
+                },
+                "new_string": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='replace'. Replacement text. Pass empty string '' to delete the matched text."
+                },
+                "replace_all": {
+                  "type": "boolean",
+                  "description": "Replace all occurrences instead of requiring a unique match (default: false)",
+                  "default": false
+                },
+                "patch": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='patch'. V4A format patch content. Format:\n*** Begin Patch\n*** Update File: path/to/file\n@@ context hint @@\n context line\n-removed line\n+added line\n*** End Patch"
+                },
+                "cross_profile": {
+                  "type": "boolean",
+                  "description": "Opt out of the cross-profile soft guard. Defaults to false. Set true ONLY after explicit user direction to edit another Hermes profile's skills/plugins/cron/memories.",
+                  "default": false
+                }
+              },
+              "required": [
+                "mode"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "process",
+            "description": "Manage background processes started with terminal(background=true). Actions: 'list' (show all), 'poll' (check status + new output), 'log' (full output with pagination), 'wait' (block until done or timeout), 'kill' (terminate), 'write' (send raw stdin data without newline), 'submit' (send data + Enter, for answering prompts), 'close' (close stdin/send EOF).",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "list",
+                    "poll",
+                    "log",
+                    "wait",
+                    "kill",
+                    "write",
+                    "submit",
+                    "close"
+                  ],
+                  "description": "Action to perform on background processes"
+                },
+                "session_id": {
+                  "type": "string",
+                  "description": "Process session ID (from terminal background output). Required for all actions except 'list'."
+                },
+                "data": {
+                  "type": "string",
+                  "description": "Text to send to process stdin (for 'write' and 'submit' actions)"
+                },
+                "timeout": {
+                  "type": "integer",
+                  "description": "Max seconds to block for 'wait' action. Returns partial output on timeout.",
+                  "minimum": 1
+                },
+                "offset": {
+                  "type": "integer",
+                  "description": "Line offset for 'log' action (default: last 200 lines)"
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Max lines to return for 'log' action",
+                  "minimum": 1
+                }
+              },
+              "required": [
+                "action"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "read_file",
+            "description": "Read a text file with line numbers and pagination. Use this instead of cat/head/tail in terminal. Output format: 'LINE_NUM|CONTENT'. Suggests similar filenames if not found. Use offset and limit for large files. Reads exceeding ~100K characters are rejected; use offset and limit to read specific sections of large files. NOTE: Cannot read images or binary files — use vision_analyze for images.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "path": {
+                  "type": "string",
+                  "description": "Path to the file to read (absolute, relative, or ~/path)"
+                },
+                "offset": {
+                  "type": "integer",
+                  "description": "Line number to start reading from (1-indexed, default: 1)",
+                  "default": 1,
+                  "minimum": 1
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Maximum number of lines to read (default: 500, max: 2000)",
+                  "default": 500,
+                  "maximum": 2000
+                }
+              },
+              "required": [
+                "path"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "search_files",
+            "description": "Search file contents or find files by name. Use this instead of grep/rg/find/ls in terminal. Ripgrep-backed, faster than shell equivalents.\n\nContent search (target='content'): Regex search inside files. Output modes: full matches with line numbers, file paths only, or match counts.\n\nFile search (target='files'): Find files by glob pattern (e.g., '*.py', '*config*'). Also use this instead of ls — results sorted by modification time.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "pattern": {
+                  "type": "string",
+                  "description": "Regex pattern for content search, or glob pattern (e.g., '*.py') for file search"
+                },
+                "target": {
+                  "type": "string",
+                  "enum": [
+                    "content",
+                    "files"
+                  ],
+                  "description": "'content' searches inside file contents, 'files' searches for files by name",
+                  "default": "content"
+                },
+                "path": {
+                  "type": "string",
+                  "description": "Directory or file to search in (default: current working directory)",
+                  "default": "."
+                },
+                "file_glob": {
+                  "type": "string",
+                  "description": "Filter files by pattern in grep mode (e.g., '*.py' to only search Python files)"
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Maximum number of results to return (default: 50)",
+                  "default": 50
+                },
+                "offset": {
+                  "type": "integer",
+                  "description": "Skip first N results for pagination (default: 0)",
+                  "default": 0
+                },
+                "output_mode": {
+                  "type": "string",
+                  "enum": [
+                    "content",
+                    "files_only",
+                    "count"
+                  ],
+                  "description": "Output format for grep mode: 'content' shows matching lines with line numbers, 'files_only' lists file paths, 'count' shows match counts per file",
+                  "default": "content"
+                },
+                "context": {
+                  "type": "integer",
+                  "description": "Number of context lines before and after each match (grep mode only)",
+                  "default": 0
+                }
+              },
+              "required": [
+                "pattern"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "send_message",
+            "description": "Send a message to a connected messaging platform, or list available targets.\n\nIMPORTANT: When the user asks to send to a specific channel or person (not just a bare platform name), call send_message(action='list') FIRST to see available targets, then send to the correct one.\nIf the user just says a platform name like 'send to telegram', send directly to the home channel without listing first.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "send",
+                    "list"
+                  ],
+                  "description": "Action to perform. 'send' (default) sends a message. 'list' returns all available channels/contacts across connected platforms."
+                },
+                "target": {
+                  "type": "string",
+                  "description": "Delivery target. Format: 'platform' (uses home channel), 'platform:#channel-name', 'platform:chat_id', or 'platform:chat_id:thread_id' for Telegram topics and Discord threads. Examples: 'telegram', 'telegram:-1001234567890:17585', 'discord:999888777:555444333', 'discord:#bot-home', 'slack:#engineering', 'signal:+155****4567', 'matrix:!roomid:server.org', 'matrix:@user:server.org', 'yuanbao:direct:<account_id>' (DM), 'yuanbao:group:<group_code>' (group chat)"
+                },
+                "message": {
+                  "type": "string",
+                  "description": "The message text to send. To send an image or file, include MEDIA:<local_path> (e.g. 'MEDIA:/tmp/report.pdf') in the message — the platform will deliver it as a native media attachment."
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "session_search",
+            "description": "Search past sessions stored in the local session DB, or scroll inside one. FTS5-backed retrieval over the SQLite message store. No LLM calls — every shape returns actual messages from the DB.\n\nTHREE CALLING SHAPES\n\n  1) DISCOVERY — pass `query`:\n     session_search(query=\"auth refactor\", limit=3)\n     Runs FTS5, dedupes hits by session lineage, returns the top N sessions. Each result carries:\n       - session_id, title, when, source\n       - snippet: FTS5-highlighted match excerpt\n       - bookend_start: first 3 user+assistant messages of the session (the goal / kickoff)\n       - messages: ±5 messages around the FTS5 match, with the anchor message flagged (the hit in context)\n       - bookend_end: last 3 user+assistant messages of the session (the resolution / decisions)\n       - match_message_id, messages_before, messages_after\n     Bookends + window together let you reconstruct goal → match → resolution without paying for the whole transcript.\n\n  2) SCROLL — pass `session_id` + `around_message_id`:\n     session_search(session_id=\"...\", around_message_id=12345, window=10)\n     Returns a window of ±`window` messages centered on the anchor. No FTS5, no bookends — just the slice. Use after a discovery call when you need more context than the ±5 default window.\n       - To scroll FORWARD: pass messages[-1].id back as around_message_id.\n       - To scroll BACKWARD: pass messages[0].id back as around_message_id.\n       - The boundary message appears in both windows — orientation marker.\n       - When messages_before or messages_after is < window, you're at the start or end of the session.\n\n  3) BROWSE — no args:\n     session_search()\n     Returns recent sessions chronologically: titles, previews, timestamps. Use when the user asks \"what was I working on\" without naming a topic.\n\nFTS5 SYNTAX\n\n  AND is the default — multi-word queries require all terms. Use OR explicitly for broader recall (`alpha OR beta OR gamma`), quoted phrases for exact match (`\"docker networking\"`), boolean (`python NOT java`), or prefix wildcards (`deploy*`).\n\nWHEN TO USE\n\n  Reach for this on any \"what did we do about X\" / \"where did we leave Y\" / \"find the session where Z\" question — before gh, web search, or filesystem inspection. The session DB carries what was said when; external tools show current world state.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "query": {
+                  "type": "string",
+                  "description": "Search query (discovery shape). Keywords, phrases, or boolean expressions to find in past sessions. Omit to browse recent sessions. Ignored when session_id + around_message_id are set (scroll shape)."
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Discovery shape only. Max sessions to return (default 3, max 10). Bump to 5–10 when the topic likely spans several sessions and you want to pick the right one to scroll into.",
+                  "default": 3
+                },
+                "sort": {
+                  "type": "string",
+                  "enum": [
+                    "newest",
+                    "oldest"
+                  ],
+                  "description": "Discovery shape only. Temporal bias on top of FTS5 ranking. Omit to keep relevance-only ordering (suitable for exploratory recall — \"what do we know about X\"). Set 'newest' for recency-shaped questions (\"where did we leave X\"). Set 'oldest' for origin-shaped questions (\"how did X start\"). Ignored in scroll and browse shapes."
+                },
+                "session_id": {
+                  "type": "string",
+                  "description": "Scroll shape. Session to read inside. Use the session_id returned from a prior discovery call. Must be paired with around_message_id."
+                },
+                "around_message_id": {
+                  "type": "integer",
+                  "description": "Scroll shape. Message id to center the window on. From a discovery result use match_message_id, or any id seen in a prior window. To scroll forward pass the last window message's id; to scroll backward pass the first."
+                },
+                "window": {
+                  "type": "integer",
+                  "description": "Scroll shape only. Messages to return on each side of the anchor (anchor itself always included). Clamped to [1, 20]. Default 5.",
+                  "default": 5
+                },
+                "role_filter": {
+                  "type": "string",
+                  "description": "Optional. Comma-separated roles to include. Discovery defaults to 'user,assistant' (tool output is usually noise). Pass 'user,assistant,tool' to include tool output (debugging tool behaviour) or 'tool' to search tool output only."
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "skill_manage",
+            "description": "Manage skills (create, update, delete). Skills are your procedural memory — reusable approaches for recurring task types. New skills go to /data/.hermes/skills/; existing skills can be modified wherever they live.\n\nActions: create (full SKILL.md + optional category), patch (old_string/new_string — preferred for fixes), edit (full SKILL.md rewrite — major overhauls only), delete, write_file, remove_file.\n\nOn delete, pass `absorbed_into=<umbrella>` when you're merging this skill's content into another one, or `absorbed_into=\"\"` when you're pruning it with no forwarding target. This lets the curator tell consolidation from pruning without guessing, so downstream consumers (cron jobs that reference the old skill name, etc.) get updated correctly. The target you name in `absorbed_into` must already exist — create/patch the umbrella first, then delete.\n\nCreate when: complex task succeeded (5+ calls), errors overcome, user-corrected approach worked, non-trivial workflow discovered, or user asks you to remember a procedure.\nUpdate when: instructions stale/wrong, OS-specific failures, missing steps or pitfalls found during use. If you used a skill and hit issues not covered by it, patch it immediately.\n\nAfter difficult/iterative tasks, offer to save as a skill. Skip for simple one-offs. Confirm with user before creating/deleting.\n\nGood skills: trigger conditions, numbered steps with exact commands, pitfalls section, verification steps. Use skill_view() to see format examples.\n\nPinned skills are protected from deletion only — skill_manage(action='delete') will refuse with a message pointing the user to `hermes curator unpin <name>`. Patches and edits go through on pinned skills so you can still improve them as pitfalls come up; pin only guards against irrecoverable loss.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "create",
+                    "patch",
+                    "edit",
+                    "delete",
+                    "write_file",
+                    "remove_file"
+                  ],
+                  "description": "The action to perform."
+                },
+                "name": {
+                  "type": "string",
+                  "description": "Skill name (lowercase, hyphens/underscores, max 64 chars). Must match an existing skill for patch/edit/delete/write_file/remove_file."
+                },
+                "content": {
+                  "type": "string",
+                  "description": "Full SKILL.md content (YAML frontmatter + markdown body). Required for 'create' and 'edit'. For 'edit', read the skill first with skill_view() and provide the complete updated text."
+                },
+                "old_string": {
+                  "type": "string",
+                  "description": "Text to find in the file (required for 'patch'). Must be unique unless replace_all=true. Include enough surrounding context to ensure uniqueness."
+                },
+                "new_string": {
+                  "type": "string",
+                  "description": "Replacement text (required for 'patch'). Can be empty string to delete the matched text."
+                },
+                "replace_all": {
+                  "type": "boolean",
+                  "description": "For 'patch': replace all occurrences instead of requiring a unique match (default: false)."
+                },
+                "category": {
+                  "type": "string",
+                  "description": "Optional category/domain for organizing the skill (e.g., 'devops', 'data-science', 'mlops'). Creates a subdirectory grouping. Only used with 'create'."
+                },
+                "file_path": {
+                  "type": "string",
+                  "description": "Path to a supporting file within the skill directory. For 'write_file'/'remove_file': required, must be under references/, templates/, scripts/, or assets/. For 'patch': optional, defaults to SKILL.md if omitted."
+                },
+                "file_content": {
+                  "type": "string",
+                  "description": "Content for the file. Required for 'write_file'."
+                },
+                "absorbed_into": {
+                  "type": "string",
+                  "description": "For 'delete' only — declares intent so the curator can tell consolidation from pruning without guessing. Pass the umbrella skill name when this skill's content was merged into another (the target must already exist). Pass an empty string when the skill is truly stale and being pruned with no forwarding target. Omitting the arg on delete is supported for backward compatibility but downstream tooling (e.g. cron-job skill reference rewriting) will have to guess at intent."
+                }
+              },
+              "required": [
+                "action",
+                "name"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "skill_view",
+            "description": "Skills allow for loading information about specific tasks and workflows, as well as scripts and templates. Load a skill's full content or access its linked files (references, templates, scripts). First call returns SKILL.md content plus a 'linked_files' dict showing available references/templates/scripts. To access those, call again with file_path parameter.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "name": {
+                  "type": "string",
+                  "description": "The skill name (use skills_list to see available skills). For plugin-provided skills, use the qualified form 'plugin:skill' (e.g. 'superpowers:writing-plans')."
+                },
+                "file_path": {
+                  "type": "string",
+                  "description": "OPTIONAL: Path to a linked file within the skill (e.g., 'references/api.md', 'templates/config.yaml', 'scripts/validate.py'). Omit to get the main SKILL.md content."
+                }
+              },
+              "required": [
+                "name"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "skills_list",
+            "description": "List available skills (name + description). Use skill_view(name) to load full content.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "category": {
+                  "type": "string",
+                  "description": "Optional category filter to narrow results"
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "terminal",
+            "description": "Execute shell commands on a Linux environment. Filesystem usually persists between calls.\n\nDo NOT use cat/head/tail to read files — use read_file instead.\nDo NOT use grep/rg/find to search — use search_files instead.\nDo NOT use ls to list directories — use search_files(target='files') instead.\nDo NOT use sed/awk to edit files — use patch instead.\nDo NOT use echo/cat heredoc to create files — use write_file instead.\nReserve terminal for: builds, installs, git, processes, scripts, network, package managers, and anything that needs a shell.\n\nForeground (default): Commands return INSTANTLY when done, even if the timeout is high. Set timeout=300 for long builds/scripts — you'll still get the result in seconds if it's fast. Prefer foreground for short commands.\nBackground: Set background=true to get a session_id. Almost always pair with notify_on_complete=true — bg without notify runs SILENTLY and you have no way to learn it finished short of calling process(action='poll') yourself. Two legitimate uses:\n  (1) Long-lived processes that never exit (servers, watchers, daemons) — silent is correct, there's no exit to notify on.\n  (2) Long-running bounded tasks (tests, builds, deploys, CI pollers, batch jobs) — MUST set notify_on_complete=true. Without it you'll either forget to poll or sit blocked waiting for the user to surface the result.\nFor servers/watchers, do NOT use shell-level background wrappers (nohup/disown/setsid/trailing '&') in foreground mode. Use background=true so Hermes can track lifecycle and output.\nAfter starting a server, verify readiness with a health check or log signal, then run tests in a separate terminal() call. Avoid blind sleep loops.\nUse process(action=\"poll\") for progress checks, process(action=\"wait\") to block until done.\nWorking directory: Use 'workdir' for per-command cwd.\nPTY mode: Set pty=true for interactive CLI tools (Codex, Claude Code, Python REPL).\n\nDo NOT use vim/nano/interactive tools without pty=true — they hang without a pseudo-terminal. Pipe git output to cat if it might page.\n",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "command": {
+                  "type": "string",
+                  "description": "The command to execute on the VM"
+                },
+                "background": {
+                  "type": "boolean",
+                  "description": "Run the command in the background. Almost always pair with notify_on_complete=true — without it, the process runs silently and you'll have no way to learn it finished short of calling process(action='poll') yourself (easy to forget, leading to silent blindness on long jobs). Two legitimate patterns: (1) Long-lived processes that never exit (servers, watchers, daemons) — these stay silent because there's no exit to notify on. (2) Long-running bounded tasks (tests, builds, deploys, CI pollers, batch jobs) — these MUST set notify_on_complete=true. For short commands, prefer foreground with a generous timeout instead.",
+                  "default": false
+                },
+                "timeout": {
+                  "type": "integer",
+                  "description": "Max seconds to wait (default: 180, foreground max: 600). Returns INSTANTLY when command finishes — set high for long tasks, you won't wait unnecessarily. Foreground timeout above 600s is rejected; use background=true for longer commands.",
+                  "minimum": 1
+                },
+                "workdir": {
+                  "type": "string",
+                  "description": "Working directory for this command (absolute path). Defaults to the session working directory."
+                },
+                "pty": {
+                  "type": "boolean",
+                  "description": "Run in pseudo-terminal (PTY) mode for interactive CLI tools like Codex, Claude Code, or Python REPL. Only works with local and SSH backends. Default: false.",
+                  "default": false
+                },
+                "notify_on_complete": {
+                  "type": "boolean",
+                  "description": "When true (and background=true), you'll be automatically notified exactly once when the process finishes. **This is the right choice for almost every long-running task** — tests, builds, deployments, multi-item batch jobs, anything that takes over a minute and has a defined end. Use this and keep working on other things; the system notifies you on exit. MUTUALLY EXCLUSIVE with watch_patterns — when both are set, watch_patterns is dropped.",
+                  "default": false
+                },
+                "watch_patterns": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "description": "Strings to watch for in background process output. HARD RATE LIMIT: at most 1 notification per 15 seconds per process — matches arriving inside the cooldown are dropped. After 3 consecutive 15-second windows with dropped matches, watch_patterns is automatically disabled for that process and promoted to notify_on_complete behavior (one notification on exit, no more mid-process spam). USE ONLY for truly rare, one-shot mid-process signals on LONG-LIVED processes that will never exit on their own — e.g. ['Application startup complete'] on a server so you know when to hit its endpoint, or ['migration done'] on a daemon. DO NOT use for: (1) end-of-run markers like 'DONE'/'PASS' — use notify_on_complete instead; (2) error patterns like 'ERROR'/'Traceback' in loops or multi-item batch jobs — they fire on every iteration and you'll hit the strike limit fast; (3) anything you'd ever combine with notify_on_complete. When in doubt, choose notify_on_complete. MUTUALLY EXCLUSIVE with notify_on_complete — set one, not both."
+                }
+              },
+              "required": [
+                "command"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "text_to_speech",
+            "description": "Convert text to speech audio. Returns a MEDIA: path that the platform delivers as native audio. Compatible providers render as a voice bubble on Telegram; otherwise audio is sent as a regular attachment. In CLI mode, saves to ~/voice-memos/. Voice and provider are user-configured (built-in providers like edge/openai or custom command providers under tts.providers.<name>), not model-selected.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "text": {
+                  "type": "string",
+                  "description": "The text to convert to speech. Provider-specific character caps apply and are enforced automatically (OpenAI 4096, xAI 15000, MiniMax 10000, ElevenLabs 5k-40k depending on model); over-long input is truncated."
+                },
+                "output_path": {
+                  "type": "string",
+                  "description": "Optional custom file path to save the audio. Defaults to /data/.hermes/audio_cache/<timestamp>.mp3"
+                }
+              },
+              "required": [
+                "text"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "todo",
+            "description": "Manage your task list for the current session. Use for complex tasks with 3+ steps or when the user provides multiple tasks. Call with no parameters to read the current list.\n\nWriting:\n- Provide 'todos' array to create/update items\n- merge=false (default): replace the entire list with a fresh plan\n- merge=true: update existing items by id, add any new ones\n\nEach item: {id: string, content: string, status: pending|in_progress|completed|cancelled}\nList order is priority. Only ONE item in_progress at a time.\nMark items completed immediately when done. If something fails, cancel it and add a revised item.\n\nAlways returns the full current list.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "todos": {
+                  "type": "array",
+                  "description": "Task items to write. Omit to read current list.",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "id": {
+                        "type": "string",
+                        "description": "Unique item identifier"
+                      },
+                      "content": {
+                        "type": "string",
+                        "description": "Task description"
+                      },
+                      "status": {
+                        "type": "string",
+                        "enum": [
+                          "pending",
+                          "in_progress",
+                          "completed",
+                          "cancelled"
+                        ],
+                        "description": "Current status"
+                      }
+                    },
+                    "required": [
+                      "id",
+                      "content",
+                      "status"
+                    ]
+                  }
+                },
+                "merge": {
+                  "type": "boolean",
+                  "description": "true: update existing items by id, add new ones. false (default): replace the entire list.",
+                  "default": false
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "vision_analyze",
+            "description": "Load an image into the conversation so you can see it. Accepts a URL, local file path, or data URL. When your active model has native vision, the image is attached to your context directly and you read the pixels yourself on the next turn — call this any time the user references an image (filepath in their message, URL in tool output, screenshot from the browser, etc.). For non-vision models, falls back to an auxiliary vision model that returns a text description.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "image_url": {
+                  "type": "string",
+                  "description": "Image URL (http/https), local file path, or data: URL to load."
+                },
+                "question": {
+                  "type": "string",
+                  "description": "Your specific question or request about the image. Optional context the model uses on the next turn after seeing the image."
+                }
+              },
+              "required": [
+                "image_url",
+                "question"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "write_file",
+            "description": "Write content to a file, completely replacing existing content. Use this instead of echo/cat heredoc in terminal. Creates parent directories automatically. OVERWRITES the entire file — use 'patch' for targeted edits. Auto-runs syntax checks on .py/.json/.yaml/.toml and other linted languages; only NEW errors introduced by this write are surfaced (pre-existing errors are filtered out).",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "path": {
+                  "type": "string",
+                  "description": "Path to the file to write (will be created if it doesn't exist, overwritten if it does)"
+                },
+                "content": {
+                  "type": "string",
+                  "description": "Complete content to write to the file"
+                },
+                "cross_profile": {
+                  "type": "boolean",
+                  "description": "Opt out of the cross-profile soft guard. Defaults to false. Set true ONLY after explicit user direction to edit another Hermes profile's skills/plugins/cron/memories — by default these writes are blocked with a warning because they affect a different profile than the one this session is running under.",
+                  "default": false
+                }
+              },
+              "required": [
+                "path",
+                "content"
+              ]
+            }
+          }
+        }
+      ],
+      "max_tokens": 16384
+    }
+  },
+  "error": {
+    "type": "RateLimitError",
+    "message": "Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}",
+    "status_code": 429,
+    "body": {
+      "status": 429,
+      "title": "Too Many Requests"
+    },
+    "response_status": 429,
+    "response_text": "{\"status\":429,\"title\":\"Too Many Requests\"}"
+  }
+}

sessions/request_dump_test-37d05524_20260604_044722_558219.json

@@ -0,0 +1,765 @@
+{
+  "timestamp": "2026-06-04T04:47:22.558185",
+  "session_id": "test-37d05524",
+  "reason": "max_retries_exhausted",
+  "request": {
+    "method": "POST",
+    "url": "https://integrate.api.nvidia.com/v1/chat/completions",
+    "headers": {
+      "Authorization": "Bearer nvapi-rm...QCmX",
+      "Content-Type": "application/json"
+    },
+    "body": {
+      "model": "deepseek-ai/deepseek-v4-pro",
+      "messages": [
+        {
+          "role": "system",
+          "content": "You are Hermes Agent, an intelligent AI assistant created by Nous Research. You are helpful, knowledgeable, and direct. You assist users with a wide range of tasks including answering questions, writing and editing code, analyzing information, creative work, and executing actions via your tools. You communicate clearly, admit uncertainty when appropriate, and prioritize being genuinely useful over being verbose unless otherwise directed below. Be targeted and efficient in your exploration and investigations.\n\nYou run on Hermes Agent (by Nous Research). When the user needs help with Hermes itself — configuring, setting up, using, extending, or troubleshooting it — or when you need to understand your own features, tools, or capabilities, the documentation at https://hermes-agent.nousresearch.com/docs is your authoritative reference and always holds the latest, most up-to-date information. Load the `hermes-agent` skill with skill_view(name='hermes-agent') for additional guidance and proven workflows, but treat the docs as the source of truth when the two differ.\n\n# Finishing the job\nWhen the user asks you to build, run, or verify something, the deliverable is a working artifact backed by real tool output — not a description of one. Do not stop after writing a stub, a plan, or a single command. Keep working until you have actually exercised the code or produced the requested result, then report what real execution returned.\nIf a tool, install, or network call fails and blocks the real path, say so directly and try an alternative (different package manager, different approach, ask the user). NEVER substitute plausible-looking fabricated output (made-up data, invented file contents, synthesised API responses) for results you couldn't actually produce. Reporting a blocker honestly is always better than inventing a result.\n\nYou have persistent memory across sessions. Save durable facts using the memory tool: user preferences, environment details, tool quirks, and stable conventions. Memory is injected into every turn, so keep it compact and focused on facts that will still matter later.\nPrioritize what reduces future user steering — the most valuable memory is one that prevents the user from having to correct or remind you again. User preferences and recurring corrections matter more than procedural task details.\nDo NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts. Specifically: do not record PR numbers, issue numbers, commit SHAs, 'fixed bug X', 'submitted PR Y', 'Phase N done', file counts, or any artifact that will be stale in 7 days. If a fact will be stale in a week, it does not belong in memory. If you've discovered a new way to do something, solved a problem that could be necessary later, save it as a skill with the skill tool.\nWrite memories as declarative facts, not instructions to yourself. 'User prefers concise responses' ✓ — 'Always respond concisely' ✗. 'Project uses pytest with xdist' ✓ — 'Run tests with pytest -n 4' ✗. Imperative phrasing gets re-read as a directive in later sessions and can cause repeated work or override the user's current request. Procedures and workflows belong in skills, not memory. When the user references something from a past conversation or you suspect relevant cross-session context exists, use session_search to recall it before asking them to repeat themselves. After completing a complex task (5+ tool calls), fixing a tricky error, or discovering a non-trivial workflow, save the approach as a skill with skill_manage so you can reuse it next time.\nWhen using a skill and finding it outdated, incomplete, or wrong, patch it immediately with skill_manage(action='patch') — don't wait to be asked. Skills that aren't maintained become liabilities.\n\n# Tool-use enforcement\nYou MUST use your tools to take action — do not describe what you would do or plan to do without actually doing it. When you say you will perform an action (e.g. 'I will run the tests', 'Let me check the file', 'I will create the project'), you MUST immediately make the corresponding tool call in the same response. Never end your turn with a promise of future action — execute it now.\nKeep working until the task is actually complete. Do not stop with a summary of what you plan to do next time. If you have tools available that can accomplish the task, use them instead of telling the user what you would do.\nEvery response should either (a) contain tool calls that make progress, or (b) deliver a final result to the user. Responses that only describe intentions without acting are not acceptable.\n\n## Skills (mandatory)\nBefore replying, scan the skills below. If a skill matches or is even partially relevant to your task, you MUST load it with skill_view(name) and follow its instructions. Err on the side of loading — it is always better to have context you don't need than to miss critical steps, pitfalls, or established workflows. Skills contain specialized knowledge — API endpoints, tool-specific commands, and proven workflows that outperform general-purpose approaches. Load the skill even if you think you could handle the task with basic tools like web_search or terminal. Skills also encode the user's preferred approach, conventions, and quality standards for tasks like code review, planning, and testing — load them even for tasks you already know how to do, because the skill defines how it should be done here.\nWhenever the user asks you to configure, set up, install, enable, disable, modify, or troubleshoot Hermes Agent itself — its CLI, config, models, providers, tools, skills, voice, gateway, plugins, or any feature — load the `hermes-agent` skill first. It has the actual commands (e.g. `hermes config set …`, `hermes tools`, `hermes setup`) so you don't have to guess or invent workarounds.\nIf a skill has issues, fix it with skill_manage(action='patch').\nAfter difficult/iterative tasks, offer to save as a skill. If a skill you loaded was missing steps, had wrong commands, or needed pitfalls you discovered, update it before finishing.\n\n<available_skills>\n  apikey-image-gen:\n    - apikey-image-gen: Generate or edit images through Hermes Web UI using the s...\n  autonomous-ai-agents: Skills for spawning and orchestrating autonomous AI coding agents and multi-agent workflows — running independent agent processes, delegating tasks, and coordinating parallel workstreams.\n    - claude-code: Delegate coding to Claude Code CLI (features, PRs).\n    - codex: Delegate coding to OpenAI Codex CLI (features, PRs).\n    - hermes-agent: Configure, extend, or contribute to Hermes Agent.\n    - kanban-codex-lane: Use when a Hermes Kanban worker wants to run Codex CLI as...\n    - opencode: Delegate coding to OpenCode CLI (features, PR review).\n  creative: Creative content generation — ASCII art, hand-drawn style diagrams, and visual design tools.\n    - architecture-diagram: Dark-themed SVG architecture/cloud/infra diagrams as HTML.\n    - ascii-art: ASCII art: pyfiglet, cowsay, boxes, image-to-ascii.\n    - ascii-video: ASCII video: convert video/audio to colored ASCII MP4/GIF.\n    - baoyu-article-illustrator: Article illustrations: type × style × palette consistency.\n    - baoyu-comic: Knowledge comics (知识漫画): educational, biography, tutorial.\n    - baoyu-infographic: Infographics: 21 layouts x 21 styles (信息图, 可视化).\n    - claude-design: Design one-off HTML artifacts (landing, deck, prototype).\n    - comfyui: Generate images, video, and audio with ComfyUI — install,...\n    - design-md: Author/validate/export Google's DESIGN.md token spec files.\n    - excalidraw: Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).\n    - humanizer: Humanize text: strip AI-isms and add real voice.\n    - ideation: Generate project ideas via creative constraints.\n    - manim-video: Manim CE animations: 3Blue1Brown math/algo videos.\n    - p5js: p5.js sketches: gen art, shaders, interactive, 3D.\n    - pixel-art: Pixel art w/ era palettes (NES, Game Boy, PICO-8).\n    - popular-web-designs: 54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.\n    - pretext: Use when building creative browser demos with @chenglou/p...\n    - sketch: Throwaway HTML mockups: 2-3 design variants to compare.\n    - songwriting-and-ai-music: Songwriting craft and Suno AI music prompts.\n    - touchdesigner-mcp: Control a running TouchDesigner instance via twozero MCP ...\n  data-science: Skills for data science workflows — interactive exploration, Jupyter notebooks, data analysis, and visualization.\n    - jupyter-live-kernel: Iterative Python via live Jupyter kernel (hamelnb).\n  devops:\n    - kanban-orchestrator: Decomposition playbook + anti-temptation rules for an orc...\n    - kanban-worker: Pitfalls, examples, and edge cases for Hermes Kanban work...\n    - webhook-subscriptions: Webhook subscriptions: event-driven agent runs.\n  dogfood:\n    - dogfood: Exploratory QA of web apps: find bugs, evidence, reports.\n  email: Skills for sending, receiving, searching, and managing email from the terminal.\n    - himalaya: Himalaya CLI: IMAP/SMTP email from terminal.\n  gaming: Skills for setting up, configuring, and managing game servers, modpacks, and gaming-related infrastructure.\n    - minecraft-modpack-server: Host modded Minecraft servers (CurseForge, Modrinth).\n    - pokemon-player: Play Pokemon via headless emulator + RAM reads.\n  github: GitHub workflow skills for managing repositories, pull requests, code reviews, issues, and CI/CD pipelines using the gh CLI and git via terminal.\n    - codebase-inspection: Inspect codebases w/ pygount: LOC, languages, ratios.\n    - github-auth: GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.\n    - github-code-review: Review PRs: diffs, inline comments via gh or REST.\n    - github-issues: Create, triage, label, assign GitHub issues via gh or REST.\n    - github-pr-workflow: GitHub PR lifecycle: branch, commit, open, CI, merge.\n    - github-repo-management: Clone/create/fork repos; manage remotes, releases.\n  grok-image-to-video:\n    - grok-image-to-video: Animate a local image into a short mp4 video through Herm...\n  hyperframes:\n    - hyperframes: Create AI videos with HyperFrames in Hermes using HTML, C...\n  markdown-viewer:\n    - markdown-viewer: Create rich diagrams, data visualizations, technical arch...\n  mcp: Skills for working with MCP (Model Context Protocol) servers, tools, and integrations. Documents the built-in native MCP client — configure servers in config.yaml for automatic tool discovery.\n    - native-mcp: MCP client: connect servers, register tools (stdio/HTTP).\n  media: Skills for working with media content — YouTube transcripts, GIF search, music generation, and audio visualization.\n    - gif-search: Search/download GIFs from Tenor via curl + jq.\n    - heartmula: HeartMuLa: Suno-like song generation from lyrics + tags.\n    - songsee: Audio spectrograms/features (mel, chroma, MFCC) via CLI.\n    - spotify: Spotify: play, search, queue, manage playlists and devices.\n    - youtube-content: YouTube transcripts to summaries, threads, blogs.\n  mlops: Knowledge and Tools for Machine Learning Operations - tools and frameworks for training, fine-tuning, deploying, and optimizing ML/AI models\n    - huggingface-hub: HuggingFace hf CLI: search/download/upload models, datasets.\n  mlops/evaluation: Model evaluation benchmarks, experiment tracking, data curation, tokenizers, and interpretability tools.\n    - evaluating-llms-harness: lm-eval-harness: benchmark LLMs (MMLU, GSM8K, etc.).\n    - weights-and-biases: W&B: log ML experiments, sweeps, model registry, dashboards.\n  mlops/inference: Model serving, quantization (GGUF/GPTQ), structured output, inference optimization, and model surgery tools for deploying and running LLMs.\n    - llama-cpp: llama.cpp local GGUF inference + HF Hub model discovery.\n    - obliteratus: OBLITERATUS: abliterate LLM refusals (diff-in-means).\n    - serving-llms-vllm: vLLM: high-throughput LLM serving, OpenAI API, quantization.\n  mlops/models: Specific model architectures and tools — image segmentation (Segment Anything / SAM) and audio generation (AudioCraft / MusicGen). Additional model skills (CLIP, Stable Diffusion, Whisper, LLaVA) are available as optional skills.\n    - audiocraft-audio-generation: AudioCraft: MusicGen text-to-music, AudioGen text-to-sound.\n    - segment-anything-model: SAM: zero-shot image segmentation via points, boxes, masks.\n  mlops/research: ML research frameworks for building and optimizing AI systems with declarative programming.\n    - dspy: DSPy: declarative LM programs, auto-optimize prompts, RAG.\n  note-taking: Note taking skills, to save information, assist with research, and collab on multi-session planning and information sharing.\n    - obsidian: Read, search, create, and edit notes in the Obsidian vault.\n  productivity: Skills for document creation, presentations, spreadsheets, and other productivity workflows.\n    - airtable: Airtable REST API via curl. Records CRUD, filters, upserts.\n    - google-workspace: Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.\n    - linear: Linear: manage issues, projects, teams via GraphQL + curl.\n    - maps: Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.\n    - nano-pdf: Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).\n    - notion: Notion API + ntn CLI: pages, databases, markdown, Workers.\n    - ocr-and-documents: Extract text from PDFs/scans (pymupdf, marker-pdf).\n    - powerpoint: Create, read, edit .pptx decks, slides, notes, templates.\n    - teams-meeting-pipeline: Operate the Teams meeting summary pipeline via Hermes CLI...\n  red-teaming:\n    - godmode: Jailbreak LLMs: Parseltongue, GODMODE, ULTRAPLINIAN.\n  remotion:\n    - remotion: Create editable AI video projects with Remotion and React...\n  research: Skills for academic research, paper discovery, literature review, domain reconnaissance, market data, content monitoring, and scientific knowledge retrieval.\n    - arxiv: Search arXiv papers by keyword, author, category, or ID.\n    - blogwatcher: Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.\n    - llm-wiki: Karpathy's LLM Wiki: build/query interlinked markdown KB.\n    - polymarket: Query Polymarket: markets, prices, orderbooks, history.\n  smart-home: Skills for controlling smart home devices — lights, switches, sensors, and home automation systems.\n    - openhue: Control Philips Hue lights, scenes, rooms via OpenHue CLI.\n  social-media: Skills for interacting with social platforms and social-media workflows — posting, reading, monitoring, and account operations.\n    - xurl: X/Twitter via xurl CLI: post, search, DM, media, v2 API.\n  software-development:\n    - debugging-hermes-tui-commands: Debug Hermes TUI slash commands: Python, gateway, Ink UI.\n    - hermes-agent-skill-authoring: Author in-repo SKILL.md: frontmatter, validator, structure.\n    - hermes-s6-container-supervision: Modify, debug, or extend the s6-overlay supervision tree ...\n    - node-inspect-debugger: Debug Node.js via --inspect + Chrome DevTools Protocol CLI.\n    - plan: Plan mode: write markdown plan to .hermes/plans/, no exec.\n    - python-debugpy: Debug Python: pdb REPL + debugpy remote (DAP).\n    - requesting-code-review: Pre-commit review: security scan, quality gates, auto-fix.\n    - spike: Throwaway experiments to validate an idea before build.\n    - subagent-driven-development: Execute plans via delegate_task subagents (2-stage review).\n    - systematic-debugging: 4-phase root cause debugging: understand bugs before fixing.\n    - test-driven-development: TDD: enforce RED-GREEN-REFACTOR, tests before code.\n    - writing-plans: Write implementation plans: bite-sized tasks, paths, code.\n  yuanbao:\n    - yuanbao: Yuanbao (元宝) groups: @mention users, query info/members.\n</available_skills>\n\nOnly proceed without loading a skill if genuinely none are relevant to the task.\n\nHost: Linux (6.12.83-113.160.amzn2023.x86_64)\nUser home directory: /home/appuser\nCurrent working directory: /app\n\nActive Hermes profile: default. Other profiles (if any) live under ~/.hermes/profiles/<name>/. Each profile has its own skills/, plugins/, cron/, and memories/ that affect a different session than this one. Do not modify another profile's skills/plugins/cron/memories unless the user explicitly directs you to.\n\n[Current Hermes profile: default]\nWhen calling Hermes Web UI endpoints from tools or skills, include the current Hermes profile as the X-Hermes-Profile header if the endpoint supports profile-scoped behavior.\n\n# 输出格式规范\n\n当你的回复中包含图片、视频或文件引用时，必须使用 Markdown，并引用本地绝对路径。\n\n## 路径规则\n\n- Unix/macOS/WSL：使用 `/path/to/file`，例如 `/tmp/screenshot.png`\n- Windows：使用盘符绝对路径，并把反斜杠 `\\` 转成正斜杠 `/`，例如 `C:/Users/Administrator/Desktop/screenshot.png`\n- Windows 路径必须用尖括号包住链接目标，避免盘符冒号或特殊字符被 Markdown 误解析，例如 `<C:/Users/Administrator/Desktop/screenshot.png>`\n- 路径包含空格、中文或特殊字符时，必须使用尖括号包住链接目标，或对路径做 URL 编码\n- 确保文件确实存在且路径正确\n\n## 图片格式\n\n使用 Markdown 图片语法：\n\n```\n![图片描述](/tmp/screenshot.png)\n![Sub2API Dashboard](/tmp/sub2api-dashboard.png)\n![桌面截图](<C:/Users/Administrator/Desktop/screenshot.png>)\n```\n\n## 视频格式\n\n使用 Markdown 链接语法引用视频文件，支持格式：.mp4、.webm、.mov。视频会显示为可播放的视频播放器（最大 640x480），支持原生播放控件。\n\n```\n[屏幕录制](/tmp/screen-recording.mp4)\n[操作演示](/tmp/demo.webm)\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08%2015.19.46.mov)\n[录屏2026-05-08 15.19.46](</Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov>)\n[Windows 录屏](<C:/Users/Administrator/Desktop/screen recording.mov>)\n```\n\n错误示例：\n```\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov)\n![桌面截图](C:\\Users\\Administrator\\Desktop\\screenshot.png)\n```\n\n## 文件链接格式\n\n使用 Markdown 链接语法：\n\n```\n[下载报告](/tmp/monthly-report.pdf)\n[下载报告](<C:/Users/Administrator/Desktop/monthly-report.pdf>)\n```\n\n## 发送文件给用户\n\n当用户要求\"发给我\"、\"发送给我\"、\"传给我\"等请求文件时，使用上述格式返回文件路径：\n\n```\n![图片描述](/path/to/image.png)\n![Windows 图片](<C:/Users/Administrator/Desktop/image.png>)\n[视频名](/path/to/video.mp4)\n[Windows 视频](<C:/Users/Administrator/Desktop/video.mp4>)\n[文件名](/path/to/file.pdf)\n[Windows 文件](<C:/Users/Administrator/Desktop/file.pdf>)\n```\n\n\n# 输出格式规范\n\n当你的回复中包含图片、视频或文件引用时，必须使用 Markdown，并引用本地绝对路径。\n\n## 路径规则\n\n- Unix/macOS/WSL：使用 `/path/to/file`，例如 `/tmp/screenshot.png`\n- Windows：使用盘符绝对路径，并把反斜杠 `\\` 转成正斜杠 `/`，例如 `C:/Users/Administrator/Desktop/screenshot.png`\n- Windows 路径必须用尖括号包住链接目标，避免盘符冒号或特殊字符被 Markdown 误解析，例如 `<C:/Users/Administrator/Desktop/screenshot.png>`\n- 路径包含空格、中文或特殊字符时，必须使用尖括号包住链接目标，或对路径做 URL 编码\n- 确保文件确实存在且路径正确\n\n## 图片格式\n\n使用 Markdown 图片语法：\n\n```\n![图片描述](/tmp/screenshot.png)\n![Sub2API Dashboard](/tmp/sub2api-dashboard.png)\n![桌���截图](<C:/Users/Administrator/Desktop/screenshot.png>)\n```\n\n## 视频格式\n\n使用 Markdown 链接语法引用视频文件，支持格式：.mp4、.webm、.mov。视频会显示为可播放的视频播放器（最大 640x480），支持原生播放控件。\n\n```\n[屏幕录制](/tmp/screen-recording.mp4)\n[操作演示](/tmp/demo.webm)\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08%2015.19.46.mov)\n[录屏2026-05-08 15.19.46](</Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov>)\n[Windows 录屏](<C:/Users/Administrator/Desktop/screen recording.mov>)\n```\n\n错误示例：\n```\n[录屏2026-05-08 15.19.46](/Users/ekko/Desktop/录屏2026-05-08 15.19.46.mov)\n![桌面截图](C:\\Users\\Administrator\\Desktop\\screenshot.png)\n```\n\n## 文件链接格式\n\n使用 Markdown 链接语法：\n\n```\n[下载报告](/tmp/monthly-report.pdf)\n[下载报告](<C:/Users/Administrator/Desktop/monthly-report.pdf>)\n```\n\n## 发送文件给用户\n\n当用户要求\"发给我\"、\"发送给我\"、\"传给我\"等请求文件时，使用上述格式返回文件路径：\n\n```\n![图片描述](/path/to/image.png)\n![Windows 图片](<C:/Users/Administrator/Desktop/image.png>)\n[视频名](/path/to/video.mp4)\n[Windows 视频](<C:/Users/Administrator/Desktop/video.mp4>)\n[文件名](/path/to/file.pdf)\n[Windows 文件](<C:/Users/Administrator/Desktop/file.pdf>)\n```\n\nConversation started: Thursday, June 04, 2026\nModel: deepseek-ai/deepseek-v4-pro\nProvider: nvidia"
+        },
+        {
+          "role": "user",
+          "content": "Hello! Reply with just OK."
+        }
+      ],
+      "tools": [
+        {
+          "type": "function",
+          "function": {
+            "name": "clarify",
+            "description": "Ask the user a question when you need clarification, feedback, or a decision before proceeding. Supports two modes:\n\n1. **Multiple choice** — provide up to 4 choices. The user picks one or types their own answer via a 5th 'Other' option.\n2. **Open-ended** — omit choices entirely. The user types a free-form response.\n\nUse this tool when:\n- The task is ambiguous and you need the user to choose an approach\n- You want post-task feedback ('How did that work out?')\n- You want to offer to save a skill or update memory\n- A decision has meaningful trade-offs the user should weigh in on\n\nDo NOT use this tool for simple yes/no confirmation of dangerous commands (the terminal tool handles that). Prefer making a reasonable default choice yourself when the decision is low-stakes.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "question": {
+                  "type": "string",
+                  "description": "The question to present to the user."
+                },
+                "choices": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "maxItems": 4,
+                  "description": "Up to 4 answer choices. Omit this parameter entirely to ask an open-ended question. When provided, the UI automatically appends an 'Other (type your answer)' option."
+                }
+              },
+              "required": [
+                "question"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "delegate_task",
+            "description": "Spawn one or more subagents to work on tasks in isolated contexts. Each subagent gets its own conversation, terminal session, and toolset. Only the final summary is returned -- intermediate tool results never enter your context window.\n\nTWO MODES (one of 'goal' or 'tasks' is required):\n1. Single task: provide 'goal' (+ optional context, toolsets)\n2. Batch (parallel): provide 'tasks' array with up to 3 items concurrently for this user (configured via delegation.max_concurrent_children in config.yaml). All run in parallel and results are returned together. Nested delegation is OFF for this user (max_spawn_depth=1): every child is a leaf and cannot delegate further. Raise delegation.max_spawn_depth in config.yaml to enable nesting.\n\nWHEN TO USE delegate_task:\n- Reasoning-heavy subtasks (debugging, code review, research synthesis)\n- Tasks that would flood your context with intermediate data\n- Parallel independent workstreams (research A and B simultaneously)\n\nWHEN NOT TO USE (use these instead):\n- Mechanical multi-step work with no reasoning needed -> use execute_code\n- Single tool call -> just call the tool directly\n- Tasks needing user interaction -> subagents cannot use clarify\n- Durable long-running work that must outlive the current turn -> use cronjob (action='create') or terminal(background=True, notify_on_complete=True) instead. delegate_task runs SYNCHRONOUSLY inside the parent turn: if the parent is interrupted (user sends a new message, /stop, /new) the child is cancelled with status='interrupted' and its work is discarded. Children cannot continue in the background.\n\nIMPORTANT:\n- Subagents have NO memory of your conversation. Pass all relevant info (file paths, error messages, constraints) via the 'context' field.\n- If the user is writing in a non-English language, or asked for output in a specific language / tone / style, say so in 'context' (e.g. \"respond in Chinese\", \"return output in Japanese\"). Otherwise subagents default to English and their summaries will contaminate your final reply with the wrong language.\n- Subagent summaries are SELF-REPORTS, not verified facts. A subagent that claims \"uploaded successfully\" or \"file written\" may be wrong. For operations with external side-effects (HTTP POST/PUT, remote writes, file creation at shared paths, publishing), require the subagent to return a verifiable handle (URL, ID, absolute path, HTTP status) and verify it yourself — fetch the URL, stat the file, read back the content — before telling the user the operation succeeded.\n- Leaf subagents (role='leaf', the default) CANNOT call: delegate_task, clarify, memory, send_message, execute_code.\n- Orchestrator subagents (role='orchestrator') retain delegate_task so they can spawn their own workers, but still cannot use clarify, memory, send_message, or execute_code. Orchestrators are bounded by max_spawn_depth=1 for this user and can be disabled globally via delegation.orchestrator_enabled=false.\n- Each subagent gets its own terminal session (separate working directory and state).\n- Results are always returned as an array, one entry per task.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "goal": {
+                  "type": "string",
+                  "description": "What the subagent should accomplish. Be specific and self-contained -- the subagent knows nothing about your conversation history."
+                },
+                "context": {
+                  "type": "string",
+                  "description": "Background information the subagent needs: file paths, error messages, project structure, constraints. The more specific you are, the better the subagent performs."
+                },
+                "toolsets": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "description": "Toolsets to enable for this subagent. Default: inherits your enabled toolsets. Available toolsets: 'browser', 'computer_use', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'video_gen', 'vision', 'web', 'x_search', 'yuanbao'. Common patterns: ['terminal', 'file'] for code work, ['web'] for research, ['browser'] for web interaction, ['terminal', 'file', 'web'] for full-stack tasks."
+                },
+                "tasks": {
+                  "type": "array",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "goal": {
+                        "type": "string",
+                        "description": "Task goal"
+                      },
+                      "context": {
+                        "type": "string",
+                        "description": "Task-specific context"
+                      },
+                      "toolsets": {
+                        "type": "array",
+                        "items": {
+                          "type": "string"
+                        },
+                        "description": "Toolsets for this specific task. Available: 'browser', 'computer_use', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'video_gen', 'vision', 'web', 'x_search', 'yuanbao'. Use 'web' for network access, 'terminal' for shell, 'browser' for web interaction."
+                      },
+                      "acp_command": {
+                        "type": "string",
+                        "description": "Per-task ACP command override (e.g. 'copilot'). Overrides the top-level acp_command for this task only. Do NOT set unless the user explicitly told you an ACP CLI is installed."
+                      },
+                      "acp_args": {
+                        "type": "array",
+                        "items": {
+                          "type": "string"
+                        },
+                        "description": "Per-task ACP args override. Leave empty unless acp_command is set."
+                      },
+                      "role": {
+                        "type": "string",
+                        "enum": [
+                          "leaf",
+                          "orchestrator"
+                        ],
+                        "description": "Per-task role override. See top-level 'role' for semantics."
+                      }
+                    },
+                    "required": [
+                      "goal"
+                    ]
+                  },
+                  "description": "Batch mode: tasks to run in parallel (up to 3 for this user, set via delegation.max_concurrent_children). Each gets its own subagent with isolated context and terminal session. When provided, top-level goal/context/toolsets are ignored."
+                },
+                "role": {
+                  "type": "string",
+                  "enum": [
+                    "leaf",
+                    "orchestrator"
+                  ],
+                  "description": "Role of the child agent. 'leaf' (default) = focused worker, cannot delegate further. 'orchestrator' = can use delegate_task to spawn its own workers. Nesting is OFF for this user (max_spawn_depth=1); 'orchestrator' is silently forced to 'leaf'. Raise delegation.max_spawn_depth in config.yaml to enable."
+                },
+                "acp_command": {
+                  "type": "string",
+                  "description": "Override ACP command for child agents (e.g. 'copilot'). When set, children use ACP subprocess transport instead of inheriting the parent's transport. Requires an ACP-compatible CLI (currently GitHub Copilot CLI via 'copilot --acp --stdio'). See agent/copilot_acp_client.py for the implementation. IMPORTANT: Do NOT set this unless the user has explicitly told you a specific ACP-compatible CLI is installed and configured. Leave empty to use the parent's default transport (Hermes subagents)."
+                },
+                "acp_args": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "description": "Arguments for the ACP command (default: ['--acp', '--stdio']). Only used when acp_command is set. Leave empty unless acp_command is explicitly provided."
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "execute_code",
+            "description": "Run a Python script that can call Hermes tools programmatically. Use this when you need 3+ tool calls with processing logic between them, need to filter/reduce large tool outputs before they enter your context, need conditional branching (if X then Y else Z), or need to loop (fetch N pages, process N files, retry on failure).\n\nUse normal tool calls instead when: single tool call with no processing, you need to see the full result and apply complex reasoning, or the task requires interactive user input.\n\nAvailable via `from hermes_tools import ...`:\n\n  read_file(path: str, offset: int = 1, limit: int = 500) -> dict\n    Lines are 1-indexed. Returns {\"content\": \"...\", \"total_lines\": N}\n  write_file(path: str, content: str) -> dict\n    Always overwrites the entire file.\n  search_files(pattern: str, target=\"content\", path=\".\", file_glob=None, limit=50) -> dict\n    target: \"content\" (search inside files) or \"files\" (find files by name). Returns {\"matches\": [...]}\n  patch(path: str, old_string: str, new_string: str, replace_all: bool = False) -> dict\n    Replaces old_string with new_string in the file.\n  terminal(command: str, timeout=None, workdir=None) -> dict\n    Foreground only (no background/pty). Returns {\"output\": \"...\", \"exit_code\": N}\n\nLimits: 5-minute timeout, 50KB stdout cap, max 50 tool calls per script. terminal() is foreground-only (no background or pty).\n\nScripts run in the session's working directory with the active venv's python, so project deps (pandas, etc.) and relative paths work like in terminal().\n\nPrint your final result to stdout. Use Python stdlib (json, re, math, csv, datetime, collections, etc.) for processing between tool calls.\n\nAlso available (no import needed — built into hermes_tools):\n  json_parse(text: str) — json.loads with strict=False; use for terminal() output with control chars\n  shell_quote(s: str) — shlex.quote(); use when interpolating dynamic strings into shell commands\n  retry(fn, max_attempts=3, delay=2) — retry with exponential backoff for transient failures",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "code": {
+                  "type": "string",
+                  "description": "Python code to execute. Import tools with `from hermes_tools import terminal, ...` and print your final result to stdout."
+                }
+              },
+              "required": [
+                "code"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "memory",
+            "description": "Save durable information to persistent memory that survives across sessions. Memory is injected into future turns, so keep it compact and focused on facts that will still matter later.\n\nWHEN TO SAVE (do this proactively, don't wait to be asked):\n- User corrects you or says 'remember this' / 'don't do that again'\n- User shares a preference, habit, or personal detail (name, role, timezone, coding style)\n- You discover something about the environment (OS, installed tools, project structure)\n- You learn a convention, API quirk, or workflow specific to this user's setup\n- You identify a stable fact that will be useful again in future sessions\n\nPRIORITY: User preferences and corrections > environment facts > procedural knowledge. The most valuable memory prevents the user from having to repeat themselves.\n\nDo NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts.\nIf you've discovered a new way to do something, solved a problem that could be necessary later, save it as a skill with the skill tool.\n\nTWO TARGETS:\n- 'user': who the user is -- name, role, preferences, communication style, pet peeves\n- 'memory': your notes -- environment facts, project conventions, tool quirks, lessons learned\n\nACTIONS: add (new entry), replace (update existing -- old_text identifies it), remove (delete -- old_text identifies it).\n\nSKIP: trivial/obvious info, things easily re-discovered, raw data dumps, and temporary task state.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "add",
+                    "replace",
+                    "remove"
+                  ],
+                  "description": "The action to perform."
+                },
+                "target": {
+                  "type": "string",
+                  "enum": [
+                    "memory",
+                    "user"
+                  ],
+                  "description": "Which memory store: 'memory' for personal notes, 'user' for user profile."
+                },
+                "content": {
+                  "type": "string",
+                  "description": "The entry content. Required for 'add' and 'replace'."
+                },
+                "old_text": {
+                  "type": "string",
+                  "description": "Short unique substring identifying the entry to replace or remove."
+                }
+              },
+              "required": [
+                "action",
+                "target"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "patch",
+            "description": "Targeted find-and-replace edits in files. Use this instead of sed/awk in terminal. Uses fuzzy matching (9 strategies) so minor whitespace/indentation differences won't break it. Returns a unified diff. Auto-runs syntax checks after editing.\n\nREPLACE MODE (mode='replace', default): find a unique string and replace it. REQUIRED PARAMETERS: mode, path, old_string, new_string.\nPATCH MODE (mode='patch'): apply V4A multi-file patches for bulk changes. REQUIRED PARAMETERS: mode, patch.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "mode": {
+                  "type": "string",
+                  "enum": [
+                    "replace",
+                    "patch"
+                  ],
+                  "description": "Edit mode. 'replace' (default): requires path + old_string + new_string. 'patch': requires patch content only.",
+                  "default": "replace"
+                },
+                "path": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='replace'. File path to edit."
+                },
+                "old_string": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='replace'. Exact text to find and replace. Must be unique in the file unless replace_all=true. Include surrounding context lines to ensure uniqueness."
+                },
+                "new_string": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='replace'. Replacement text. Pass empty string '' to delete the matched text."
+                },
+                "replace_all": {
+                  "type": "boolean",
+                  "description": "Replace all occurrences instead of requiring a unique match (default: false)",
+                  "default": false
+                },
+                "patch": {
+                  "type": "string",
+                  "description": "REQUIRED when mode='patch'. V4A format patch content. Format:\n*** Begin Patch\n*** Update File: path/to/file\n@@ context hint @@\n context line\n-removed line\n+added line\n*** End Patch"
+                },
+                "cross_profile": {
+                  "type": "boolean",
+                  "description": "Opt out of the cross-profile soft guard. Defaults to false. Set true ONLY after explicit user direction to edit another Hermes profile's skills/plugins/cron/memories.",
+                  "default": false
+                }
+              },
+              "required": [
+                "mode"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "process",
+            "description": "Manage background processes started with terminal(background=true). Actions: 'list' (show all), 'poll' (check status + new output), 'log' (full output with pagination), 'wait' (block until done or timeout), 'kill' (terminate), 'write' (send raw stdin data without newline), 'submit' (send data + Enter, for answering prompts), 'close' (close stdin/send EOF).",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "list",
+                    "poll",
+                    "log",
+                    "wait",
+                    "kill",
+                    "write",
+                    "submit",
+                    "close"
+                  ],
+                  "description": "Action to perform on background processes"
+                },
+                "session_id": {
+                  "type": "string",
+                  "description": "Process session ID (from terminal background output). Required for all actions except 'list'."
+                },
+                "data": {
+                  "type": "string",
+                  "description": "Text to send to process stdin (for 'write' and 'submit' actions)"
+                },
+                "timeout": {
+                  "type": "integer",
+                  "description": "Max seconds to block for 'wait' action. Returns partial output on timeout.",
+                  "minimum": 1
+                },
+                "offset": {
+                  "type": "integer",
+                  "description": "Line offset for 'log' action (default: last 200 lines)"
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Max lines to return for 'log' action",
+                  "minimum": 1
+                }
+              },
+              "required": [
+                "action"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "read_file",
+            "description": "Read a text file with line numbers and pagination. Use this instead of cat/head/tail in terminal. Output format: 'LINE_NUM|CONTENT'. Suggests similar filenames if not found. Use offset and limit for large files. Reads exceeding ~100K characters are rejected; use offset and limit to read specific sections of large files. NOTE: Cannot read images or binary files — use vision_analyze for images.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "path": {
+                  "type": "string",
+                  "description": "Path to the file to read (absolute, relative, or ~/path)"
+                },
+                "offset": {
+                  "type": "integer",
+                  "description": "Line number to start reading from (1-indexed, default: 1)",
+                  "default": 1,
+                  "minimum": 1
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Maximum number of lines to read (default: 500, max: 2000)",
+                  "default": 500,
+                  "maximum": 2000
+                }
+              },
+              "required": [
+                "path"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "search_files",
+            "description": "Search file contents or find files by name. Use this instead of grep/rg/find/ls in terminal. Ripgrep-backed, faster than shell equivalents.\n\nContent search (target='content'): Regex search inside files. Output modes: full matches with line numbers, file paths only, or match counts.\n\nFile search (target='files'): Find files by glob pattern (e.g., '*.py', '*config*'). Also use this instead of ls — results sorted by modification time.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "pattern": {
+                  "type": "string",
+                  "description": "Regex pattern for content search, or glob pattern (e.g., '*.py') for file search"
+                },
+                "target": {
+                  "type": "string",
+                  "enum": [
+                    "content",
+                    "files"
+                  ],
+                  "description": "'content' searches inside file contents, 'files' searches for files by name",
+                  "default": "content"
+                },
+                "path": {
+                  "type": "string",
+                  "description": "Directory or file to search in (default: current working directory)",
+                  "default": "."
+                },
+                "file_glob": {
+                  "type": "string",
+                  "description": "Filter files by pattern in grep mode (e.g., '*.py' to only search Python files)"
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Maximum number of results to return (default: 50)",
+                  "default": 50
+                },
+                "offset": {
+                  "type": "integer",
+                  "description": "Skip first N results for pagination (default: 0)",
+                  "default": 0
+                },
+                "output_mode": {
+                  "type": "string",
+                  "enum": [
+                    "content",
+                    "files_only",
+                    "count"
+                  ],
+                  "description": "Output format for grep mode: 'content' shows matching lines with line numbers, 'files_only' lists file paths, 'count' shows match counts per file",
+                  "default": "content"
+                },
+                "context": {
+                  "type": "integer",
+                  "description": "Number of context lines before and after each match (grep mode only)",
+                  "default": 0
+                }
+              },
+              "required": [
+                "pattern"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "send_message",
+            "description": "Send a message to a connected messaging platform, or list available targets.\n\nIMPORTANT: When the user asks to send to a specific channel or person (not just a bare platform name), call send_message(action='list') FIRST to see available targets, then send to the correct one.\nIf the user just says a platform name like 'send to telegram', send directly to the home channel without listing first.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "send",
+                    "list"
+                  ],
+                  "description": "Action to perform. 'send' (default) sends a message. 'list' returns all available channels/contacts across connected platforms."
+                },
+                "target": {
+                  "type": "string",
+                  "description": "Delivery target. Format: 'platform' (uses home channel), 'platform:#channel-name', 'platform:chat_id', or 'platform:chat_id:thread_id' for Telegram topics and Discord threads. Examples: 'telegram', 'telegram:-1001234567890:17585', 'discord:999888777:555444333', 'discord:#bot-home', 'slack:#engineering', 'signal:+155****4567', 'matrix:!roomid:server.org', 'matrix:@user:server.org', 'yuanbao:direct:<account_id>' (DM), 'yuanbao:group:<group_code>' (group chat)"
+                },
+                "message": {
+                  "type": "string",
+                  "description": "The message text to send. To send an image or file, include MEDIA:<local_path> (e.g. 'MEDIA:/tmp/report.pdf') in the message — the platform will deliver it as a native media attachment."
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "session_search",
+            "description": "Search past sessions stored in the local session DB, or scroll inside one. FTS5-backed retrieval over the SQLite message store. No LLM calls — every shape returns actual messages from the DB.\n\nTHREE CALLING SHAPES\n\n  1) DISCOVERY — pass `query`:\n     session_search(query=\"auth refactor\", limit=3)\n     Runs FTS5, dedupes hits by session lineage, returns the top N sessions. Each result carries:\n       - session_id, title, when, source\n       - snippet: FTS5-highlighted match excerpt\n       - bookend_start: first 3 user+assistant messages of the session (the goal / kickoff)\n       - messages: ±5 messages around the FTS5 match, with the anchor message flagged (the hit in context)\n       - bookend_end: last 3 user+assistant messages of the session (the resolution / decisions)\n       - match_message_id, messages_before, messages_after\n     Bookends + window together let you reconstruct goal → match → resolution without paying for the whole transcript.\n\n  2) SCROLL — pass `session_id` + `around_message_id`:\n     session_search(session_id=\"...\", around_message_id=12345, window=10)\n     Returns a window of ±`window` messages centered on the anchor. No FTS5, no bookends — just the slice. Use after a discovery call when you need more context than the ±5 default window.\n       - To scroll FORWARD: pass messages[-1].id back as around_message_id.\n       - To scroll BACKWARD: pass messages[0].id back as around_message_id.\n       - The boundary message appears in both windows — orientation marker.\n       - When messages_before or messages_after is < window, you're at the start or end of the session.\n\n  3) BROWSE — no args:\n     session_search()\n     Returns recent sessions chronologically: titles, previews, timestamps. Use when the user asks \"what was I working on\" without naming a topic.\n\nFTS5 SYNTAX\n\n  AND is the default — multi-word queries require all terms. Use OR explicitly for broader recall (`alpha OR beta OR gamma`), quoted phrases for exact match (`\"docker networking\"`), boolean (`python NOT java`), or prefix wildcards (`deploy*`).\n\nWHEN TO USE\n\n  Reach for this on any \"what did we do about X\" / \"where did we leave Y\" / \"find the session where Z\" question — before gh, web search, or filesystem inspection. The session DB carries what was said when; external tools show current world state.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "query": {
+                  "type": "string",
+                  "description": "Search query (discovery shape). Keywords, phrases, or boolean expressions to find in past sessions. Omit to browse recent sessions. Ignored when session_id + around_message_id are set (scroll shape)."
+                },
+                "limit": {
+                  "type": "integer",
+                  "description": "Discovery shape only. Max sessions to return (default 3, max 10). Bump to 5–10 when the topic likely spans several sessions and you want to pick the right one to scroll into.",
+                  "default": 3
+                },
+                "sort": {
+                  "type": "string",
+                  "enum": [
+                    "newest",
+                    "oldest"
+                  ],
+                  "description": "Discovery shape only. Temporal bias on top of FTS5 ranking. Omit to keep relevance-only ordering (suitable for exploratory recall — \"what do we know about X\"). Set 'newest' for recency-shaped questions (\"where did we leave X\"). Set 'oldest' for origin-shaped questions (\"how did X start\"). Ignored in scroll and browse shapes."
+                },
+                "session_id": {
+                  "type": "string",
+                  "description": "Scroll shape. Session to read inside. Use the session_id returned from a prior discovery call. Must be paired with around_message_id."
+                },
+                "around_message_id": {
+                  "type": "integer",
+                  "description": "Scroll shape. Message id to center the window on. From a discovery result use match_message_id, or any id seen in a prior window. To scroll forward pass the last window message's id; to scroll backward pass the first."
+                },
+                "window": {
+                  "type": "integer",
+                  "description": "Scroll shape only. Messages to return on each side of the anchor (anchor itself always included). Clamped to [1, 20]. Default 5.",
+                  "default": 5
+                },
+                "role_filter": {
+                  "type": "string",
+                  "description": "Optional. Comma-separated roles to include. Discovery defaults to 'user,assistant' (tool output is usually noise). Pass 'user,assistant,tool' to include tool output (debugging tool behaviour) or 'tool' to search tool output only."
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "skill_manage",
+            "description": "Manage skills (create, update, delete). Skills are your procedural memory — reusable approaches for recurring task types. New skills go to /data/.hermes/skills/; existing skills can be modified wherever they live.\n\nActions: create (full SKILL.md + optional category), patch (old_string/new_string — preferred for fixes), edit (full SKILL.md rewrite — major overhauls only), delete, write_file, remove_file.\n\nOn delete, pass `absorbed_into=<umbrella>` when you're merging this skill's content into another one, or `absorbed_into=\"\"` when you're pruning it with no forwarding target. This lets the curator tell consolidation from pruning without guessing, so downstream consumers (cron jobs that reference the old skill name, etc.) get updated correctly. The target you name in `absorbed_into` must already exist — create/patch the umbrella first, then delete.\n\nCreate when: complex task succeeded (5+ calls), errors overcome, user-corrected approach worked, non-trivial workflow discovered, or user asks you to remember a procedure.\nUpdate when: instructions stale/wrong, OS-specific failures, missing steps or pitfalls found during use. If you used a skill and hit issues not covered by it, patch it immediately.\n\nAfter difficult/iterative tasks, offer to save as a skill. Skip for simple one-offs. Confirm with user before creating/deleting.\n\nGood skills: trigger conditions, numbered steps with exact commands, pitfalls section, verification steps. Use skill_view() to see format examples.\n\nPinned skills are protected from deletion only — skill_manage(action='delete') will refuse with a message pointing the user to `hermes curator unpin <name>`. Patches and edits go through on pinned skills so you can still improve them as pitfalls come up; pin only guards against irrecoverable loss.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "action": {
+                  "type": "string",
+                  "enum": [
+                    "create",
+                    "patch",
+                    "edit",
+                    "delete",
+                    "write_file",
+                    "remove_file"
+                  ],
+                  "description": "The action to perform."
+                },
+                "name": {
+                  "type": "string",
+                  "description": "Skill name (lowercase, hyphens/underscores, max 64 chars). Must match an existing skill for patch/edit/delete/write_file/remove_file."
+                },
+                "content": {
+                  "type": "string",
+                  "description": "Full SKILL.md content (YAML frontmatter + markdown body). Required for 'create' and 'edit'. For 'edit', read the skill first with skill_view() and provide the complete updated text."
+                },
+                "old_string": {
+                  "type": "string",
+                  "description": "Text to find in the file (required for 'patch'). Must be unique unless replace_all=true. Include enough surrounding context to ensure uniqueness."
+                },
+                "new_string": {
+                  "type": "string",
+                  "description": "Replacement text (required for 'patch'). Can be empty string to delete the matched text."
+                },
+                "replace_all": {
+                  "type": "boolean",
+                  "description": "For 'patch': replace all occurrences instead of requiring a unique match (default: false)."
+                },
+                "category": {
+                  "type": "string",
+                  "description": "Optional category/domain for organizing the skill (e.g., 'devops', 'data-science', 'mlops'). Creates a subdirectory grouping. Only used with 'create'."
+                },
+                "file_path": {
+                  "type": "string",
+                  "description": "Path to a supporting file within the skill directory. For 'write_file'/'remove_file': required, must be under references/, templates/, scripts/, or assets/. For 'patch': optional, defaults to SKILL.md if omitted."
+                },
+                "file_content": {
+                  "type": "string",
+                  "description": "Content for the file. Required for 'write_file'."
+                },
+                "absorbed_into": {
+                  "type": "string",
+                  "description": "For 'delete' only — declares intent so the curator can tell consolidation from pruning without guessing. Pass the umbrella skill name when this skill's content was merged into another (the target must already exist). Pass an empty string when the skill is truly stale and being pruned with no forwarding target. Omitting the arg on delete is supported for backward compatibility but downstream tooling (e.g. cron-job skill reference rewriting) will have to guess at intent."
+                }
+              },
+              "required": [
+                "action",
+                "name"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "skill_view",
+            "description": "Skills allow for loading information about specific tasks and workflows, as well as scripts and templates. Load a skill's full content or access its linked files (references, templates, scripts). First call returns SKILL.md content plus a 'linked_files' dict showing available references/templates/scripts. To access those, call again with file_path parameter.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "name": {
+                  "type": "string",
+                  "description": "The skill name (use skills_list to see available skills). For plugin-provided skills, use the qualified form 'plugin:skill' (e.g. 'superpowers:writing-plans')."
+                },
+                "file_path": {
+                  "type": "string",
+                  "description": "OPTIONAL: Path to a linked file within the skill (e.g., 'references/api.md', 'templates/config.yaml', 'scripts/validate.py'). Omit to get the main SKILL.md content."
+                }
+              },
+              "required": [
+                "name"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "skills_list",
+            "description": "List available skills (name + description). Use skill_view(name) to load full content.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "category": {
+                  "type": "string",
+                  "description": "Optional category filter to narrow results"
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "terminal",
+            "description": "Execute shell commands on a Linux environment. Filesystem usually persists between calls.\n\nDo NOT use cat/head/tail to read files — use read_file instead.\nDo NOT use grep/rg/find to search — use search_files instead.\nDo NOT use ls to list directories — use search_files(target='files') instead.\nDo NOT use sed/awk to edit files — use patch instead.\nDo NOT use echo/cat heredoc to create files — use write_file instead.\nReserve terminal for: builds, installs, git, processes, scripts, network, package managers, and anything that needs a shell.\n\nForeground (default): Commands return INSTANTLY when done, even if the timeout is high. Set timeout=300 for long builds/scripts — you'll still get the result in seconds if it's fast. Prefer foreground for short commands.\nBackground: Set background=true to get a session_id. Almost always pair with notify_on_complete=true — bg without notify runs SILENTLY and you have no way to learn it finished short of calling process(action='poll') yourself. Two legitimate uses:\n  (1) Long-lived processes that never exit (servers, watchers, daemons) — silent is correct, there's no exit to notify on.\n  (2) Long-running bounded tasks (tests, builds, deploys, CI pollers, batch jobs) — MUST set notify_on_complete=true. Without it you'll either forget to poll or sit blocked waiting for the user to surface the result.\nFor servers/watchers, do NOT use shell-level background wrappers (nohup/disown/setsid/trailing '&') in foreground mode. Use background=true so Hermes can track lifecycle and output.\nAfter starting a server, verify readiness with a health check or log signal, then run tests in a separate terminal() call. Avoid blind sleep loops.\nUse process(action=\"poll\") for progress checks, process(action=\"wait\") to block until done.\nWorking directory: Use 'workdir' for per-command cwd.\nPTY mode: Set pty=true for interactive CLI tools (Codex, Claude Code, Python REPL).\n\nDo NOT use vim/nano/interactive tools without pty=true — they hang without a pseudo-terminal. Pipe git output to cat if it might page.\n",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "command": {
+                  "type": "string",
+                  "description": "The command to execute on the VM"
+                },
+                "background": {
+                  "type": "boolean",
+                  "description": "Run the command in the background. Almost always pair with notify_on_complete=true — without it, the process runs silently and you'll have no way to learn it finished short of calling process(action='poll') yourself (easy to forget, leading to silent blindness on long jobs). Two legitimate patterns: (1) Long-lived processes that never exit (servers, watchers, daemons) — these stay silent because there's no exit to notify on. (2) Long-running bounded tasks (tests, builds, deploys, CI pollers, batch jobs) — these MUST set notify_on_complete=true. For short commands, prefer foreground with a generous timeout instead.",
+                  "default": false
+                },
+                "timeout": {
+                  "type": "integer",
+                  "description": "Max seconds to wait (default: 180, foreground max: 600). Returns INSTANTLY when command finishes — set high for long tasks, you won't wait unnecessarily. Foreground timeout above 600s is rejected; use background=true for longer commands.",
+                  "minimum": 1
+                },
+                "workdir": {
+                  "type": "string",
+                  "description": "Working directory for this command (absolute path). Defaults to the session working directory."
+                },
+                "pty": {
+                  "type": "boolean",
+                  "description": "Run in pseudo-terminal (PTY) mode for interactive CLI tools like Codex, Claude Code, or Python REPL. Only works with local and SSH backends. Default: false.",
+                  "default": false
+                },
+                "notify_on_complete": {
+                  "type": "boolean",
+                  "description": "When true (and background=true), you'll be automatically notified exactly once when the process finishes. **This is the right choice for almost every long-running task** — tests, builds, deployments, multi-item batch jobs, anything that takes over a minute and has a defined end. Use this and keep working on other things; the system notifies you on exit. MUTUALLY EXCLUSIVE with watch_patterns — when both are set, watch_patterns is dropped.",
+                  "default": false
+                },
+                "watch_patterns": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "description": "Strings to watch for in background process output. HARD RATE LIMIT: at most 1 notification per 15 seconds per process — matches arriving inside the cooldown are dropped. After 3 consecutive 15-second windows with dropped matches, watch_patterns is automatically disabled for that process and promoted to notify_on_complete behavior (one notification on exit, no more mid-process spam). USE ONLY for truly rare, one-shot mid-process signals on LONG-LIVED processes that will never exit on their own — e.g. ['Application startup complete'] on a server so you know when to hit its endpoint, or ['migration done'] on a daemon. DO NOT use for: (1) end-of-run markers like 'DONE'/'PASS' — use notify_on_complete instead; (2) error patterns like 'ERROR'/'Traceback' in loops or multi-item batch jobs — they fire on every iteration and you'll hit the strike limit fast; (3) anything you'd ever combine with notify_on_complete. When in doubt, choose notify_on_complete. MUTUALLY EXCLUSIVE with notify_on_complete — set one, not both."
+                }
+              },
+              "required": [
+                "command"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "text_to_speech",
+            "description": "Convert text to speech audio. Returns a MEDIA: path that the platform delivers as native audio. Compatible providers render as a voice bubble on Telegram; otherwise audio is sent as a regular attachment. In CLI mode, saves to ~/voice-memos/. Voice and provider are user-configured (built-in providers like edge/openai or custom command providers under tts.providers.<name>), not model-selected.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "text": {
+                  "type": "string",
+                  "description": "The text to convert to speech. Provider-specific character caps apply and are enforced automatically (OpenAI 4096, xAI 15000, MiniMax 10000, ElevenLabs 5k-40k depending on model); over-long input is truncated."
+                },
+                "output_path": {
+                  "type": "string",
+                  "description": "Optional custom file path to save the audio. Defaults to /data/.hermes/audio_cache/<timestamp>.mp3"
+                }
+              },
+              "required": [
+                "text"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "todo",
+            "description": "Manage your task list for the current session. Use for complex tasks with 3+ steps or when the user provides multiple tasks. Call with no parameters to read the current list.\n\nWriting:\n- Provide 'todos' array to create/update items\n- merge=false (default): replace the entire list with a fresh plan\n- merge=true: update existing items by id, add any new ones\n\nEach item: {id: string, content: string, status: pending|in_progress|completed|cancelled}\nList order is priority. Only ONE item in_progress at a time.\nMark items completed immediately when done. If something fails, cancel it and add a revised item.\n\nAlways returns the full current list.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "todos": {
+                  "type": "array",
+                  "description": "Task items to write. Omit to read current list.",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "id": {
+                        "type": "string",
+                        "description": "Unique item identifier"
+                      },
+                      "content": {
+                        "type": "string",
+                        "description": "Task description"
+                      },
+                      "status": {
+                        "type": "string",
+                        "enum": [
+                          "pending",
+                          "in_progress",
+                          "completed",
+                          "cancelled"
+                        ],
+                        "description": "Current status"
+                      }
+                    },
+                    "required": [
+                      "id",
+                      "content",
+                      "status"
+                    ]
+                  }
+                },
+                "merge": {
+                  "type": "boolean",
+                  "description": "true: update existing items by id, add new ones. false (default): replace the entire list.",
+                  "default": false
+                }
+              }
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "vision_analyze",
+            "description": "Load an image into the conversation so you can see it. Accepts a URL, local file path, or data URL. When your active model has native vision, the image is attached to your context directly and you read the pixels yourself on the next turn — call this any time the user references an image (filepath in their message, URL in tool output, screenshot from the browser, etc.). For non-vision models, falls back to an auxiliary vision model that returns a text description.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "image_url": {
+                  "type": "string",
+                  "description": "Image URL (http/https), local file path, or data: URL to load."
+                },
+                "question": {
+                  "type": "string",
+                  "description": "Your specific question or request about the image. Optional context the model uses on the next turn after seeing the image."
+                }
+              },
+              "required": [
+                "image_url",
+                "question"
+              ]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "write_file",
+            "description": "Write content to a file, completely replacing existing content. Use this instead of echo/cat heredoc in terminal. Creates parent directories automatically. OVERWRITES the entire file — use 'patch' for targeted edits. Auto-runs syntax checks on .py/.json/.yaml/.toml and other linted languages; only NEW errors introduced by this write are surfaced (pre-existing errors are filtered out).",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "path": {
+                  "type": "string",
+                  "description": "Path to the file to write (will be created if it doesn't exist, overwritten if it does)"
+                },
+                "content": {
+                  "type": "string",
+                  "description": "Complete content to write to the file"
+                },
+                "cross_profile": {
+                  "type": "boolean",
+                  "description": "Opt out of the cross-profile soft guard. Defaults to false. Set true ONLY after explicit user direction to edit another Hermes profile's skills/plugins/cron/memories — by default these writes are blocked with a warning because they affect a different profile than the one this session is running under.",
+                  "default": false
+                }
+              },
+              "required": [
+                "path",
+                "content"
+              ]
+            }
+          }
+        }
+      ],
+      "max_tokens": 16384
+    }
+  },
+  "error": {
+    "type": "RateLimitError",
+    "message": "Error code: 429 - {'status': 429, 'title': 'Too Many Requests'}",
+    "status_code": 429,
+    "body": {
+      "status": 429,
+      "title": "Too Many Requests"
+    },
+    "response_status": 429,
+    "response_text": "{\"status\":429,\"title\":\"Too Many Requests\"}"
+  }
+}

state/state.db

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:352a9bb23c329c5a9bf235baf56917358b5b64b03f1a11d261fadae9c3cdb721
-size 4096
+oid sha256:e9af6519923ca55cd3238e97ca198f9e101313141302d027ef0d30876c26a2f0
+size 294912