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


Recherchiere mit Camofox im Internet das österreichische Recht:

Kann ein Belastungs- und Veräußerungsverbot auch auf den Hälfteanteil nur eingetragen werden?


Explanation:
Der Nutzer fragt nach österreichischem Recht, speziell ob ein Belastungs- und Veräußerungsverbot auch nur auf einen Hälfteanteil eingetragen werden kann. Er möchte, dass ich mit Camofox (dem Browser-Dienst auf ZimaOS) recherchiere.

Lass mich die relevanten Skills laden: zimaos-camofox-browser für die Browser-Nutzung, und dann über den Browser recherchieren.


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'


Explanation: The user wants me to research Austrian law about whether a Belastungs- und Veräußerungsverbot (encumbrance and sale prohibition) can be registered only on a half share (Hälfteanteil) of a property. Let me look at the RIS legal research reference first, then use Camofox to search the Austrian legal database.


# RIS (Rechtsinformationssystem) Legal Research Workflow

Proven multi-tool approach for researching Austrian laws, DBA treaties, and tax regulations on JS-heavy government sites (RIS, Findok). Developed during DBA Österreich-Türkei pension research, 05.06.2026.

## The Problem

Austrian government legal databases (RIS, Findok) are JavaScript-rendered SPAs. Direct `curl` returns empty shells or HTML framework. Even jina.ai often gets "Rechtsvorschrift nicht in Kraft" / 404 because these sites use WebForms-style session tokens and stateful page rendering that server-side readers can't replay.

## The Fix: Three-Tool Chain

### Tool 1: Camofox Browser (stateful rendering)
Use when jina.ai returns empty pages or 404s. The browser runs the JS, handles sessions, renders the actual document.

```bash
# Check Camofox is running
curl -fsS http://127.0.0.1:9377/health

# Open a tab with the legal document
curl -s -X POST "http://127.0.0.1:9377/tabs" \
  -H "Content-Type: application/json" \
  -d '{"userId":"kiwi","sessionKey":"default","url":"https://www.ris.bka.gv.at/..."}'

# Wait for JS rendering (5s minimum for RIS)
sleep 5

# Take screenshot
curl -s "http://127.0.0.1:9377/tabs/$TAB/screenshot?userId=kiwi&sessionKey=default" \
  -o /tmp/legal_page.png

# Extract links (for finding sub-articles, related docs)
curl -s "http://127.0.0.1:9377/tabs/$TAB/links?userId=kiwi&sessionKey=default"
```

### Tool 2: jina.ai reader (fast, works when state isn't needed)
Try first — it's much faster. Best for: document metadata (Kurztitel, Kundmachungsorgan, Inkrafttretensdatum), and some article text when the RIS URL resolves statically.

```bash
curl -sL "https://r.jina.ai/<RIS_DOCUMENT_URL>" \
  -H "Accept: text/plain"
```

**When jina works:** Good for "Stammdaten" like document title, BGBl number, date. The DBA overview page (NOR40110804) worked perfectly.

**When jina fails:** When RIS pages use ASP.NET postback and session state — the server returns "20003915 nicht mehr in Kraft" or "404 Nicht gefunden" because the reader can't replay the WebForms lifecycle.

### Tool 3: vision_analyze (reads screenshots)
When jina fails and browser screenshots are the only rendered content:

```
vision_analyze(image_url=/tmp/ris_page.png, question="What document titles and numbers are listed?")
```

**Critical pitfall:** vision_analyze can hallucinate legal text. It's good for:
- Extracting structured elements (table columns, document numbers, dates)
- Reading short labels and navigation items
- Identifying page status (e.g., "nicht mehr in Kraft")

It's NOT reliable for:
- Long paragraphs of legal prose (will paraphrase/hallucinate)
- Precise statutory language (invents plausible-sounding but wrong text)

## RIS Specific Patterns

### Finding a DBA (Double Taxation Treaty)

