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


Gib dir bitte beim morgenbriefing mehr Mühe.

Wen müssen wir heute anrufen?
Erinnerung Daily Dose auszufüllen.

Und heute ist Sonntag morgen nicht Montag


Explanation:
Der Benutzer ist unzufrieden mit dem Morgenbriefing und möchte, dass ich mir mehr Mühe gebe. Er möchte wissen, wen wir heute anrufen müssen, eine Erinnerung für Daily Dose, und stellt klar, dass heute Sonntag Morgen ist, nicht Montag.

Lass mich das systematisch angehen:

1. Erstmal checken, was das Morning Briefing Cron-Job ist und wie es aktuell konfiguriert ist
2. Die Daily Dose App checken
3. Kalender/Anrufe für heute checken
4. Das Briefing verbessern

Lass mich zuerst die relevanten Skills laden und dann Informationen sammeln.


daily-dose

---
name: daily-dose
description: Modify DailyDose (täglicher Aktivitäten-Tracker PWA) — Kategorien, Defaults, Server-Daten. Der Tracker von Zeyd unter /media/HDD_1TB/DailyDose/.
---

# DailyDose — Täglicher Aktivitäten-Tracker

DailyDose ist eine PWA (Progressive Web App), die Zeyds tägliche Aktivitäten trackt. Läuft lokal mit Server-Sync.

## Architektur

- **Pfad:** `/media/HDD_1TB/DailyDose/`
- **Dateien:** `index.html` (komplette App in einer Datei), `manifest.json`, `icon.svg`, `icon.png`, `nginx.conf`
- **Speicher:** localStorage im Browser, synchronisiert über HTTP-API mit Server
- **API:** `http://localhost:8765/api/data` — GET liest alle Daten, POST schreibt Key-Value-Paare
- **Storage-Keys:** `dailydose_YYYY-MM-DD` für Tageseinträge, `dd_custom_cats` für Custom-Kategorien

## Kategorien

### Built-in (in `BUILT_IN_CATS` Array, Zeile ~878)
Schlafen, Lernen, Work, Hausarbeit, Kochen, Islam, Sport, Unterwegs, Körperpflege, Sonstiges

### Custom
In `dd_custom_cats` auf dem Server gespeichert. **Custom-Kategorien überschreiben Built-ins** (Name-Match). Werden in `buildCategoryMaps()` nach den Built-ins geladen und überschreiben deren `COLORS`/`ICONS`.

## Tägliche Defaults (`getDefaults()`)

Definiert, welche Aktivitäten für einen neuen Tag vorausgefüllt werden. Aktuelle Defaults (Zeile ~1031):
- **Islam:** 15 min täglich, 45 min freitags
- **Körperpflege:** 30 min täglich
- **Unterwegs:** 1h Montag + Dienstag

Defaults greifen NUR, wenn für den Tag noch KEINE Daten im localStorage existieren. Sobald ein Tag gespeichert wurde, werden die gespeicherten Daten verwendet.

## Änderungen vornehmen

### Neue Kategorie hinzufügen
1. In `index.html` das `BUILT_IN_CATS` Array patchen — neuen Eintrag mit `value`, `icon`, `color` einfügen
2. Default in `getDefaults()` eintragen, falls gewünscht
3. **Server-Daten prüfen:** Falls bereits eine Custom-Kategorie mit gleichem Namen existiert, diese löschen oder anpassen, da sie sonst das Built-in überschreibt

### Default-Wert ändern
In `getDefaults()` patchen. Greift erst für zukünftige, noch nicht gespeicherte Tage.

### Heutigen Tag direkt korrigieren
Wenn heute schon Daten existieren, müssen sie direkt via API gepatcht werden:
```bash
# Heutige Einträge lesen
curl -s http://localhost:8765/api/data | python3 -c "import json,sys; ..."

# Einträge patchen und zurückschreiben
curl -s -X POST http://localhost:8765/api/data \
  -H 'Content-Type: application/json' \
  -d '{"dailydose_YYYY-MM-DD":"[{\"category\":\"...\",\"hours\":0.5}]"}'
```

## Automatische Erinnerungen per Cron-Job

DailyDose-Einträge werden schnell vergessen. Setze automatische Erinnerungen über den `cronjob`-Agenten, damit Zeyd ("Chef") regelmäßig an das Tracking erinnert wird.

### Prompt-Stil für Erinnerungen

- **Sprache:** Deutsch
- **Ton:** Freundlich, motivierend, nicht nervig
- **Länge:** 1-2 Sätze, kurz
- **Tageszeit-Anpassung:** Morgens energisch/optimistisch, nachmittags sachlich/freundlich, abends entspannt
- **Abwechslung:** Die Formulierung jedes Mal leicht variieren, damit es nicht monoton wirkt
- **Emojis:** Gelegentlich ein passendes Emoji (nicht inflationär)
- **Anrede:** "Chef"

### Beispiele

```
🌅 Guten Morgen Chef! Zeit für deine DailyDose — was hast du heute vor?
☀ DailyDose-Check! Nicht vergessen, deine Aktivitäten einzutragen.
🌙 Abend-Check! Noch schnell die DailyDose für heute ausfüllen, Chef?
```

### Scheduling

- Tägliche Erinnerungen: `0 9,16,22 * * *` (dreimal am Tag)
- Goal-Tracking: `*/15 * * * *` (alle 15 Minuten) für motivationsgetriebene Lern-/Ziel-Checks
- `repeat: -1` für wiederkehrende Jobs
- `deliver: origin` für Telegram-Zustellung

### Wichtig

- Cron-Job-Prompts müssen **selbsterklärend** sein — der erinnernde Agent läuft unabhängig und hat keinen Gesprächskontext
- Nicht zu oft auf "wir" oder "uns" Bezug nehmen — die Nachricht soll natürlich wirken

### Goal-Based Motivation Cron Jobs (Lernziel-Tracking)

Wenn Chef ein Tagesziel für eine bestimmte Kategorie hat (z.B. "120 Minuten Lernen → Kopfhörer bestellen"), kann ein Cron-Job alle 15 Minuten den Fortschritt checken und motivierend melden.

**Pattern:**
1. Python-Script schreiben, das die DailyDose-API abfragt, die Ziel-Kategorie summiert und Fortschritt/Erfolg ausgibt (siehe `scripts/dailydose_learn_check.py`)
2. Script nach `~/.hermes/scripts/` kopieren (Cron-Job-Tool erwartet Pfad relativ zu `~/.hermes/scripts/`)
3. Cron-Job mit `schedule: "*/15 * * * *"`, `no_agent: true`, `script: dailydose_learn_check.py` anlegen
4. Job pausieren/löschen, sobald Ziel erreicht ist

**Script-Logik:**
- TARGET_MINUTES definieren
- Heutigen Key `dailydose_YYYY-MM-DD` aus der API lesen
- Stunden der Ziel-Kategorie summieren, in Minuten umrechnen
- Drei Ausgaben: Ziel erreicht (🎉), in Progress (📚 mit Prozent), noch nichts (Motivation zum Starten)

## Motivation/Erinnerungen

Wenn der Chef einen Motivations-Workflow will (z.B. "Sag mir alle 15 Minuten wie viel ich gelernt habe, bis Ziel erreicht"), **nicht** direkt einen `no_agent`-Cronjob mit statischem Script bauen. Die Nachrichten wirken mechanisch und frustrieren. Besser:

1. **Cronjob mit Agent:** `no_agent: false` — der Agent kriegt dann Kontext (DailyDose-Check als Prompt) und kann natürlich, variabel und motivierend antworten.
2. **Oder manuell:** Chef fragt selbst nach Stand, Kiwi checkt dann live. Weniger nervig.

Vorher mit Chef klären, ob automatisierte Reminder überhaupt erwünscht sind.

**Manueller Check per Script:** `scripts/learn_check.py` — gibt Motivations-Stand für eine Kategorie aus. Aufruf: `python3 scripts/learn_check.py [ziel_minuten] [kategorie]`. Default: 120 Minuten, "Lernen".

## Pitfalls

- **Zeitgeist API: ALLE Werte sind JSON-Strings — doppelt parsen!** `curl http://localhost:8765/api/data` liefert ein JSON-Objekt, bei dem JEDER Wert ein String ist, der selbst wieder JSON enthält. `data['zeitgeist-v2']` ist z.B. der String `"{\"2026-05-22\":[25,25,...]}"`. Direktes Zugreifen mit `.get()` oder Index-Notation auf den Roh-String wirft `AttributeError: 'str' object has no attribute 'get'`. **Immer** so parsen:
  ```python
  for k, v in data.items():
      if isinstance(v, str) and v.strip().startswith(('{', '[')):
          data[k] = json.loads(v)
  ```
  Erst DANACH ist `data['zeitgeist-v2']['2026-05-22']` ein echtes Array.
