Skip to content

CRONJOBS.md

Latest commit

 

History

History
239 lines (198 loc) · 9.3 KB

CRONJOBS.md

File metadata and controls

239 lines (198 loc) · 9.3 KB

Hermes Cron Jobs Snapshot

Last refreshed: 2026-06-08 09:01:53 KST

Rule for future sessions: when the user asks about cron jobs, scheduled updates, weekly automation, or the two-stage autoupdate flow, read this file first, then refresh live state with hermes cron list or the Hermes cronjob tool. Update this file whenever a cron job is created, removed, paused/resumed, or materially changed.

Current Jobs

1. weekly-memory-input-healthcheck

  • Job ID: dc5d7731e05b
  • State: active / scheduled
  • Schedule: 0 9 * * 1
  • Human time: every Monday 09:00 KST
  • Repeat: 3/52
  • Delivery: origin Discord thread
  • Enabled toolsets: terminal, file, memory, session_search, skills
  • Next run: 2026-06-15 09:00:00 KST
  • Last run: 2026-06-01 09:10:50 KST
  • Last status: ok
  • Purpose: weekly Hermes memory/input-layer health check. Checks memory, auxiliary routing, llmwiki/NotebookLM/Axiom-related health signals and reports concisely in Korean.

2. Sync NotebookLM inventory to llmwiki

  • Job ID: d12f70a1f85c
  • State: active / scheduled
  • Schedule: 20 6 * * *
  • Human time: daily 06:20 KST
  • Repeat: forever
  • Delivery: origin Discord thread
  • Script: sync_notebooklm_inventory.py
  • Mode: no-agent (script stdout delivered directly)
  • Next run: 2026-06-09 06:20:00 KST
  • Last run: 2026-06-08 06:23:32 KST
  • Last status: ok
  • Purpose: script-only sync of NotebookLM inventory into llmwiki routing metadata, normally ~/wiki/_meta/notebooklm-inventory.md. It should stay silent unless the script emits output or errors.

3. Stage 1 - Hermes internal stack autoupdate

  • Job ID: 5a930e7ae514
  • State: active / scheduled
  • Schedule: 0 8 * * 1
  • Human time: every Monday 08:00 KST
  • Repeat: 4/52
  • Delivery: origin Discord thread
  • Workdir: /Users/yorha/.hermes/hermes-agent
  • Skills: hermes-agent, yorha-two-stage-autoupdate-flow
  • Enabled toolsets: terminal, file, web, skills, session_search
  • Next run: 2026-06-15 08:00:00 KST
  • Last run: 2026-06-08 08:06:20 KST
  • Last status: ok
  • Delivery note: latest recorded delivery failure: Discord send failed: cannot schedule new futures after interpreter shutdown. The run itself completed and its output can still be consumed by Stage 2 context.
  • Purpose: Stage 1 of Yorha's two-stage autoupdate system. Checks and safely updates the local/internal Hermes/Emil stack only: Hermes Agent, skills, MCP servers, Hindsight, llmwiki, NotebookLM CLI, semble_rs, CommandCode Bridge, LaunchAgents/helpers, etc.
  • Important boundary: must preserve secrets, auth files, personal memory, Google cookies, and private notebooks. It should not mutate generated/public projects.

4. Stage 2 - Hermes Memory Stack project autoupdate

  • Job ID: 1eef61060057
  • State: active / scheduled
  • Schedule: 0 9 * * 1
  • Human time: every Monday 09:00 KST
  • Repeat: 3/52
  • Delivery: Discord thread 1505008463636598814:1505008704083460096
  • Skills: github-pr-workflow, yorha-artifact-commit-flow, yorha-two-stage-autoupdate-flow
  • Workdir: /Users/yorha/dev/hermes-memory-stack
  • Next run: 2026-06-15 09:00:00 KST
  • Last run: 2026-06-01 09:04:58 KST
  • Last status: ok
  • Purpose: Stage 2 of Yorha's two-stage autoupdate system. Checks/updates/repackages/pushes generated or packaged projects, currently focused on this repo (hermes-memory-stack).
  • Important boundary: starts from clean main, pulls latest, checks upstream references, updates only meaningful safe changes, verifies thoroughly, commits/pushes only if verification passes. It should not update Yorha's internal Hermes stack.

5. CommandCode CLI update watch + Bridge impact review

  • Job ID: c4441ff76b09
  • State: active / scheduled
  • Schedule: 0 9 * * *
  • Human time: daily 09:00 KST
  • Repeat: forever
  • Delivery: origin Discord thread
  • Skills: commandcode-bridge-operations
  • Workdir: /Users/yorha/dev/commandcode-bridge
  • Next run: 2026-06-09 09:00:00 KST
  • Last run: 2026-06-07 09:05:24 KST
  • Last status: ok
  • Purpose: monitors CommandCode CLI updates and reviews impact on Yorha's CommandCode Bridge integration.

6. Kimi Code NotebookLM source-pack weekly update check

  • Job ID: 83bac0c30ea3
  • State: active / scheduled
  • Schedule: 10 9 * * 1
  • Human time: every Monday 09:10 KST
  • Repeat: 5/52
  • Delivery: origin Discord thread
  • Script: kimi_code_source_pack_check.sh
  • Mode: no-agent (script stdout delivered directly)
  • Next run: 2026-06-08 09:10:00 KST
  • Last run: 2026-06-01 09:14:46 KST
  • Last status: ok
  • Purpose: weekly NotebookLM source-pack update check for Kimi Code materials.

