← Back to library

Have a coding agent review your Logseq journal

wosk on Hacker News handed Codex the docs for Logseq's bundled command line tool, and the agent worked out queries to digest journal entries across many months. Tags with status properties for job applications and research projects made structured summaries possible.

  • OutcomePoint a coding agent at your note app's command line tool so it can summarize months of journal pages and report on tagged items such as job applications.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditwosk on Hacker News
View original
Works with
Custom agentClaude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Give the agent the CLI docsPaste the command reference so it knows the available queries.
  2. Define your tagsExplain which tags and status values mark applications or projects.
  3. Ask for a period summaryRequest a summary of journal pages for a date range.
  4. Roll up statusesHave it list tagged items grouped by status.
  5. 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)

Prompt5 variables
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?
No. The author just shared the CLI documentation and the agent worked out the commands.
How does version control work?
Export the database file and commit it to git.

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.

More in Career & Learning

All 37 Career & Learning playbooks →

Related playbooks

Career & LearningSkill✓ AI dry run

Learn any topic with a strict Socratic tutor skill

Load Jane Street's open-source tutoring skill into Claude, ChatGPT or a coding agent so that when you ask to be taught something, it first tests what you already know, keeps a 0 to 5 level for each part of the topic, quizzes you one question at a time without handing over answers, re-tests older material by surprise, and only ends the course after a final mixed exam.

Credit: janestreet

Minutes
Career & LearningSkill✓ AI dry run

Run a literature review by chasing citations

Start from a few seed papers and have an agent expand the set through backward and forward citations, screen candidates, and refine the review in rounds.

Credit: u/ZS-Portfolio on r/AIToolBench

Under an hour
Career & LearningRoutine✓ AI dry run

Copy homework due dates from a school portal to a calendar

Have an agent sign in to the school portal daily, pick out each assignment and its deadline, and put them on your kid's calendar along with an advance nudge.

Credit: fnordpiglet on Hacker News

Under an hour
Career & LearningWorkflow✓ AI dry run

Revive decades-old assembly code with a coding agent

Have a coding agent get old source compiling with a modern compatible assembler and emulator, and use the old comments to hunt known bugs.

Credit: TacticalCoder on Hacker News

An afternoon+
Career & LearningWorkflow✓ AI dry run

Run a systematic review with an agent and checkpoints

Let a research agent draft the questions and screening rules, edit both yourself, then let it search, screen, extract data and produce a PRISMA-style review you audit.

Credit: Mushtaq Bilal, PhD (@MushtaqBilalPhD)

Under an hour