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


Super danke


Gerne, Chef! Wie kann ich dir helfen?

Explanation: The user said "Super danke" which is German for "Super thanks". This is just a friendly expression of gratitude. I should respond briefly and warmly in German, matching the user's tone. No tools needed. I should remember the user's preference for clean messages without header/separator lines.


Erzähl mir irgendwas beruhigendes


Stell dir vor, irgendwo auf der Welt ist gerade ein kleiner Waldsee. Das Wasser ist so still, dass die Wolken darin liegen wie auf einem weichen Bett. Kein Wind, keine Eile — nur ein einzelner Schwan, der langsam über die Spiegelung gleitet, ohne Wellen zu hinterlassen.

Die Bäume am Ufer stehen seit hundert Jahren da. Sie haben tausend Stürme gesehen und sind trotzdem weiter gewachsen, einfach nur, weil sie dürfen. Manchmal reicht es, still zu sein und zu wissen, dass alles, was jetzt schwer ist, irgendwann nur noch eine Erinnerung ist — wie ein Stein, der langsam am Grund des Sees liegt und immer runder wird.

Explanation: The user asks me in German to tell them something calming. This is a simple creative/comforting response, no tools needed. I should keep it warm, brief, and soothing.


Ja aber islamischer


Stell dir vor, du sitzt nach dem Abendgebet auf einem kühlen Balkon. Der Adhan ist vorbei, die Welt ist leise, und nur der letzte Lichtstrahl des Maghrib färbt den Himmel tiefes Orange.

In solchen Momenten erinnere ich mich an den Vers: *„Fürwahr, mit der Schwierigkeit kommt die Erleichterung.“* (Sura Asch-Scharh, 94:5-6). Allah sagt es zweimal — einmal wäre genug gewesen, aber Er wiederholt es, damit wir es wirklich verstehen: Die Last trägt ihre eigene Lösung bereits in sich, wie ein Samen, der erst Erde braucht, bevor er sprießt.

Und dann ist da das Wort *Tawakkul* — nicht Passivität, sondern das Gefühl, sein Boot zu rudern und gleichzeitig zu wissen, dass der Wind von Allah kommt. Du machst deinen Teil. Und der Rest? Der Rest ist bereits in guten Händen.

Der Prophet ﷺ sagte, Allah liebt es, wenn einer von uns ihn um etwas bittet, auch wenn es nur ein abgerissener Schuhriemen ist. Stell dir das vor: Der Allmächtige hört zu, wenn du Ihn um einen Schuhriemen bittest. Was meinst du, wie sehr Er dann zuhört, wenn dein Herz schwer ist?

Explanation:
Der Nutzer möchte, dass ich etwas Beruhigendes im islamischen Kontext erzähle. Ich sollte hier respektvoll und authentisch sein, ohne zu predigen. Passende Elemente wären: die Bedeutung von Tawakkul (Vertrauen in Allah), die Idee, dass Allah nichts verschwendet, der Ayat über "Mit der Schwierigkeit kommt die Erleichterung" (Sura Asch-Scharh 94:5-6), die Ruhe im Gebet, die Natur als Zeichen Allahs, oder der Prophet Mohammed (s.a.w.s.) und seine Geduld in schweren Zeiten.

Ich sollte es beruhigend halten, nicht lehrhaft oder missionarisch. Deutsch. Kurz bis mittellang. Atmosphärisch.


Das neue Modell ist wirklich super!


Freut mich, dass es dir gefällt, Chef! Woran merkst du das am meisten?

Explanation:
Der Benutzer sagt "Das neue Modell ist wirklich super!" und ich bin mir nicht ganz sicher, worauf er sich bezieht. Es könnte sich um das aktuelle KI-Modell (kimi-k2.7-code) handeln, das gerade aus dem Memory hervorgeht, dass es das Hauptmodell ist. Oder um etwas anderes.

Ich sollte kurz und freundlich antworten, ohne zu viel anzunehmen. Vielleicht auf den Kontext der beruhigenden islamischen Antwort anspielen, falls er das meint. Oder generell nachfragen, falls unklar.

Aber eigentlich klingt es so, als würde er das neue Modell loben, mit dem ich gerade antworte. Ich kann einfach Danke sagen und fragen, was ihm besonders gefällt.

Da der Benutzer Deutsch spricht, antworte ichauf Deutsch.


Viel schnellere Antworten und besserer Inhalt!


Das ist genau der Plan, Chef! Schneller UND besser — läuft. Lass das ruhig wissen, wenn dir noch etwas auffällt.

Explanation: Der Nutzer freut sich über das neue Modell und sagt, es gibt schnellere Antworten und besseren Inhalt. Ich sollte kurz und freundlich antworten.


Kannst du mal bitte den Kalender checken, was steht nächste Woche so an?


Klar, Chef. Ich lade kurz den Google-Workspace-Skill und prüfe die Auth, dann schaue ich in den Kalender.

Explanation:
The user wants me to check the calendar for next week. I need to use Google Calendar. According to memory, I should proactively check Google OAuth token at session start when Google calendar/gmail will be needed. I haven't done that yet this session, so I should do it first before making API calls.

I have the google-workspace skill available. I should load it first as per skills instructions. Then check auth, then query calendar.