1. Search RIS: `https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Bundesnormen&Suchworte=T%C3%BCrkei+Doppelbesteuerung&...`
2. Open in Camofox, screenshot the results table
3. Extract document links from `/links` endpoint — each article row links to `.../eli/bgbl/iii/2009/96/A18/NOR40110822`
4. The NOR number increments: Art 1 = NOR40110805, Art 18 = NOR40110822, Art 23 = NOR40110826
5. Load individual article pages via jina.ai: `https://r.jina.ai/https://www.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40110822/NOR40110822.html`

### Finding EStG Paragraphs

RIS URL pattern for EStG 1988 (Gesetzesnummer 10004570):
```
https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10004570&FassungVom=05.06.2026&Artikel=&Paragraf=2&Anlage=
```

### Findok (BMF Tax Rulings)

URL pattern: `https://findok.bmf.gv.at/findok/search/show?q=<searchterm>`
- Uses JavaScript search — direct curl/jina rarely works
- For EStR 2000 (Einkommensteuerrichtlinien): use the "Richtlinien" navigation link in Camofox

## Worked Example: DBA Austria-Turkey Art 18 (Pensions)

1. **jina.ai on RIS search results** → 404 (ASP.NET session state)
2. **Camofox to RIS search** → Screenshot showed 10 results: "Doppelbesteuerung – Einkommensteuer (Türkei)" BGBl III 96/2009
3. **links endpoint** → Extracted NOR pattern: A1=NOR40110805
4. **jina.ai on individual articles** → Clean markdown for each article:
   - Art 18 (NOR40110822): "Ruhegehälter ... nur in dem Staat besteuert werden, in dem der Empfänger ansässig ist"
   - Art 19 (NOR40110823): "ÖFFENTLICHER DIENST" with citizenship exceptions
   - Art 23 (NOR40110826): Method article — lit. a Befreiungsmethode, lit. d Progressionsvorbehalt
5. **Camofox for EStG § 25, FinStrG § 29** → Screenshots for document status verification

## Lessons Learned

- **Don't fight RIS with curl alone.** The session token model defeats stateless HTTP. Accept that browser automation is the primary path for RIS.
- **jina.ai is the first resort, not the only resort.** Try it, but when it 404s on an obviously valid page, switch to Camofox immediately.
- **vision_analyze is the last resort for text.** Use it for structure/scaffolding, then use jina.ai on discovered URLs for the actual text.
- **NOR number patterns let you skip pagination.** Once you find the base NOR for Art 1, you can probe Art 18 by adding 17 to the number.


Explanation:
The user wants me to research Austrian law using Camofox browser. The specific question is: "Kann ein Belastungs- und Veräußerungsverbot auch auf den Hälfteanteil nur eingetragen werden?"

This is about Austrian property law (Grundbuchsrecht) — specifically whether a "Belastungs- und Veräußerungsverbot" (encumbrance and sale prohibition) can be registered only on a half-share of a property.

Let me follow the RIS legal research workflow from the skill. First, I should check if Camofox is running, then search for relevant legal sources. Let me also try jina.ai first for faster results, and use Camofox for the actual RIS search.

The relevant laws would be:
- GBG 1955 (Grundbuchsgesetz)
- ABGB (Allgemeines bürgerliches Gesetzbuch) — specifically § 364c about Belastungs- und Veräußerungsverbot
- Relevant OGH decisions (RIS-Justiz)
- Commentary/literature

Let me start by searching RIS for relevant materials. I'll use multiple approaches in parallel.

todo

Camofox-Verfügbarkeit prüfen + RIS-Suche starten

ABGB § 364c recherchieren (Belastungs- und Veräußerungsverbot)

OGH-Judikatur zu Veräußerungsverbot auf Miteigentumsanteil suchen

Ergebnisse zusammenfassen und Rechtslage darstellen


Explanation:
Let me start by checking if Camofox is available, then search RIS for the relevant law and case law about Belastungs- und Veräußerungsverbot (encumbrance and disposal prohibition) on a half-share of property. This relates to § 364c ABGB.

Let me first check Camofox health, then do the research.


terminal

