When should you use it?
- Your notes app has a command line
- You track applications or projects with tags
- You want a monthly look back
Not for: Notes apps with no export or CLI; Journals you would not share with a cloud model
What do you need, and what do you get?
You need
- Note app CLI docs
- Tag and status conventions
You get
- Monthly summary of journals
- Status roll-up of tagged items
How does it work, step by step?
- Give the agent the CLI docsPaste the command reference so it knows the available queries.
- Define your tagsExplain which tags and status values mark applications or projects.
- Ask for a period summaryRequest a summary of journal pages for a date range.
- Roll up statusesHave it list tagged items grouped by status.
- Keep historyExport the database to git before large automated changes.
The prompt
Our own prompt, inspired by wosk on Hacker News and written to work in Custom agent and Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Using the {notes_app} CLI documented here: {cli_docs} Summarize my journal pages from {start} to {end} in under 300 words, then list every page tagged {tag} grouped by its status value. Run read-only commands only.
Inspired by wosk on Hacker News: Hacker News comment on using Codex with the Logseq command line. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Beta note apps change formats; recheck the CLI docs after updates.
- An agent with write access to notes can damage them; start read-only.
Our take
You often do not need a connector: a documented CLI plus an agent that can run commands is enough. Structure in the notes does the heavy lifting, since a tag with a status property makes queries precise. wosk's approach needs no special integration: hand the agent the command reference for Logseq's bundled CLI and let it work out the queries. What makes the summaries precise is the structure already in the notes, tags with status properties for applications and research projects, so the agent can group items rather than guess. If your journal is loose prose, add a few consistent tags before trying this. Start read-only, since an agent with write access can damage a note database, and export it to git before any automated change. Beta note apps change formats, so recheck the CLI docs after an update. Think about what is in your journal before sending months of entries to a cloud model; some people will want a local model for this.
Where the time goes back: Looking back across months of notes becomes one request instead of an evening of scrolling.
FAQ
Does it need special integration?
How does version control work?
Source and credit
Inspired by wosk on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on using Codex with the Logseq command line
- Creator
- wosk on Hacker News
- Published on
- Hacker News
- Original date
- Jul 13, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.