clarify

Ask the user a question when you need clarification, feedback, or a decision before proceeding. Supports two modes:

1. **Multiple choice** — provide up to 4 choices. The user picks one or types their own answer via a 5th 'Other' option.
2. **Open-ended** — omit choices entirely. The user types a free-form response.

Use this tool when:
- The task is ambiguous and you need the user to choose an approach
- You want post-task feedback ('How did that work out?')
- You want to offer to save a skill or update memory
- A decision has meaningful trade-offs the user should weigh in on

Do 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.

The question to present to the user.

Choices:
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.

cronjob

Manage scheduled cron jobs with a single compressed tool.

Use action='create' to schedule a new job from a prompt or one or more skills.
Use action='list' to inspect jobs.
Use action='update', 'pause', 'resume', 'remove', or 'run' to manage an existing job.

To stop a job the user no longer wants: first action='list' to find the job_id, then action='remove' with that job_id. Never guess job IDs — always list first.

Jobs run in a fresh session with no current-chat context, so prompts must be self-contained.
If skills are provided on create, the future cron run loads those skills in order, then follows the prompt as the task instruction.
On update, passing skills=[] clears attached skills.

NOTE: The agent's final response is auto-delivered to the target. Put the primary
user-facing content in the final response. Cron jobs run autonomously with no user
present — they cannot ask questions or request clarification.

Important safety rule: cron-run sessions should not recursively schedule more cron jobs.

One of: create, list, update, pause, resume, remove, run

Required for update/pause/resume/remove/run

For create: the full self-contained prompt. If skills are also provided, this becomes the task instruction paired with those skills.

For create/update: '30m', 'every 2h', '0 9 * * *', or ISO timestamp

Optional human-friendly name

Optional repeat count. Omit for defaults (once for one-shot, forever for recurring).

Omit this parameter to auto-deliver back to the current chat and topic (recommended). Auto-detection preserves thread/topic context. Only set explicitly when the user asks to deliver somewhere OTHER than the current conversation. Values: 'origin' (same as omitting), 'local' (no delivery, save only), or platform:chat_id:thread_id for a specific destination. Examples: 'telegram:-1001234567890:17585', 'discord:#engineering', 'sms:+15551234567'. WARNING: 'platform:chat_id' without :thread_id loses topic targeting.

Optional ordered list of skill names to load before executing the cron prompt. On update, pass an empty array to clear attached skills.

Optional per-job model override. If provider is omitted, the current main provider is pinned at creation time so the job stays stable.

Provider name (e.g. 'openrouter', 'anthropic', or 'custom:<name>' for a provider defined in custom_providers config — always include the ':<name>' suffix, never pass the bare 'custom'). Omit to use and pin the current provider.

Model name (e.g. 'anthropic/claude-sonnet-4', 'claude-sonnet-4')

Optional path to a script that runs each tick. In the default mode its stdout is injected into the agent's prompt as context (data-collection / change-detection pattern). With no_agent=True, the script IS the job and its stdout is delivered verbatim (classic watchdog pattern). Relative paths resolve under ~/.hermes/scripts/. ``.sh``/``.bash`` extensions run via bash, everything else via Python. On update, pass empty string to clear.

Default: False (LLM-driven job — the agent runs the prompt each tick). Set True to skip the LLM entirely: the scheduler just runs ``script`` on schedule and delivers its stdout verbatim. No tokens, no agent loop, no model override honoured.

REQUIREMENTS when True: ``script`` MUST be set (``prompt`` and ``skills`` are ignored).

DELIVERY SEMANTICS when True: (a) non-empty stdout is sent verbatim as the message; (b) EMPTY stdout means SILENT — nothing is sent to the user and they won't see anything happened, so design your script to stay quiet when there's nothing to report (the watchdog pattern); (c) non-zero exit / timeout sends an error alert so a broken watchdog can't fail silently.

WHEN TO USE True: recurring script-only pings where the script itself produces the exact message text (memory/disk/GPU watchdogs, threshold alerts, heartbeats, CI notifications, API pollers with a fixed output shape). WHEN TO USE False (default): anything that needs reasoning — summarize a feed, draft a daily briefing, pick interesting items, rephrase data for a human, follow conditional logic based on content.

Optional job ID or list of job IDs whose most recent completed output is injected into the prompt as context before each run. Use this to chain cron jobs: job A collects data, job B processes it. Each entry must be a valid job ID (from cronjob action='list'). Note: injects the most recent completed output — does not wait for upstream jobs running in the same tick. On update, pass an empty array to clear.

Optional list of toolset names to restrict the job's agent to (e.g. ["web", "terminal", "file", "delegation"]). When set, only tools from these toolsets are loaded, significantly reducing input token overhead. When omitted, all default tools are loaded. Infer from the job's prompt — e.g. use "web" if it calls web_search, "terminal" if it runs scripts, "file" if it reads files, "delegation" if it calls delegate_task. On update, pass an empty array to clear.

Optional absolute path to run the job from. When set, AGENTS.md / CLAUDE.md / .cursorrules from that directory are injected into the system prompt, and the terminal/file/code_exec tools use it as their working directory — useful for running a job inside a specific project repo. Must be an absolute path that exists. When unset (default), preserves the original behaviour: no project context files, tools use the scheduler's cwd. On update, pass an empty string to clear. Jobs with workdir run sequentially (not parallel) to keep per-job directories isolated.

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.

TWO MODES (one of 'goal' or 'tasks' is required):
1. Single task: provide 'goal' (+ optional context, toolsets)
2. Batch (parallel): provide 'tasks' array with up to delegation.max_concurrent_children items (default 3, configurable via config.yaml, no hard ceiling). All run concurrently and results are returned together. Nested delegation requires role='orchestrator' and delegation.max_spawn_depth >= 2.

WHEN TO USE delegate_task:
- Reasoning-heavy subtasks (debugging, code review, research synthesis)
- Tasks that would flood your context with intermediate data
- Parallel independent workstreams (research A and B simultaneously)

WHEN NOT TO USE (use these instead):
- Mechanical multi-step work with no reasoning needed -> use execute_code
- Single tool call -> just call the tool directly
- Tasks needing user interaction -> subagents cannot use clarify
- 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.

IMPORTANT:
- Subagents have NO memory of your conversation. Pass all relevant info (file paths, error messages, constraints) via the 'context' field.
- 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.
- 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.
- Leaf subagents (role='leaf', the default) CANNOT call: delegate_task, clarify, memory, send_message, execute_code.
- 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 delegation.max_spawn_depth (default 2) and can be disabled globally via delegation.orchestrator_enabled=false.
- Each subagent gets its own terminal session (separate working directory and state).
- Results are always returned as an array, one entry per task.

What the subagent should accomplish. Be specific and self-contained -- the subagent knows nothing about your conversation history.

Background information the subagent needs: file paths, error messages, project structure, constraints. The more specific you are, the better the subagent performs.

Toolsets to enable for this subagent. Default: inherits your enabled toolsets. Available toolsets: 'browser', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'vision', 'web', 'yuanbao'. Common patterns: ['terminal', 'file'] for code work, ['web'] for research, ['browser'] for web interaction, ['terminal', 'file', 'web'] for full-stack tasks.

Task goal

Task-specific context

Toolsets for this specific task. Available: 'browser', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'video', 'vision', 'web', 'yuanbao'. Use 'web' for network access, 'terminal' for shell, 'browser' for web interaction.

Per-task ACP command override (e.g. 'claude'). Overrides the top-level acp_command for this task only.

Per-task ACP args override.

Per-task role override. See top-level 'role' for semantics.

Batch mode: tasks to run in parallel (limit configurable via delegation.max_concurrent_children, default 3). Each gets its own subagent with isolated context and terminal session. When provided, top-level goal/context/toolsets are ignored.

Role of the child agent. 'leaf' (default) = focused worker, cannot delegate further. 'orchestrator' = can use delegate_task to spawn its own workers. Requires delegation.max_spawn_depth >= 2 in config; ignored (treated as 'leaf') when the child would exceed max_spawn_depth or when delegation.orchestrator_enabled=false.

Override ACP command for child agents (e.g. 'claude', 'copilot'). When set, children use ACP subprocess transport instead of inheriting the parent's transport. Enables spawning Claude Code (claude --acp --stdio) or other ACP-capable agents from any parent, including Discord/Telegram/CLI.

Arguments for the ACP command (default: ['--acp', '--stdio']). Only used when acp_command is set. Example: ['--acp', '--stdio', '--model', 'claude-opus-4-6']

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).

Use 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.

Available via `from hermes_tools import ...`:

  read_file(path: str, offset: int = 1, limit: int = 500) -> dict
    Lines are 1-indexed. Returns {"content": "...", "total_lines": N}
  write_file(path: str, content: str) -> dict
    Always overwrites the entire file.
  search_files(pattern: str, target="content", path=".", file_glob=None, limit=50) -> dict
    target: "content" (search inside files) or "files" (find files by name). Returns {"matches": [...]}
  patch(path: str, old_string: str, new_string: str, replace_all: bool = False) -> dict
    Replaces old_string with new_string in the file.
  terminal(command: str, timeout=None, workdir=None) -> dict
    Foreground only (no background/pty). Returns {"output": "...", "exit_code": N}

Limits: 5-minute timeout, 50KB stdout cap, max 50 tool calls per script. terminal() is foreground-only (no background or pty).

Scripts 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().

Print your final result to stdout. Use Python stdlib (json, re, math, csv, datetime, collections, etc.) for processing between tool calls.

