Logseq

An open-source, outliner-first personal knowledge tool where every line is an independently addressable block. The LLM Wiki pattern is renderer-agnostic and works in Logseq as well as Obsidian.

What it is

Logseq is a local-first, open-source (AGPL-3.0) PKM tool built around an outliner format. Each line is a block with its own UUID, independently referenceable and addressable. It includes daily journal pages, block-level references between pages, and graph view — much like Obsidian, but with a fundamentally different data model.

Core difference from Obsidian for LLM Wiki use

• Format: logseq uses outliner format (- prefix per line). obsidian uses flat markdown. The llm-wiki pattern is renderer-agnostic — Karpathy’s model does not depend on any specific viewer, and the /llm-wiki.yml schema can adjust output per tool.
• Block granularity: Logseq’s block-level addressability is genuinely useful for LLM appends — the agent can add content to a specific block without restructuring the entire page. In flat markdown, insertion requires rewriting the page.
• Namespace style: Logseq uses triple-underscore namespaces (Wiki___Tech___Strapi.md) to convert hierarchical concepts into flat files. This is a serialization quirk that matters for tooling but not for the underlying pattern.

Relationship to this vault

This vault is obsidian-native because:

1. Flat markdown is more legible for manual reading and editing
2. Larger plugin ecosystem
3. More mature mobile experience
4. Better virtualization for larger vaults

The core pattern — raw/, wiki/, index.md, log.md, AGENTS.md — is identical regardless of viewer. Switching to Logseq would only change the serialization layer.

Where Logseq fits in the PKM landscape

• second-brain — Logseq can serve as a second-brain front-end, but its block-first model changes how the human interacts with compiled knowledge
• notion — another alternative PKM tool; unlike Notion, Logseq is open-source and local-first
• knowledge-management-approaches-vs-llm-wiki — broader comparison including Logseq vs Obsidian vs traditional wikis

Choose Logseq when:

• You prefer outliner/day-first thinking over document-first
• Block-level references and task management (TODO/DOING/DONE) matter
• AGPL-3.0 licensing and fully auditable codebase matter
• You are comfortable with a smaller plugin ecosystem (~100 plugins vs Obsidian’s 1,800+)
• Mobile app beta quality is acceptable

Strengths relative to LLM Wiki

• Every block is independently addressable — great for targeted LLM appends
• Built-in task management with priorities and scheduling
• Fully open-source
• Daily journal workflow is first-class

Weaknesses relative to Obsidian

• Outliner format is less natural for hand-editing than flat markdown
• Triple-underscore namespace scheme adds tooling complexity
• Smaller ecosystem
• Mobile app is less mature

Relationship to this vault

This vault is Obsidian-native because:

1. Flat markdown is more legible for manual reading and editing
2. Larger plugin ecosystem
3. More mature mobile experience
4. Better virtualization for larger vaults

The core pattern — raw/, wiki/, index.md, log.md, AGENTS.md — is identical regardless of viewer. Switching to Logseq would only change the serialization layer.

Sources