Use Codex to summarize Logseq journals from the CLI

They used Codex with the Logseq CLI docs to query a note graph and turn months of journals and tagged pages into summaries.

Done with CodexĀ· IntermediateĀ· Jul 2026

What they did
wosk gave Codex the Logseq CLI documentation and had it installed next to Logseq, so the agent could learn how to search the graph. After that, Codex pulled information from journal entries spanning months and from tagged pages like job applications with status fields and research projects. Wosk also handled version control by exporting the .edn file and checking it in with git.
How it went
The setup let Codex produce summaries from long stretches of journals, and tagged blocks made the searches feel straightforward. Wosk described the whole workflow as very alpha, and shared no counts or measurements.
Tips
A one-way markdown mirror can make agent access easier because the database stays synced out to markdown. Since the tools are still alpha, it helps to watch the Discord for changes before relying on the workflow.

Try it yourself with Codex

I’m using [agent name] with the Logseq CLI docs. Read the docs at [URL or path], connect to my Logseq graph at [path], and summarize journal entries from [date range] plus pages tagged [tag]. Include main themes, open tasks, and the current status of each project or application. Draft the summary in [file name], then pause and ask for my approval before you send, submit, delete, or change anything in my notes.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

2 more reports of this

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.