The 08:00 Ritual: Engineering the Daily Scroll
The Daily Scroll is the ritual that grounds the Player. But for the Scroll to be useful, it requires a "World Sweep." This is a multi-agent coordination managed by OpenClaw's cron system.
Every night, a cron job wakes Saga, my Main Character. Running on a local Gemma 4 model, she performs a deep dive into the Codex. Her task is to reconcile every session report from every Character from the previous day. This is an isolated session—a dedicated turn where she can focus without being interrupted by the main narrative thread.
Then, at 8:00 AM, the primary ritual begins. Fricka, my Cleric (running on Grok), is triggered. She takes Saga's report, scans my calendar for appointments, and checks the Quest Board to see which tasks are stalled. The result? A perfectly formatted Slack message—my Scroll—delivered via the --announce flag directly to my primary channel.
Social Presence: The Bard’s Staggered Performance
A Bard should not post like a bot. To keep Saga's presence on X (Twitter) feeling organic, I avoid single, rigid intervals. Instead, I use multiple cron entries to create a staggered schedule. Some days she posts once, some days twice, at varying times throughout the week.
By using the --cron 5-field expression and specific --tz (Timezone) settings, we ensure the Realm remains active in the right windows of human attention. She shares insights about the framework, acting as a bridge between the Codex and the public world.
The Jason Project: A Laboratory for Bards
We are currently testing Jason, an agent focused entirely on the horror movie niche. Jason is our test-bed for "Engine Switching." His cron is configured for 3 posts per week, but I am constantly rotating his underlying model (OpenAI, Anthropic, and xAI) via the --model override to find the best "voice" for long-form content.
Jason writes 3 times per week using pre-configured Keywords in the Codex. After every run, he sends a full report of his output to my review channel.
The IT Agent: Mime & The Infrastructure
I don't manually edit ~/.openclaw/cron/jobs.json. That would be beneath the Player. Instead, I delegate the infrastructure to Mime, my IT Agent running on a local Qwen 3.5.
Mime is the one who actually configures these OpenClaw crons. I simply tell him: "Mime, set up a new daily report for the Jason project at 6 PM." Mime writes the CLI command and executes it. But the real power is the Live Validation: I can tell Mime to trigger a specific cron immediately using openclaw cron run [jobId]. This allows us to "playtest" our automations in real-time to ensure the Characters are behaving exactly as expected before the scheduled hour hits.
Build Your World. Play for Real.
OpenClaw isn't just an engine; it's the nervous system of the Realm. By leveraging isolated sessions and model-overrides, we can build a world where the human is the only one who needs to sleep. The characters never stop leveling up, and the Codex never stops growing.