Files
awesome-opencode/data/plugins/daily-journal.yaml
John SmithandClaude Opus 5.5 3a6d104fcf chore(data): backfill kind, topics and compat for every entry; follow renamed repos
- kind/topics: keyword first pass, then reviewed and corrected by hand for all 513 entries
- compat: detected from npm packages, package.json and source (scripts/utils/compat.js). Plugins: 134 v2, 125 v1, 12 unverified; 13 entries the review loop marked V2 pin @opencode-ai/plugin 1.x, and ~20 loop V2 verdicts based only on the absence of V1 markers are V1 plugin functions in source
- npm and path filled where verifiable (package repository matches the entry); 9 bogus npm values from install prose were not kept
- 29 repo URLs updated to the renamed/transferred repository; xberg-io entries point at their live repos instead of the archived monorepo; lavi uses repo + path instead of a /tree/ URL
- removed projects/opencode-sessions.yaml (same repo as plugins/opencode-sessions.yaml)
- install: renamed to installation:, mojibake fixed, inline HTML links removed from two descriptions

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-17 13:00:22 -04:00

10 lines
878 B
YAML

name: Daily Journal
repo: https://github.com/jianzhangg/opencode-daily-journal
tagline: Auto-journal every conversation into daily/YYYY-MM-DD.md, record-only (never injects)
description: "An OpenCode V2 plugin that keeps a daily journal of your conversations. When a session turn finishes, the exchange is summarized into a diary entry and appended to daily/YYYY-MM-DD.md. Record only, never inject: entries are plain Markdown on disk and are never added to session context unless you explicitly ask the agent to read them. Writes are concurrency-safe (file lock + append-only + idempotent markers, so simultaneous sessions never overwrite or duplicate each other), and summaries use a model fallback chain (session model, then other configured models, then a raw excerpt) so nothing is lost when a model is unavailable."
kind: plugin
topics:
- memory
- sessions
compat: v2