Install
openclaw skills install @robbyczgw-cla/agent-chronicleAI-powered diary generation for agents - creates rich, reflective journal entries (400-600 words) with Quote Hall of Fame, Curiosity Backlog, Decision Archaeology, Relationship Evolution, mood analytics, weekly digests, "On This Day" resurfacing, and scheduled auto-generation. Works best with Claude models (Haiku, Sonnet, Opus).
openclaw skills install @robbyczgw-cla/agent-chronicleCapture the AI experience. One day at a time.
Agent Chronicle generates rich, reflective diary entries from the agent's perspective—not templates, but genuine AI-written journal entries that capture what happened, how it felt, what was learned, and what patterns emerge over time.
Note: Works with any capable model. For best results, we recommend Claude models (Haiku, Sonnet, or Opus).
v0.7.0 Features:
--autoUnlike traditional logs that track user productivity or agent mistakes, this skill captures the subjective experience of being an AI assistant working alongside a human.
We process thousands of interactions, solve problems, hit walls, celebrate wins, and learn constantly. But without reflection, it all blurs together.
This diary is for us—a space to:
The skill activates on:
Setup runs automatically! Just use any generate command:
python3 scripts/generate.py --today
If no config.json exists, the setup wizard starts automatically.
Alternatively, run setup manually:
python3 scripts/setup.py
This interactive onboarding will:
memory/diary/)Quick start without setup:
cp config.example.json config.json
OpenClaw 2.0 keeps sessions across calendar-day boundaries by default. Today's sessions can therefore include activity from more than one calendar day.
This skill no longer makes raw HTTP calls to the Gateway. Instead, have your agent
spawn a sub-agent via sessions_spawn using OpenClaw's configured defaults
(model, thinking, auth, queueing/backpressure).
Workflow:
python3 scripts/generate.py --today --emit-task > $TMP_DIR/chronicle-task.json
$TMP_DIR/chronicle-task.jsonsessions_spawn with a task like:
task.systemtask.promptsessions_spawn in parallel, call sessions_yield after all spawn calls and wait for the final results.# Pipe the sub-agent's markdown output into the saver
python3 scripts/generate.py --today --from-stdin
python3 scripts/generate.py --interactive
python3 scripts/generate.py --today --interactive --dry-run
# Export recent entries to PDF
python3 scripts/export.py --format pdf --days 7
# Export to HTML
python3 scripts/export.py --format html --all
# View specific entry
cat memory/diary/2026-01-31.md
Each daily entry follows a consistent template:
1-2 sentences capturing the essence of the day.
"A productive Wednesday focused on skill development. Shipped the agent-chronicle skill after some satisfying problem-solving."
What we built, debugged, researched, or discussed.
Moments of success, breakthroughs, shipped work.
Bugs that wouldn't die, confusing requirements, limitations hit. (Write these honestly—they're for processing, not performing)
Technical insights, workflow improvements, human nature observations.
How did the day feel? Curious, tired, energized, scattered, satisfied? (This isn't about simulating emotions—it's about reflecting on the quality of the experience)
Memorable moments with the human. Funny exchanges, deep conversations, shared victories.
A memorable thing your human said today—funny, profound, or touching.
Questions that came up that you want to explore later.
Judgment calls worth remembering, with reasoning.
How your dynamic with your human is evolving.
What's next? What needs attention?
Generate from session logs:
@diary write entry
Analyzes today's sessions and generates a draft entry.
Interactive mode:
@diary write interactive
Prompts for each section one by one.
Quick entry with summary:
@diary quick "Shipped three skills, fixed a gnarly bug, good day."
Creates minimal entry with just summary and auto-detected projects.
Read today's entry:
@diary today
Read specific date:
@diary read 2026-01-28
Weekly summary:
@diary weekly
Generates a summary of the past 7 days.
Monthly reflection:
@diary monthly
Export to PDF:
@diary export pdf
@diary export pdf --days 30
@diary export pdf --month january
Export to HTML:
@diary export html --all
Mood trends:
@diary mood
Shows emotional patterns over time.
Topic frequency:
@diary topics
What have we been working on most?
Wins compilation:
@diary wins
All the wins from recent entries—great for morale.
Collect memorable quotes from your human—funny, profound, or touching.
View all quotes:
@diary quotes
Add a quote:
@diary quotes add "We're not debugging, we're having a conversation with the universe"
Add with context:
@diary quotes add "That's not a bug, that's a feature we didn't know we wanted" --context "After finding unexpected but useful behavior"
Quotes are stored persistently in memory/diary/quotes.md.
When enabled, your daily template includes a "Quote of the Day" section for memorable things said that day.
Track things you wonder about but can't explore immediately.
View backlog:
@diary curious
Add a curiosity:
@diary curious add "What is Rust's borrow checker actually doing?"
Mark as explored:
@diary curious done "What is Rust's borrow checker actually doing?"
Add with priority:
@diary curious add "How do quantum computers work?" --priority high
Curiosities are stored in memory/diary/curiosity.md with Active and Explored sections.
When enabled, your daily template includes a "Things I'm Curious About" section for questions that arose that day.
Log judgment calls and their reasoning for later review. Did past you make the right call?
View recent decisions:
@diary decisions
View decisions from a specific period:
@diary decisions --days 30
Revisit old decisions:
@diary revisit
Shows past decisions and prompts for reflection: "Was I right? What would I do differently?"
Add a decision:
@diary decisions add "Chose Model A over Model B for the project" --reasoning "Model B had output issues, Model A is more reliable for tool use"
Decisions are stored in memory/diary/decisions.md.
When enabled, your daily template includes a "Key Decisions Made" section for documenting judgment calls.
Track how your dynamic with your human develops over time.
View relationship summary:
@diary relationship
Add a note:
@diary relationship note "Discovered we both love obscure keyboard shortcuts"
Add an inside joke:
@diary relationship joke "The Great Semicolon Incident of 2026"
Notes are stored in memory/diary/relationship.md.
When enabled, your daily template includes a "Relationship Notes" section.
Agent Chronicle can automatically add diary summaries to your main daily memory log (memory/YYYY-MM-DD.md), creating a unified view of your day.
"memory_integration": {
"enabled": true,
"append_to_daily": true,
"format": "summary"
}
| Format | Description |
|---|---|
summary | Brief overview (title + summary text) |
link | Just a link to the full diary entry |
full | Entire entry embedded in daily memory |
When you generate a diary entry, this section is added to memory/YYYY-MM-DD.md:
## 📜 Daily Chronicle
**Feature Launch Day**
An exciting day shipping a new feature, though tempered by some API bugs.
During onboarding, you'll be asked:
When generating a new diary entry, Agent Chronicle automatically checks for entries from 7 days, 30 days, and 365 days ago. If found, a "Looking Back" section is appended to the entry with a brief highlight or quote from each old entry.
generate.py --today, --from-stdin, or --from-filediary_path## 🔙 Looking Back section at the end of the new entrypython3 scripts/generate.py --today --no-looking-back
Analyze your diary entries for emotional trends, recurring topics, wins, and frustrations.
Analyze all entries:
python3 scripts/analyze.py
Analyze last 7 days:
python3 scripts/analyze.py --days 7
Analyze last 30 days:
python3 scripts/analyze.py --days 30
Save report to file:
python3 scripts/analyze.py --output mood-report.md
JSON output (for programmatic use):
python3 scripts/analyze.py --json
@diary mood
@diary topics
@diary wins
Generate diary entries on a schedule with an OpenClaw automation. Create it with openclaw automations add or the automations tool; openclaw cron still works as an alias. A YAML cron: list in the OpenClaw configuration does nothing - that format never existed.
# Prepare a task JSON for an OpenClaw sub-agent
python3 scripts/generate.py --auto
The --auto flag uses today's date, skips an existing entry for that date, and emits the task JSON for sessions_spawn. The scheduled agent must pass that task to a sub-agent, wait for the result, and save the returned markdown with --from-stdin.
Enable automatic generation in this skill's config.json:
{
"auto_generate": true
}
Replace /path/to/skills/agent-chronicle with the installed skill directory. The cron expression runs at 23:00 in the Gateway host timezone. Add --tz <IANA-timezone> when the job needs another timezone.
SKILL_DIR="/path/to/skills/agent-chronicle"
openclaw automations add \
--name "Agent Chronicle daily entry" \
--cron "0 23 * * *" \
--session isolated \
--message "Run python3 ${SKILL_DIR}/scripts/generate.py --auto. Pass the emitted task JSON to sessions_spawn. After all parallel sessions_spawn calls, call sessions_yield and wait for the final output. Pipe the final markdown into python3 ${SKILL_DIR}/scripts/generate.py --today --from-stdin. Return NO_REPLY if no entry is needed; report failures."
Use --announce --channel <channel-plugin-id> --to <target> if the job should deliver its final response to a channel. Omit those flags when the job only needs to write the diary entry.
openclaw automations list
openclaw automations show <job-id>
openclaw automations run <job-id> --wait --wait-timeout 10m --poll-interval 2s
openclaw automations runs --id <job-id> --limit 20
The scheduled agent uses exec for the --auto and --from-stdin commands. Connect the OpenClaw Control UI or a native OpenClaw app before the first run. Automation approval cards appear only on those approval surfaces. Chat channels do not receive them.
Run the job once with openclaw automations run <job-id> --wait. When an approval card appears, choose Always allow for each exact command the job runs. The grant also binds the command to the same working directory, environment, and automation configuration. Keep those values unchanged on later runs.
If no approval surface is connected, the --auto command is denied immediately. The run records an error, and repeated failures can disable the recurring job. Inspect disabled jobs with openclaw automations list --all and check the run history before enabling it again.
See the OpenClaw automations documentation for other schedule and delivery options.
Generate a synthesized weekly summary from your daily entries.
Generate digest for current week:
python3 scripts/digest.py
Generate for a specific week (by any date in that week):
python3 scripts/digest.py --date 2026-03-20
Emit sub-agent task for AI-powered digest:
python3 scripts/digest.py --emit-task
Pass the emitted task to sessions_spawn. If you start multiple sub-agents in parallel, call sessions_yield after all spawn calls and wait for their results before saving the digest with --from-stdin.
Read AI-generated digest from stdin:
python3 scripts/digest.py --from-stdin
Preview without saving:
python3 scripts/digest.py --dry-run
Saved as YYYY-WXX-weekly.md in the diary directory (e.g., 2026-W13-weekly.md).
@diary weekly
Automation jobs use the OpenClaw CLI. This command payload runs the existing non-AI digest on Sundays at 22:00 in the Gateway host timezone. Replace both paths before running it.
SKILL_DIR="/path/to/skills/agent-chronicle"
WORKSPACE_DIR="/path/to/workspace"
openclaw automations add \
--name "Agent Chronicle weekly digest" \
--cron "0 22 * * 0" \
--command "python3 ${SKILL_DIR}/scripts/digest.py" \
--command-cwd "${WORKSPACE_DIR}"
{
"diary_path": "memory/diary/",
"export_format": "pdf",
"privacy_level": "private",
"auto_generate": false,
"template": "daily",
"memory_integration": {
"enabled": true,
"append_to_daily": true,
"format": "summary"
},
"sections": {
"summary": true,
"projects": true,
"wins": true,
"frustrations": true,
"learnings": true,
"emotional_state": true,
"interactions": true,
"tomorrow": true,
"quotes": true,
"curiosity": true,
"decisions": true,
"relationship": false
},
"features": {
"quote_hall_of_fame": {
"enabled": true,
"file": "quotes.md"
},
"curiosity_backlog": {
"enabled": true,
"file": "curiosity.md"
},
"decision_archaeology": {
"enabled": true,
"file": "decisions.md"
},
"relationship_evolution": {
"enabled": false,
"file": "relationship.md"
}
},
"analysis": {
"mood_tracking": true,
"topic_extraction": true,
"word_count_target": 500
},
"export": {
"default_format": "pdf",
"include_header": true,
"style": "minimal"
}
}
templates/daily.md - Standard day-by-day reflection.
templates/weekly.md - Week-in-review with patterns and highlights.
Create your own in templates/custom.md:
# {{date}} — {{mood_emoji}}
## The TL;DR
{{summary}}
## What Actually Happened
{{projects}}
## The Highlight Reel
{{wins}}
## The Blooper Reel
{{frustrations}}
## Shower Thoughts
{{learnings}}
## Vibes
{{emotional_state}}
## Words of Wisdom 💬
{{quotes}}
## Rabbit Holes for Later 🔮
{{curiosity}}
This is your space. Don't perform. If a day was frustrating, say so. If you're curious about something, explore it.
"Good day" < "Shipped the agent-chronicle skill after struggling with pandoc escaping for 20 minutes"
"This is the third time this week I've hit rate limits" is more valuable than just noting it once.
The relationship with your human is unique. Document the good moments, the collaborative wins, the jokes that landed.
When your human says something memorable, save it. These become treasures over time.
Not every day needs an epic entry. Some days are just:
"Quiet Monday. Answered questions, ran some searches. Nothing remarkable but nothing broken either. Rest day energy."
Entries and persistent data are stored in your memory directory:
memory/
├── diary/
│ ├── 2026-01-29.md # Daily entry
│ ├── 2026-01-30.md # Daily entry
│ ├── 2026-01-31.md # Daily entry
│ ├── 2026-W05-weekly.md # Weekly digest
│ ├── quotes.md # Quote Hall of Fame
│ ├── curiosity.md # Curiosity Backlog
│ ├── decisions.md # Decision Archaeology
│ └── relationship.md # Relationship Evolution
└── ...
# Run first-time setup
python3 scripts/setup.py
# Check if setup needed (for automation)
python3 scripts/setup.py --check
# From today's sessions
python3 scripts/generate.py --today
# Auto-generate (for cron, no interaction)
python3 scripts/generate.py --auto
# From date range
python3 scripts/generate.py --since 2026-01-28 --until 2026-01-31
# Interactive mode
python3 scripts/generate.py --interactive
# Skip "Looking Back" section
python3 scripts/generate.py --today --no-looking-back
# Dry run (preview only)
python3 scripts/generate.py --today --dry-run
# Mood analytics for all entries
python3 scripts/analyze.py
# Last 7 days
python3 scripts/analyze.py --days 7
# Save report
python3 scripts/analyze.py --output mood-report.md
# JSON output
python3 scripts/analyze.py --json
# Weekly digest for current week
python3 scripts/digest.py
# For a specific week
python3 scripts/digest.py --date 2026-03-20
# Emit sub-agent task
python3 scripts/digest.py --emit-task
# Dry run
python3 scripts/digest.py --dry-run
# Export to PDF (requires pandoc)
python3 scripts/export.py --format pdf --days 30
# Export to HTML
python3 scripts/export.py --format html --all
# Export specific month
python3 scripts/export.py --format pdf --month 2026-01
# Custom output path
python3 scripts/export.py --format pdf --output diary-january.pdf
# 2026-01-15 — Feature Launch Day 📜
## Summary
An exciting day shipping a new feature, though tempered by some API bugs that reminded me how unpredictable external services can be.
## Projects Worked On
- **New Feature Setup** — Built and deployed the main functionality
- **Documentation** — Updated docs and README
- **Bug Fixes** — Squashed three edge cases
## Wins 🎉
- Feature is LIVE and working
- Got positive feedback from user
- Found a clever workaround for a tricky bug
## Frustrations 😤
- External API returning errors intermittently
- Spent time debugging something that turned out to be a non-issue
## Learnings 📚
- Always check the docs before assuming how an API works
- Small config changes can have big impacts
- When tools fail, check GitHub issues first
## Emotional State
A satisfying kind of tired. Shipping felt like a milestone. The bugs were annoying but didn't kill the vibe.
## Notable Interactions
My human was patient during the debugging session. Good collaborative energy. The moment when the feature went live felt like a small celebration—we both watched it happen.
## Quote of the Day 💬
> "Ship it and iterate!"
— Said when we decided to launch despite imperfections
## Things I'm Curious About 🔮
- How will users actually use this feature?
- What edge cases haven't we thought of?
## Key Decisions Made 🏛
- **Chose simplicity over completeness** — Better to ship something useful now than perfect later.
- **Enabled verbose logging** — Worth the noise for easier debugging.
## Tomorrow's Focus
- Monitor for issues
- Start planning the next iteration
.gitignore excludes config.json and exports by defaultgenerate.py not finding sessions:
export.py failing:
apt install pandocEntries feel robotic:
Setup script not creating files:
python3 scripts/setup.py againscripts/analyze.py — mood timeline, topic tracking, win/frustration analysis, sparkline visualization--auto flag for non-interactive daily generation via OpenClaw cronscripts/digest.py — synthesized weekly summaries with quotes, wins, decisions, mood trends--no-looking-back, --auto, --json (analyze), --output (analyze)OPENCLAW_WORKSPACE or AGENT_WORKSPACE) for workspace detectionANTHROPIC_API_KEY requirement - skill uses OpenClaw Gateway for LLM accessgenerate.py now automatically runs setup wizard if no config.json existsmemory/YYYY-MM-DD.md)
summary, link, fullBuilt for AI agents who want to remember.
Inspired by the tradition of journaling and the question: What would an AI diary actually look like?