Output: {"ok":true,"engine":"camoufox","browserConnected":false,"browserRunning":false,"activeTabs":0,"activeSessions":0,"consecutiveFailures":0,"memory":{"rssMb":224,"heapUsedMb":88,"nativeMemMb":136}}


Camofox läuft. Ich öffne jetzt parallele Recherchen: jina.ai für ABGB § 364c und OGH-Judikatur, plus Camofox-Screenshot als Fallback.

Explanation:
Camofox is running, browser not connected yet (lazy init). Let me open a tab to the RIS search for the ABGB § 364c — that's the core provision about Belastungs- und Veräußerungsverbote.

Let me also try jina.ai in parallel for faster results on ABGB § 364c and relevant OGH decisions.

curl -s -X POST "http://127.0.0.1:9377/tabs" \
  -H "Content-Type: application/json" \
  -d '{"userId":"kiwi","sessionKey":"default","url":"https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Artikel=&Paragraf=364c&Anlage="}' 2>&1

curl -sL "https://r.jina.ai/https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c" \
  -H "Accept: text/plain" 2>&1 | head -300

curl -sL "https://r.jina.ai/https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Suchworte=Ver%C3%A4u%C3%9Ferungsverbot+H%C3%A4lfteanteil+Miteigentumsanteil+364c" \
  -H "Accept: text/plain" 2>&1 | head -300


Output:
Title: RIS - Allgemeines bürgerliches Gesetzbuch § 364c

URL Source: https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c

Markdown Content:
# RIS - Allgemeines bürgerliches Gesetzbuch § 364c - Bundesrecht konsolidiert, Fassung vom 06.08.2026