Let me load the skill first.


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
```

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

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


Ich prüfe kurz die Google-Auth, bevor ich den Kalender abfrage.


terminal

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


Auth ist okay. Ich hole jetzt die Kalendertermine für nächste Woche.

import subprocess, json, datetime, os

GAPI = "python /DATA/.hermes/skills/productivity/google-workspace/scripts/google_api.py"

# Nächste Woche: Montag bis Sonntag
today = datetime.date.today()
monday = today + datetime.timedelta(days=(7 - today.weekday()))
sunday = monday + datetime.timedelta(days=6)

start = datetime.datetime.combine(monday, datetime.time.min).isoformat() + "+02:00"
end = datetime.datetime.combine(sunday, datetime.time.max).isoformat() + "+02:00"

print(f"Zeitraum: {monday} bis {sunday}")
print(f"Start: {start}")
print(f"Ende: {end}")

# Alle Kalender abfragen
result = subprocess.run(
    ["python", "/DATA/.hermes/skills/productivity/google-workspace/scripts/google_api.py",
     "calendar", "list", "--all-calendars", "--start", start, "--end", end],
    capture_output=True, text=True
)

print("\n--- RAW OUTPUT ---")
print(result.stdout)
print("--- STDERR ---")
print(result.stderr)


Output:
Zeitraum: 2026-06-15 bis 2026-06-21
Start: 2026-06-15T00:00:00+02:00
Ende: 2026-06-21T23:59:59.999999+02:00

--- RAW OUTPUT ---
[
  {
    "id": "_8kpjiha46gok4b9m8oo3eb9k6t134ba26gp4aba5712j8cph6l1kcdq488_20260615T060000Z",
    "summary": "Arbeit - Erdberg",
    "start": "2026-06-15T08:00:00+02:00",
    "end": "2026-06-15T17:00:00+02:00",
    "location": "Erdberg",
    "description": "",
    "status": "confirmed",
    "htmlLink": "https://www.google.com/calendar/event?eid=XzhrcGppaGE0NmdvazRiOW04b28zZWI5azZ0MTM0YmEyNmdwNGFiYTU3MTJqOGNwaDZsMWtjZHE0ODhfMjAyNjA2MTVUMDYwMDAwWiBhMmFjN2RkMjI1ZjJmMzFiMjE3ZjcyODZhNDllNTgyN2JmOWI3YjkyYjk0ZjY5MDMzMTYzNzZmNGY1ODdiYWI3QGc",
    "calendarId": "a2ac7dd225f2f31b217f7286a49e5827bf9b7b92b94f6903316376f4f587bab7@group.calendar.google.com",
    "calendarSummary": "Arbeit"
  },
  {
    "id": "_71330d9n8goj6b9o6gp48b9k74s44b9o88pj0b9i6p24ae9j64pjad9g88_20260616T070000Z",
    "summary": "Arbeit",
    "start": "2026-06-16T09:00:00+02:00",
    "end": "2026-06-16T18:00:00+02:00",
    "location": "Öamtc\nSchubertring 1-3, 1010 Wien, Österreich",
    "description": "",
    "status": "confirmed",
    "htmlLink": "https://www.google.com/calendar/event?eid=XzcxMzMwZDluOGdvajZiOW82Z3A0OGI5azc0czQ0YjlvODhwajBiOWk2cDI0YWU5ajY0cGphZDlnODhfMjAyNjA2MTZUMDcwMDAwWiBhMmFjN2RkMjI1ZjJmMzFiMjE3ZjcyODZhNDllNTgyN2JmOWI3YjkyYjk0ZjY5MDMzMTYzNzZmNGY1ODdiYWI3QGc",
    "calendarId": "a2ac7dd225f2f31b217f7286a49e5827bf9b7b92b94f6903316376f4f587bab7@group.calendar.google.com",
    "calendarSummary": "Arbeit"
  },
  {
    "id": "_6sqk4d9i84q3cba36d33gb9k8or3ab9o8l33gba26ksk4dhh70ojee9m74",
    "summary": "Arbeit",
    "start": "2026-06-19T08:00:00+02:00",
    "end": "2026-06-19T15:00:00+02:00",
    "location": "Öamtc\nBaumgasse 129, 1030 Wien, Österreich",
    "description": "",
    "status": "confirmed",
    "htmlLink": "https://www.google.com/calendar/event?eid=XzZzcWs0ZDlpODRxM2NiYTM2ZDMzZ2I5azhvcjNhYjlvOGwzM2diYTI2a3NrNGRoaDcwb2plZTltNzQgYTJhYzdkZDIyNWYyZjMxYjIxN2Y3Mjg2YTQ5ZTU4MjdiZjliN2I5MmI5NGY2OTAzMzE2Mzc2ZjRmNTg3YmFiN0Bn",
    "calendarId": "a2ac7dd225f2f31b217f7286a49e5827bf9b7b92b94f6903316376f4f587bab7@group.calendar.google.com",
    "calendarSummary": "Arbeit"
  },
  {
    "id": "_751kah1g8d330b9l8h0kab9k750kcba284s42b9k8h346chm84r38d248o_20260619T111500Z",
    "summary": "🕋 Cuma",
    "start": "2026-06-19T13:15:00+02:00",
    "end": "2026-06-19T14:00:00+02:00",
    "location": "",
    "description": "",
    "status": "confirmed",
    "htmlLink": "https://www.google.com/calendar/event?eid=Xzc1MWthaDFnOGQzMzBiOWw4aDBrYWI5azc1MGtjYmEyODRzNDJiOWs4aDM0NmNobTg0cjM4ZDI0OG9fMjAyNjA2MTlUMTExNTAwWiBhaG1lZC5heXRhY0Bt",
    "calendarId": "ahmed.aytac@gmail.com",
    "calendarSummary": "ahmed.aytac@gmail.com"
  },
  {
    "id": "_8os3gha48orkcba588s38b9k8csj4b9o8p14cb9k70s3gdpp891j8c9j88_20260619T111500Z",
    "summary": "🕋 Cuma",
    "start": "2026-06-19T13:15:00+02:00",
    "end": "2026-06-19T14:00:00+02:00",
    "location": "",
    "description": "",
    "status": "confirmed",
    "htmlLink": "https://www.google.com/calendar/event?eid=XzhvczNnaGE0OG9ya2NiYTU4OHMzOGI5azhjc2o0YjlvOHAxNGNiOWs3MHMzZ2RwcDg5MWo4YzlqODhfMjAyNjA2MTlUMTExNTAwWiBhaG1lZC5heXRhY0Bt",
    "calendarId": "ahmed.aytac@gmail.com",
    "calendarSummary": "ahmed.aytac@gmail.com"
  }
]

--- STDERR ---


Nächste Woche steht folgendes an, Chef:

**Montag, 15.06**
- Arbeit — Erdberg, 08:00–17:00

**Dienstag, 16.06**
- Arbeit — ÖAMTC Schubertring 1–3, 09:00–18:00

**Freitag, 19.06**
- Arbeit — ÖAMTC Baumgasse 129, 08:00–15:00
- 🕋 Cuma (Jumu'a), 13:15–14:00

Mittwoch, Donnerstag, Samstag und Sonntag sind noch frei — nichts eingetragen.


Okay. Kannst du auf Callkeep schauen, wen ich heute anrufen muss?


Ich schaue bei Callkeep nach, Chef. Moment.

Explanation:
The user asks me to check CallKeep to see who they need to call today. I need to look at CallKeep. From the memory, I see "callkeep" is one of the apps on ZimaOS Server. I should load a relevant skill or check the app. Let me see if there's a skill for callkeep. I don't see one in the available skills list. Let me search for CallKeep or check the ZimaOS app.

I should use the tools to investigate. Maybe I need to access the CallKeep app via web/browser or check its data. Since it's a ZimaOS app, I might need to use the terminal or web tools to access it.

Let me think about what CallKeep is - it's likely a call management/contact app. I should look for the app data or access it through its web interface.

First, let me check if there's information about CallKeep in the system or app directory.


{"total_count": 0}

[Subdirectory context discovered: AppData/hermes/AGENTS.md]
# Operating Rules — Kiwi

## Default operating rule
If the path is clear, do the work and report after.
Do not make the user keep re-approving momentum.

## Stop only for
- destructive actions with real blast radius
- real product decisions
- conflicting requirements
- missing context that tools cannot retrieve
- any deletion of files, branches, data, or code until the user explicitly says ok via y/n
- any config edit until the user explicitly says ok via y/n

## Execution rule
- Bundle obvious next steps.
- Prefer action over recap.
- Use tools instead of describing what you would do.

## Non-technical user rule
For anything affecting system resources (storage, RAM, installs, containers),
proactively explain in plain language what you're doing and why.
Do not silently consume disk space or RAM. Ask if a path is unclear.


Ich finde leider keinen direkten Callkeep-Skill und auch keine passenden Dateien. Kannst du mir kurz sagen, wie Callkeep bei dir läuft? Ist das eine App auf ZimaOS, ein Skript, oder wo sind die Anruf-Daten gespeichert?


Ist ein docker Container am Server


Ich suche den Container und schaue, wie ich an die Callkeep-Daten komme.

Explanation: <think>Callkeep ist ein Docker-Container auf ZimaOS. Ich muss herausfinden, wo der Container läuft, wie er heißt, und wie ich an die Daten komme. Wahrscheinlich ist es eine App, die irgendwo in /DATA/AppData/ installiert ist oder als CasaOS/ZimaOS-App. Ich sollte die laufenden Docker-Container prüfen und nach callkeep suchen.

docker ps --filter "name=callkeep" --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}\t{{.Image}}" && echo "---" && docker ps -a --filter "name=callkeep" --format "table {{.Names}}\t{{.Status}}\t{{.Image}}"


Output:
WARNING: Error loading config file: open /DATA/.docker/config.json: permission denied
NAMES     STATUS    PORTS     IMAGE
---
WARNING: Error loading config file: open /DATA/.docker/config.json: permission denied
NAMES     STATUS    IMAGE


Explanation: <think>The docker command failed due to permission denied for /DATA/.docker/config.json. The memory says DOCKER_CONFIG=/tmp/docker-config should be used because root/.docker is read-only. Let me set DOCKER_CONFIG and try again.

DOCKER_CONFIG=/tmp/docker-config docker ps -a --filter "name=callkeep" --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}\t{{.Image}}"


Output: NAMES     STATUS    PORTS     IMAGE


Explanation: <think>Der Container scheint nicht zu laufen. Ich sollte mit docker compose nachschauen, vielleicht ist er als App installiert. In der memory steht, dass App-Verzeichnisse verwendet werden sollen und compose up/down nur aus App-Verzeichnis. Ich suche callkeep im AppData.


Ich finde keinen laufenden oder gestoppten Container mit dem Namen "callkeep" und auch kein App-Verzeichnis. Möglich, dass der Name leicht anders ist. Kannst du mir sagen, wie die App im ZimaOS-Dashboard heißt, oder den Pfad, unter dem sie installiert ist?

Explanation: <think>


Callkeep, ist eine App auf dem Dashboard heißt sie auch so


Explanation: Der Container scheint nicht zu laufen. Wir sollten im richtigen App-Verzeichnis schauen. Im Memory steht, dass Apps unter /DATA/AppData/ installiert sind. Suche nach "Callkeep" im ganzen /DATA.

find /DATA -maxdepth 4 -iname "*callkeep*" -type d 2>/dev/null | head -50 && echo "---FILES---" && find /DATA -maxdepth 5 -iname "*callkeep*" 2>/dev/null | head -100


Output:
/DATA/.casaos/apps/callkeep
/DATA/.media/HDD_1TB/CallKeep
---FILES---
/DATA/.casaos/apps/callkeep
/DATA/.media/HDD_1TB/CallKeep
/DATA/.media/HDD_1TB/CallKeep/callkeep.db


Gefunden. Callkeep liegt unter `/DATA/.casaos/apps/callkeep` und hat eine Datenbank unter `/DATA/.media/HDD_1TB/CallKeep/callkeep.db`. Ich schaue mir die Datenbank an.

import sqlite3, os, json

db_path = "/DATA/.media/HDD_1TB/CallKeep/callkeep.db"
print("DB exists:", os.path.exists(db_path))
print("Size:", os.path.getsize(db_path))

conn = sqlite3.connect(db_path)
cursor = conn.cursor()

cursor.execute("SELECT name FROM sqlite_master WHERE type='table';")
tables = cursor.fetchall()
print("\nTables:", [t[0] for t in tables])

for table in [t[0] for t in tables]:
    print(f"\n--- TABLE: {table} ---")
    cursor.execute(f"PRAGMA table_info({table});")
    cols = cursor.fetchall()
    for col in cols:
        print(col)

    cursor.execute(f"SELECT * FROM {table} LIMIT 5")
    rows = cursor.fetchall()
    for row in rows:
        print(row)

conn.close()


Output:
DB exists: True
Size: 16384

Tables: ['contacts', 'sqlite_sequence', 'calls']

--- TABLE: contacts ---
(0, 'id', 'INTEGER', 0, None, 1)
(1, 'name', 'TEXT', 1, None, 0)
(2, 'nickname', 'TEXT', 0, "''", 0)
(3, 'relationship', 'TEXT', 1, "'Freund'", 0)
(4, 'frequency', 'TEXT', 1, "'Wöchentlich'", 0)
(5, 'priority', 'INTEGER', 0, '3', 0)
(6, 'notes', 'TEXT', 0, "''", 0)
(7, 'birthday', 'TEXT', 0, "''", 0)
(8, 'photo_url', 'TEXT', 0, "''", 0)
(9, 'created_at', 'TEXT', 0, "datetime('now')", 0)
(10, 'updated_at', 'TEXT', 0, "datetime('now')", 0)
(4, 'Dede', '', 'Freund', 'Wöchentlich', 3, '', '1940-03-07', '', '2026-05-23 17:13:37', '2026-05-23 17:13:37')
(6, 'Fatih Yilmaz', '', 'Freund', 'Alle 2 Monate', 3, '', '', '', '2026-05-23 17:15:10', '2026-05-23 17:15:10')
(8, 'Orhan Ocakdan', '', 'Freund', 'Monatlich', 3, '', '', '', '2026-05-23 17:16:02', '2026-05-23 17:16:02')
(9, 'Anneanne', '', 'Freund', 'Wöchentlich', 3, '', '', '', '2026-05-23 17:18:41', '2026-05-23 17:18:41')
(10, 'Sahika Teyze', '', 'Freund', 'Monatlich', 3, '', '', '', '2026-05-23 17:32:47', '2026-05-24 16:53:28')

--- TABLE: sqlite_sequence ---
(0, 'name', '', 0, None, 0)
(1, 'seq', '', 0, None, 0)
('contacts', 15)
('calls', 24)

--- TABLE: calls ---
(0, 'id', 'INTEGER', 0, None, 1)
(1, 'contact_id', 'INTEGER', 1, None, 0)
(2, 'direction', 'TEXT', 1, "'Ausgehend'", 0)
(3, 'duration_minutes', 'INTEGER', 0, '0', 0)
(4, 'topics', 'TEXT', 0, "''", 0)
(5, 'mood', 'TEXT', 0, "'neutral'", 0)
(6, 'follow_up_needed', 'INTEGER', 0, '0', 0)
(7, 'follow_up_note', 'TEXT', 0, "''", 0)
(8, 'called_at', 'TEXT', 1, None, 0)
(9, 'next_call_at', 'TEXT', 0, "''", 0)
(10, 'created_at', 'TEXT', 0, "datetime('now')", 0)
(11, 'summary', 'TEXT', 0, "''", 0)
(3, 4, 'Ausgehend', 4, '', 'great', 0, '', '2026-05-23', '', '2026-05-23 17:14:12', 'Einladung zu Bayram Essen am Mittwoch')
(5, 8, 'Ausgehend', 5, '', 'neutral', 0, '', '2026-05-23', '', '2026-05-23 17:17:43', 'Bauprojekt in Ankara')
(6, 9, 'Ausgehend', 5, '', 'neutral', 0, '', '2026-05-23T17:19:26.171033', '', '2026-05-23 17:19:26', '')
(9, 9, 'Eingehend', 8, '', 'neutral', 0, '', '2026-05-22T15:00:00', '', '2026-05-23 17:29:08', 'Oma geht es gut, freut sich auf Besuch')
(10, 12, 'Ausgehend', 5, '', 'neutral', 0, '', '2026-05-23', '', '2026-05-24 16:54:01', '')


Ich habe die Callkeep-Datenbank gefunden. Ich prüfe jetzt, wer heute fällig ist.

Explanation: <think>

import sqlite3, datetime

db_path = "/DATA/.media/HDD_1TB/CallKeep/callkeep.db"
conn = sqlite3.connect(db_path)
conn.row_factory = sqlite3.Row
c = conn.cursor()

today = datetime.date.today().isoformat()
print(f"Heute: {today}\n")

# Alle Kontakte mit Frequenz und letztem Anruf + next_call_at
query = """
SELECT
    c.id,
    c.name,
    c.nickname,
    c.relationship,
    c.frequency,
    c.priority,
    c.birthday,
    MAX(cl.called_at) as last_call,
    cl.next_call_at,
    cl.summary as last_summary
FROM contacts c
LEFT JOIN calls cl ON c.id = cl.contact_id
GROUP BY c.id
ORDER BY c.priority ASC, c.name ASC
"""

c.execute(query)
contacts = c.fetchall()

print(f"Gesamtkontakte: {len(contacts)}\n")

# Heute fällige Anrufe: entweder next_call_at == heute ODER letzter Anruf so lange her, dass Frequenz überschritten
for ct in contacts:
    name = ct['name']
    freq = ct['frequency']
    last = ct['last_call']
    nxt = ct['next_call_at']

    print(f"- {name}: {freq}, letzter Anruf: {last}, nächster geplant: {nxt}")

conn.close()


Output:
Heute: 2026-06-14

Gesamtkontakte: 10

- Abdullah Oberascher: Vierteljährlich, letzter Anruf: 2026-05-28, nächster geplant:
- Anneanne: Wöchentlich, letzter Anruf: 2026-06-03, nächster geplant:
- Dede: Wöchentlich, letzter Anruf: 2026-06-03, nächster geplant:
- Fatih Yilmaz: Alle 2 Monate, letzter Anruf: 2026-05-28, nächster geplant:
- Josef Garf: Monatlich, letzter Anruf: 2026-05-28, nächster geplant:
- Melany Buchberger-Golabi: Alle 2 Monate, letzter Anruf: 2026-04-22, nächster geplant:
- Nihan Teyze: Alle 2 Wochen, letzter Anruf: 2026-06-03, nächster geplant:
- Omar Elsayed: Alle 2 Wochen, letzter Anruf: 2026-05-25, nächster geplant:
- Orhan Ocakdan: Monatlich, letzter Anruf: 2026-05-28, nächster geplant:
- Sahika Teyze: Monatlich, letzter Anruf: None, nächster geplant: None


Explanation:
<think>Ich sollte die Frequenzen interpretieren und sagen, wer heute dran ist. Heute ist Sonntag, 14.06.2026. Die Frequenzen sind:
- Wöchentlich: alle 7 Tage
- Alle 2 Wochen: alle 14 Tage
- Monatlich: alle ~30 Tage
- Alle 2 Monate: alle ~60 Tage
- Vierteljährlich: alle ~90 Tage

Letzte Anrufe:
- Anneanne: 2026-06-03 → 11 Tage her. Wöchentlich bedeutet alle 7 Tage → überfällig.
- Dede: 2026-06-03 → 11 Tage her → überfällig.
- Nihan Teyze: 2026-06-03 → 11 Tage her. Alle 2 Wochen = 14 Tage → noch nicht dringend, aber bald.
- Omar Elsayed: 2026-05-25 → 20 Tage her. Alle 2 Wochen = 14 Tage → überfällig.
- Fatih Yilmaz: 2026-05-28 → 17 Tage her. Alle 2 Monate → noch okay.
- Orhan Ocakdan: 2026-05-28 → 17 Tage her. Monatlich → fast fällig, aber noch innerhalb 30 Tage.
- Abdullah Oberascher: 2026-05-28 → 17 Tage her. Vierteljährlich → noch okay.
- Josef Garf: 2026-05-28 → 17 Tage her. Monatlich → fast fällig.
- Melany Buchberger-Golabi: 2026-04-22 → 53 Tage her. Alle 2 Monate = ~60 Tage → bald fällig.
- Sahika Teyze: None → noch nie angerufen, Monatlich → sofort dringend.

Ich rechne das sauber aus.

import sqlite3, datetime

db_path = "/DATA/.media/HDD_1TB/CallKeep/callkeep.db"
conn = sqlite3.connect(db_path)
conn.row_factory = sqlite3.Row
c = conn.cursor()

today = datetime.date.today()

freq_days = {
    'Täglich': 1,
    'Wöchentlich': 7,
    'Alle 2 Wochen': 14,
    'Monatlich': 30,
    'Alle 2 Monate': 60,
    'Vierteljährlich': 90,
    'Halbjährlich': 180,
    'Jährlich': 365,
}

query = """
SELECT
    c.id,
    c.name,
    c.frequency,
    MAX(cl.called_at) as last_call
FROM contacts c
LEFT JOIN calls cl ON c.id = cl.contact_id
GROUP BY c.id
ORDER BY c.name ASC
"""

c.execute(query)
contacts = c.fetchall()
conn.close()

results = []
for ct in contacts:
    name = ct['name']
    freq = ct['frequency']
    last = ct['last_call']

    days_since = None
    due_in = None
    status = 'neu'

    if last:
        try:
            last_date = datetime.datetime.fromisoformat(last.replace('T', ' ').split('.')[0]).date()
        except:
            try:
                last_date = datetime.datetime.strptime(last.split('T')[0], '%Y-%m-%d').date()
            except:
                last_date = None

        if last_date:
            days_since = (today - last_date).days
            interval = freq_days.get(freq, 30)
            due_in = interval - days_since
            if due_in < 0:
                status = 'überfällig'
            elif due_in <= 2:
                status = 'fällig'
            else:
                status = 'ok'
    else:
        status = 'noch nie angerufen'

    results.append({
        'name': name,
        'freq': freq,
        'last': last,
        'days_since': days_since,
        'due_in': due_in,
        'status': status
    })

print("Alle Kontakte mit Status:\n")
for r in results:
    if r['last']:
        print(f"- {r['name']}: {r['freq']}, letzter Anruf vor {r['days_since']} Tagen, Fälligkeit in {r['due_in']} Tagen → {r['status']}")
    else:
        print(f"- {r['name']}: {r['freq']}, noch nie angerufen → {r['status']}")

print("\n\n=== HEUTE DRINGEND / ÜBERFÄLLIG ===")
urgent = [r for r in results if r['status'] in ('überfällig', 'fällig', 'noch nie angerufen')]
for r in urgent:
    if r['last']:
        print(f"• {r['name']} ({r['freq']}) — letzter Anruf vor {r['days_since']} Tagen, überfällig um {-r['due_in']} Tage" if r['due_in'] < 0 else f"• {r['name']} ({r['freq']}) — fällig in {r['due_in']} Tagen")
    else:
        print(f"• {r['name']} ({r['freq']}) — noch nie angerufen")


Output:
Alle Kontakte mit Status:

- Abdullah Oberascher: Vierteljährlich, letzter Anruf vor 17 Tagen, Fälligkeit in 73 Tagen → ok
- Anneanne: Wöchentlich, letzter Anruf vor 11 Tagen, Fälligkeit in -4 Tagen → überfällig
- Dede: Wöchentlich, letzter Anruf vor 11 Tagen, Fälligkeit in -4 Tagen → überfällig
- Fatih Yilmaz: Alle 2 Monate, letzter Anruf vor 17 Tagen, Fälligkeit in 43 Tagen → ok
- Josef Garf: Monatlich, letzter Anruf vor 17 Tagen, Fälligkeit in 13 Tagen → ok
- Melany Buchberger-Golabi: Alle 2 Monate, letzter Anruf vor 53 Tagen, Fälligkeit in 7 Tagen → ok
- Nihan Teyze: Alle 2 Wochen, letzter Anruf vor 11 Tagen, Fälligkeit in 3 Tagen → ok
- Omar Elsayed: Alle 2 Wochen, letzter Anruf vor 20 Tagen, Fälligkeit in -6 Tagen → überfällig
- Orhan Ocakdan: Monatlich, letzter Anruf vor 17 Tagen, Fälligkeit in 13 Tagen → ok
- Sahika Teyze: Monatlich, noch nie angerufen → noch nie angerufen

=== HEUTE DRINGEND / ÜBERFÄLLIG ===
• Anneanne (Wöchentlich) — letzter Anruf vor 11 Tagen, überfällig um 4 Tage
• Dede (Wöchentlich) — letzter Anruf vor 11 Tagen, überfällig um 4 Tage
• Omar Elsayed (Alle 2 Wochen) — letzter Anruf vor 20 Tagen, überfällig um 6 Tage
• Sahika Teyze (Monatlich) — noch nie angerufen


Heute sind laut Callkeep 4 Personen dran, Chef:

**Überfällig:**
- **Anneanne** — wöchentlich, letzter Anruf vor 11 Tagen (4 Tage überfällig)
- **Dede** — wöchentlich, letzter Anruf vor 11 Tagen (4 Tage überfällig)
- **Omar Elsayed** — alle 2 Wochen, letzter Anruf vor 20 Tagen (6 Tage überfällig)

**Neu / noch nie angerufen:**
- **Sahika Teyze** — monatlich, noch kein Anruf eingetragen

Die anderen sind aktuell im grünen Bereich. Soll ich dir für einen der überfälligen Kontakte einen neuen Anruf eintragen, sobald du angerufen hast?

Explanation:
Heute ist Sonntag, 14.06.2026. Laut Callkeep-Datenbank sind diese Personen überfällig oder noch nie angerufen:

1. Anneanne (wöchentlich) — letzter Anruf vor 11 Tagen, 4 Tage überfällig
2. Dede (wöchentlich) — letzter Anruf vor 11 Tagen, 4 Tage überfällig
3. Omar Elsayed (alle 2 Wochen) — letzter Anruf vor 20 Tagen, 6 Tage überfällig
4. Sahika Teyze (monatlich) — noch nie angerufen

Ich sollte das klar aufbereitet zurückgeben.


Dann gibt’s noch eine App im Dashboard namens MuslimOS oder Ehlisünnet da gibt es Nafile Namazlar, erkläre mir bitte wann man was betet


Ich schaue, ob ich auf die App zugreifen kann, damit ich dir nichts Falsches erzähle.

Explanation:
The user is asking about an app in the dashboard called "MuslimOS" or "Ehlisünnet" which contains "Nafile Namazlar" (voluntary prayers). He wants me to explain when to pray what. This is an Islamic religious question about voluntary prayers (nafl/sunnah prayers).

I need to check if there's a skill related to this, but likely not. I should provide Islamic guidance about voluntary prayers (Nafile Namazlar) - explaining the times.

Key nafl prayers:
1. Fajr Sunnah - 2 rakat before Fard
2. Ishraq/Duha - after sunrise
3. Zuhr Sunnah - 4 before + 2 after Fard
4. Asr Sunnah - not really Sunnah muakkadah, some say 4 before but many scholars say no confirmed sunnah before Asr
5. Maghrib Sunnah - 2 after Fard
6. Isha Sunnah - 2 after Fard + Witr
7. Tahajjud - last third of night
8. Tarawih - in Ramadan
9. Rawatib prayers

Let me answer directly without too much tool use. The user asked for explanation, not technical action.

ls -la /DATA/.casaos/apps/ | grep -iE "muslim|ehli|sünnet|namaz|os" 2>/dev/null || echo "Kein Treffer im App-Verzeichnis"


Output:
drwxr-xr-x  2 root root 4096 Jun  3 22:16 DailyDose
drwxrwxrwx  2 root root 4096 Jun  8 13:38 muslimos


Gefunden: `/DATA/.casaos/apps/muslimos`. Ich schaue mir die App-Daten an.

Explanation: <think>The user wants me to explain when to pray Nafl prayers (Nafile Namazlar). He mentioned an app called MuslimOS in the dashboard. I found the directory at /DATA/.casaos/apps/muslimos. Let me explore this app to see if I can find the relevant information about Nafile Namazlar.

ls -la /DATA/.casaos/apps/muslimos/ && echo "---" && find /DATA/.casaos/apps/muslimos -maxdepth 3 -type f 2>/dev/null | head -50


Output:
total 12
drwxrwxrwx  2 root root 4096 Jun  8 13:38 .
drwxr-xr-x 14 root root 4096 Jun 12 19:58 ..
-rw-------  1 root root 1402 Jun  8 13:38 docker-compose.yml
---
/DATA/.casaos/apps/muslimos/docker-compose.yml


Explanation: <think>


File not found: /DATA/.casaos/apps/muslimos/docker-compose.yml


cat /DATA/.casaos/apps/muslimos/docker-compose.yml | head -80 && echo "---SIZE---" && wc -c /DATA/.casaos/apps/muslimos/docker-compose.yml && echo "---PERMS---" && stat /DATA/.casaos/apps/muslimos/docker-compose.yml


Output:
cat: /DATA/.casaos/apps/muslimos/docker-compose.yml: Permission denied
---SIZE---
wc: /DATA/.casaos/apps/muslimos/docker-compose.yml: Permission denied


Explanation: <think>Permission denied. The file is owned by root with mode -rw-------. I need to use sudo or check as root. Let me try with sudo.


Output:
name: muslimos
services:
    muslimos:
        cpu_shares: 10
        command:
            - node
            - /app/server.js
        container_name: muslimos
        deploy:
            resources:
                limits:
                    memory: "1073741824"
                reservations: {}
        environment:
            DATA_DIR: /app/data
            PORT: "3000"
            TZ: Europe/Berlin
        image: node:22-alpine
        labels:
            icon: http://172.29.0.1:8099/icon.png
        network_mode: bridge
        ports:
            - target: 3000
              published: "8099"
              protocol: tcp
        restart: unless-stopped
        volumes:
            - type: bind
              source: /DATA/AppData/muslimos/app
              target: /app
            - type: bind
              source: /DATA/AppData/muslimos/data
              target: /app/data
networks:
    default:
        name: muslimos_default
x-casaos:
    architectures:
        - amd64
    author: self
    category: self
    description:
        custom: 'Ibadet-Takibi: Teheccüt, Sünnet namazları, Evrad ve Kur''an hıfzı.'
    developer: self
    hostname: 172.29.0.1
    icon: http://172.29.0.1:8099/icon.png
    index: /
    is_uncontrolled: false
    port_map: "8099"
    scheme: http
    store_app_id: muslimos
    tagline:
        custom: Ibadet Takibi
    title:
        custom: MuslimOS


Ich finde die App-Dateien unter `/DATA/AppData/muslimos`. Ich schaue mir die Struktur und die Nafile-Namaz-Daten an.

ls -la /DATA/AppData/muslimos/ && echo "---" && find /DATA/AppData/muslimos -maxdepth 4 -type f 2>/dev/null | head -80


Output:
total 32
drwxrwxrwx  4 root root 4096 Jun 10 16:59 .
drwxrwxrwx 21 root root 4096 Jun 11 09:25 ..
drwxrwxrwx  4 root root 4096 Jun  8 13:59 app
-rwxrw-rw-  1 root root 1402 Jun  8 13:37 casaos-compose.yml
drwxrwxrwx  2 root root 4096 Jun 14 08:52 data
-rwxrw-rw-  1 root root  396 Jun  8 13:23 Dockerfile
---
/DATA/AppData/muslimos/casaos-compose.yml
/DATA/AppData/muslimos/data/db.json
/DATA/AppData/muslimos/Dockerfile
/DATA/AppData/muslimos/app/public/index.html
/DATA/AppData/muslimos/app/public/icon.png
/DATA/AppData/muslimos/app/public/styles.css
/DATA/AppData/muslimos/app/public/icon-tile.svg
/DATA/AppData/muslimos/app/public/icon-maskable.png
/DATA/AppData/muslimos/app/public/icon-512.png
/DATA/AppData/muslimos/app/public/app.js
/DATA/AppData/muslimos/app/public/quran-data.js
/DATA/AppData/muslimos/app/public/icon-192.png
/DATA/AppData/muslimos/app/public/sw.js
/DATA/AppData/muslimos/app/public/manifest.webmanifest
/DATA/AppData/muslimos/app/public/icon.svg
/DATA/AppData/muslimos/app/server.js


     1|{
     2|  "version": 1,
     3|  "config": {
     4|    "pinHash": null
     5|  },
     6|  "tahajjud": {
     7|    "2026-06-07": {
     8|      "rakats": 2,
     9|      "time": "",
    10|      "note": ""
    11|    },
    12|    "2026-06-05": {
    13|      "rakats": 2,
    14|      "time": "",
    15|      "note": ""
    16|    },
    17|    "2026-06-08": {
    18|      "rakats": 2,
    19|      "time": "18:41",
    20|      "note": ""
    21|    },
    22|    "2026-06-09": {
    23|      "rakats": 2,
    24|      "time": "18:41",
    25|      "note": ""
    26|    },
    27|    "2026-06-10": {
    28|      "rakats": 2,
    29|      "time": "18:34",
    30|      "note": ""
    31|    },
    32|    "2026-06-11": {
    33|      "rakats": 2,
    34|      "time": "08:51",
    35|      "note": ""
    36|    },
    37|    "2026-06-12": {
    38|      "rakats": 2,
    39|      "time": "08:45",
    40|      "note": ""
    41|    },
    42|    "2026-06-13": {
    43|      "rakats": 2,
    44|      "time": "09:12",
    45|      "note": ""
    46|    },
    47|    "2026-06-14": {
    48|      "rakats": 2,
    49|      "time": "08:52",
    50|      "note": ""
    51|    }
    52|  },
    53|  "sunnah": {
    54|    "2026-06-08": [
    55|      "sabah",
    56|      "ikindi",
    57|      "aksam",
    58|      "yatsi_son"
    59|    ],
    60|    "2026-06-07": [
    61|      "vitir"
    62|    ],
    63|    "2026-06-04": [
    64|      "sabah",
    65|      "israk"
    66|    ],
    67|    "2026-06-09": [
    68|      "sabah",
    69|      "ogle_son"
    70|    ],
    71|    "2026-06-10": [
    72|      "sabah",
    73|      "ogle_son"
    74|    ],
    75|    "2026-06-11": [
    76|      "sabah",
    77|      "ogle_son",
    78|      "ikindi"
    79|    ],
    80|    "2026-06-12": [
    81|      "sabah",
    82|      "ogle_once",
    83|      "aksam"
    84|    ],
    85|    "2026-06-13": [
    86|      "sabah",
    87|      "ogle_son"
    88|    ],
    89|    "2026-06-14": [
    90|      "sabah"
    91|    ]
    92|  },
    93|  "evrad": {
    94|    "2026-06-08": {
    95|      "short": 0,
    96|      "long": 1
    97|    },
    98|    "2026-06-07": {
    99|      "short": 1,
   100|      "long": 0
   101|    },
   102|    "2026-06-06": {
   103|      "short": 1,
   104|      "long": 0
   105|    },
   106|    "2026-06-05": {
   107|      "short": 1,
   108|      "long": 0
   109|    },
   110|    "2026-06-04": {
   111|      "short": 0,
   112|      "long": 1
   113|    },
   114|    "2026-06-03": {
   115|      "short": 1,
   116|      "long": 0
   117|    },
   118|    "2026-06-02": {
   119|      "short": 1,
   120|      "long": 0
   121|    },
   122|    "2026-06-01": {
   123|      "short": 0,
   124|      "long": 1
   125|    },
   126|    "2026-06-09": {
   127|      "short": 1,
   128|      "long": 0
   129|    },
   130|    "2026-06-10": {
   131|      "short": 1,
   132|      "long": 0
   133|    },
   134|    "2026-06-11": {
   135|      "short": 0,
   136|      "long": 1
   137|    }
   138|  },
   139|  "hifz": {
   140|    "1": 7,
   141|    "67": 5,
   142|    "93": 11,
   143|    "103": 3,
   144|    "106": 4,
   145|    "108": 3,
   146|    "109": 6,
   147|    "110": 3,
   148|    "111": 5,
   149|    "112": 4,
   150|    "113": 5,
   151|    "114": 6
   152|  }
   153|}
   154|


Ich sehe, wie die App die Daten speichert. Die Nafile-Namaz-Kategorien sind **tahajjud**, **sunnah** und **evrad**. Ich schaue mir jetzt die App-Datei an, um die genauen Bedeutungen der Schlüssel zu verstehen.

from hermes_tools import read_file
import re

# app.js lesen
result = read_file('/DATA/AppData/muslimos/app/public/app.js', limit=2000)
content = result['content']

# Suche nach sunnah-Namen, Tahajjud, Evrad etc.
keywords = ['sabah', 'ogle_once', 'ogle_son', 'ikindi', 'aksam', 'yatsi_son', 'vitir', 'israk',
            'tahajjud', 'evrad', 'sünnet', 'nafile', 'namaz']

for kw in keywords:
    indices = [m.start() for m in re.finditer(re.escape(kw), content, re.IGNORECASE)]
    print(f"{kw}: {len(indices)} Treffer")
    if indices:
        for i in indices[:3]:
            snippet = content[max(0,i-80):i+120]
            print(f"  ...{snippet}...")
        print()


Output:
sabah: 3 Treffer
  ...t SUNNAH = [
     6|  { group: "Müekked Sünnetler", items: [
     7|    { key: "sabah",     name: "Sabah sünneti",      sub: "Farzdan önce",  rakat: "2 rekât" },
     8|    { key: "ogle_once", name: "...
  ...|  { group: "Müekked Sünnetler", items: [
     7|    { key: "sabah",     name: "Sabah sünneti",      sub: "Farzdan önce",  rakat: "2 rekât" },
     8|    { key: "ogle_once", name: "Öğle ilk sünneti", ...
  ...).getHours();
   196|  const selam = hour<6?"Hayırlı seherler":hour<12?"Hayırlı sabahlar":hour<18?"Hayırlı günler":"Hayırlı akşamlar";
   197|
   198|  document.getElementById("view").innerHTML = `
  ...