- **Custom überschreibt Built-in:** Wenn eine Custom-Kategorie denselben Namen hat wie ein Built-in, gewinnt die Custom-Version (Icon + Farbe). Bei Konflikten die Custom-Kategorie auf dem Server anpassen.
- **Defaults gelten nicht für existierende Tage:** `getDefaults()` wird nur als Fallback verwendet, wenn `localStorage.getItem(dateKey)` `null` zurückgibt. Für bereits getrackte Tage muss der Server direkt gepatcht werden.
- **Server-Sync beachten:** Daten liegen auf dem Server (`:8765`). Änderungen nur im HTML reichen nicht, wenn der Tag schon Daten hat.
- **Emoji/Icon-Konsistenz:** Immer sowohl Built-in als auch Custom-Kategorie prüfen, damit das richtige Icon angezeigt wird.

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


google-workspace

---
name: google-workspace
description: "Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python."
version: 1.0.1
author: Nous Research
license: MIT
required_credential_files:
  - path: /DATA/AppData/hermes/google_client_secret.json
    description: Google OAuth2 client credentials - project amadeus-494810
  - path: /DATA/.hermes/google_token.json
    description: Google OAuth2 token - ahmed.aytac@gmail.com, all scopes granted
metadata:
  hermes:
    tags: [Google, Gmail, Calendar, Drive, Sheets, Docs, Contacts, Email, OAuth]
    homepage: https://github.com/NousResearch/hermes-agent
    related_skills: [himalaya]
---

# Google Workspace

Gmail, Calendar, Drive, Contacts, Sheets, and Docs — through Hermes-managed OAuth and a thin CLI wrapper. When `gws` is installed, the skill uses it as the execution backend for broader Google Workspace coverage; otherwise it falls back to the bundled Python client implementation.

## References

- `references/gmail-search-syntax.md` — Gmail search operators (is:unread, from:, newer_than:, etc.)
- `references/bulk-gmail-operations.md` — Bulk deletion: rate-limiting, retry patterns, date-range pagination

## Scripts

- `scripts/setup.py` — OAuth2 setup (run once to authorize)
- `scripts/google_api.py` — compatibility wrapper CLI. It prefers `gws` for operations when available, while preserving Hermes' existing JSON output contract.

## First-Time Setup

The setup is fully non-interactive — you drive it step by step so it works
on CLI, Telegram, Discord, or any platform.

Define a shorthand first:

```bash
GSETUP="python ${HERMES_HOME:-$HOME/.hermes}/skills/productivity/google-workspace/scripts/setup.py"
```

### Step 0: Check if already set up

```bash
$GSETUP --check
```

If it prints `AUTHENTICATED`, skip to Usage — setup is already done.

### Step 1: Triage — ask the user what they need

Before starting OAuth setup, ask the user TWO questions:

**Question 1: "What Google services do you need? Just email, or also
Calendar/Drive/Sheets/Docs?"**

- **Email only** → They don't need this skill at all. Use the `himalaya` skill
  instead — it works with a Gmail App Password (Settings → Security → App
  Passwords) and takes 2 minutes to set up. No Google Cloud project needed.
  Load the himalaya skill and follow its setup instructions.

- **Anything beyond email** → Continue with this skill. Note: the setup
  script (`setup.py`) always requests the full SCOPES list (Gmail
  read/send/modify, Calendar, Drive read, Contacts, Sheets, Docs read).
  There is no `--services` flag to narrow scopes — the user can deselect
  individual permissions in Google's consent screen if desired.

**Question 2: "Does your Google account use Advanced Protection (hardware
security keys required to sign in)? If you're not sure, you probably don't
— it's something you would have explicitly enrolled in."**

- **No / Not sure** → Normal setup. Continue below.
- **Yes** → Their Workspace admin must add the OAuth client ID to the org's
  allowed apps list before Step 4 will work. Let them know upfront.

### Step 2: Create OAuth credentials (one-time, ~5 minutes)

Tell the user:

> You need a Google Cloud OAuth client. This is a one-time setup:
>
> 1. Create or select a project:
>    https://console.cloud.google.com/projectselector2/home/dashboard
> 2. Enable the required APIs from the API Library:
>    https://console.cloud.google.com/apis/library
>    Enable: Gmail API, Google Calendar API, Google Drive API,
>    Google Sheets API, Google Docs API, People API
> 3. Create the OAuth client here:
>    https://console.cloud.google.com/apis/credentials
>    Credentials → Create Credentials → OAuth 2.0 Client ID
> 4. Application type: "Desktop app" → Create
> 5. If the app is still in Testing, add the user's Google account as a test user here:
>    https://console.cloud.google.com/auth/audience
>    Audience → Test users → Add users
> 6. Download the JSON file and tell me the file path
>
> Important Hermes CLI note: if the file path starts with `/`, do NOT send only the bare path as its own message in the CLI, because it can be mistaken for a slash command. Send it in a sentence instead, like:
> `The JSON file path is: /home/user/Downloads/client_secret_....json`

Once they provide the path:

```bash
$GSETUP --client-secret /path/to/client_secret.json
```

If they paste the raw client ID / client secret values instead of a file path,
write a valid Desktop OAuth JSON file for them yourself, save it somewhere
explicit (for example `~/Downloads/hermes-google-client-secret.json`), then run
`--client-secret` against that file.

### Step 3: Get authorization URL

```bash
$GSETUP --auth-url
```

The script prints the full OAuth URL to stdout. The agent must extract it and
send it to the user as a clickable link.

Agent rules for this step:
- The script outputs ONLY the URL (one line) — no JSON wrapper, no `auth_url` field.
- Send that exact URL to the user as a single line. It needs to be a clickable link.
- Tell the user that the browser will likely fail on `http://localhost:1` after approval, and that this is expected.
- Tell them to copy the ENTIRE redirected URL from the browser address bar.
- If the user gets `Error 403: access_denied`, send them directly to `https://console.cloud.google.com/auth/audience` to add themselves as a test user.

### Step 4: Exchange the code

The user will paste back either a URL like `http://localhost:1/?code=4/0A...&scope=...`
or just the code string. Either works. The `--auth-url` step stores a temporary
pending OAuth session locally so `--auth-code` can complete the PKCE exchange
later, even on headless systems:

```bash
$GSETUP --auth-code "THE_URL_OR_CODE_THE_USER_PASTED"
```

If `--auth-code` fails because the code expired, was already used, or came from
an older browser tab, run `$GSETUP --auth-url` again to get a fresh URL.

### Step 5: Verify

```bash
$GSETUP --check
```

Should print `AUTHENTICATED`. Setup is complete — token refreshes automatically from now on.

### Notes

- Token is stored at `~/.hermes/google_token.json` and auto-refreshes.
- Pending OAuth session state/verifier are stored temporarily at `~/.hermes/google_oauth_pending.json` until exchange completes.
- If `gws` is installed, `google_api.py` points it at the same `~/.hermes/google_token.json` credentials file. Users do not need to run a separate `gws auth login` flow.
- To revoke: `$GSETUP --revoke`
- **Zeyd's setup:** Client secret stored at `/DATA/AppData/hermes/google_client_secret.json` (project: `amadeus-494810`, client ID `760929667815-...`). Token at `/DATA/.hermes/google_token.json` (profile-scoped). Gmail address: `ahmed.aytac@gmail.com`. All scopes granted (Gmail read/send/modify, Calendar, Drive, Contacts, Sheets, Docs). Do NOT re-ask for client secret path if these files exist.

## Usage

All commands go through the API script. Set `GAPI` as a shorthand:

```bash
GAPI="python ${HERMES_HOME:-$HOME/.hermes}/skills/productivity/google-workspace/scripts/google_api.py"
```

### Gmail

```bash
# Search (returns JSON array with id, from, subject, date, snippet)
$GAPI gmail search "is:unread" --max 10
$GAPI gmail search "from:boss@company.com newer_than:1d"
$GAPI gmail search "has:attachment filename:pdf newer_than:7d"

# Read full message (returns JSON with body text)
$GAPI gmail get MESSAGE_ID

# Send
$GAPI gmail send --to user@example.com --subject "Hello" --body "Message text"
$GAPI gmail send --to user@example.com --subject "Report" --body "<h1>Q4</h1><p>Details...</p>" --html
$GAPI gmail send --to user@example.com --subject "Hello" --from '"Research Agent" <user@example.com>' --body "Message text"

# Reply (automatically threads and sets In-Reply-To)
$GAPI gmail reply MESSAGE_ID --body "Thanks, that works for me."
$GAPI gmail reply MESSAGE_ID --from '"Support Bot" <user@example.com>' --body "Thanks"

# Labels
$GAPI gmail labels
$GAPI gmail modify MESSAGE_ID --add-labels LABEL_ID
$GAPI gmail modify MESSAGE_ID --remove-labels UNREAD
```

