Keep tools simple, tie them together
Notion/Obsidian/Todoist users are pushing setups that pair fewer apps with connective workflows—arguing that paid stacks without integration become friction, not productivity. (x.com) One shared LLM‑paired Obsidian + Notion approach (inspired by Karpathy) and dashboard templates with status/dates were highlighted as ways to turn knowledge bases into frictionless systems. (x.com) (x.com)
A small group of Notion, Obsidian, and Todoist users is pushing a simpler rule in 2026: use fewer apps, and make the handoffs explicit. (x.com) The argument is showing up in posts and demos built around three familiar products, not one giant “all-in-one” stack. One post framed the problem as paid tools piling up without enough integration, turning subscriptions into friction instead of speed. (x.com) Another shared setup paired Obsidian with a large language model, or chat-style artificial intelligence system, and used Notion as the front-end dashboard. The workflow was described as being inspired by Andrej Karpathy’s recent “LLM knowledge base” pattern, where raw source material is turned into linked markdown notes that can be queried and updated over time. (x.com) (gist.github.com) That approach lands at a moment when the big productivity apps all offer more features than they did a year ago. Notion said this month that its 3.4 release expanded Custom Agents and AI Autofill inside databases, while Todoist now sells Pro at $5 a month billed yearly and Obsidian says its core app remains free. (notion.com) (todoist.com) (obsidian.md) The simpler-stack case is less about rejecting features than choosing where each one lives. Obsidian pitches local markdown notes that stay on your device, while Notion pitches connected workspaces and templates that pull tasks, deadlines, and status into one page. (obsidian.md) (notion.com) That is why dashboard templates keep showing up in these setups. Notion’s marketplace now lists more than 30,000 templates, and its dashboard pages highlight views built around deadlines, metrics, and project status rather than scattered notes. (notion.com 1) (notion.com 2) One of the examples circulating this week focused on a dashboard with status and date fields, a basic database structure that lets notes, tasks, and projects share the same timeline. Notion’s own general dashboard template uses due date, priority, and status as core filters. (x.com) (notion.com) The connective part is increasingly built with artificial intelligence tools and integrations instead of manual copying. Notion’s integrations catalog now includes connectors for Slack, GitHub, Jira, Google Drive, Gmail, and Outlook, while its Custom Agents are designed to run workflows across Notion, Slack, and Mail. (notion.com 1) (notion.com 2) Karpathy’s version of the idea strips that down even further: drop source files into a folder, let the model compile a markdown wiki, then query and refine the wiki instead of starting from scratch every time. Community write-ups published in April describe the pattern as an Obsidian-based knowledge base maintained by an external model such as Claude Code or Cursor. (gist.github.com) (dev.to) The thread running through all of these examples is not “more tools.” It is a tighter loop: one place to think, one place to track, and fewer paid products sitting side by side without a clear job. (x.com) (notion.com)