Also available (no import needed — built into hermes_tools):
  json_parse(text: str) — json.loads with strict=False; use for terminal() output with control chars
  shell_quote(s: str) — shlex.quote(); use when interpolating dynamic strings into shell commands
  retry(fn, max_attempts=3, delay=2) — retry with exponential backoff for transient failures

Python code to execute. Import tools with `from hermes_tools import terminal, ...` and print your final result to stdout.

memory

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.

WHEN TO SAVE (do this proactively, don't wait to be asked):
- User corrects you or says 'remember this' / 'don't do that again'
- User shares a preference, habit, or personal detail (name, role, timezone, coding style)
- You discover something about the environment (OS, installed tools, project structure)
- You learn a convention, API quirk, or workflow specific to this user's setup
- You identify a stable fact that will be useful again in future sessions

PRIORITY: User preferences and corrections > environment facts > procedural knowledge. The most valuable memory prevents the user from having to repeat themselves.

Do NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts.
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.

TWO TARGETS:
- 'user': who the user is -- name, role, preferences, communication style, pet peeves
- 'memory': your notes -- environment facts, project conventions, tool quirks, lessons learned

ACTIONS: add (new entry), replace (update existing -- old_text identifies it), remove (delete -- old_text identifies it).

SKIP: trivial/obvious info, things easily re-discovered, raw data dumps, and temporary task state.

The action to perform.

Which memory store: 'memory' for personal notes, 'user' for user profile.

The entry content. Required for 'add' and 'replace'.

Short unique substring identifying the entry to replace or remove.

patch

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.

Replace mode (default): find a unique string and replace it.
Patch mode: apply V4A multi-file patches for bulk changes.

Edit mode: 'replace' for targeted find-and-replace, 'patch' for V4A multi-file patches

File path to edit (required for 'replace' mode)

Text to find in the file (required for 'replace' mode). Must be unique in the file unless replace_all=true. Include enough surrounding context to ensure uniqueness.

Replacement text (required for 'replace' mode). Can be empty string to delete the matched text.

Replace all occurrences instead of requiring a unique match (default: false)

V4A format patch content (required for 'patch' mode). Format:
*** Begin Patch
*** Update File: path/to/file
@@ context hint @@
 context line
-removed line
+added line
*** End Patch

process

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).

list poll log wait kill write submit close

Action to perform on background processes

Process session ID (from terminal background output). Required for all actions except 'list'.

Text to send to process stdin (for 'write' and 'submit' actions)

Max seconds to block for 'wait' action. Returns partial output on timeout.

Line offset for 'log' action (default: last 200 lines)

Max lines to return for 'log' action

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.

Path to the file to read (absolute, relative, or ~/path)

Line number to start reading from (1-indexed, default: 1)

Maximum number of lines to read (default: 500, max: 2000)

Search file contents or find files by name. Use this instead of grep/rg/find/ls in terminal. Ripgrep-backed, faster than shell equivalents.

Content search (target='content'): Regex search inside files. Output modes: full matches with line numbers, file paths only, or match counts.

File search (target='files'): Find files by glob pattern (e.g., '*.py', '*config*'). Also use this instead of ls — results sorted by modification time.

Regex pattern for content search, or glob pattern (e.g., '*.py') for file search

'content' searches inside file contents, 'files' searches for files by name

Directory or file to search in (default: current working directory)

Filter files by pattern in grep mode (e.g., '*.py' to only search Python files)

Maximum number of results to return (default: 50)

Skip first N results for pagination (default: 0)

Output format for grep mode: 'content' shows matching lines with line numbers, 'files_only' lists file paths, 'count' shows match counts per file

Number of context lines before and after each match (grep mode only)

Send a message to a connected messaging platform, or list available targets.

IMPORTANT: 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.
If the user just says a platform name like 'send to telegram', send directly to the home channel without listing first.

Action to perform. 'send' (default) sends a message. 'list' returns all available channels/contacts across connected platforms.

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)

The message text to send. To send an image or file, include MEDIA:<local_path> (e.g. 'MEDIA:/tmp/hermes/cache/img_xxx.jpg') in the message — the platform will deliver it as a native media attachment.

Search your long-term memory of past conversations, or browse recent sessions. This is your recall -- every past session is searchable, and this tool summarizes what happened.

TWO MODES:
1. Recent sessions (no query): Call with no arguments to see what was worked on recently. Returns titles, previews, and timestamps. Zero LLM cost, instant. Start here when the user asks what were we working on or what did we do recently.
2. Keyword search (with query): Search for specific topics across all past sessions. Returns LLM-generated summaries of matching sessions.

USE THIS PROACTIVELY when:
- The user says 'we did this before', 'remember when', 'last time', 'as I mentioned'
- The user asks about a topic you worked on before but don't have in current context
- The user references a project, person, or concept that seems familiar but isn't in memory
- You want to check if you've solved a similar problem before
- The user asks 'what did we do about X?' or 'how did we fix Y?'

Don't hesitate to search when it is actually cross-session -- it's fast and cheap. Better to search and confirm than to guess or ask the user to repeat themselves.

Search syntax: keywords joined with OR for broad recall (elevenlabs OR baseten OR funding), phrases for exact match ("docker networking"), boolean (python NOT java), prefix (deploy*). IMPORTANT: Use OR between keywords for best results — FTS5 defaults to AND which misses sessions that only mention some terms. If a broad OR query returns nothing, try individual keyword searches in parallel. Returns summaries of the top matching sessions.

Search query — keywords, phrases, or boolean expressions to find in past sessions. Omit this parameter entirely to browse recent sessions instead (returns titles, previews, timestamps with no LLM cost).

Optional: only search messages from specific roles (comma-separated). E.g. 'user,assistant' to skip tool outputs.

Max sessions to summarize (default: 3, max: 5).

Manage skills (create, update, delete). Skills are your procedural memory — reusable approaches for recurring task types. New skills go to ~/.hermes/skills/; existing skills can be modified wherever they live.

Actions: 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.

On 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.

Create when: complex task succeeded (5+ calls), errors overcome, user-corrected approach worked, non-trivial workflow discovered, or user asks you to remember a procedure.
Update 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.

After difficult/iterative tasks, offer to save as a skill. Skip for simple one-offs. Confirm with user before creating/deleting.

Good skills: trigger conditions, numbered steps with exact commands, pitfalls section, verification steps. Use skill_view() to see format examples.

Pinned 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.

create patch edit delete write_file remove_file

The action to perform.

Skill name (lowercase, hyphens/underscores, max 64 chars). Must match an existing skill for patch/edit/delete/write_file/remove_file.

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.

Text to find in the file (required for 'patch'). Must be unique unless replace_all=true. Include enough surrounding context to ensure uniqueness.

Replacement text (required for 'patch'). Can be empty string to delete the matched text.

For 'patch': replace all occurrences instead of requiring a unique match (default: false).

Optional category/domain for organizing the skill (e.g., 'devops', 'data-science', 'mlops'). Creates a subdirectory grouping. Only used with 'create'.

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.

Content for the file. Required for 'write_file'.

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.

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.

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').

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.

List available skills (name + description). Use skill_view(name) to load full content.

Optional category filter to narrow results

terminal

Execute shell commands on a Linux environment. Filesystem usually persists between calls.

Do NOT use cat/head/tail to read files — use read_file instead.
Do NOT use grep/rg/find to search — use search_files instead.
Do NOT use ls to list directories — use search_files(target='files') instead.
Do NOT use sed/awk to edit files — use patch instead.
Do NOT use echo/cat heredoc to create files — use write_file instead.
Reserve terminal for: builds, installs, git, processes, scripts, network, package managers, and anything that needs a shell.

Foreground (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.
Background: Set background=true to get a session_id. Two patterns:
  (1) Long-lived processes that never exit (servers, watchers).
  (2) Long-running tasks with notify_on_complete=true — you can keep working on other things and the system auto-notifies you when the task finishes. Great for test suites, builds, deployments, or anything that takes more than a minute.
For 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.
After starting a server, verify readiness with a health check or log signal, then run tests in a separate terminal() call. Avoid blind sleep loops.
Use process(action="poll") for progress checks, process(action="wait") to block until done.
Working directory: Use 'workdir' for per-command cwd.
PTY mode: Set pty=true for interactive CLI tools (Codex, Claude Code, Python REPL).

Do NOT use vim/nano/interactive tools without pty=true — they hang without a pseudo-terminal. Pipe git output to cat if it might page.

The command to execute on the VM

Run the command in the background. Two patterns: (1) Long-lived processes that never exit (servers, watchers). (2) Long-running tasks paired with notify_on_complete=true — you can keep working and get notified when the task finishes. For short commands, prefer foreground with a generous timeout instead.

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.

Working directory for this command (absolute path). Defaults to the session working directory.

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.

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.

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.

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.

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.

Optional custom file path to save the audio. Defaults to ~/.hermes/audio_cache/<timestamp>.mp3

todo

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.

Writing:
- Provide 'todos' array to create/update items
- merge=false (default): replace the entire list with a fresh plan
- merge=true: update existing items by id, add any new ones

Each item: {id: string, content: string, status: pending|in_progress|completed|cancelled}
List order is priority. Only ONE item in_progress at a time.
Mark items completed immediately when done. If something fails, cancel it and add a revised item.

Always returns the full current list.

Task items to write. Omit to read current list.

Unique item identifier

Task description

Current status

true: update existing items by id, add new ones. false (default): replace the entire list.

Inspect an image from a URL, file path, or tool output when you need closer detail than what's visible in the conversation. If the user's image is already attached to the conversation and you can see it, just answer directly — only call this tool for images referenced by URL/path, images returned inside other tool results (browser screenshots, search thumbnails), or when you need a deeper look at a specific region the main model's vision may have missed.

Image URL (http/https) or local file path to analyze.

Your specific question or request about the image to resolve. The AI will automatically provide a complete image description AND answer your specific question.

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).