Seitenbereiche:
*   [Zum Inhalt (Accesskey 0)](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c#main)
*   [Zur Navigationsleiste (Accesskey 1)](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c#navigation)
*   [Kontakt (Accesskey 4)](https://www.ris.bka.gv.at/UI/Kontakt.aspx)
*   [Impressum (Accesskey 5)](https://www.ris.bka.gv.at/UI/Impressum.aspx)
*   [Datenschutzerklärung (Accesskey 6)](https://www.ris.bka.gv.at/UI/Datenschutz.aspx)
*   [Barrierefreiheitserklärung (Accesskey 7)](https://www.ris.bka.gv.at/UI/Barrierefreiheit.aspx)
*   [Sitemap (Accesskey 8)](https://www.ris.bka.gv.at/UI/SiteMap.aspx)
*   [English](https://www.ris.bka.gv.at/defaultEn.aspx) (Accesskey 9)

[![Image 1: Rechtsinformationssystem des Bundes](https://www.ris.bka.gv.at/Images/RisHeader.jpg)](https://www.ris.bka.gv.at/default.aspx)

[Navigationsleiste:](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c)

*   [Startseite](https://www.ris.bka.gv.at/default.aspx)
*   [Bund](https://www.ris.bka.gv.at/Bund/)
*   [Länder](https://www.ris.bka.gv.at/Land/)
*   [Bezirke](https://www.ris.bka.gv.at/Bezirke/)
*   [Gemeinden](https://www.ris.bka.gv.at/Gemeinde/)
*   [Judikatur](https://www.ris.bka.gv.at/Judikatur/)
*   [Kundmachungen, Erlässe](https://www.ris.bka.gv.at/Sonstige/)
*   [Gesamtabfrage](https://www.ris.bka.gv.at/Gesamtabfrage/)

# Bundesrecht konsolidiert: Allgemeines bürgerliches Gesetzbuch § 364c, Fassung vom 06.08.2026

*   [Druckansicht (Accesskey D)](http://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c&ShowPrintPreview=True)

## Allgemeines bürgerliches Gesetzbuch § 364c

*   Gesamte Rechtsvorschrift [heute](https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622 "Gesamte Rechtsvorschrift in der heutigen Fassung anzeigen") / [Fassung vom 06.08.2026](https://www.ris.bka.gv.at/GeltendeFassungDatumsauswahl.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=2026-08-06 "Gesamte Rechtsvorschrift in der Fassung vom 06.08.2026 anzeigen")
*   [§ 364b am 06.08.2026](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=2026-08-06&Artikel=&Paragraf=364b&Anlage=&Uebergangsrecht= "§ 364b in der Fassung vom 06.08.2026 anzeigen")
*   [§ 365 am 06.08.2026](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=2026-08-06&Artikel=&Paragraf=365&Anlage=&Uebergangsrecht= "§ 365 in der Fassung vom 06.08.2026 anzeigen")
*   [Alle Fassungen](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c#alleFassungen)

    1.   [§ 364c heute](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&Artikel=&Paragraf=364c&Anlage=&Uebergangsrecht= "§ 364c in der heutigen Fassung anzeigen")
    2.   [§ 364c gültig ab 01.01.2010](https://www.ris.bka.gv.at/eli/jgs/1811/946/P364c/NOR40112785 "§ 364c in der Fassung vom 08.06.2026 anzeigen")zuletzt geändert durch BGBl. I Nr. 135/2009
    3.   [§ 364c gültig von 01.01.1917 bis 31.12.2009](https://www.ris.bka.gv.at/eli/jgs/1811/946/P364c/NOR12018092 "§ 364c in der Fassung vom 31.12.2009 anzeigen")zuletzt geändert durch RGBl. Nr. 69/1916

### Begleitende Dokumente

 Hauptdokument

[![Image 2: Web-Seite](https://www.ris.bka.gv.at/Images/htm.gif)](https://www.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40112785/NOR40112785.html "Web-Seite: § 364c Allgemeines bürgerliches Gesetzbuch")[![Image 3: RTF-Dokument](https://www.ris.bka.gv.at/Images/doc.gif)](https://www.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40112785/NOR40112785.rtf "RTF-Dokument: § 364c Allgemeines bürgerliches Gesetzbuch")[![Image 4: PDF-Dokument](https://www.ris.bka.gv.at/Images/pdf.gif)](https://www.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40112785/NOR40112785.pdf "PDF-Dokument: § 364c Allgemeines bürgerliches Gesetzbuch")

### Kurztitel

 Allgemeines bürgerliches Gesetzbuch

### Kundmachungsorgan

[JGS Nr. 946/1811](https://alex.onb.ac.at/cgi-content/alex?aid=jgs&datum=10120003&seite=00000275) zuletzt geändert durch [BGBl. I Nr. 135/2009](https://www.ris.bka.gv.at/eli/bgbl/I/2009/135)

### Typ

 BG

### §/Artikel/Anlage

 § 364c

### Inkrafttretensdatum

 01.01.2010

### Außerkrafttretensdatum

### Abkürzung

 ABGB

### Index

 20/01 Allgemeines bürgerliches Gesetzbuch (ABGB)

### Text

##### §364c.Paragraph 364 c,

Ein vertragsmäßiges oder letztwilliges Veräußerungs- oder Belastungsverbot hinsichtlich einer Sache oder eines dinglichen Rechtes verpflichtet nur den ersten Eigentümer, nicht aber seine Erben oder sonstigen Rechtsnachfolger. Gegen Dritte wirkt es dann, wenn es zwischen Ehegatten, eingetragenen Partnern, Eltern und Kindern, Wahl- oder Pflegekindern oder deren Ehegatten oder eingetragenen Partnern begründet und im öffentlichen Buche eingetragen wurde.

### Schlagworte

 Eigentümer, Veräußerungsverbot, Wahlkind

### Im RIS seit

 15.01.2010

### Zuletzt aktualisiert am

 02.09.2025

### Gesetzesnummer

 10001622

### Dokumentnummer

 NOR40112785

### European Legislation Identifier (ELI)

[https://ris.bka.gv.at/eli/jgs/1811/946/P364c/NOR40112785](https://www.ris.bka.gv.at/eli/jgs/1811/946/P364c/NOR40112785)

[Zum Seitenanfang](https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001622&FassungVom=08.06.2026&Paragraf=364c#header).

## Über diese Seite

*    © 2026 Bundeskanzleramt der Republik Österreich


Output:
Title: RIS - Justiz - Suche

URL Source: https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Suchworte=Ver%C3%A4u%C3%9Ferungsverbot+H%C3%A4lfteanteil+Miteigentumsanteil+364c

Markdown Content:
## Suchformular

Die eingegebene Suchabfrage liefert keine Treffer.

Dokumenttyp![Image 1](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=RsField)Dokumenttyp
*   Rechtssätze (RS)
*   Entscheidungstexte (TE)
Suchworte![Image 2](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=SuchworteField)
Entscheidungsdatum von![Image 3](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=VonDatumField)[![Image 4: Kalender öffnen](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Themes/NovaGray/Image/DatePicker.gif)](https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Suchworte=Ver%C3%A4u%C3%9Ferungsverbot+H%C3%A4lfteanteil+Miteigentumsanteil+364c# "Kalender öffnen")Entscheidungsdatum bis [![Image 5: Kalender öffnen](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Themes/NovaGray/Image/DatePicker.gif)](https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Suchworte=Ver%C3%A4u%C3%9Ferungsverbot+H%C3%A4lfteanteil+Miteigentumsanteil+364c# "Kalender öffnen")
Neu im RIS seit![Image 6](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=ImRisSeitField)
Änderungen seit![Image 7](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=AenderungenSeitField)
Zivilrecht, Strafrecht![Image 8](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=RechtsgebietField)
Gericht![Image 9](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=GerichtField)
Geschäftszahl![Image 10](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=GZField)
Fundstelle, Schlagworte![Image 11](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=FundstelleField)
Rechtssatznummer![Image 12](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=RechtssatznummerField)
Rechtliche Beurteilung![Image 13](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=RechtssatzField)
Norm![Image 14](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)[](https://www.ris.bka.gv.at/UI/Help.aspx?Abfrage=Justiz&Field=NormField)Beispiel: ABGB §879 Abs3
![Image 15](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)![Image 16](https://www.ris.bka.gv.at/res/Remotion.Web/v1.20.8.10000/Image/Spacer.gif)


Die RIS-Justiz-Suche mit den genauen Keywords war leer. Ich suche jetzt breiter — direkt über die Camofox-Justizsuche mit kürzeren Schlagworten und parallel per jina.ai in der Fachliteratur.

Explanation:
Ich habe den Gesetzestext zu § 364c ABGB. Die Judikatur-Suche mit den spezifischen Keywords ergab keine Treffer. Jetzt muss ich über die Camofox-Justiz-Suche breiter suchen — mit den richtigen Suchbegriffen für die OGH-Judikatur zum Thema "Belastungs- und Veräußerungsverbot auf Miteigentumsanteil". Außerdem sollte ich auch den Screenshot von ABGB § 364c machen und die Kommentarliteratur suchen.

Lass mich:
1. § 364c Screenshot nehmen
2. Breitere OGH-Suche mit besseren Schlagworten (z.B. "Belastungs- und Veräußerungsverbot Miteigentum", "364c Hälfteanteil")
3. jina.ai für Google-Suche nach "Veräußerungsverbot Hälfteanteil Miteigentumsanteil" verwenden (weil RIS die Suchworte evtl. anders indiziert)

# Screenshot von ABGB § 364c in Camofox
TAB="a9b600f9-a081-4375-a844-6652c6eccfe1"
sleep 5
curl -s "http://127.0.0.1:9377/tabs/$TAB/screenshot?userId=kiwi&sessionKey=default" -o /tmp/abgb_364c.png 2>&1
echo "Screenshot saved: $(stat -c%s /tmp/abgb_364c.png) bytes"

# Breitere OGH-Justizsuche: "Veräußerungsverbot" + "Miteigentumsanteil"
curl -s -X POST "http://127.0.0.1:9377/tabs" \
  -H "Content-Type: application/json" \
  -d '{"userId":"kiwi","sessionKey":"default","url":"https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Suchworte=Ver%C3%A4u%C3%9Ferungsverbot+Miteigentumsanteil&ImRisSeit=Undefined&VonDatum=&BisDatum=&ImRisSeitVonDatum=&ImRisSeitBisDatum=&AenderungenSeit=Undefined&Rechtsgebiet=Undefined&Gericht=Undefined&Rechtssatznummer=&Fundstelle=&Rechtssatz=&Norm=&Entscheidungsart=Undefined&Dokumentnummer=&Index=&Kundmachungsorgan=&Uebergangsrecht=&FassungVom=08.06.2026"}' 2>&1

# jina.ai für "Veräußerungsverbot Miteigentumsanteil Hälfte" Google-basierte Fachartikel
curl -sL "https://r.jina.ai/https://www.google.com/search?q=%C3%B6sterreich+ABGB+364c+Belastungsverbot+Ver%C3%A4u%C3%9Ferungsverbot+Miteigentumsanteil+H%C3%A4lfteanteil+OGH" \
  -H "Accept: text/plain" 2>&1 | head -500


Output: Screenshot saved: 186372 bytes


Output:
Title: https://www.google.com/search?q=%C3%B6sterreich+ABGB+364c+Belastungsverbot+Ver%C3%A4u%C3%9Ferungsverbot+Miteigentumsanteil+H%C3%A4lfteanteil+OGH

URL Source: https://www.google.com/search?q=%C3%B6sterreich+ABGB+364c+Belastungsverbot+Ver%C3%A4u%C3%9Ferungsverbot+Miteigentumsanteil+H%C3%A4lfteanteil+OGH

Warning: Target URL returned error 429: Too Many Requests

Markdown Content:
**About this page**

Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot. [Why did this happen?](https://www.google.com/search?q=%C3%B6sterreich+ABGB+364c+Belastungsverbot+Ver%C3%A4u%C3%9Ferungsverbot+Miteigentumsanteil+H%C3%A4lfteanteil+OGH#)

IP address: 2600:1900:0:2105::1b00

Time: 2026-06-08T08:56:59Z

URL: https://www.google.com/search?q=%C3%B6sterreich+ABGB+364c+Belastungsverbot+Ver%C3%A4u%C3%9Ferungsverbot+Miteigentumsanteil+H%C3%A4lfteanteil+OGH


Explanation:
Let me analyze what I have so far:

1. **ABGB § 364c** retrieved successfully via jina.ai - clear text of the law
2. **OGH search**: I got results listing for "Veräußerungsverbot + Miteigentumsanteil" in Camofox, need to check the screenshot
3. **Google search via jina.ai**: blocked with 429

Now I need to:
- Get the Camofox screenshot for the OGH search results
- Try alternative searches for the specific question about Belastungs- und Veräußerungsverbot on half-share (Hälfteanteil)
- Also try RIS Justiz search with "364c" as Norm

Let me also try OGH search with just "364c Hälfte" or "364c Miteigentumsanteil" and get results from the Camofox tabs.

# Screenshot der OGH-Suchergebnisse
TAB="ba36627e-e32e-4281-aea0-520329154cde"
sleep 6
curl -s "http://127.0.0.1:9377/tabs/$TAB/screenshot?userId=kiwi&sessionKey=default" -o /tmp/ogh_suche.png 2>&1
echo "Screenshot saved: $(stat -c%s /tmp/ogh_suche.png) bytes"

# jina.ai auf RIS-Justizsuche mit Norm-Filter "ABGB §364c"
curl -sL "https://r.jina.ai/https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Suchworte=Ver%C3%A4u%C3%9Ferungsverbot+364c&Rechtssatz=&Fundstelle=&Norm=ABGB+%C2%A7364c" \
  -H "Accept: text/plain" 2>&1 | head -400

# Camofox: OGH-Suche "364c Hälfteanteil"
curl -s -X POST "http://127.0.0.1:9377/tabs" \
  -H "Content-Type: application/json" \
  -d '{"userId":"kiwi","sessionKey":"default","url":"https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Suchworte=364c+H%C3%A4lfteanteil+Belastungsverbot+Ver%C3%A4u%C3%9Ferungsverbot"}' 2>&1


Output: Screenshot saved: 181907 bytes