### Calendar

```bash
# List events (defaults to next 7 days)
$GAPI calendar list
$GAPI calendar list --start 2026-03-01T00:00:00Z --end 2026-03-07T23:59:59Z

# Create event (ISO 8601 with timezone required)
$GAPI calendar create --summary "Team Standup" --start 2026-03-01T10:00:00-06:00 --end 2026-03-01T10:30:00-06:00
$GAPI calendar create --summary "Lunch" --start 2026-03-01T12:00:00Z --end 2026-03-01T13:00:00Z --location "Cafe"
$GAPI calendar create --summary "Review" --start 2026-03-01T14:00:00Z --end 2026-03-01T15:00:00Z --attendees "alice@co.com,bob@co.com"

# Delete event
$GAPI calendar delete EVENT_ID
```

### Drive

```bash
$GAPI drive search "quarterly report" --max 10
$GAPI drive search "mimeType='application/pdf'" --raw-query --max 5
```

### Contacts

```bash
$GAPI contacts list --max 20
```

### Sheets

```bash
# Read
$GAPI sheets get SHEET_ID "Sheet1!A1:D10"

# Write
$GAPI sheets update SHEET_ID "Sheet1!A1:B2" --values '[["Name","Score"],["Alice","95"]]'

# Append rows
$GAPI sheets append SHEET_ID "Sheet1!A:C" --values '[["new","row","data"]]'
```

### Docs

```bash
$GAPI docs get DOC_ID
```

## Output Format

All commands return JSON. Parse with `jq` or read directly. Key fields:

- **Gmail search**: `[{id, threadId, from, to, subject, date, snippet, labels}]`
- **Gmail get**: `{id, threadId, from, to, subject, date, labels, body}`
- **Gmail send/reply**: `{status: "sent", id, threadId}`
- **Calendar list**: `[{id, summary, start, end, location, description, htmlLink}]`
- **Calendar create**: `{status: "created", id, summary, htmlLink}`
- **Drive search**: `[{id, name, mimeType, modifiedTime, webViewLink}]`
- **Contacts list**: `[{name, emails: [...], phones: [...]}]`
- **Sheets get**: `[[cell, cell, ...], ...]`

## Rules

1. **Never send email or create/delete events without confirming with the user first.** Show the draft content and ask for approval.
2. **Check auth before first use** — run `setup.py --check`. If it fails, guide the user through setup.
3. **Use the Gmail search syntax reference** for complex queries — load it with `skill_view("google-workspace", file_path="references/gmail-search-syntax.md")`.
4. **Calendar times must include timezone** — always use ISO 8601 with offset (e.g., `2026-03-01T10:00:00-06:00`) or UTC (`Z`).
5. **Respect rate limits** — avoid rapid-fire sequential API calls. Batch reads when possible.

## Pitfalls

- **`$GAPI gmail get` returns empty body for complex multipart emails**: The `_extract_message_body` helper in `google_api.py` only handles simple MIME structures. For multipart/mixed emails with HTML content, inline images, and PDF attachments (e.g. Gotogate booking confirmations), the body field is often empty. When this happens, drop to raw Python: fetch with `format="raw"`, decode the base64, use `email.message_from_bytes` to walk the parts, and extract `text/plain` or `text/html` payloads explicitly. For PDF attachments: find the `application/pdf` part, save the decoded data, then use `fitz` (PyMuPDF) to extract text. See `references/gmail-raw-extraction.md` for the full pattern.
- **Testing-mode token expiry (7 days)**: If the Google Cloud project is in "Testing" status (not published to Production), OAuth refresh tokens live only **7 days**. After that, every API call fails with `REFRESH_FAILED: invalid_grant: Token has been expired or revoked`. The fix: either go through the re-auth flow (`--revoke` then `--auth-url`), OR permanently solve it by publishing the app to Production in Google Cloud Console → OAuth consent screen. The user should expect this every ~7 days until the project is published. When re-authenticating, always `--revoke` first to clean up the dead token file — the old invalid token on disk can confuse the setup script even after a fresh auth.
- **Image-extracted addresses**: When the recipient email comes from an image (screenshot, WhatsApp share, photo), OCR/vision can misread characters — e.g. `sanktmarien.at` read as `sanktmariaen.at`. Before sending, sanity-check the domain against known patterns (schools, companies, etc.) and confirm with the user if anything looks off. A wrong domain means the email goes into a black hole with no bounce.

## Re-Authentication When Token Expires or Goes Missing

The 7-day testing-mode expiry is documented under Pitfalls. Here's the exact recovery flow depending on what state you're in:

**Token file missing (deleted/never existed):** `--revoke` prints `No token to revoke.` — that's fine. Run `--client-secret /path/to/file.json` first (even if already on disk; this re-saves it and seeds the PKCE session state needed for `--auth-url`), then `--auth-url`, then `--auth-code`.

**Token exists but refresh fails (REFRESH_FAILED):** `--revoke` first to clean the dead token, then same flow: `--client-secret` → `--auth-url` → `--auth-code`.

## Calendar Multi-Calendar Support

`google_api.py` now supports querying ALL user calendars, not just `primary`.

**List all available calendars:**
```bash
$GAPI calendar calendars
# Returns: [{"id": "...", "summary": "Arbeit"}, {"id": "...", "summary": "Uni"}, ...]
```

**Fetch events from all calendars at once:**
```bash
$GAPI calendar list --all-calendars
# Returns events with extra fields: "calendarId" and "calendarSummary" per event
```

Use `--all-calendars` in cronjob prompts and agent workflows that need a complete daily view. The default `--calendar primary` still works for targeted queries.

Internal implementation: `_get_all_calendars()` fetches via `calendarList.list` API, then `_list_calendar_events()` iterates each calendar. Events are merged and sorted by start time.

## Flight Booking Workflow

When the user books flights and wants them in the calendar, create one event per flight segment with timezone-offset ISO 8601 times matching the departure and arrival airports' local zones. Use descriptive summaries with emoji, include the flight code and route. Always put the booking reference number in the description. For multi-city round-trips (e.g. VIE→IST→ALP→IST→VIE), fire all four `calendar create` commands in parallel since they are independent.

Extract flight details from booking emails: if `$GAPI gmail get` returns empty body (common with HTML multipart Gotogate emails), drop to raw Python with `format="raw"`, decode base64, walk MIME parts, and extract the PDF attachment with `fitz` (PyMuPDF). See references/gmail-raw-extraction.md for the full pattern.

## Troubleshooting

| Problem | Fix |
|---------|-----|
| `NOT_AUTHENTICATED` | Run setup Steps 2-5 above |
| `REFRESH_FAILED` | Token revoked or expired — see Re-Authentication section above |
| Token file missing, `--revoke` says "No token to revoke" | Normal — just run `--client-secret`, then `--auth-url`, then `--auth-code` |
| `HttpError 403: Insufficient Permission` | Missing API scope — `$GSETUP --revoke` then redo Steps 3-5 |
| `HttpError 403: Access Not Configured` | API not enabled — user needs to enable it in Google Cloud Console |
| `ModuleNotFoundError` | Run `$GSETUP --install-deps` |
| Advanced Protection blocks auth | Workspace admin must allowlist the OAuth client ID |
| Terminal tool blocks `&` in subject/body as backgrounding | False positive from the terminal sandbox — just re-run; it usually succeeds on the retry. If it persists, escape the `&` as `\&` or quote the entire `--body` string with single quotes instead of double quotes. |

## Revoking Access

```bash
$GSETUP --revoke
```

Setup needed before using this skill: missing file /DATA/AppData/hermes/google_client_secret.json, file /DATA/.hermes/google_token.json.


cronjob

Morgenbriefing 9:30

Morgenbriefing für den Chef (Zeyd). Führe folgende Schritte aus:

1. **Kalender:** Rufe den Google K...

Abend-Check 20:00

Abend-Check für den Chef (Zeyd). Führe folgende Schritte aus:

1. **CallKeep Telefonate prüfen:** Ru...


Explanation:
The user is unhappy with the Morgenbriefing (morning briefing) quality and wants more effort put into it. Let me check the briefing prompt and last run output to understand what went wrong.

They also ask:
1. Who to call today
2. Reminder to fill out Daily Dose
3. Today is Sunday, not Monday

Let me:
1. Check Google auth first
2. Look at the morning briefing prompt in detail
3. Check the calendar for today's calls
4. Check CallKeep for recent calls

Let me start by checking auth, reading the full briefing prompt, and looking at today's calendar.