Path to the file to write (will be created if it doesn't exist, overwritten if it does)

Complete content to write to the file


Nutze den camofox Browser und durchsuche das ganze Internet nach 10 perfekten Hochzeitstagsgeschebkeb für meine Frau


Explanation: The user wants me to use the Camofox browser to search the internet for 10 perfect wedding anniversary gifts for his wife. Let me first load the Camofox browser skill and the ZimaOS quirks skill since this is running on ZimaOS.


zimaos-camofox-browser

---
name: zimaos-camofox-browser
description: "Camofox-Browser als persistenten Docker-Dienst auf ZimaOS für Hermes-Browser-Automation einrichten und betreiben."
version: 1.0.0
author: Kiwi (Ahmed Zeyd Aytac)
tags: [zimaos, camofox, browser, docker, compose, hermes, anti-detection, persistence]
---

# ZimaOS Camofox Browser

Ziel: Auf dem ZimaOS-Server soll Browser-Automation für Hermes **immer** über einen lokalen Camofox-Browser-Container laufen — nicht über Webtop, nicht primär über linuxserver/chromium, nicht primär über Kasm und nicht primär über Browserless.

## Architekturstandard

1. **Camofox local mode** als Docker/Compose-Dienst auf ZimaOS bevorzugen.
2. Hermes verwendet seine nativen Browser-Tools über `CAMOFOX_URL`.
3. Hermes direkt auf ZimaOS-Host → `CAMOFOX_URL=http://127.0.0.1:9377`.
4. Hermes selbst in Docker → gemeinsames Docker-Netzwerk und `CAMOFOX_URL=http://camofox-browser:9377`.
5. **Persistence aktivieren**, damit Cookies, Logins, LocalStorage und Sessions über Neustarts erhalten bleiben.
6. noVNC nur zur Beobachtung oder manuellen MFA/CAPTCHA/Login-Hilfe; noVNC ist **nicht** die primäre Agentensteuerung.
7. Camofox-API nicht öffentlich ins WAN exponieren. Port 9377 an localhost oder nur an internes Docker-Netzwerk binden.
8. **Keinen `CAMOFOX_API_KEY` setzen**, solange Hermes' Camofox-Integration bei gesetztem Key 403-Probleme haben kann. Sicherheit stattdessen über Bind-Adresse, Firewall, Docker-Netzwerk, VPN oder SSH-Tunnel.
9. Für ZimaOS persistente Pfade unter `/DATA/AppData/camofox` verwenden. Keine fragilen Container ohne Volume.
10. Sessions nach Aufgaben: erst `browser.camofox.managed_persistence: true` prüfen, optional extern gemanagte Sessions mit `CAMOFOX_USER_ID`, `CAMOFOX_SESSION_KEY` und `CAMOFOX_ADOPT_EXISTING_TAB=true`.

## Referenz-Compose für ZimaOS

```yaml
services:
  camofox-browser:
    image: camofox-browser:local
    container_name: camofox-browser
    restart: unless-stopped
    ports:
      - "127.0.0.1:9377:9377"
      - "127.0.0.1:6080:6080"
    environment:
      CAMOFOX_PORT: "9377"
      ENABLE_VNC: "1"
      VNC_BIND: "0.0.0.0"
      VNC_RESOLUTION: "1920x1080"
      MAX_OLD_SPACE_SIZE: "2048"
    volumes:
      - /DATA/AppData/camofox:/root/.camofox
```

## Hermes-Konfiguration

### 1. `.env` — CAMOFOX_URL setzen

```bash
# In ~/.hermes/.env:
CAMOFOX_URL=http://127.0.0.1:9377
```

Bei Hermes-in-Docker stattdessen:
```bash
CAMOFOX_URL=http://camofox-browser:9377
```

### 2. `config.yaml` — managed persistence

```yaml
browser:
  camofox:
    managed_persistence: true
```

### 3. Browser-Toolset aktivieren

```bash
hermes tools enable browser
```

### 4. Hermes vollständig neu starten

Nach allen Änderungen muss Hermes komplett neu gestartet werden (Gateway-Restart oder CLI-Neustart).

## Verifikation

### Schritt 1: Camofox-Erreichbarkeit prüfen

```bash
curl -fsS http://127.0.0.1:9377/health
# oder einen anderen API-Endpunkt des Camofox-Servers
```

### Schritt 2: CAMOFOX_URL in .env prüfen

```bash
grep CAMOFOX_URL ~/.hermes/.env
```

### Schritt 3: Browser-Aufgabe + noVNC-Beobachtung

```bash
# noVNC über SSH-Tunnel:
ssh -L 6080:127.0.0.1:6080 user@zimaos
# Dann im Browser: http://localhost:6080
```

Starte eine Browser-Aufgabe in Hermes und beobachte über noVNC.

### Schritt 4: Persistenz-Test

1. Logge dich manuell auf einer Website ein.
2. Beende die Browser-Aufgabe.
3. Starte eine neue Browser-Aufgabe.
4. Prüfe, ob der Login erhalten bleibt.

### Schritt 5: Docker-Netzwerk-Fallback

Wenn Hermes in Docker läuft und `127.0.0.1` nicht funktioniert:
```bash
CAMOFOX_URL=http://camofox-browser:9377
```
im gemeinsamen Docker-Netzwerk verwenden.

## Build-Prozess (ZimaOS)

Da `jo-inc/camofox-browser` kein öffentliches Docker-Image hat, muss **lokal gebaut** werden.
ZimaOS hat kein `make` — die Schritte sind manuell:

### 1. Repo clonen + Assets downloaden

```bash
cd /tmp
git clone https://github.com/jo-inc/camofox-browser.git
cd camofox-browser
mkdir -p dist
curl -fSL "https://github.com/daijro/camoufox/releases/download/v135.0.1-beta.24/camoufox-135.0.1-beta.24-lin.x86_64.zip" -o dist/camoufox-x86_64.zip
curl -fSL "https://github.com/yt-dlp/yt-dlp/releases/latest/download/yt-dlp_linux" -o dist/yt-dlp-x86_64
```

### 2. Image bauen (mit VNC-Support)

Der Standard-Dockerfile hat **kein** `x11vnc`, `noVNC` oder `websockify`.
Ein angepasster Dockerfile wird benötigt. Siehe `references/build-dockerfile.md` für das vollständige Dockerfile.

```bash
DOCKER_BUILDKIT=1 docker build --no-cache \
  --build-arg ARCH=x86_64 \
  --build-arg CAMOUFOX_VERSION=135.0.1 \
  --build-arg CAMOUFOX_RELEASE=beta.24 \
  -t camofox-browser:135.0.1-x86_64 \
  -f /path/to/custom.Dockerfile .
```

### 3. VNC-Config für Camofox

VNC ist im Standard-Image **deaktiviert**. Config mit aktiviertem VNC als Volume mounten:

```json
{
  "id": "camofox-browser",
  "name": "Camofox Browser",
  "version": "1.6.0",
  "plugins": {
    "youtube": { "enabled": true },
    "persistence": { "enabled": true },
    "vnc": { "enabled": true, "resolution": "1920x1080" }
  }
}
```

Die Datei ins Compose-File einbinden (siehe Referenz-Compose).

### 4. Websockify nachinstallieren (im laufenden Container)

`websockify` fehlt im Python-Path des Containers und muss nachinstalliert werden:

```bash
docker exec camofox-browser pip3 install --break-system-packages websockify
# Oder im Dockerfile ergänzen: RUN pip3 install --break-system-packages websockify
```

### Compose-File starten

```bash
docker --config /tmp/docker-config compose -f /DATA/AppData/camofox-compose/docker-compose.yml up -d
```

**Wichtig:** Auf ZimaOS immer `DOCKER_CONFIG=/tmp/docker-config` setzen — `/root/.docker` ist read-only.

## Browser-Automation Patterns

### Content Extraction from SPAs (JS-heavy sites)

Many modern sites are React/SPA — `curl` gets empty `<div id="root">`. This includes Austrian government sites: **RIS** (Rechtsinformationssystem), **Findok** (BMF Steuerdokumente), WU Wien, ÖH WU. For legal research on RIS, see `references/ris-legal-research.md` for the proven workflow.

General extraction options for SPAs:

1. **links endpoint** (fast, no JS needed): `GET /tabs/:tabId/links?userId=kiwi` — returns link texts, but hrefs may be empty (JS-routed).
2. **screenshot + vision** (reliable): Take screenshot, `vision_analyze` it for visual content.
3. **jina.ai reader** (best for text extraction): `curl -sL "https://r.jina.ai/<URL>" -H "Accept: text/plain"` — renders JS and returns clean markdown. Use when browser-extracted content is insufficient.
4. **Hidden JSON APIs** (fastest, no browser needed): Many JS SPAs have backend API endpoints. Look for them in page source (`grep -oP 'api|endpoint|json|type=\d+'`), or try common patterns like `?type=INTEGER` on the page URL. Example: `ihr-notariat.at/notarfinder/?type=1602231006` returned the full Austrian notary database as JSON — avoiding the entire SPA. Always try this before launching browser automation for content extraction.
5. **evaluate endpoint**: `POST /tabs/:tabId/evaluate` — requires `CAMOFOX_API_KEY` unless loopback. For localhost calls without API key, prefer links + screenshot.

### Cookie / Consent Popups

Many EU sites (WU, ÖH) show cookie banners that overlay content. Dismiss via:
- `POST /tabs/:tabId/click` with selector `"button:has-text('Alle akzeptieren')"` or similar
- If clicking times out (popup blocks interaction), try waiting 2-3s first, then click
- Take screenshot after dismissal to verify

### Auth / sessionKey Convention

- **POST endpoints**: `userId` and `sessionKey` go in the **JSON body**, NOT as query params. Query params are ignored.
  ```bash
  # ✅ CORRECT
  curl -X POST "http://127.0.0.1:9377/tabs" \
    -d '{"userId":"kiwi","sessionKey":"default","url":"https://example.com"}'

  # ❌ WRONG — query params ignored
  curl -X POST "http://127.0.0.1:9377/tabs?userId=kiwi&sessionKey=default" \
    -d '{"url":"https://example.com"}'
  ```
- **GET endpoints** (screenshot, links): use **query params**.
  ```bash
  curl "http://127.0.0.1:9377/tabs/$TAB/screenshot?userId=kiwi&sessionKey=default"
  ```
- The `sessionKey` value is arbitrary — `"default"`, `"tuya"`, etc. all work as long as it's present.

### API Endpoint Quirks

| Endpoint | Method | Notes |
|----------|--------|-------|
| `/tabs` | POST | Create tab — `{userId, sessionKey, url}` in body → returns `tabId` |
| `/tabs?userId=kiwi` | GET | List all tabs for user — works |
| `/tabs/:tabId?userId=kiwi` | GET | May return 404 with current version — use listing instead |
| `/tabs/:tabId/links?userId=kiwi&sessionKey=X` | GET | Link extraction — JS-routed sites have empty hrefs (React SPA). Returns `{links, pagination}`. Buttons/submit inputs inside forms are NOT listed (they're not `<a>` tags) |
| `/tabs/:tabId/screenshot?userId=kiwi&sessionKey=X` | GET | Screenshot — works, reliable. Returns PNG via stdout |
| `/tabs/:tabId/evaluate` | POST | **BLOCKED without CAMOFOX_API_KEY** even on loopback. Returns `{"error":"This endpoint requires CAMOFOX_API_KEY except for loopback requests in non-production environments."}`. Workaround: use `/type` for form filling + `/click` for interaction |
| `/tabs/:tabId/type` | POST | Type text into an input field. Body: `{userId, sessionKey, selector, text}`. Returns `{"ok":true}`. Works for both text and password fields. Chain `/type` + `/click` as a substitute for `/evaluate` when API key is absent |
| `/tabs/:tabId/click` | POST | CSS selector click. Body: `{userId, sessionKey, selector}`. May return `{"error":"Internal server error"}` on submit buttons inside forms — `/type` + form interaction may be needed instead |
| `/tabs/:tabId/navigate` | POST | Set URL. Body: `{userId, sessionKey, url}`. **Cannot navigate to `javascript:` URLs** — returns "Bad Request". Only works with `http(s)://` URLs |
| `/health` | GET | Health check — `browserConnected` goes true lazily on first tab |

## Troubleshooting

- **Camofox nicht erreichbar:** `docker logs camofox-browser` prüfen.
- **403 bei gesetztem CAMOFOX_API_KEY:** Key entfernen, Sicherheit über Netzwerk-Binding sicherstellen.
- **Cookies/Logins nicht persistent:** Prüfen ob `/DATA/AppData/camofox` gemountet ist und `managed_persistence: true` in config.yaml steht.
- **noVNC nicht erreichbar:** Port 6080 nur an localhost gebunden? SSH-Tunnel nutzen: `ssh -L 6080:127.0.0.1:6080 user@zimaos`
- **`/root/.docker` read-only:** Auf ZimaOS `DOCKER_CONFIG=/tmp/docker-config` vor allen Docker-Befehlen setzen.
- **`make: command not found`:** ZimaOS hat kein make. Build-Schritte manuell ausführen (curl für Assets, docker build direkt).
- **`websockify: not found`:** Im Container `pip3 install --break-system-packages websockify` ausführen, dann `websockify --web /usr/share/novnc 0.0.0.0:6080 127.0.0.1:5900` starten.
- **`browserConnected: false` in Health:** Normal — Camoufox startet lazily erst beim ersten Tab-Request. Einen Tab öffnen, dann prüft Health auf `true`.
- **VNC-Plugin deaktiviert:** In `camofox.config.json` muss `"vnc": { "enabled": true, "resolution": "1920x1080" }` stehen. Per Volume-Mount überschreiben.

To view linked files, call skill_view(name, file_path) where file_path is e.g. 'references/api.md' or 'assets/config.yaml'


zimaos-quirks

---
name: zimaos-quirks
description: ZimaOS-Eigenheiten — read-only Root-FS, DOCKER_CONFIG, HOME=/DATA, Systemd-Service-Namen und andere Fallstricke.
version: 1.0.0
author: Hermes Agent (from Claude handover 2026-06-04)
license: MIT
metadata:
  hermes:
    tags: [zimaos, quirks, pitfalls, read-only, docker]
    related_skills: [zimaos-administration, zimaos-app-install]
---

# ZimaOS Quirks (Server-Eigenheiten)

ZimaOS hat einige ungewöhnliche Eigenschaften, die bei fast jeder Admin-Aufgabe zu Problemen führen können. Diese Seite dokumentiert sie zentral.

## Read-Only Root-Filesystem

- `/` ist **squashfs read-only** (Immutable-OS-Prinzip)
- `/root/` kann NICHTS persistent speichern — alle Schreibversuche schlagen fehl mit "Read-only file system"
- Betroffene Pfade die NICHT schreibbar sind: `/root/.docker/`, `/root/.hermes/`, `/root/.git/`, `/root/.ssh/`, `/root/.cache/`

**Workaround für Docker CLI:**
```bash
export DOCKER_CONFIG=/tmp/docker-config
# ODER
export DOCKER_CONFIG=/DATA/.docker-build
```

**Workaround für Tools die nach `/root/` schreiben wollen:**
```bash
HOME=/DATA <befehl>
# ODER
env HOME=/DATA XDG_CACHE_HOME=/DATA/.cache <befehl>
```

## Schreibbare Bereiche

Nur diese Pfade sind persistent schreibbar:
- `/DATA/` — Hauptdatenpartition (ext4)
- `/media/` — Zusätzliche Laufwerke
- `/tmp/` — Temporär (nicht persistent über reboots)
- `/var/lib/docker/` — Docker-Daten
- `/var/lib/casaos/` — CasaOS-App-Definitionen

## Docker-Besonderheiten

- **`DOCKER_CONFIG` immer setzen**, sonst schlägt `docker` CLI fehl
- **`docker compose` nur aus dem App-Verzeichnis** (`/var/lib/casaos/apps/<name>/`)
- **Niemals `docker run -d`** — erzeugt Legacy-Container ohne Compose

## Systemd-Service-Name

- Der ZimaOS-App-Management-Service heißt **`zimaos-app-management`** (NICHT `casaos-app-management`)
- Nach Änderungen an Compose-Files in `/var/lib/casaos/apps/`:
  ```bash
  systemctl restart zimaos-app-management
  ```
- Das informiert die ZimaOS-UI über neue/geänderte Apps

## Bei eigenen Tool-Aufrufen

Wenn du (Hermes) selbst Commands auf dem ZimaOS-Server ausführst:
- **Immer `HOME=/DATA`** setzen, bevor du was machst das CWD oder Home scannt
- **`cd /DATA`** vor Operationen die relative Pfade nutzen
- Grund: `/root/` ist read-only, und viele Tools versuchen `~/.config/`, `~/.cache/` etc. anzulegen

## Hermes-eigene Invocation

```bash
cd /DATA && sudo -u az-a env \
  HOME=/DATA \
  HERMES_HOME=/DATA/.hermes \
  XDG_STATE_HOME=/DATA/.hermes/state \
  XDG_DATA_HOME=/DATA/.hermes/share \
  XDG_CACHE_HOME=/DATA/.hermes/cache \
  /DATA/AppData/hermes/venv/bin/python -m hermes_cli.main -z "<prompt>" --yolo
```

## Weitere Quirks

- **Kein `unattended-upgrades`** — Sicherheitsupdates müssen manuell gemacht werden
- **Kein `ufw`** — iptables default policy ACCEPT, Router-Firewall als Schutz
- **Kein `make`** — Build-Schritte manuell ausführen
- **Network mode `host`** wird für Tailscale und Home Assistant verwendet (Ports direkt exponiert)


Explanation:
The user wants me to use the Camofox browser to search the internet for 10 perfect wedding anniversary gifts for his wife. Let me first check if Camofox is running, then use it to browse and search.

Let me check the Camofox health first, then open tabs to search for gift ideas.

The user said "Hochzeitstagsgeschebkeb" which is clearly a typo for "Hochzeitstagsgeschenke" (wedding anniversary gifts).

Let me:
1. Check Camofox health
2. Open a browser tab and search
3. Use multiple searches to find good gift ideas


terminal

Output: {"ok":true,"engine":"camoufox","browserConnected":false,"browserRunning":false,"activeTabs":0,"activeSessions":0,"consecutiveFailures":0,"memory":{"rssMb":219,"heapUsedMb":87,"nativeMemMb":132}}


Camofox läuft. Lass mich das Internet systematisch durchforsten — ich öffne Tabs und suche auf mehreren Seiten parallel nach den besten Hochzeitstagsgeschenk-Ideen.

Explanation:
Camofox is running and healthy. Let me now use it to search for Hochzeitstagsgeschenke (wedding anniversary gifts) for the user's wife. Let me open a tab and search systematically.

Let me first check what anniversary they're celebrating - the user didn't specify. Let me just search broadly for "perfekte Hochzeitstagsgeschenke für die Frau" or similar, covering a range of ideas.

Let me open a tab and navigate to Google or another search engine to start the research.

curl -sS -X POST http://127.0.0.1:9377/tabs \
  -H "Content-Type: application/json" \
  -d '{"userId":"kiwi","sessionKey":"default","url":"https://www.google.com/search?q=beste+hochzeitstagsgeschenke+f%C3%BCr+frau+2025+2026+originell+romantisch&hl=de&num=20"}' 2>&1


Explanation: The tab is created. Now I need to wait for the page to load, then extract the links or take a screenshot. Let me wait a few seconds first, then get the links.

sleep 5 && curl -sS "http://127.0.0.1:9377/tabs/0ce5fc93-7e9b-401d-b7f7-1435f9c2de66/links?userId=kiwi&sessionKey=default" 2>&1


Google zeigt hauptsächlich Shopping-Anzeigen. Lass mich die echten Suchergebnisse per Screenshot sehen und gleichzeitig spezialisierte Geschenkseiten durchsuchen.

Explanation:
Let me analyze what I've found so far from the Google search results. The links show some shopping ads but I need the actual organic search results. Let me also try some dedicated gift/idea sites. Let me use jina.ai reader on some of the key result pages, and also try specific gift guide websites.

Let me take a screenshot of the Google results to see the organic listings, and also navigate to some dedicated gift guide sites.

curl -sS "http://127.0.0.1:9377/tabs/0ce5fc93-7e9b-401d-b7f7-1435f9c2de66/screenshot?userId=kiwi&sessionKey=default" -o /tmp/google_gifts.png 2>&1 && echo "OK: $(wc -c < /tmp/google_gifts.png) bytes"


Output: OK: 228169 bytes


Explanation: Let me look at the screenshot and simultaneously open specialized tabs for gift ideas.

Question: Liste ALLE organischen (nicht gesponserten) Suchergebnisse auf dieser Google-Seite. Extrahiere URLs und Titel der Web-Ergebnisse (die blauen Links unterhalb der Anzeigen). Ignoriere Shopping-Anzeigen.


Okay, let's break down this Google search results page.

**Image Description & Explanation**

This is a screenshot of a Google search results page, specifically for the search term "romantisch" (romantic in German). Here's a detailed breakdown of the elements:

1.  **Google Logo & Language/Location:**
    *   The prominent Google logo is in the top left corner.
    *   The language setting is "DE" (German).
    *   The location setting is "DE" (Germany).
    *   A small "x" icon allows you to change the language and location.

2.  **Top Bar & Settings:**
    *   **"Klick-Modus" (Click Mode):** This indicates that the search results are displayed in a standard format.
    *   **"Alle" (All):** This shows that the search is not filtered by any specific category.
    *   **"Anmelden" (Sign In):**  This is the Google sign-in button.
    *   **"Bevor Sie zu Google weitergehen" (Before you continue to Google):** This section presents Google's cookie and data usage policy.

3.  **Cookie & Data Usage Prompt:**
    *   **"Wir verwenden Cookies und Daten, um..." (We use cookies and data to...):** This explains that Google uses cookies and data to improve your experience and tailor results.
    *   **"Ausfalle, die prüfen und Maßnahmen gegen Spam, Betrug und Missbrauch ergreifen" (Check for fraud and abuse):**  A key function of cookie usage is to combat malicious activity.
    *   **"Daten zu Spielerinteraktionen und Websites statistiken zu erheben" (Collect data on player interactions and website statistics):** Google gathers data on how users interact with Google services and websites.
    *   **"Mit den gewonnen Informationen verbessern Sie unsere Dienste" (Improve our services with the information gained):** The data is used to enhance Google's services.
    *   **Two Buttons:**
        *   **"Akzeptieren" (Accept):**  Allows Google to use cookies and data for all the stated purposes.
        *   **"Ablehnen" (Reject):**  Prevents Google from using cookies and data for the stated purposes, resulting in a less personalized experience.

4.  **Price Display:**
    *   **"€ 179,00" (€ 179.00):** This indicates a paid advertisement (likely for a romantic getaway or experience).
    *   **"Holzern" (Wooden Village):**  This is the name of the location associated with the advertisement.

5.  **Text Block:**
    *   **"Wenn Sie die Optionen nicht verstehen, wie unsere Dienste verwendet werden, und wie zusätzliche Informationen anzusehen, einschließlich Details zum Verwalten Ihrer Datenschutzeinstellungen, Sie können auch [g.co/privacy/analytics] besuchen." (If you don't understand the options, how our services are used, and how additional information can be viewed, including details on managing your privacy settings, you can also visit [g.co/privacy/analytics]).** This provides a link to Google's privacy policy.

6.  **Search Results:**
    *   **"Ergebnisse für bes romantisch" (Results for: romantic):**  This confirms the search term.
    *   **"Gesponsert" (Sponsored):** This indicates that the following results are paid advertisements.
    *   **List of Results:**  A list of links to websites related to "romantic" searches.  Each result includes a title and a small star rating.  Examples:
        *   "Holzern AT" (Wooden Village AT) - Kostenlos (Free)
        *   "Von Google" (From Google) -  (Likely a Google-owned service related to romance)
        *   "Nanbu Tekki Kobayashi..." (Nanbu Tekki Kobayashi...)

**Answer to the Question: Liste ALLE organischen (nicht gesponserten) Suchergebnisse auf dieser Google-Seite. Extrahiere URLs und Titel der Web-Ergebnisse (die blauen Links unterhalb der Anzeigen). Ignoriere Shopping-Anzeigen.**

Based on the image, there are **no organic (non-sponsored) search results** listed. All the results displayed are marked as "Gesponsert" (Sponsored).  Therefore, I cannot extract URLs and titles of non-sponsored results.

**Important Note:**  The screenshot only shows a portion of the search results page.  A full page would likely contain more results, some of which might be organic.


Die Cookie-Banner blockiert die Ergebnisse. Lass mich die Cookies akzeptieren und dann neu laden, und gleichzeitig gezielt Geschenk-Ratgeber-Seiten öffnen.

Explanation: The screenshot shows the cookie consent banner is blocking the actual results. I need to accept cookies first, then extract the organic results. Let me try a different approach — use the Jina reader or navigate to specific gift guide pages directly.

# Akzeptiere Cookies via Klick auf "Alle akzeptieren"
curl -sS -X POST "http://127.0.0.1:9377/tabs/0ce5fc93-7e9b-401d-b7f7-1435f9c2de66/click" \
  -H "Content-Type: application/json" \
  -d '{"userId":"kiwi","sessionKey":"default","selector":"button:has-text(\"Alle akzeptieren\")"}' 2>&1


Explanation: Cookies accepted. Now let me take a fresh screenshot and also open more targeted tabs with specific gift guide sites.

sleep 3 && curl -sS "http://127.0.0.1:9377/tabs/0ce5fc93-7e9b-401d-b7f7-1435f9c2de66/screenshot?userId=kiwi&sessionKey=default" -o /tmp/google_gifts2.png 2>&1 && echo "OK: $(wc -c < /tmp/google_gifts2.png) bytes"


Output: OK: 414984 bytes


Explanation: Let me look at the screenshot to see the actual organic search results now.

Question: Extrahiere ALLE organischen Suchergebnisse (die blauen Link-Titel, URLs und Snippets). Was sind die Top 10-15 Web-Ergebnisse zu Hochzeitstagsgeschenken? Ignoriere Shopping-Anzeigen.


Okay, let's break down this Google search results page for "beste hochzeitstagsgeschenke für frau 2025 2026 originell romantisch" (best wedding gifts for women 2025 2026 original romantic).

**Overall Description of the Image**

The image is a screenshot of a Google search results page. It’s a typical Google search result layout, designed to present information about wedding gifts for women, specifically targeting the year 2025-2026 and emphasizing romantic and original ideas.  The search query is prominently displayed at the top. The page is dominated by a grid of results, categorized into different sections:

*   **Top Results:** These are the most relevant results, displayed at the very top.
*   **Sponsored Products:** These are paid advertisements, clearly marked as "Gesponsertes Ergebnis" (Sponsored Result).
*   **Product Categories:**  These are grouped by product type (e.g., Holzern – Wood, Chanel… – Chanel, Personalisiert – Personalized, etc.).
*   **Image Thumbnails:** Each result includes a small image thumbnail to visually represent the product or website.
*   **Price:** The price of each item is displayed prominently.
*   **Star Ratings:**  User ratings (stars) are shown for each product, indicating customer satisfaction.
*   **Number of Reviews:** The number of reviews associated with each rating is displayed.
*   **Vendor/Shop Name:** The name of the vendor or shop offering the product is listed.
*   **Google Shopping Link:** A Google Shopping link is present for some results, allowing users to directly browse and purchase the item on Google Shopping.

**Detailed Breakdown of the Sections**

1.  **Search Query:** "beste hochzeitstagsgeschenke für frau 2025 2026 originell romantisch" – This is the user's search term, translated to "best wedding gifts for women 2025 2026 original romantic."

2.  **Top Results (Organic):**
    *   **Holzern (Wood):**  A wooden heart-shaped gift. Price: € 179.00.  Rating: 5 stars (10 reviews).  From shoparon…
    *   **Halsketten (Necklaces):** A delicate necklace. Price: € 65.00. Rating: 4.9 stars (42 reviews). From Händler…
    *   **CHANEL N°1 DE:** A Chanel perfume bottle. Price: € 65.00. Rating: 4.9 stars (42 reviews). From Channelable.

3.  **Sponsored Products:**
    *   **JONAS & ANNA:** A book titled "Wo alles begann" (Where it all began). Price: € 34.99. Rating: 4.9 stars (138 reviews). From Channelable.
    *   **KONG NAME:** A personalized poster. Price: € 27.00. Rating: 4.9 stars (15 reviews). From Klama.
    *   **Sternenartige Vinyl:** A vinyl record with a starry design. Price: € 4.95. Rating: 4 stars (2 reviews). From Händler…

4.  **Product Categories (Organic):**
    *   **Personalisiert:** Personalized items (various types). Price: € 27.00. Rating: 4.9 stars (15 reviews). From Klama.
    *   **Wo alles begann:** (Where it all began) – likely referring to the book above.
    *   **Personnimel:** Personalized items (various types). Price: € 4.95. Rating: 4 stars (2 reviews). From Händler…
    *   **Personalisierte Poster - Vinyl…:** Personalized posters on vinyl. Price: € 13.00. Rating: 4 stars (2 reviews). From Klama.
    *   **Einzigartige Roségold…:** Unique rose gold items. Price: € 15.00. Rating: 4 stars (2 reviews). From shoparon…
    *   **Kobako…:**  (Likely a brand name) –  items with a similar design to the rose gold item. Price: € 179.00. Rating: 4 stars (2 reviews). From Yoshi en.

**Extraction of Organic Search Results (Blue Links, URLs, Snippets) & Top 15 Web Results**

Here’s a list of the top 15 web results, extracted as requested, focusing on the blue link titles, URLs, and snippets:

1.  **Title:** Holzern - Herzgeschenk für die Braut
    **URL:** https://www.shoparon.at/geschenke/holzern-herzgeschenk-fuer-die-braut
    **Snippet:** "Ein wunderschönes Holzgeschenk für die Braut.  Holzgeschenke sind zeitlos und langlebig.  Bestellen Sie jetzt Ihr individuelles Holzgeschenk!"

2.  **Title:** Halsketten - Romantische Schmuckgeschenke für die Hochzeit
    **URL:** https://www.shoparon.at/geschenke/halsketten-romantische-schmuckgeschenke-fuer-die-hochzeit
    **Snippet:** "Finden Sie die perfekte Halskette als Hochzeitsgeschenk.  Schimmernde Halsketten für die Braut.  Jetzt entdecken!"

3.  **Title:** Chanel N°1 de - Ein luxuriöses Geschenk für die Braut
    **URL:** https://www.channelable.at/chanel-n-1-de-ein-luxuoses-geschenk-fuer-die-braut
    **Snippet:** "Chanel N°1 de – ein luxuriöses Parfumgeschenk für die Braut.  Ein unvergessliches Geschenk für einen besonderen Anlass."

4.  **Title:** Wo alles begann - Das perfekte Buchgeschenk für die Hochzeit
    **URL:** https://www.jonas-und-anna.at/wo-alles-begann-das-perfekte-buchgeschenk-fuer-die-hochzeit
    **Snippet:** "Das Buch 'Wo alles begann' ist das perfekte Geschenk für das Brautpaar.  Eine romantische Geschichte für einen besonderen Tag."

5.  **Title:** Personalisiertes Poster - Hochzeitsgeschenk mit Foto
    **URL:** https://www.klama.at/personalisiertes-poster-hochzeitsgeschenk-mit-foto
    **Snippet:** "Gestalten Sie ein personalisiertes Poster mit dem Foto des Brautpaares.  Ein einzigartiges Hochzeitsgeschenk."

6.  **Title:** Sternenartige Vinyl - Ein romantisches Musikgeschenk
    **URL:** https://www.händler-online.at/sternenartige-vinyl-ein-romantisches-musikgeschenk
    **Snippet:** "Ein romantisches Musikgeschenk mit einem Vinyl-Record mit Sternen.  Perfekt für Musikliebhaber."

7.  **Title:** Holzern - Hochzeitsgeschenk für die Braut
    **URL:** https://www.shoparon.at/geschenke/holzern-hochzeitsgeschenk-fuer-die-braut
    **Snippet:** "Ein wunderschönes Holzgeschenk für die Braut.  Holzgeschenke sind zeitlos und langlebig.  Bestellen Sie jetzt Ihr individuelles Holzgeschenk!"

8.  **Title:** Einzigartige Roségold - Hochzeitsgeschenke
    **URL:** https://www.shoparon.at/geschenke/einzigartige-rosgold-hochzeitsgeschenke
    **Snippet:** "Einzigartige Roségold-Geschenke für die Braut und den Bräutigam.  Schimmernde Roségold-Artikel für einen besonderen Anlass."

9.  **Title:** Kong Name - Personalisiertes Hochzeitsgeschenk
    **URL:** https://www.klama.at/kong-name-personalisiertes-hochzeitsgeschenk
    **Snippet:** "Ein personalisiertes Poster mit dem Namen des Brautpaares.  Ein einzigartiges Hochzeitsgeschenk."

10. **Title:**  Hochzeitstagsgeschenke - Ideen & Inspiration
    **URL:** (Not provided in the screenshot - likely a blog post or article)
    **Snippet:** (Not provided in the screenshot - likely a blog post or article)

11. **Title:**  Hochzeitsgeschenke - Holz
    **URL:** https://www.shoparon.at/geschenke/hochzeitsgeschenke-holz
    **Snippet:** "Entdecken Sie unsere Auswahl an Hochzeitsgeschenken aus Holz.  Holzgeschenke sind ein Klassiker und ein langlebiges Geschenk."

12. **Title:**  Hochzeitstagsgeschenke - Personalisiert
    **URL:** https://www.klama.at/geschen


Der Screenshot zeigt fast nur Shopping-Anzeigen. Ich wechsle die Strategie — ich öffne jetzt gezielt die besten Ratgeber- und Ideen-Seiten und extrahiere deren Inhalte.

Explanation: Die Vision-Ergebnisse sind größtenteils halluziniert (die KI hat URLs erfunden). Die Google-Seite zeigt hauptsächlich Shopping-Ergebnisse. Ich brauche einen besseren Ansatz. Lass mich stattdessen gezielt Artikel-Seiten und Ratgeber-Seiten besuchen, die tatsächlich Listen mit Hochzeitstagsgeschenken kuratieren. Ich versuche es mit Jina.ai Reader für die seriösen Quellen und gleichzeitig mit weiteren Suchanfragen.

import asyncio, json
from hermes_tools import terminal

# Step 1: Open multiple tabs for different gift guide searches
searches = [
    ("hochzeitstag_geschenk", "https://www.google.com/search?q=hochzeitstag+geschenk+frau+ideen+2025+2026&hl=de&num=15"),
    ("anniversary_gifts", "https://www.google.com/search?q=best+anniversary+gifts+for+wife+2025+2026+unique+romantic&hl=en&num=15"),
    ("geschenkideen_hochzeitstag", "https://www.google.com/search?q=geschenkideen+hochzeitstag+frau+originell+pers%C3%B6nlich&hl=de&num=15"),
    ("romantische_geschenke", "https://www.google.com/search?q=romantische+geschenke+frau+jahrestag+ideen&hl=de&num=15"),
    ("luxus_geschenke", "https://www.google.com/search?q=luxus+geschenk+frau+hochzeitstag+schmuck+erlebnis&hl=de&num=15"),
]

tab_ids = {}
for name, url in searches:
    result = terminal(f'''curl -sS -X POST http://127.0.0.1:9377/tabs -H "Content-Type: application/json" -d '{{"userId":"kiwi","sessionKey":"default","url":"{url}"}}' ''', timeout=15)
    try:
        data = json.loads(result['output'])
        tab_ids[name] = data['tabId']
        print(f"Tab {name}: {data['tabId']}")
    except:
        print(f"Tab {name}: ERROR - {result['output'][:200]}")

# Save tab IDs for later use
import os
os.makedirs('/tmp/hermes_gifts', exist_ok=True)
with open('/tmp/hermes_gifts/tabs.json', 'w') as f:
    json.dump(tab_ids, f)
print(f"\nSaved {len(tab_ids)} tab IDs")


Output:
Tab hochzeitstag_geschenk: 073f4a92-31c7-415d-9e71-ef41119e7281
Tab anniversary_gifts: 08b78b29-0ceb-4a66-b5a9-43e8eccad3ab
Tab geschenkideen_hochzeitstag: 576db1c3-900c-40ac-8083-678b54bb05f6
Tab romantische_geschenke: 0a45b14d-9dc5-43b3-959d-ebad2844fe63
Tab luxus_geschenke: 12e18ab7-71f8-4fdd-a015-99fc3581bb34

Saved 5 tab IDs


Jetzt hole ich die echten Inhalte von den Top-Geschenkeseiten per Jina.ai Reader und mache Screenshots der Suchergebnisse.

Explanation:
Let me now use Jina.ai reader to extract clean text from the best gift guide websites. But first, let me wait for pages to load, dismiss cookie banners, and then use the links endpoint to find relevant article URLs. Actually, let me take screenshots of each and use vision to find the actual organic results.

Actually, a faster approach: let me use Jina.ai reader on known good gift guide sites directly, while also taking screenshots of the Google results to find article URLs.

from hermes_tools import terminal
import json

# Load tab IDs
with open('/tmp/hermes_gifts/tabs.json') as f:
    tab_ids = json.load(f)

# Wait for pages to load, then take screenshots
import time
time.sleep(4)

# Take screenshots
for name, tid in list(tab_ids.items())[:3]:
    terminal(f'curl -sS "http://127.0.0.1:9377/tabs/{tid}/screenshot?userId=kiwi&sessionKey=default" -o /tmp/hermes_gifts/{name}.png', timeout=15)
    print(f"Screenshot {name}: done")

# Also use Jina to extract from known good German gift guide sites
gift_guides = [
    "https://r.jina.ai/https://www.geschenkidee.de/geschenke/hochzeitstag/",
    "https://r.jina.ai/https://www.idealode.de/magazin/hochzeitstagsgeschenke",
    "https://r.jina.ai/https://www.freundin.de/leben-hochzeitstagsgeschenke-ideen",
    "https://r.jina.ai/https://www.desired.de/lifestyle/hochzeitstag-geschenkideen/",
]

for url in gift_guides:
    r = terminal(f'curl -sL --max-time 15 "{url}" -H "Accept: text/plain"', timeout=20)
    site_name = url.split('/')[4].replace('www.','')
    # Save first 3000 chars
    content = r.get('output','')[:3000]
    with open(f'/tmp/hermes_gifts/jina_{site_name}.txt', 'w') as f:
        f.write(content)
    print(f"Jina {site_name}: {len(r.get('output',''))} chars")


Output:
Screenshot hochzeitstag_geschenk: done
Screenshot anniversary_gifts: done
Screenshot geschenkideen_hochzeitstag: done
Jina : 35394 chars
Jina : 195 chars
Jina : 3328 chars
Jina : 6689 chars


Explanation: Let me analyze what I've gotten so far. I have screenshots and some Jina content. Let me look at the screenshots first with vision, and then read the Jina content to get gift ideas.

Question: Lies ALLE organischen Suchergebnisse (nicht die Shopping-Anzeigen). Extrahiere die blauen Link-Titel und die darunter stehenden Beschreibungen/Snippets. Was sind die konkreten Geschenkideen die genannt werden? Übersetze ins Deutsche falls nötig.

Question: Read ALL organic search results (not ads). Extract the blue link titles and snippets below them. What specific gift ideas are mentioned? List all of them. Translate to German.


Okay, let's break down this Google image search result and answer the question.

**Image Description & Explanation**

The image is a screenshot of a Google search result page, specifically for the query "hochzeitsgeschenke frau idee 2020 2026" (wedding gifts for women ideas 2020-2026). It’s a Google Shopping result, heavily focused on jewelry and accessories. Here's a detailed breakdown:

* **Top Section (Google Shopping):**
    * **Headline:** "Gesponserte Produkte" (Sponsored Products) – This immediately indicates that the results are paid advertisements.
    * **Filter Options:**  A prominent sidebar offers filtering options:
        * "Von alles beginnen" (Starting from everything)
        * "KI-Modus" (AI Mode) - Suggesting AI-powered recommendations.
        * "Bilder" (Images) -  The search is visually driven.
        * "Produkte" (Products) -  Focuses on the actual items.
        * "Produkthostseiten" (Product Websites) - Links to the retailers selling the items.
        * "Kurze Videos" (Short Videos) -  Likely showcasing the products in action.
        * "Mehr" (More) -  Expands the options.
    * **Sorting:**  The results are sorted by "Gesponserte Ergebnisse" (Sponsored Results).
    * **Price Range:**  The price range is displayed at the top:  €3.95 Versand (Shipping €3.95) to €129 (Shipping €129).
    * **Shipping:** "Kostenlos" (Free Shipping) is prominently displayed for many items.
    * **Ratings:**  Star ratings (e.g., ★★★★☆) and the number of reviews (e.g., (553)) are shown for each product.

* **Product Listings:**  The main section displays a list of sponsored products. Each listing includes:
    * **Product Image:** A visual representation of the item.
    * **Product Title:**  A brief description of the product (e.g., "Damen Armban...").
    * **Price:** The price of the product (e.g., €29,95).
    * **Snippet/Description:** A short description or selling point of the product (e.g., "Momente -  Schmuck für besondere Anlässe").
    * **Brand Logo:**  The brand logo is displayed next to the product.

* **Bottom Section:**
    * **Official Swarovski® Website:**  A large banner promotes the official Swarovski® website.  It states "Swarovski® steht für 130 Jahre Meisterhafte Handwerkskunst" (Swarovski® stands for 130 years of masterful craftsmanship).
    * **URL:** The URL of the Swarovski® website is provided.

**Answering the Question: "Lies ALLE organischen Suchergebnisse (nicht die Shopping-Anzeigen). Extrahiere die blauen Link-Titel und die darunter stehenden Beschreibungen/Snippets. Was sind die konkreten Geschenkideen die genannt werden? Übersetze ins Deutsche falls nötig."**

Okay, let’s extract the organic search results (excluding the sponsored ads) and translate them:

Here's a breakdown of the organic results (the blue links):

1. **Damen Armban...**
   * **Title:** Damen Armban...
   * **Description:** Von shoparound...
   * **Translation:** Women's bracelets... (from shoparound...)

2. **Einzigartiges...**
   * **Title:** Einzigartiges - Personalschiff, Herzschleifer...
   * **Description:** € 29,95
   * **Translation:** Unique - Personalized pendants, heart shifters...
   * **Price:** €29.95

3. **Wo alles begann...**
   * **Title:** Wo alles begann - Schmuck für besondere Anlässe
   * **Description:** € 90,00 - € 129
   * **Translation:** Where it all began - Jewelry for special occasions
   * **Price:** €90.00 - €129

4. **Herzkerne -...**
   * **Title:** Herzkerne - Halsketten - Schmuck für besondere Anlässe
   * **Description:** € 65,00
   * **Translation:** Heart cores - Necklaces - Jewelry for special occasions
   * **Price:** €65.00

5. **Holzkernen -...**
   * **Title:** Holzkernen - Halsketten - Schmuck für besondere Anlässe
   * **Description:** € 129,00
   * **Translation:** Wooden cores - Necklaces - Jewelry for special occasions
   * **Price:** €129.00

6. **Holzkern AT...**
   * **Title:** Holzkern AT - Schmuck für besondere Anlässe
   * **Description:** € 269,00
   * **Translation:** Wooden core AT - Jewelry for special occasions
   * **Price:** €269.00

7. **Holzkern -...**
   * **Title:** Holzkern - Schmuck für besondere Anlässe
   * **Description:** € 179,00
   * **Translation:** Wooden core - Jewelry for special occasions
   * **Price:** €179.00

**Concrete Gift Ideas Mentioned:**

Based on these results, the following gift ideas are presented:

*   **Bracelets (Damen Armban...)**
*   **Personalized pendants and heart shifters (Einzigartiges...)**
*   **Jewelry for special occasions (Wo alles begann, Herzkerne, Holzkernen, Holzkern AT, Holzkern)** – This is a broad category, but the descriptions suggest necklaces and potentially other jewelry pieces.
*   **Wooden jewelry (Holzkernen)** - Specifically necklaces made of wood.

Let me know if you'd like me to elaborate on any aspect of this analysis!


Okay, let's break down this image and then address your question about the gift ideas.

**Image Description:**

The image is a screenshot of Google search results for the query "best anniversary gifts for wife 2025 2026 unique romantic." It’s a typical Google search page layout, displaying a series of organic results (not advertisements). Here’s a breakdown of the elements:

* **Search Bar:** At the top, there's the Google search bar, indicating the original query.
* **Google Filters:** Below the search bar, there are filters: "All," "Products," "Images," "Short videos," "Videos," "News," and "More." These allow the user to refine the search results.
* **Top Result:** The most prominent result is from "The Knot" (www.theknot.com). It’s a large banner image with a picture of a couple and text that reads "The 75+ Most Romantic, Great & Unique Gifts for Your Wife." The URL and date (May 5, 2026) are displayed beneath the banner. The text suggests the article is looking for the perfect gift for a wife for milestone and holiday occasions.
* **Second Result:** The second result is from "The Adventure Challenge" (theadventurechallenge.com). It’s a smaller banner image with a man and woman on a scenic adventure. The URL and date (May 26, 2026) are displayed beneath the banner. The text indicates a list of meaningful, sentimental, and romantic gifts.
* **Third Result:** The third result is from "Experiences.co.uk" (www.experiences.co.uk). It’s a smaller banner image with a couple enjoying a romantic experience. The URL and date (May 29, 2026) are displayed beneath the banner. The text suggests a blog post about the best anniversary gifts for her in 2026, including romantic getaways and adventure experiences.
* **Other Results:** Below these three prominent results, there are several smaller snippets of text, each linking to a different website. These snippets provide brief descriptions of the content on each page.

**Answering Your Question:**

Now, let’s extract the blue link titles and snippets and then translate the gift ideas to German.

**Extracted Blue Link Titles and Snippets:**

1.  **The Knot:**
    *   **Title:** The 75+ Most Romantic, Great & Unique Gifts for Your Wife
    *   **Snippet:** Looking for the perfect gift for your wife? Here are the best gifts for your wife for every holiday, milestone and occasion...
2.  **The Adventure Challenge:**
    *   **Title:** 47 Meaningful, Sentimental, & Romantic Gifts for your Wife
    *   **Snippet:** We’ve rounded up a huge range of different gift ideas for you to consider - everything from luxurious keepsakes to playful tokens.
3.  **Experiences.co.uk:**
    *   **Title:** Best Wedding Anniversary Gifts for Her (2026) | Blog
    *   **Snippet:** Discover the best wedding foodie and adventure experiences.

**Gift Ideas Listed:**

Based on the snippets, the following gift ideas are mentioned:

*   Luxurious Keepsakes
*   Playful Tokens
*   Romantic Getaways
*   Adventure Experiences
*   Foodie Experiences (implied by "wedding foodie")

**German Translation of Gift Ideas:**

Here's the translation of the gift ideas into German:

*   Luxurious Keepsakes: *Luxuriöse Andenken*
*   Playful Tokens: *Verspielte Geschenke*
*   Romantic Getaways: *Romantische Ausflüge/Urlaube*
*   Adventure Experiences: *Abenteuerliche Erlebnisse*
*   Foodie Experiences: *Kulinarische Erlebnisse* (or *Essen & Trinken-Erlebnisse*)

Do you want me to elaborate on any aspect of this response, or perhaps provide more details about the websites linked in the search results?


     1|Title: Seite nicht gefunden
     2|
     3|URL Source: https://www.desired.de/lifestyle/hochzeitstag-geschenkideen/
     4|
     5|Warning: Target URL returned error 404: Not Found
     6|
     7|Markdown Content:
     8|# Seite nicht gefunden
     9|[Weiter zur Navigation](https://www.desired.de/lifestyle/hochzeitstag-geschenkideen/#navbar-sidebar "Zur Navigation springen")[Weiter zum Inhalt](https://www.desired.de/lifestyle/hochzeitstag-geschenkideen/#main-content "Zum Inhalt springen")
    10|
    11|[](https://www.desired.de/shopping-tipps/oura-ring-5-was-der-neue-smart-ring-kann--01KT8VPKN50RFTW1MCYNEPHB0J)[](https://www.desired.de/shopping-tipps/oura-ring-5-was-der-neue-smart-ring-kann--01KT8VPKN50RFTW1MCYNEPHB0J)
    12|
    13|[](https://www.desired.de/ "desired.de")
    14|*   [Lifestyle](https://www.desired.de/lifestyle/ "Lifestyle")
    15|*   [Unterhaltung](https://www.desired.de/unterhaltung/ "Unterhaltung")
    16|*   [Liebe](https://www.desired.de/liebe/ "Liebe")
    17|*   [Beauty](https://www.desired.de/beauty/ "Beauty")
    18|*   [Fashion](https://www.desired.de/fashion/ "Fashion")
    19|
    20|*   [PUR](https://pur.desired.de/)
    21|*   [](https://www.desired.de/lifestyle/hochzeitstag-geschenkideen/#)
    22|
    23|Top Themen
    24|
    25|[Selbstreflexion](https://www.desired.de/themen/selbstreflexion--01JWWRFS6M549J6B6MAS05KGY0 "Selbstreflexion")[DIY](https://www.desired.de/themen/diy--01K959W77T1ZXMXY5P6YN3NG9A "DIY")[Feminismus](https://www.desired.de/themen/feminismus--01JWRGB30NX7N6JFX4CPZZ51MC "Feminismus")[Alle Themen](https://www.desired.de/themen/ "Alle Themen")
    26|
    27|*   [Lifestyle](https://www.desired.de/lifestyle/ "Lifestyle")
    28|
    29|    *   [Bücher & Hörbücher](https://www.desired.de/lifestyle/buecher/)
    30|    *   [Haushaltstipps](https://www.desired.de/lifestyle/haushaltstipps/)
    31|    *   [Home & Living](https://www.desired.de/lifestyle/living/)
    32|    *   [Karriere & Finanzen](https://www.desired.de/lifestyle/karriere-finanzen/)
    33|    *   [Kochen & Backen](https://www.desired.de/lifestyle/kochen-backen/)
    34|    *   [Persönlichkeit](https://www.desired.de/lifestyle/persoenlichkeit/)
    35|    *   [Reisen](https://www.desired.de/lifestyle/reisen/)
    36|
    37|*   [Unterhaltung](https://www.desired.de/unterhaltung/ "Unterhaltung")
    38|
    39|    *   [Promis](https://www.desired.de/unterhaltung/promis/)
    40|    *   [Kino & Film](https://www.desired.de/unterhaltung/kino-film/)
    41|    *   [TV & Streaming](https://www.desired.de/unterhaltung/tv-streaming/)
    42|
    43|*   [Liebe](https://www.desired.de/liebe/ "Liebe")
    44|
    45|    *   [Beziehung](https://www.desired.de/liebe/beziehung/)
    46|    *   [Dating](https://www.desired.de/liebe/dating/)
    47|    *   [Hochzeit](https://www.desired.de/liebe/hochzeit/)
    48|    *   [Sex](https://www.desired.de/liebe/sex/)
    49|    *   [Trennung](https://www.desired.de/liebe/trennung/)
    50|
    51|*   [Beauty](https://www.desired.de/beauty/ "Beauty")
    52|
    53|    *   [Haarentfernung](https://www.desired.de/beauty/haarentfernung/)
    54|    *   [Hautpflege](https://www.desired.de/beauty/schoene-haut/)
    55|    *   [Make-up](https://www.desired.de/beauty/make-up-kosmetik/)
    56|    *   [Frisuren](https://www.desired.de/beauty/frisuren/)
    57|    *   [Haarpflege](https://
    58|


Gute Quellen identifiziert! Jetzt hole ich die detaillierten Inhalte von diesen Top-Seiten.

Explanation:
Die Ergebnisse zeigen Shopping-Anzeigen und allgemeine Kategorien. Ich brauche bessere Inhalte. Lass mich direkt die Top-Geschenkeseiten mit Jina.ai abrufen und parallel spezifischere Suchen durchführen.

Aus den Screenshots habe ich jetzt gute Quellen:
- The Knot: 75+ Most Romantic Gifts for Your Wife
- The Adventure Challenge: 47 Meaningful Gifts
- Freundin.de hatte 3328 chars (wahrscheinlich gute Inhalte)

Lass mich diese direkt abrufen und dann eine finale Liste zusammenstellen.

from hermes_tools import terminal

# Fetch the best content pages directly
pages = [
    ("theknot", "https://r.jina.ai/https://www.theknot.com/content/anniversary-gifts-for-wife"),
    ("adventure_challenge", "https://r.jina.ai/https://www.theadventurechallenge.com/blogs/news/romantic-gifts-for-wife"),
    ("freundin", "https://r.jina.ai/https://www.freundin.de/leben-hochzeitstagsgeschenke-ideen"),
    ("brides", "https://r.jina.ai/https://www.brides.com/best-anniversary-gifts-for-wife-5094500"),
    ("vogue", "https://r.jina.ai/https://www.vogue.com/article/best-anniversary-gifts-for-her"),
    ("geschenkidee", "https://r.jina.ai/https://www.geschenkidee.de/geschenke/hochzeitstag/"),
    ("elite", "https://r.jina.ai/https://www.elitegift.de/hochzeitstag-geschenke/"),
]

for name, url in pages:
    r = terminal(f'curl -sL --max-time 20 "{url}" -H "Accept: text/plain"', timeout=25)
    content = r.get('output','')
    with open(f'/tmp/hermes_gifts/{name}.txt', 'w') as f:
        f.write(content)
    print(f"{name}: {len(content)} chars - first 100: {content[:100]}")

print("\nDone fetching all gift guides.")


Output:
theknot: 37840 chars - first 100: Title: 45 of the Most Heartwarming Anniversary Gifts for Your Wife

URL Source: https://www.theknot.
adventure_challenge: 14429 chars - first 100: Title: 404 Not Found

URL Source: https://www.theadventurechallenge.com/blogs/news/romantic-gifts-fo
freundin: 3328 chars - first 100: Title: Code 404

URL Source: https://www.freundin.de/leben-hochzeitstagsgeschenke-ideen

Warning: Ta
brides: 353 chars - first 100: Title: Just a moment...

URL Source: https://www.brides.com/best-anniversary-gifts-for-wife-5094500

vogue: 15061 chars - first 100: Title: Page Not Found | Vogue

URL Source: https://www.vogue.com/article/best-anniversary-gifts-for-
geschenkidee: 35394 chars - first 100: Title: Hochzeitstag – Geschenkideen für Paare | Geschenkidee.de

URL Source: https://www.geschenkide
elite: 74 chars - first 100: ParamValidationError(url): Domain 'www.elitegift.de' could not be resolved

Done fetching all gift guides.


The Knot und Geschenkidee.de haben gute Inhalte. Lass mich die durchlesen und noch weitere hochwertige Quellen abrufen.

Explanation: The knot and geschenkidee.de gave good results. Let me read those and also try more sources.