7. Command Code NotebookLM source-pack weekly update check

  • Job ID: 16bb136952b6
  • State: active / scheduled
  • Schedule: 20 9 * * 1
  • Human time: every Monday 09:20 KST
  • Repeat: 4/52
  • Delivery: origin Discord thread
  • Script: command_code_source_pack_check.sh
  • Mode: no-agent (script stdout delivered directly)
  • Next run: 2026-06-08 09:20:00 KST
  • Last run: 2026-06-01 09:23:31 KST
  • Last status: ok
  • Purpose: weekly NotebookLM source-pack update check for Command Code materials.

8. github-stars-to-threads-profile

  • Job ID: 0daa6a52f7e3
  • State: active / scheduled
  • Schedule: */15 * * * *
  • Human time: every 15 minutes
  • Repeat: forever
  • Delivery: origin Discord thread
  • Script: github_stars_threads_check.py
  • Next run: 2026-06-08 09:15:00 KST
  • Last run: 2026-06-08 09:00:41 KST
  • Last status: ok
  • Purpose: checks GitHub star count and updates the Threads profile when needed.

9. Hermes Agent NotebookLM source-pack weekly update check

  • Job ID: ec4c8e1f1b81
  • State: active / scheduled
  • Schedule: 30 9 * * 1
  • Human time: every Monday 09:30 KST
  • Repeat: 4/52
  • Delivery: origin Discord thread
  • Script: hermes_agent_source_pack_check.sh
  • Mode: no-agent (script stdout delivered directly)
  • Next run: 2026-06-08 09:30:00 KST
  • Last run: 2026-06-01 09:34:43 KST
  • Last status: ok
  • Purpose: weekly NotebookLM source-pack update check for Hermes Agent materials.

10. Qwen Code NotebookLM source-pack weekly update check

  • Job ID: 307061cdaa6c
  • State: active / scheduled
  • Schedule: 50 9 * * 1
  • Human time: every Monday 09:50 KST
  • Repeat: 3/52
  • Delivery: origin Discord thread
  • Script: qwen_code_source_pack_check.sh
  • Mode: no-agent (script stdout delivered directly)
  • Next run: 2026-06-08 09:50:00 KST
  • Last run: 2026-06-01 09:53:52 KST
  • Last status: ok
  • Purpose: weekly NotebookLM source-pack update check for Qwen Code materials.

11. CMUX Korean Docs NotebookLM source-pack weekly update check

  • Job ID: d709a075d5a6
  • State: active / scheduled
  • Schedule: 40 9 * * 1
  • Human time: every Monday 09:40 KST
  • Repeat: forever
  • Delivery: origin Discord thread
  • Script: cmux_ko_docs_source_pack_refresh.sh
  • Mode: no-agent (script stdout delivered directly)
  • Next run: 2026-06-08 09:40:00 KST
  • Last run: 2026-06-01 09:41:10 KST
  • Last status: ok
  • Purpose: weekly NotebookLM source-pack refresh for CMUX Korean documentation.

12. Cron failure self-healing watchdog

  • Job ID: 78ee1ebc9fe4
  • State: active / scheduled
  • Schedule: 15 10 * * *
  • Human time: daily 10:15 KST
  • Repeat: forever
  • Delivery: origin Discord thread
  • Next run: 2026-06-08 10:15:00 KST
  • Last run: 2026-06-07 10:17:29 KST
  • Last status: ok
  • Purpose: watches recent cron failures and attempts/report safe self-healing where configured.

13. CuaDriver residual process cleanup

  • Job ID: f42e4b3fa5ce
  • State: active / scheduled
  • Schedule: every 30m
  • Human time: every 30 minutes
  • Repeat: forever
  • Delivery: origin Discord thread
  • Script: cleanup_cuadriver_residuals.sh
  • Mode: no-agent (script stdout delivered directly)
  • Next run: 2026-06-08 09:18:39 KST
  • Last run: 2026-06-08 08:48:39 KST
  • Last status: ok
  • Purpose: cleans up residual CuaDriver helper processes while preserving the active service.

Two-stage update mental model

  1. Stage 1 = internal stack

    • Local Hermes/Emil runtime and integrations.
    • Examples: Hermes Agent, skills, Axiom Perception MCP, Hindsight, llmwiki, NotebookLM CLI, semble_rs, CommandCode Bridge.

  2. Stage 2 = generated/published projects

    • Repositories and artifacts created or maintained by Emil/Hermes.
    • Current primary target: /Users/yorha/dev/hermes-memory-stack.
    • Examples: installer scripts, README/ACKNOWLEDGEMENTS, generated infographics, packaging logic.

Keep these as separate jobs so failures are isolated.

Update procedure for this file

When cron state changes:

  1. Run live listing:
hermes cron list

or use the Hermes cronjob tool with action='list'.

  1. Update the affected job section here.
  2. If a new scheduled job belongs to a repo/workspace, note its workdir and boundaries.
  3. If a job is removed, move it to an "Old/Removed jobs" section with removal date and reason instead of silently deleting it, unless Yorha asks for a clean file.
  4. Commit this file with the same change set if the cron change is part of this project update.

Notes

  • Cron prompts must be self-contained; future cron runs do not inherit chat context.
  • Cron jobs must not recursively create more cron jobs.
  • Stage 2 may consume Stage 1's most recent output as context, but should not require Stage 1 to have succeeded in the same tick.
  • Delivery target origin usually means the Discord thread where the job was created; explicit discord:<guild_or_channel>:<thread> delivery means the job is pinned to that Discord target.