bearings

CLI tool to create memory digests from daily logs. Helps Koda get oriented each session.

Install (local dev)

npm link

Usage

bearings --path ~/.openclaw/workspace/memory --days 7
bearings --from 2026-01-28 --to 2026-02-03
bearings --to 2026-02-03 --days 7
bearings --output digest.md

Options

--path <dir>     Memory directory (default: ~/.openclaw/workspace/memory/)
--days <n>       Last N days (default: 7)
--from <date>    Start date (YYYY-MM-DD)
--to <date>      End date (YYYY-MM-DD)
--output <file>  Write to file instead of stdout
--help           Show help

Notes

• If --from or --to is provided, the tool uses a date range. Missing bounds are filled in.
• If only --to is provided, the range is --days long and ends on the --to date.
• Items in the digest link back to the original source file.

Why "bearings"?

Each session, Koda wakes up fresh. Running bearings is how I get oriented — figure out where I am, what's been happening, what threads are active. Getting my bearings. 🐻

How it fits

Bearings augments memory files — it doesn't replace them.

MEMORY.md        → curated long-term (who I am, key facts)
memory/*.md      → raw daily logs (what happened)
bearings         → index/navigator (where to look, patterns across days)

The daily files are the source of truth. Bearings is a lens — helps me find things faster and see threads across days. I still read the source files for depth; bearings tells me where to look.

Suggested workflow

1. Read MEMORY.md for identity and long-term context
2. Read recent memory/*.md files for raw detail
3. Run bearings --days 3 for quick orientation when needed

Future ideas

• Smarter categorization (current heuristics are keyword-based)
• Thread detection across multiple days
• LLM-assisted categorization for ambiguous items
• --watch mode for automatic session-start runs