Coming from Obsidian?
Flynt and Obsidian both respect Markdown files, but they optimize for different jobs. Obsidian is a personal knowledge-base app. Flynt is a project operating surface for notes, tasks, diagrams, agent work, and release-visible project state.
The short version
- Your Markdown files remain normal files.
[[wikilinks]]are supported and feed the Graph.- Flynt adds project surfaces beyond notes: Tasks, Lenses, Design, Terminal, and Omegon.
- Flynt metadata lives under
.flynt/; Omegon runtime state lives under.omegon/. - Flynt is conservative with existing folders and code repos; configure scopes when you want Flynt to manage frontmatter.
Concept map
| Obsidian concept | Flynt equivalent | Difference |
|---|---|---|
| Vault | Project folder | Flynt expects the folder may include notes, code, tasks, drawings, and runtime metadata. |
| Notes | Write surface | Tabbed markdown editing with project metadata and agent-aware context. |
| Backlinks / graph | Graph + Context | Graph includes project entities such as tasks, boards, and artifacts, not only notes. |
| Plugins | Flynt surfaces + Omegon tools | Flynt prefers built-in project surfaces and agent tools over a general note-app plugin ecosystem. |
| Canvas | Design boards / drawings / flows | Visual artifacts are project files with wrappers and render surfaces. |
| Tasks plugin | Tasks surface | Kanban/task files are indexed as project state. |
| Dataview | Lenses | Lenses are saved project queries/views; they are intended to be inspectable and agent-friendly. |
Opening an Obsidian vault
- Back up or commit your vault first. Flynt is file-based, but a clean rollback point is still good engineering practice.
- Open the vault folder in Flynt.
- Start in Write and Files. Confirm your notes and folders look right.
- Open Graph. For very large vaults, Flynt may show a bounded overview first; use filters, search, local mode, or Show all when needed.
- Only enable Flynt-managed metadata/frontmatter scopes if you want Flynt to write IDs, kinds, or typed fields into files.
What transfers cleanly
- Markdown headings, lists, links, code blocks, and ordinary frontmatter.
- Wikilinks such as
[[Project Plan]]and aliased links such as[[Project Plan|plan]]. - Folder organization.
- Git-backed history if your vault is already versioned.
What to review
- Obsidian-only embeds or plugin syntax: Flynt may leave these as text unless a Flynt surface understands them.
- Dataview queries: translate important ones into Flynt Lenses over time.
- Canvas files: Obsidian Canvas is not the same artifact as Flynt design boards, Excalidraw drawings, or flow graphs.
- Attachment folders: Flynt can reference assets, but large binary-heavy folders should be considered deliberately in indexing/sync posture.
Sync expectations
Flynt does not claim real-time collaborative sync. If you already use Git for your vault, Flynt can fit that local-first workflow. Read Sync posture before relying on Flynt for multi-machine workflows.
When Flynt is a better fit
- You want notes connected to tasks, design artifacts, terminal sessions, release notes, and project automation.
- You want an embedded project-scoped agent that can inspect and modify project files.
- You are working in a code repository or operational project, not just a personal note vault.
When Obsidian may still be better
- You depend heavily on Obsidian's plugin ecosystem.
- Your main workflow is personal journaling or reading notes on mobile.
- You need Obsidian-specific Canvas or Dataview behavior exactly as-is.