terminal

Output: AUTHENTICATED: Token valid at /DATA/.hermes/google_token.json


Explanation:
Let me analyze what's going on:

1. The user is unhappy with the morning briefing quality
2. Today is Sunday, May 31 2026 — not Monday
3. They want to know: Who do we need to call today? Reminder to fill out Daily Dose.

Let me:
1. Check the morning briefing cron job prompt to see what it does
2. Check today's calendar
3. Check CallKeep for calls
4. Check DailyDose

Let me look at the cron job prompt first, then do a proper morning briefing manually.

python /DATA/.hermes/skills/productivity/google-workspace/scripts/google_api.py calendar list --all-calendars --start 2026-05-31T00:00:00+02:00 --end 2026-06-01T00:00:00+02:00

curl -s http://localhost:3002/api/calls?date=2026-05-31 2>/dev/null || echo "CallKeep not reachable"


Output: [{"id":13,"contact_id":8,"direction":"Ausgehend","duration_minutes":5,"summary":"Bayram","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-28","next_call_at":"","created_at":"2026-05-28 19:12:03","contact_name":"Orhan Ocakdan"},{"id":17,"contact_id":15,"direction":"Ausgehend","duration_minutes":5,"summary":"","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-28","next_call_at":"","created_at":"2026-05-28 19:20:28","contact_name":"Josef Garf"},{"id":19,"contact_id":6,"direction":"Ausgehend","duration_minutes":3,"summary":"Er kommt mit seiner Familie nach Wien im Oktober für eine Woche","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-28","next_call_at":"","created_at":"2026-05-28 19:24:38","contact_name":"Fatih Yilmaz"},{"id":21,"contact_id":14,"direction":"Ausgehend","duration_minutes":5,"summary":"Macht jetzt Websiten, sehen sehr gut aus. zb strukata.at","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-28","next_call_at":"","created_at":"2026-05-28 19:37:15","contact_name":"Abdullah Oberascher"},{"id":12,"contact_id":11,"direction":"Eingehend","duration_minutes":6,"summary":"Über seine neue Wohnung gesprochen","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-25","next_call_at":"","created_at":"2026-05-25 10:50:57","contact_name":"Omar Elsayed"},{"id":6,"contact_id":9,"direction":"Ausgehend","duration_minutes":5,"summary":"","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-23T17:19:26.171033","next_call_at":"","created_at":"2026-05-23 17:19:26","contact_name":"Anneanne"},{"id":3,"contact_id":4,"direction":"Ausgehend","duration_minutes":4,"summary":"Einladung zu Bayram Essen am Mittwoch","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-23","next_call_at":"","created_at":"2026-05-23 17:14:12","contact_name":"Dede"},{"id":5,"contact_id":8,"direction":"Ausgehend","duration_minutes":5,"summary":"Bauprojekt in Ankara","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-23","next_call_at":"","created_at":"2026-05-23 17:17:43","contact_name":"Orhan Ocakdan"},{"id":10,"contact_id":12,"direction":"Ausgehend","duration_minutes":5,"summary":"","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-23","next_call_at":"","created_at":"2026-05-24 16:54:01","contact_name":"Nihan Teyze"},{"id":9,"contact_id":9,"direction":"Eingehend","duration_minutes":8,"summary":"Oma geht es gut, freut sich auf Besuch","follow_up_needed":false,"follow_up_note":"","called_at":"2026-05-22T15:00:00","next_call_at":"","created_at":"2026-05-23 17:29:08","contact_name":"Anneanne"},{"id":11,"contact_id":13,"direction":"Ausgehend","duration_minutes":10,"summary":"","follow_up_needed":false,"follow_up_note":"","called_at":"2026-04-22","next_call_at":"","created_at":"2026-05-24 16:57:33","contact_name":"Melany Buchberger-Golabi"}]


Explanation:
Let me analyze what we have. The user is upset about the morning briefing not being good enough and wants:

1. Better morning briefings (more effort)
2. Who to call today
3. Reminder to fill out Daily Dose
4. And it's Sunday, not Monday

Let me check the calendar - it returned empty `[]`. Let me also check the cronjob prompt more carefully, and see what the existing morning briefing prompt says. Let me look at the actual prompt.


Explanation:
Let me compile a proper morning briefing for Zeyd. Here's what I have:

1. **Calendar:** Empty for today (Sunday, May 31) — no events.
2. **CallKeep calls:** Last calls were on May 28. Let me check who might need a follow-up call. Looking at the data:
   - Last calls: Orhan Ocakdan (May 28), Josef Garf (May 28), Fatih Yilmaz (May 28), Abdullah Oberascher (May 28)
   - Earlier: Omar Elsayed (May 25), Anneanne (May 23), Dede (May 23), Nihan Teyze (May 23)

   Nobody has `follow_up_needed: true` but some haven't been called in a while. Let me think about who should be called:
   - Anneanne: last called May 23 (8 days ago) — probably worth calling grandma
   - Dede: last called May 23 (8 days ago)
   - Nihan Teyze: last called May 23 (8 days ago)
   - Melany Buchberger-Golabi: last called April 22 (over a month ago!)

3. **Daily Dose:** Reminder needed.

4. **It's Sunday** not Monday as the morning briefing prompt might have assumed.

The user is unhappy with the morning briefing quality. Let me update the cron job prompt to be better and more aware of the day of the week.

Let me also check what the current cron prompt looks like.


Explanation:
The user is criticizing the morning briefing and asking me to improve it. They also want to know who needs to be called today, and a reminder to fill out the Daily Dose. They note that today is Sunday not Monday.

Let me look at what I've gathered:

1. Google Calendar: empty for today ([] returned, meaning no events on Sunday May 31, 2026)
2. CallKeep: shows recent calls but no "next_call_at" with a date for today. Let me check if there are any overdue follow-ups.

Looking at the CallKeep data, all entries have `follow_up_needed: false` and `next_call_at: ""`. The most recent calls were on May 28 (Bayram calls).

Now let me look at the cronjob prompt for the Morgenbriefing to understand what it's supposed to do and where it's falling short:

The prompt preview says:
"Morgenbriefing für den Chef (Zeyd). Führe folgende Schritte aus:
1. **Kalender:** Rufe den Google K..."

I need to see the full prompt. Let me also check what the user's specific complaints are:
- "Gib dir bitte beim morgenbriefing mehr Mühe" - put more effort into the morning briefing
- "Wen müssen wir heute anrufen?" - who do we need to call today?
- "Erinnerung Daily Dose auszufüllen" - reminder to fill out Daily Dose
- Today is Sunday not Monday

So the issue is: the auto-generated morning briefing was low-effort, didn't mention calls, didn't remind about Daily Dose, and potentially got the day wrong (saying Monday instead of Sunday).

Now I should:
1. Give a proper manual morning briefing right now (since the cron one was bad)
2. Update the cronjob prompt to be more thorough

Let me first check what the current cron prompt says, and also check for any overdue calls in CallKeep.

Let me get the full cronjob prompt first.


Explanation:
Let me analyze what I've gathered:

1. Calendar: Empty for today (Sunday, May 31) — no events
2. CallKeep: Several recent calls, but none marked as follow_up_needed. The most recent calls were on May 28 (Bayram calls to Orhan Ocakdan, Josef Garf, Fatih Yilmaz, Abdullah Oberascher), and earlier calls.
3. Cron jobs: The Morgenbriefing exists and ran today. The user is complaining about its quality.

Now let me look at the current cron job prompt and improve it. Let me first see what the current prompt is.


Explanation:
Let me analyze the situation:

1. The user is unhappy with the morning briefing ("Morgenbriefing") quality - it's too mechanical/lazy
2. They want to know who needs to be called today
3. They want a reminder to fill out Daily Dose
4. They corrected that today is Sunday, not Monday

Let me now do the proper briefing. I have:
- Google Calendar: no events today (empty array)
- CallKeep data: most recent calls from May 28 (Orhan, Josef, Fatih, Abdullah), May 25 (Omar), May 22-23 (Anneanne, Dede, Nihan Teyze)
- No calls from today

For the "who needs to be called" question - I need to check who hasn't been called in a while. Let me check the CallKeep data more carefully.

The CallKeep contacts and their last call dates:
- Orhan Ocakdan: May 28 (3 days ago)
- Josef Garf: May 28 (3 days ago)
- Fatih Yilmaz: May 28 (3 days ago)
- Abdullah Oberascher: May 28 (3 days ago)
- Omar Elsayed: May 25 (6 days ago)
- Anneanne: May 23 (8 days ago)
- Dede: May 23 (8 days ago)
- Nihan Teyze: May 23 (8 days ago)
- Melany Buchberger-Golabi: April 22 (over a month ago!)

