1In short
Morion is a notebook and task board built for coding agents: MCP with per-folder permissions, cited answers from your notes, tickets agents claim, and workflows. It is not an outliner. Pick it when the notes are a software project, not a second brain.
Logseq is an open-source outliner for journals, blocks and queries; since April its file-based line is frozen and the new database version, with an MCP server and a CLI, is in beta. Obsidian is a notebook of plain Markdown files with thousands of plugins; agents reach it through a CLI or community MCP servers.
2Where Logseq and Obsidian stop for agents
On 24 April 2026 Logseq became two products. Logseq OG keeps notes as Markdown or Org files and gets security fixes only. Logseq, the DB version, keeps the graph in a local database, adds typed tags and tables, and ships a local MCP server and a CLI for agents; its first public beta came in July with a data-loss warning. Notes no longer live as plain Markdown files an agent can edit directly.
- Logseq’s MCP server is limited. It cannot read block children or edit pages and properties yet, and one token opens the whole graph.
- Obsidian stays plain Markdown. Agents come in through its CLI, which needs the app running, or through community MCP servers.
- Both give an agent everything. Neither sets per-folder permissions for agents; the agent sees the whole vault or graph.
- Neither has a work queue. Logseq tracks task statuses in tables and lists; Obsidian’s kanban is a view. No agent claims a card.
3Side by side
| Logseq | Obsidian | Morion | |
|---|---|---|---|
| Outliner with block references and queries | — | ||
| Plain Markdown files | |||
| Official MCP server | — | ||
| Folder and per-note permissions for agents | — | — | |
| Kanban board | — | ||
| Tickets agents claim, with work packets | — | — | |
| Answers that cite the note, with a status | — | — | |
| Workflow runner with a human gate | — | — | |
| Mobile app and sync | — | ||
| Open source | — | ||
| App free with no limits |
has it, has part of it, — does not. As of September 2026, without community plugins. Logseq: the DB version (beta) has the MCP server and a Markdown mirror; OG keeps files; Sync and Publish are paid and invite-only; mobile is invite-only. Obsidian links and embeds blocks but is not an outliner; its Sync and Publish are paid. Morion keeps notes in one local file and exports .md; its Free plan has a monthly allowance of MCP calls. Plans are on the pricing page. Morion 2.0 has a Free plan and is not open source; Morion Community, the open-source edition with fewer features, is free under Apache 2.0.
4When agents do the work
Both Logseq and Obsidian are made for a person thinking in notes. When Claude Code or Codex work in them, you add the parts yourself: a server, a CLAUDE.md that explains the structure, a way to hand over tasks. Morion starts from the other end:
- Agents see what you allow. Per folder: visible, create, update, delete; per note: visible, update, delete.
- The agent finds its own context. Mo picks the notes a question needs when it is asked and answers with the source note and a status on each claim.
- Work is tickets. A board from Backlog to Done, claims that never collide, a work packet with the related notes for whichever agent picks a ticket up, and Auto-code to run it with a review and a gate that asks you in chat when the agent has a question.
Keep Logseq or Obsidian for journals and thinking; move the project work into Morion. Import is .md files; block references and queries do not carry over. Related: Obsidian alternative and Notion alternative.
5Which one fits you
if you think in journals and blocks.
if you want a plain-Markdown vault with plugins.
if Claude Code or Codex work the notes as a project: tickets, permissions and cited answers.
if you want to keep the journal where it is and move project folders into Morion as .md files.
6Questions
Since April 2026 Logseq OG keeps notes as Markdown or Org files and gets security fixes only. The DB version stores the graph in a local database, adds typed tags, tables and an MCP server, and is in public beta.
In OG, as Markdown files. In the DB version, through its MCP server or CLI; the MCP server cannot yet read block children or edit pages and properties, and one token opens the whole graph.
For agents that edit files, often yes: an Obsidian vault is plain Markdown. Neither app has built-in AI, per-folder permissions for agents or a board agents claim work from.
Logseq thinks in blocks and journals; Obsidian thinks in pages and links. Obsidian stays plain Markdown in a folder; Logseq OG does too but is frozen, and the new Logseq keeps a database with a one-way Markdown mirror. This year most switchers moved from Logseq to Obsidian, some with Claude Code doing the migration; others stayed on OG.
No. The DB version tracks tasks with statuses such as Backlog, Todo, Doing, In Review and Done, shown in table, list and gallery views. There is no board view.
Yes. Export or copy the Markdown pages and import the .md files into a Morion folder. Block references and queries do not carry over.
Sources: logseq.com, the Logseq repositories, docs and forum, obsidian.md, checked on 25 September 2026. More comparisons: all comparisons.