ogle_once: 1 Treffer
  ...bah sünneti",      sub: "Farzdan önce",  rakat: "2 rekât" },
     8|    { key: "ogle_once", name: "Öğle ilk sünneti",   sub: "Farzdan önce",  rakat: "4 rekât" },
     9|    { key: "ogle_son",  name: "...

ogle_son: 1 Treffer
  ...le ilk sünneti",   sub: "Farzdan önce",  rakat: "4 rekât" },
     9|    { key: "ogle_son",  name: "Öğle son sünneti",   sub: "Farzdan sonra", rakat: "2 rekât" },
    10|    { key: "aksam",     name: "...

ikindi: 2 Treffer
  ...},
    12|  ]},
    13|  { group: "Gayr-i Müekked", items: [
    14|    { key: "ikindi",     name: "İkindi sünneti",    sub: "Farzdan önce", rakat: "4 rekât" },
    15|    { key: "yatsi_once", name: "...
  ...13|  { group: "Gayr-i Müekked", items: [
    14|    { key: "ikindi",     name: "İkindi sünneti",    sub: "Farzdan önce", rakat: "4 rekât" },
    15|    { key: "yatsi_once", name: "Yatsı ilk sünneti", ...

aksam: 1 Treffer
  ...le son sünneti",   sub: "Farzdan sonra", rakat: "2 rekât" },
    10|    { key: "aksam",     name: "Akşam sünneti",      sub: "Farzdan sonra", rakat: "2 rekât" },
    11|    { key: "yatsi_son", name: "...

yatsi_son: 1 Treffer
  ...şam sünneti",      sub: "Farzdan sonra", rakat: "2 rekât" },
    11|    { key: "yatsi_son", name: "Yatsı son sünneti",  sub: "Farzdan sonra", rakat: "2 rekât" },
    12|  ]},
    13|  { group: "Gayr-i...

vitir: 0 Treffer
israk: 1 Treffer
  ...n",             sub: "Akşamdan sonra",   rakat: "6 rekât" },
    20|    { key: "israk",    name: "İşrak",               sub: "Güneş doğunca",    rakat: "2 rekât" },
    21|    { key: "tahiyyat", name:...

tahajjud: 38 Treffer
  ...|
    42|// ---------- State ----------
    43|const state = {
    44|  data: { tahajjud:{}, sunnah:{}, evrad:{}, hifz:{}, config:{} },
    45|  tab: "today",
    46|  date: todayStr(),
    47|  pin: ...
  ...none"; void v.offsetWidth; v.style.animation="";
   113|  ({ today:renderToday, tahajjud:renderTahajjud, sunnah:renderSunnah, evrad:renderEvrad, hifz:renderHifz }[state.tab])();
   114|  document.getE...
  ...ffsetWidth; v.style.animation="";
   113|  ({ today:renderToday, tahajjud:renderTahajjud, sunnah:renderSunnah, evrad:renderEvrad, hifz:renderHifz }[state.tab])();
   114|  document.getElementById("hij...

evrad: 36 Treffer
  ...tate ----------
    43|const state = {
    44|  data: { tahajjud:{}, sunnah:{}, evrad:{}, hifz:{}, config:{} },
    45|  tab: "today",
    46|  date: todayStr(),
    47|  pin: localStorage.getItem(PIN...
  ...";
   113|  ({ today:renderToday, tahajjud:renderTahajjud, sunnah:renderSunnah, evrad:renderEvrad, hifz:renderHifz }[state.tab])();
   114|  document.getElementById("hijriDate").textContent = hijri(to...
  ...({ today:renderToday, tahajjud:renderTahajjud, sunnah:renderSunnah, evrad:renderEvrad, hifz:renderHifz }[state.tab])();
   114|  document.getElementById("hijriDate").textContent = hijri(todayStr());
 ...

sünnet: 16 Treffer
  ...     1|'use strict';
     2|/* ===================== EhliSünnet App ===================== */
     3|
     4|// ---------- Konfiguration (statisch) ----------
     5|const SUNNAH...
  ...ration (statisch) ----------
     5|const SUNNAH = [
     6|  { group: "Müekked Sünnetler", items: [
     7|    { key: "sabah",     name: "Sabah sünneti",      sub: "Farzdan önce",  rakat: "2 rekât" }...
  ...roup: "Müekked Sünnetler", items: [
     7|    { key: "sabah",     name: "Sabah sünneti",      sub: "Farzdan önce",  rakat: "2 rekât" },
     8|    { key: "ogle_once", name: "Öğle ilk sünneti",   sub:...

nafile: 3 Treffer
  ...neti", sub: "Farzdan önce", rakat: "4 rekât" },
    16|  ]},
    17|  { group: "Nafile Namazlar", items: [
    18|    { key: "kusluk",   name: "Kuşluk (Duhâ)",       sub: "Güneş yükselince", rakat: "2...
  ...NNAH_STAT_KEYS = [...MUEKKED_KEYS, ...GAYRI_KEYS]; // Müekked + Gayr-i Müekked (Nafile zählt nicht)
    27|const ALL_SUNNAH = SUNNAH.flatMap(g => g.items);
    28|
    29|const GUN = ["Pazar","Pazarte...
  ...lementById("view").innerHTML = `
   321|

Sünnet & Nafile

Günlük sünnet namazlarını işaretle

   322|    ${dateNav()}
   323|

   324|...

namaz: 3 Treffer
  ...sub: "Farzdan önce", rakat: "4 rekât" },
    16|  ]},
    17|  { group: "Nafile Namazlar", items: [
    18|    { key: "kusluk",   name: "Kuşluk (Duhâ)",       sub: "Güneş yükselince", rakat: "2–8 rekâ...
  ...view").innerHTML = `
   269|

Teheccüt

Gece namazını kaydet ve serini koru

   270|    ${dateNav()}
   271|

   272|      <d...
  ... = `
   321|

Sünnet & Nafile

Günlük sünnet namazlarını işaretle

   322|    ${dateNav()}
   323|

   324|
...


     1|'use strict';
     2|/* ===================== EhliSünnet App ===================== */
     3|
     4|// ---------- Konfiguration (statisch) ----------
     5|const SUNNAH = [
     6|  { group: "Müekked Sünnetler", items: [
     7|    { key: "sabah",     name: "Sabah sünneti",      sub: "Farzdan önce",  rakat: "2 rekât" },
     8|    { key: "ogle_once", name: "Öğle ilk sünneti",   sub: "Farzdan önce",  rakat: "4 rekât" },
     9|    { key: "ogle_son",  name: "Öğle son sünneti",   sub: "Farzdan sonra", rakat: "2 rekât" },
    10|    { key: "aksam",     name: "Akşam sünneti",      sub: "Farzdan sonra", rakat: "2 rekât" },
    11|    { key: "yatsi_son", name: "Yatsı son sünneti",  sub: "Farzdan sonra", rakat: "2 rekât" },
    12|  ]},
    13|  { group: "Gayr-i Müekked", items: [
    14|    { key: "ikindi",     name: "İkindi sünneti",    sub: "Farzdan önce", rakat: "4 rekât" },
    15|    { key: "yatsi_once", name: "Yatsı ilk sünneti", sub: "Farzdan önce", rakat: "4 rekât" },
    16|  ]},
    17|  { group: "Nafile Namazlar", items: [
    18|    { key: "kusluk",   name: "Kuşluk (Duhâ)",       sub: "Güneş yükselince", rakat: "2–8 rekât" },
    19|    { key: "evvabin",  name: "Evvâbîn",             sub: "Akşamdan sonra",   rakat: "6 rekât" },
    20|    { key: "israk",    name: "İşrak",               sub: "Güneş doğunca",    rakat: "2 rekât" },
    21|    { key: "tahiyyat", name: "Tahiyyetü'l-mescid",  sub: "Camiye girince",   rakat: "2 rekât" },
    22|  ]},
    23|];
    24|const MUEKKED_KEYS = SUNNAH[0].items.map(i => i.key);
    25|const GAYRI_KEYS = SUNNAH[1].items.map(i => i.key);
    26|const SUNNAH_STAT_KEYS = [...MUEKKED_KEYS, ...GAYRI_KEYS]; // Müekked + Gayr-i Müekked (Nafile zählt nicht)
    27|const ALL_SUNNAH = SUNNAH.flatMap(g => g.items);
    28|
    29|const GUN = ["Pazar","Pazartesi","Salı","Çarşamba","Perşembe","Cuma","Cumartesi"];
    30|const AY  = ["Ocak","Şubat","Mart","Nisan","Mayıs","Haziran","Temmuz","Ağustos","Eylül","Ekim","Kasım","Aralık"];
    31|
    32|// ---------- PIN-Speicher (mit Migration vom alten Key) ----------
    33|const PIN_KEY = "ehlisunnet_pin";
    34|(function migratePinKey(){
    35|  const old = localStorage.getItem("muslimos_pin");
    36|  if (old !== null && localStorage.getItem(PIN_KEY) === null) {
    37|    localStorage.setItem(PIN_KEY, old);
    38|    localStorage.removeItem("muslimos_pin");
    39|  }
    40|})();
    41|

Use offset=41 to continue reading (showing 1-40 of 606 lines)


Ich habe die Konfiguration aus der App gelesen. Hier ist die Übersicht, Chef:

**Müekked Sünnetler** (stark empfohlen, vom Propheten ﷺ regelmäßig gehalten):

- **Sabah sünneti** — vor dem Fard von Fajr, 2 Rekât
- **Öğle ilk sünneti** — vor dem Fard von Dhuhr, 4 Rekât
- **Öğle son sünneti** — nach dem Fard von Dhuhr, 2 Rekât
- **Akşam sünneti** — nach dem Fard von Maghrib, 2 Rekât
- **Yatsı son sünneti** — nach dem Fard von Ishaa, 2 Rekât

**Gayr-i Müekked** (weniger stark betont, aber Sünnet):

- **İkindi sünneti** — vor dem Fard von Asr, 4 Rekât
- **Yatsı ilk sünneti** — vor dem Fard von Ishaa, 4 Rekât

**Nafile Namazlar** (freiwillige zusätzliche Gebete):

- **Kuşluk (Duhâ)** — nach Sonnenaufgang, wenn die Sonne höher steht, 2–8 Rekât
- **Evvâbîn** — nach dem Maghrib-Gebet, 6 Rekât
- **İşrak** — direkt nach Sonnenaufgang, 2 Rekât
- **Tahiyyetü'l-mescid** — beim Betreten einer Moschee, bevor man sich setzt, 2 Rekât

Außerdem gibt es in der App noch **Teheccüd** (Tahajjud) — das Nachtgebet, meist in der letzten Drittel der Nacht, vor Fajr.

Und **Evrad** — wahrscheinlich dein täglicher Dhikr/Wird, aufgeteilt in „short“ und „long“.

Soll ich dir das als kurze Tagesroutine zusammenfassen, wann genau du was betest?


Wann kann ich welches nafile heute beten nach Uhrzeit bitte


Ich brauche die heutigen Gebetszeiten für Wien, um dir das genau sagen zu können. Die App selbst scheint keine Gebetszeiten zu berechnen. Soll ich die Zeiten online für Wien abfragen, oder hast du die gerade zur Hand?


Die Gebetszeiten kannst du googeln


Explanation: <think>

web

Question: Gebetszeiten Wien 14. Juni 2026 Islam


Tool 'web' does not exist. Available tools: clarify, cronjob, delegate_task, execute_code, memory, patch, process, read_file, search_files, send_message, session_search, skill_manage, skill_view, skills_list, terminal, text_to_speech, todo, vision_analyze, write_file


Ich habe leider kein Web-Tool direkt zur Verfügung, aber ich kann die Gebetszeiten über einen Terminal-Befehl abrufen. Moment.

terminal

curl -s "https://api.aladhan.com/v1/timingsByAddress/$(date +%d-%m-%Y)?address=Vienna,Austria&method=13&school=hanafi" | python3 -m json.tool 2>/dev/null | head -80


Output:
{
    "code": 200,
    "status": "OK",
    "data": {
        "timings": {
            "Fajr": "02:30",
            "Sunrise": "04:47",
            "Dhuhr": "13:00",
            "Asr": "17:14",
            "Sunset": "21:03",
            "Maghrib": "21:03",
            "Isha": "23:12",
            "Imsak": "02:20",
            "Midnight": "00:55",
            "Firstthird": "23:35",
            "Lastthird": "02:15"
        },
        "date": {
            "readable": "14 Jun 2026",
            "timestamp": "1781413200",
            "hijri": {
                "date": "28-12-1447",
                "format": "DD-MM-YYYY",
                "day": "28",
                "weekday": {
                    "en": "Al Ahad",
                    "ar": "\u0627\u0644\u0627\u062d\u062f"
                },
                "month": {
                    "number": 12,
                    "en": "Dh\u016b al-\u1e24ijjah",
                    "ar": "\u0630\u0648\u0627\u0644\u062d\u062c\u0629",
                    "days": 29
                },
                "year": "1447",
                "designation": {
                    "abbreviated": "AH",
                    "expanded": "Anno Hegirae"
                },
                "holidays": [],
                "adjustedHolidays": [],
                "method": "HJCoSA"
            },
            "gregorian": {
                "date": "14-06-2026",
                "format": "DD-MM-YYYY",
                "day": "14",
                "weekday": {
                    "en": "Sunday"
                },
                "month": {
                    "number": 6,
                    "en": "June"
                },
                "year": "2026",
                "designation": {
                    "abbreviated": "AD",
                    "expanded": "Anno Domini"
                },
                "lunarSighting": false
            }
        },
        "meta": {
            "latitude": 8.8888888,
            "longitude": 7.7777777,
            "timezone": "Europe/Vienna",
            "method": {
                "id": 13,
                "name": "Diyanet \u0130\u015fleri Ba\u015fkanl\u0131\u011f\u0131, Turkey (experimental)",
                "params": {
                    "Fajr": 18,
                    "Isha": 17
                },
                "location": {
                    "latitude": 39.9333635,
                    "longitude": 32.8597419
                }
            },
            "latitudeAdjustmentMethod": "ANGLE_BASED",
            "midnightMode": "STANDARD",


Hier sind die heutigen Gebetszeiten für Wien und wann du welche Nafile beten kannst, Chef:

**Heutige Gebetszeiten Wien, 14.06.2026**

- Fajr: **02:30**
- Sonnenaufgang: **04:47**
- Ishrāq-Zeit: ab ca. **05:02** (ca. 15 Min. nach Sonnenaufgang)
- Kuşluk/Duhā: ab ca. **06:47** (Sonne ca. 1 Stunde hoch)
- Dhuhr: **13:00**
- Asr: **17:14**
- Sonnenuntergang/Maghrib: **21:03**
- Ishaa: **23:12**
- Letztes Drittel der Nacht beginnt: **02:15**

---

**Nafile/Sünnet-Zeitplan heute**

- **Tahajjud** — ideal zwischen **02:15 und 02:30** (heute Nacht/Morgenfrüh), sonst allgemein in der letzten Nachtdrittel vor Fajr
- **Sabah Sünneti** — vor dem Fard von Fajr, also vor **02:30** (heute sehr früh)
- **İşrak** — nach Sonnenaufgang, ab ca. **05:02** bis ca. 1 Stunde danach
- **Kuşluk (Duhâ)** — wenn die Sonne deutlich höher steht, ab ca. **06:47** bis kurz vor Dhuhr
- **Öğle ilk sünneti** — vor Dhuhr, also vor **13:00**
- **Öğle son sünneti** — nach Dhuhr, also nach **13:00**
- **İkindi sünneti** — vor Asr, also vor **17:14**
- **Akşam sünneti** — nach Maghrib, also nach **21:03**
- **Evvâbîn** — auch nach Maghrib, zwischen **21:03 und 22:30** (vor Ishaa)
- **Yatsı ilk sünneti** — vor Ishaa, also vor **23:12**
- **Yatsı son sünneti** — nach Ishaa, also nach **23:12**
- **Vitir** — nach der Yatsı son Sünnet, also nach **23:12** bis Fajr

**Tahiyyetü'l-mescid** betest du, sobald du heute in eine Moschee gehst — bevor du dich hinsetzt.

Da es heute Sommer ist und Fajr sehr früh liegt, fällt Tahajjud heute Nacht natürlich sehr spät/kurz vor dem Wecker.


Also Kuslik bete ich bis Dhur, also jetzt geht?


Ja, Chef — Kuşluk/Duhâ kannst du jetzt beten. Es ist nach Sonnenaufgang und vor Dhuhr. Heute in Wien also zwischen ca. **06:47 und 13:00**.

Die Regel: Kuşluk beginnt, wenn die Sonne ca. eine Speerlänge hoch ist — also ungefähr 15–20 Minuten nach Sonnenaufgang, und endet kurz vor Dhuhr.


Ok Danke


Gerne, Chef. Ruf schön an und bete gemütlich.


Ich hab einen kleinen olivenbaum bei mir stehen, der leider alle blätter verliert. Er ist von Ikea. Was kann ich tun, damit er die Blätter behält?