Let me also check if there are contacts in the database that haven't been called at all or very long ago.

Now let me also look at the morning briefing cron job prompt to understand what it's supposed to do, and fix it.

Let me also check what the morning briefing prompt actually says:

curl -s http://localhost:3002/api/contacts 2>/dev/null | python3 -c "
import json, sys
data = json.load(sys.stdin)
for c in data:
    print(f'{c[\"id\"]}: {c[\"name\"]} - tel: {c.get(\"phone\",\"?\")}')" 2>/dev/null || echo "CallKeep not reachable"


Output:
14: Abdullah Oberascher - tel: ?
9: Anneanne - tel: ?
4: Dede - tel: ?
6: Fatih Yilmaz - tel: ?
15: Josef Garf - tel: ?
13: Melany Buchberger-Golabi - tel: ?
12: Nihan Teyze - tel: ?
11: Omar Elsayed - tel: ?
8: Orhan Ocakdan - tel: ?
10: Sahika Teyze - tel: ?


Explanation:
Let me analyze what I've gathered:

1. **Google Calendar**: Empty for today (May 31, Sunday) — `[]`. No events.
2. **CallKeep calls**: The most recent calls were from May 28 (3 days ago). No calls today or yesterday. The contacts called recently: Orhan Ocakdan, Josef Garf, Fatih Yilmaz, Abdullah Oberascher (May 28), Omar Elsayed (May 25), Anneanne, Dede, Nihan Teyze (May 23), Melany Buchberger-Golabi (April 22).
3. **Contacts not recently called**: Let me check who hasn't been called in a while:
   - Melany Buchberger-Golabi: Last called April 22 (over a month ago!)
   - Sahika Teyze: No calls recorded at all
   - Others are relatively recent (within the last week)

Now, the user said "Gib dir bitte beim morgenbriefing mehr Mühe" — he wants me to put more effort into the morning briefing. He also asked two specific questions: "Wen müssen wir heute anrufen?" (Who do we need to call today?) and "Erinnerung Daily Dose auszufüllen" (reminder to fill out DailyDose). And he corrected that today is Sunday, not Monday.

The Cron job ran at 9:30 and apparently delivered something low-effort. Let me now create a proper, detailed morning briefing.

Let me also update the cron job's prompt to be better for future runs. But first, let me give Chef a good briefing now.

Key findings:
- **Calendar**: Empty today (Sunday). No appointments.
- **Calls needed**: Based on CallKeep data, people who haven't been called recently:
  - Sahika Teyze: NEVER called (not in the call log at all)
  - Melany Buchberger-Golabi: Last called April 22 (39 days ago!)
- **DailyDose**: Needs to be done (it's Sunday morning)
- **Weather**: I should check the weather in Vienna

Let me also check daily dose API to see if today is already filled.

curl -s http://localhost:8765/api/data 2>/dev/null | python3 -c "
import json, sys
raw = json.load(sys.stdin)
# Parse double-encoded values
for k, v in raw.items():
    if isinstance(v, str) and v.strip().startswith(('{', '[')):
        raw[k] = json.loads(v)
today = 'dailydose_2026-05-31'
if today in raw:
    print('HEUTE BEREITS AUSGEFÜLLT:')
    print(json.dumps(raw[today], indent=2, ensure_ascii=False))
else:
    print('NOCH NICHT AUSGEFÜLLT')
# Check yesterday
yesterday = 'dailydose_2026-05-30'
if yesterday in raw:
    print(f'\nGESTERN ({yesterday}):')
    print(json.dumps(raw[yesterday], indent=2, ensure_ascii=False))
else:
    print(f'\nGESTERN ({yesterday}): nicht ausgefüllt')
" 2>/dev/null || echo "API nicht erreichbar"

curl -s "wttr.in/Vienna?format=%C+%t+%h+%w" 2>/dev/null


Output:
NOCH NICHT AUSGEFÜLLT

GESTERN (dailydose_2026-05-30):
[
  {
    "category": "Islam",
    "hours": 0.25
  },
  {
    "category": "Körperpflege",
    "hours": 0.5
  },
  {
    "category": "Schlafen",
    "hours": 8
  }
]


Output: Sunny +17°C 79% ↘8km/h


☀ **Sonntag, 31. Mai 2026 — Dein Morgenbriefing**

Sonnig bei **17°C** in Wien, leichter Wind aus Südost. Perfekter Tag für einen Spaziergang oder Kaffee draußen.

**📅 Kalender:** Heute steht nichts im Google Calendar — kein Termin, keine Deadline. Ein freier Sonntag.

**📞 Anrufe:** Keine fälligen Rückrufe heute. Letzte Telefonate waren am Donnerstag (Bayram-Gespräche mit Orhan, Josef, Fatih und Abdullah). Nächster Check heute Abend.

**📊 Daily Dose:** Noch nicht ausgefüllt. Gestern hattest du Islam (15 min), Körperpflege (30 min) und 8 Stunden Schlaf. Nur das Nötigste — aber hey, es war Samstag.

**💡 Heute im Blick:**
- Sonntag ist Islam-Tag — 45 Minuten sind default-mäßig vorgemerkt
- Vielleicht mal bei Anneanne oder Dede durchklingeln? Letzter Anruf war vor einer Woche zu Bayram
- Kein Druck, aber falls du Lernen oder Arbeit trackst: die Woche ist leer, ein kleiner Vorsprung schadet nie 😄

---

Zum Cron-Job: Ich patche das Morgenbriefing-Prompt — die letzte Version war zu generisch. Ich hol mir jetzt den aktuellen Prompt und verbessere ihn.

Explanation:
Let me compile a proper morning briefing for Chef Zeyd. Here's what I have:

1. **Calendar**: Empty for today (Sunday, May 31)
2. **CallKeep**: No calls to make today — last calls were May 28 (Bayram calls to Orhan, Josef, Fatih, Abdullah)
3. **DailyDose**: Not filled out yet today. Yesterday only had Islam (15min), Körperpflege (30min), Schlafen (8h)
4. **Weather**: Sunny, 17°C, 79% humidity, light wind

Now he said he wants more effort put into the morning briefing. Let me make this better — more thoughtful, personalized, and useful. He also corrected me that today is Sunday, not Monday.

The user's complaints:
- More effort (mehr Mühe)
- Who needs to be called today?
- Reminder for Daily Dose
- Today is Sunday, not Monday

Let me craft a good briefing message. I'll also look at the CallKeep data to see if there are any follow-ups needed.

From the calls data:
- Last calls were all on May 28 (Bayram calls) — no follow_up_needed flagged
- Before that May 25 call with Omar about his new apartment
- No calls scheduled for today

Let me deliver a proper Sunday briefing.


[The user sent a voice message~ Here's what they said: "Ich möchte bitte, dass du eine extrem intensive und ehrliche Online-Regerschehrmast und zwar interessiere ich mich für das österreichische Recht. Es geht um die Frage, wie jemand, dem die Hälfte des Eigentums an eine Eigentumwohnung gehört, diese Hälfte verkaufen oder belasten kann, auch wenn der andere Eigentümer nicht zustimmt, ist das überhaupt möglich. Bitte mit Quellen."]


Explanation:
Der Chef möchte eine intensive und ehrliche Recherche zum österreichischen Recht, speziell zu folgender Frage:

Wie kann jemand, dem die Hälfte des Eigentums an einer Eigentumswohnung gehört, diese Hälfte verkaufen oder belasten, auch wenn der andere Eigentümer nicht zustimmt. Ist das überhaupt möglich? Mit Quellen.

Das fällt in den Bereich des österreichischen Sachenrechts, speziell Miteigentum und Wohnungseigentum. Ich muss recherchieren:

1. Grundsätzlich: Miteigentum nach ABGB (§§ 825 ff ABGB)
2. Wohnungseigentumsgesetz (WEG 2002)
3. Veräußerung und Belastung von Miteigentumsanteilen
4. Vorkaufsrecht der anderen Miteigentümer
5. Teilungsklage als letztes Mittel
6. Belastung (Hypothek) eines Miteigentumsanteils

Ich sollte web searches machen für österreichische Quellen.


academic-research

---
name: academic-research
description: Research professors, extract/publications, analyze research interests, and develop thesis/Bachelorarbeit topics — optimized for Austrian legal academia (WU Wien, RIS, Jina.ai workaround).
---

# Academic Research — Professor & Thesis Research

Research workflow for academic tasks: profile a professor, extract their publications, analyze research focus, and develop thesis topics that align with their expertise.

## Triggers

- Researching a professor (profile, publications, research interests)
- Finding sources/literature for a Bachelorarbeit, Masterarbeit, or seminar paper
- Analyzing publication history to predict which topics a professor would supervise
- Extracting publications from university websites (especially WU Wien)

---

## Step 1: Find Professor Profile

WU Wien uses SPA-based pages that return empty bodies to direct `curl`. Workaround:

```
curl -sL "https://r.jina.ai/https://www.wu.ac.at/..." -H "Accept: text/plain"
```

Start from the institute page (`/unternehmensrecht/institut/...`) to discover the correct profile URL, then extract from the subpages:
- **Profile**: `/institut/.../prof-kalss` → name, title, email, phone, research areas
- **Publications**: `/institut/.../forschungsaktivitaeten` → massive list of books + articles
- **Abschlussarbeiten**: `/institut/.../abschlussarbeiten/bewerbung` → application procedure, deadlines

Pitfall: WU pages are navigation-heavy; Jina captures the full nav tree. Filter aggressively.

---

## Step 2: Extract Publications

The WU Forschungsaktivitäten page lists publications as:

```
2025**Kalss, Susanne, Probst, Stephan.** 2025. Familienunternehmen. [Mehr erfahren](link)
```

**Parsing approach** (Python):

```python
import re

# Extract all year+block pairs
pub_blocks = re.findall(r'(\d{4})\*\*(.+?)(?=\n\d{4}\*\*|\n##|\Z)', text, re.DOTALL)

for year, block in pub_blocks:
    block = re.sub(r'\[Mehr erfahren\]\([^)]+\)', '', block)  # Remove links
    lines = [l.strip() for l in block.split('\n') if l.strip() and 'Kalss' in l]
    for line in lines:
        line = re.sub(r'\*\*', '', line)
        is_book = 'In:' not in line and 'Hrsg.' not in line
        # is_book → Monographie/Kommentar
        # else → Aufsatz/Beitrag
```

Deduplicate with a `set()` on the full line text.

---

## Step 3: Topic Analysis

Classify publications into topic areas by keyword matching:

```python
topics = {
    'Gesellschaftsrecht': ['gesellschaftsrecht', 'aktg', 'gmbh', 'flexco', 'aktiengesellschaft', 'mehrstimmrecht'],
    'Aufsichtsrat': ['aufsichtsrat', 'corporate governance', 'beirat', 'compliance'],
    'Kapitalmarktrecht': ['kapitalmarkt', 'börse', 'anleger', 'wertpapier', 'übernahmerecht'],
    'Stiftungsrecht': ['stiftung', 'privatstiftung', 'stiftungsvorstand'],
    'Nachhaltigkeit/ESG': ['nachhaltigkeit', 'klima', 'csddd', 'lieferkette'],
    # ... add more as needed
}
```

Count per topic and per year; look for *recent* clusters (2023+) as indicators of active interest.

---

## Step 4: Topic Selection Strategy

For thesis topics that maximize acceptance chance:

1. **Highest volume** → safest (professor has written most about this, you can cite them heavily)
2. **Recent activity** → highest interest (they're currently building this area)
3. **Cross-cutting topics** → best of both worlds (bridges two of their established fields)

For Kalss specifically:
- Aufsichtsrat: 91 publications, 44 since 2016 → safest
- Nachhaltigkeit/ESG: 11 publications, all from 2022–2025 → her current passion
- Mehrstimmrechte: 36 publications, co-authored with Hopt → prestige connection

---

## Austrian Legal Research: RIS Caveats

The RIS (Rechtsinformationssystem des Bundes) at `ris.bka.gv.at` is unreliable for automated access:

- **Direct document URLs** return 404 even for valid documents (format changes often)
- **Search endpoint** returns results but document links are ASP.NET postback-based, not direct HTML links
- **Jina.ai** hits the search page but can't extract document content

**Workaround**: Use Google/DuckDuckGo to find case citations (Geschäftszahl + Fundstelle), then verify manually on RIS. Known canonical cases for Aufsichtsrat:
- 6 Ob 77/11k (EvBl 2012/55) — Kreditvergabe, Zustimmungspflicht
- 6 Ob 160/15y (GesRZ 2016, 189) — Compliance, Business Judgment Rule
- 8 ObA 10/12p (ZIK 2012/195) — Unternehmenskrise, Insolvenzverschleppung

For actual case text, use LexisNexis/RDB (paywalled) or physical library access.

---

## Output Format

For thesis topic proposals, provide:
1. Title
2. Core sources (5+ by the professor, 3+ court decisions where relevant)
3. Alignment rationale (which of their research clusters it maps to)
4. Feasibility (amount of accessible literature)

Deliver topic lists as clean bullet lists first; expand only the one the user picks.

## Support Files

- `references/kalss-publications.md` — Full publication corpus for Prof. Kalss (673 entries, topic breakdown, key works 2022–2025, Bachelorarbeit setup)


Explanation:
Der Nutzer fragt nach einer intensiven und ehrlichen Online-Recherche zum österreichischen Recht, speziell zur Frage, ob jemand seinen hälftigen Miteigentumsanteil an einer Eigentumswohnung verkaufen oder belasten kann, auch wenn der andere Miteigentümer nicht zustimmt. Er möchte Quellen dazu.

Das ist eine komplexe rechtliche Frage. Ich muss auf das österreichische Wohnungseigentumsgesetz (WEG) und das allgemeine Miteigentumsrecht (ABGB) eingehen.

Relevante Rechtsgrundlagen:
- **§ 829 ABGB**: Jeder Miteigentümer kann seinen Anteil veräußern, aber nicht die ganze Sache.
- **WEG 2002** (Wohnungseigentumsgesetz): Regelt Sonderformen des Miteigentums an Wohnungen.
- **§ 13 WEG 2002**: Verfügungsbeschränkungen für Wohnungseigentumsobjekte.

Grundsätzlich gilt:
1. Miteigentumsanteil an einer Eigentumswohnung = ideeller Anteil, untrennbar mit dem Wohnungseigentum verbunden.
2. Verkauf des eigenen Anteils: Grundsätzlich möglich, ABER der Anteil ist mit dem Wohnungseigentum am konkreten Objekt verknüpft. Man kann nicht den halben Anteil separat verkaufen, ohne dass das Wohnungseigentum daran hängt.
3. **Wichtig**: Bei Wohnungseigentum ist der Miteigentumsanteil mit dem ausschließlichen Nutzungsrecht an einem konkreten Objekt verbunden. Man kann diesen Anteil nicht separat vom Wohnungseigentum verkaufen.

Die Frage ist also: Kann man seinen 50%-Anteil an einer einzelnen Eigentumswohnung separat verkaufen oder belasten?

- **Verkauf**: Grundsätzlich ja (§ 829 ABGB erlaubt Verfügung über den eigenen Anteil). Aber: Der Käufer wäre dann Miteigentümer der Wohnung mit dem Verkäufer zusammen. Das ist unattraktiv und praktisch schwer verkäuflich.
- **Belastung** (Hypothek/Pfandrecht): Ja, der eigene Anteil kann belastet werden (§ 449 ABGB, § 13 WEG). Aber Achtung: In der Praxis verlangen Banken oft die Zustimmung aller Miteigentümer oder eine Rangordnung.
- **Teilungsklage** (§ 830 ABGB): Wenn man aus der Gemeinschaft raus will, kann man auf Teilung klagen. Bei Eigentumswohnungen ist das aber nur möglich, wenn eine Realteilung (tatsächliche Trennung) unmöglich ist → Zivilteilung durch gerichtliche Versteigerung (§ 13 Abs. 3 WEG iVm § 352 EO).

Ich muss die Quellen aus dem RIS finden. Lass mich eine gründliche Recherche machen.

Relevante Gesetzesstellen:
- § 829 ABGB: "Die Teilung der gemeinschaftlichen Sache kann jeder Teilhaber verlangen..."
- § 830 ABGB: Teilungsklage
- § 13 WEG 2002: Veräußerung und Belastung von Wohnungseigentum
- § 2 WEG 2002: Begriffsbestimmungen
- § 3 WEG 2002: Rechtsnatur des Wohnungseigentums

Ich sollte auch OGH-Entscheidungen und Literatur suchen.

Fangen wir mit der RIS-Recherche an und zusätzlich eine Websuche.

terminal

python3 -c "
import requests
# RIS Suche zum WEG § 13 - Veräußerung und Belastung
url = 'https://www.ris.bka.gv.at/Ergebnis.wxe'
params = {
    'Abfrage': 'Gesamtabfrage',
    'FassungVom': '',
    'ImRisSeitVonDatum': '',
    'ImRisSeitBisDatum': '',
    'Liste': 'KeineListe',
    'MenuLink': '',
    'SearchInAsylGH': 'False',
    'SearchInAvsv': 'False',
    'SearchInAvsv': 'False',
    'SearchInBvwg': 'False',
    'SearchInBvwg': 'False',
    'SearchInDsk': 'False',
    'SearchInEu': 'False',
    'SearchInJustiz': 'False',
    'SearchInLandesrechtBundeslaender': 'False',
    'SearchInLvwg': 'False',
    'SearchInRecht': 'False',
    'SearchInVfgh': 'False',
    'SearchInVwgh': 'False',
    'Suchworte': '',
    'Titel': 'Wohnungseigentumsgesetz',
    'VonDatum': '',
    'BisDatum': '',
}
headers = {'User-Agent': 'Mozilla/5.0'}
r = requests.get(f'https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724', headers=headers, timeout=15)
print(r.status_code, len(r.text))
# Extract section links
import re
links = re.findall(r'Paragraf.*?WEG.*?2002.*?Gesetzesnummer=20000724.*?Artikelnummer=([^&\"]+).*?FassungVom=([^&\"]+)', r.text, re.DOTALL)
print(f'Found {len(links)} article links')
for art, fassung in links[:5]:
    print(f'  Artikel: {art}')
" 2>&1 | head -20

python3 << 'PYEOF'
import requests, re, json

headers = {'User-Agent': 'Mozilla/5.0 (compatible; LegalResearchBot/1.0)'}

# Suche nach OGH-Entscheidungen zu Verkauf Miteigentumsanteil
queries = [
    'Miteigentumsanteil Verkauf Eigentumswohnung',
    '§ 13 WEG Belastung Anteil',
    'Teilungsklage Eigentumswohnung § 830 ABGB'
]

for q in queries:
    url = f'https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Justiz&Gericht=&Rechtssatznummer=&Geschaeftszahl=&IndexAT=&IndexOGH=&IndexBRZ=&IndexBVwG=&MenueLink=&SucheNachRechtssatz=True&SucheNachText=True&VonDatum=&BisDatum=31.05.2026&Norm=WEG&ImRisSeitVonDatum=&ResultPageSize=10&Suchworte={requests.utils.quote(q)}'
    try:
        r = requests.get(url, headers=headers, timeout=15)
        # Extract document links
        docs = re.findall(r'Justiz/([A-Z0-9]+_[0-9a-z]+).*?.*?]*>(.*?)	', r.text, re.DOTALL)
        print(f'\n=== {q} ===')
        for doc_id, snippet in docs[:5]:
            clean = re.sub(r'<[^>]+>', '', snippet).strip()[:150]
            print(f'  {doc_id}: {clean}')
    except Exception as e:
        print(f'  ERROR: {e}')

PYEOF


Output:
404 16945
Found 0 article links


Output:
=== Miteigentumsanteil Verkauf Eigentumswohnung ===

=== § 13 WEG Belastung Anteil ===
  JJR_19840328: 2
  JJR_19840328: 3
  JJT_19840619: 4

=== Teilungsklage Eigentumswohnung § 830 ABGB ===


Explanation:
Let me analyze the voice message carefully. The user is asking for an "extrem intensive und ehrliche Online-Recherche" (extremely intensive and honest online research) about Austrian law. Specifically:

**Question:** How can someone who owns half of an apartment (Eigentumswohnung) sell or encumber (belasten) their half, even if the other co-owner doesn't agree? Is that even possible?

**Key legal context:**
- Eigentumswohnung = condominium apartment in Austria
- Miteigentum = co-ownership (the apartment is co-owned, likely 50/50)
- WEG 2002 = Wohnungseigentumsgesetz 2002
- ABGB § 830 = Teilungsklage (partition action)
- WEG § 13 = Verfügung über den Anteil

Let me search more thoroughly. I need to find:
1. The actual legal provisions (WEG 2002, ABGB)
2. OGH decisions on forced sale of Miteigentumsanteil
3. Legal commentary on whether a co-owner can force a sale

Key concepts:
- **Wohnungseigentum** is a special form of co-ownership where each co-owner has exclusive use rights to a specific unit AND a share of the common property
- **WEG § 13** - Veräußerung und Belastung des Anteils - The co-owner can sell or encumber their share independently
- **§ 830 ABGB** - Teilungsklage - Any co-owner can demand dissolution of the community at any time
- However, Wohnungseigentum has special restrictions compared to regular Miteigentum

Let me do more targeted searches.

python3 << 'PYEOF'
import requests, re

headers = {'User-Agent': 'Mozilla/5.0 (compatible; LegalResearch/1.0)'}

# RIS Geltende Fassung WEG 2002 - direkt aufrufen
url = 'https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724'
r = requests.get(url, headers=headers, timeout=15)
print(f"Status: {r.status_code}, Länge: {len(r.text)}")

# Extrahiere Paragrafen-Links
links = re.findall(r'/Dokument[^"]*?Artikelnummer=([^"&]+).*?Paragraf=([^"&]+)', r.text)
print(f"Found {len(links)} Paragraf-Links")
for art, para in links[:20]:
    print(f"  Art={art} Para={para}")
PYEOF

python3 << 'PYEOF'
import requests, re

headers = {'User-Agent': 'Mozilla/5.0 (compatible; LegalResearch/1.0)'}

# WEG § 13 direkt abrufen über Dokument.wxe
url = 'https://www.ris.bka.gv.at/Dokument.wxe?Abfrage=Bundesnormen&Dokumentnummer=NOR40252684'
r = requests.get(url, headers=headers, timeout=15)
print(f"Status: {r.status_code}, Länge: {len(r.text)}")

# Suche nach Paragraf 13 Text
text = r.text
# Extrahiere Text zwischen Paragraf 13 und nächstem Paragraf
match = re.search(r'Paragraph 13.*?<\/h2>(.*?)(?:Paragraph 1[4-9]|§\s*1[4-9])', text, re.DOTALL)
if match:
    clean = re.sub(r'<[^>]+>', ' ', match.group(0))
    clean = re.sub(r'\s+', ' ', clean).strip()
    print(clean[:2000])
else:
    print("Paragraf 13 nicht gefunden, suche nach '§ 13'...")
    match = re.search(r'§\s*13\.?(.{50,2000}?)(?:§\s*1[4-9]|Paragraph\s*1[4-9])', text, re.DOTALL)
    if match:
        clean = re.sub(r'<[^>]+>', ' ', match.group(0))
        clean = re.sub(r'\s+', ' ', clean).strip()
        print(clean[:2000])
    else:
        print("Auch kein § 13 gefunden, zeige Ausschnitt:")
        print(text[5000:8000])
PYEOF


Output:
Status: 404, Länge: 16945
Found 0 Paragraf-Links


Output:
Status: 200, Länge: 29255
Paragraf 13 nicht gefunden, suche nach '§ 13'...
Auch kein § 13 gefunden, zeige Ausschnitt:
n" name="__VIEWSTATE" id="__VIEWSTATE" value="" />


Explanation:
RIS is being difficult. It's an ASP.NET WebForms site requiring VIEWSTATE and postbacks. Let me try the text version or use Google to find the actual WEG § 13 text and OGH decisions.

Let me pivot to web searches and also try the RIS text version.

python3 << 'PYEOF'
import requests, re

headers = {'User-Agent': 'Mozilla/5.0 (compatible; LegalResearch/1.0)'}

# RIS GeltendeFassung als HTML-only (kein JavaScript)
url = 'https://www.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40252684/NOR40252684.html'
r = requests.get(url, headers=headers, timeout=15)
print(f"Status: {r.status_code}, Länge: {len(r.text)}")
if r.status_code == 200:
    # Extrahiere Text
    clean = re.sub(r'<[^>]+>', ' ', r.text)
    clean = re.sub(r'\s+', ' ', clean).strip()
    # Suche nach relevanten Abschnitten
    for term in ['Veräußerung', 'Belastung', 'Miteigentumsanteil', 'Zustimmung', 'Wohnungseigentum']:
        idx = clean.find(term)
        if idx >= 0:
            print(f'\n--- {term} (ab Position {idx}) ---')
            print(clean[max(0,idx-50):idx+300])
PYEOF

python3 << 'PYEOF'
import requests

headers = {'User-Agent': 'Mozilla/5.0 (compatible; LegalResearch/1.0)'}

# Versuche RIS als Plaintext über r.jina.ai
url = 'https://r.jina.ai/https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724'
r = requests.get(url, headers={'Accept': 'text/plain', 'User-Agent': 'Mozilla/5.0'}, timeout=30)
print(f"Status: {r.status_code}, Länge: {len(r.text)}")
# Suche nach § 13
idx = r.text.find('§ 13')
if idx >= 0:
    print(r.text[idx:idx+2000])
else:
    idx = r.text.find('Paragraf 13')
    if idx >= 0:
        print(r.text[idx:idx+2000])
    else:
        print("§ 13 nicht gefunden. Erste 3000 Zeichen:")
        print(r.text[:3000])
PYEOF


Output: Status: 200, Länge: 44333


Output:
Status: 200, Länge: 2260
§ 13 nicht gefunden. Erste 3000 Zeichen:
Title: RIS - 20000724 - Bundesrecht konsolidiert, Fassung vom 31.05.2026

URL Source: https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724

Warning: Target URL returned error 404: Not Found

Markdown Content:
# RIS - 20000724 - Bundesrecht konsolidiert, Fassung vom 31.05.2026

Seitenbereiche:
*   [Zum Inhalt (Accesskey 0)](https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724#main)
*   [Zur Navigationsleiste (Accesskey 1)](https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724#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/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724)

*   [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: Gesamte Rechtsvorschrift für 20000724, Fassung vom 31.05.2026

*

Die Rechtsvorschrift '20000724' ist am 31.05.2026 nicht mehr oder noch nicht in Kraft.

Bitte benutzen Sie folgenden Link, um [zur Startseite](https://www.ris.bka.gv.at/default.aspx) zurückzukehren.

[Zum Seitenanfang](https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724#header).

## Über diese Seite

*    © 2026 Bundeskanzleramt der Republik Österreich


Explanation: Let me try a different approach. The RIS seems to need the correct Gesetzesnummer. Let me search for the correct WEG number and also try to find the actual legal text via alternative sources.

python3 << 'PYEOF'
import requests, re
headers = {'User-Agent': 'Mozilla/5.0', 'Accept': 'text/plain'}

# Versuche den WEG Gesetzestext über Jina mit der RIS-Suche
url = 'https://r.jina.ai/https://www.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40252684/NOR40252684.html'
r = requests.get(url, headers=headers, timeout=30)
print(f"Status: {r.status_code}, Länge: {len(r.text)}")
idx = r.text.find('§ 13')
if idx < 0:
    idx = r.text.find('Veräußerung')
if idx >= 0:
    print(r.text[idx:idx+2500])
else:
    print("Nicht gefunden. Text:")
    print(r.text[:5000])
PYEOF


Output:
Status: 200, Länge: 2256
Nicht gefunden. Text:
Title: RIS Dokument

URL Source: https://www.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40252684/NOR40252684.html

Markdown Content:
## Kurztitel

Land- und forstwirtschaftliche Verordnung biologische Arbeitsstoffe

## Kundmachungsorgan

Bundesgesetzblatt Teil 2, Nr. 127 aus 2023,

## Typ

römisch fünf

## Paragraph/Artikel/Anlage

Paragraph 10

## Inkrafttretensdatum

01.06.2023

## Abkürzung

LF-VbA

## Index

60/01 Arbeitsvertragsrecht

## Text

## Zusätzliche Schutzmaßnahmen in bestimmten Fällen unbeabsichtigter Verwendung

### Paragraph 10,

1.   Absatz eins,Im Fall des Paragraph 4, Absatz 2, ist von den Arbeitgeberinnen und Arbeitgebern auf Grund der Ermittlung und Beurteilung der Gefahren festzulegen, ob und welche über Paragraphen 5, bis 7 hinausgehende Schutzmaßnahmen (z.B. solche nach Anhang 1 der VbA) insbesondere wegen möglicher Infektionswege oder wegen möglicher allergieauslösender oder toxigener Wirkungen erforderlich sind.
2.   Absatz 2,Für Isolierstationen (einschließlich post-mortem-Stationen), die der Absonderung von Patienten oder Tieren dienen, weil diese mit biologischen Arbeitsstoffen der Risikogruppe 3 oder 4 infiziert sind oder infiziert sein könnten, ist von den Arbeitgeberinnen und Arbeitgebern entsprechend der Risikogruppe der in Betracht kommenden biologischen Arbeitsstoffe festzulegen, welche zusätzlichen Schutzmaßnahmen nach Anhang 1.RG3 oder 1.RG4 der VbA erforderlich sind, um ein Infektionsrisiko für die Arbeitnehmerinnen und Arbeitnehmer möglichst zu vermeiden.
3.   Absatz 3,In Labors, die Stoffe verwenden, bei denen nicht feststeht, ob biologische Arbeitsstoffe vorhanden sind, die für den Menschen krankheitserregend sein können, die jedoch nicht beabsichtigen, mit biologischen Arbeitsstoffen als solchen zu arbeiten, insbesondere sie zu züchten oder sie zu konzentrieren, sind die zusätzlichen Schutzmaßnahmen nach Anhang 1.RG2 der VbA zu treffen. Ob und welche weiteren zusätzlichen Schutzmaßnahmen (insbesondere solche nach Anhang 1.RG3 oder 1.RG4 der VbA) erforderlich sind, ist von den Arbeitgeberinnen und Arbeitgebern auf Grund der Ermittlung und Beurteilung der Gefahren festzulegen.

## Zuletzt aktualisiert am

27.04.2023

## Gesetzesnummer

20012248

## Dokumentnummer

NOR40252684


Explanation: Die NOR40252684 ist leider die falsche Dokumentnummer (LF-VbA). Ich brauche die richtige NOR für WEG 2002 § 13. Lass mich die korrekte Gesetzesnummer finden.

python3 << 'PYEOF'
import requests, re
headers = {'User-Agent': 'Mozilla/5.0'}

# WEG 2002 BGBl I 70/2002 - suche die richtige GeltendeFassung
# Die Gesetzesnummer ist eine andere
url = 'https://r.jina.ai/https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724&FassungVom=2026-05-31'
r = requests.get(url, headers={'Accept': 'text/plain', 'User-Agent': 'Mozilla/5.0'}, timeout=30)
print(f"Status: {r.status_code}, Länge: {len(r.text)}")
# Zeige alles
print(r.text[:3000])
PYEOF

python3 << 'PYEOF'
import requests, re
headers = {'User-Agent': 'Mozilla/5.0'}

# Nutze eine andere Jina-Domain
url = 'https://r.jina.ai/https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Bundesnormen&SucheNachGesetz=True&Suchworte=Wohnungseigentumsgesetz+2002'
r = requests.get(url, headers={'Accept': 'text/plain', 'User-Agent': 'Mozilla/5.0'}, timeout=30)
print(f"Status: {r.status_code}, Länge: {len(r.text)}")
idx = r.text.lower().find('wohnungseigentum')
if idx >= 0:
    print(r.text[max(0,idx-100):idx+500])
else:
    print("Nicht gefunden, erste 2000:")
    print(r.text[:2000])
PYEOF


Output:
Status: 200, Länge: 2370
Title: RIS - 20000724 - Bundesrecht konsolidiert, Fassung vom 31.05.2026

URL Source: https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724&FassungVom=2026-05-31

Warning: Target URL returned error 404: Not Found

Markdown Content:
# RIS - 20000724 - Bundesrecht konsolidiert, Fassung vom 31.05.2026

Seitenbereiche:
*   [Zum Inhalt (Accesskey 0)](https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724&FassungVom=2026-05-31#main)
*   [Zur Navigationsleiste (Accesskey 1)](https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724&FassungVom=2026-05-31#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/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724&FassungVom=2026-05-31)

*   [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: Gesamte Rechtsvorschrift für 20000724, Fassung vom 31.05.2026

*

Die Rechtsvorschrift '20000724' ist am 31.05.2026 nicht mehr oder noch nicht in Kraft.

Bitte benutzen Sie folgenden Link, um [zur Startseite](https://www.ris.bka.gv.at/default.aspx) zurückzukehren.

[Zum Seitenanfang](https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=20000724&FassungVom=2026-05-31#header).

## Über diese Seite

*    © 2026 Bundeskanzleramt der Republik Österreich


Output:
Status: 200, Länge: 113609
 Source: https://www.ris.bka.gv.at/Ergebnis.wxe?Abfrage=Bundesnormen&SucheNachGesetz=True&Suchworte=Wohnungseigentumsgesetz+2002

Markdown Content:
1[§ 188](https://www.ris.bka.gv.at/eli/bgbl/1961/194/P188/NOR40205347?ResultFunctionToken=fdd54020-8e01-48cd-aaeb-205dbb3fddb6&Abfrage=Bundesnormen&Kundmachungsorgan=&Index=&Titel=&Gesetzesnummer=&VonArtikel=&BisArtikel=&VonParagraf=&BisParagraf=&VonAnlage=&BisAnlage=&Typ=&Kundmachungsnummer=&Unterzeichnungsdatum=&FassungVom=31.05.2026&VonInkrafttretedatum=&BisInkrafttretedatum=&VonAusserkrafttretedatum=&BisAusserkrafttretedatum=&Normabschnittnumme