---
title: "Roadmap"
description: "Public release snapshot for Amnesia Reader across working-now, beta, 1.0.0, and exploratory tracks."
canonical: https://amnesia-docs.pages.dev/roadmap/
source: "src/content/docs/roadmap.md"
---

# Roadmap

# Amnesia Reader roadmap

This is the canonical public product readiness snapshot used by agents, evaluators, and integrators.
Snapshot date: **2026-08-24**.

No published fixed date commitments are included below; these are public gating snapshots with
status, blockers, and scope boundaries.

## Working now (pre-alpha)

- EPUB and PDF rendering are functional and actively used; both remain under active defect
  remediation and interaction-consistency hardening rather than being release-ready.
- Source-linked highlights, notes, bookmarks, links, and selection handoff keep reading connected to
  Markdown workflows.
- The shipped integration API surfaces for notes, links, MuPDF text/selection, and event delivery are
  usable.
- Discovery and machine surfaces are available through `/docs-index.json`, `/llms.txt`, `/index.md`,
  and route-level Markdown twins.
- Obsidian-native workflow surfaces (Canvases, Workspaces, and graph-aware notes) are the main user-facing
  pattern in released behavior.
- Server features are present in the system and optional, but local file setup does not require them.

## Before beta

Beta readiness requires completing and hardening all of the following:

- Remaining EPUB/PDF renderer defects and interaction inconsistencies, which are under active
  remediation today.
- User-data hardening for dependable persistence, integrity, migration, and recovery of user-created
  reading and research state.
- Server functionality completion and runtime hardening: sync, cache, OPDS, and library-exchange
  paths exist but need hardened recovery, retry, and offline behavior before beta.
- Collections completion and product integration. Collections persistence, API, export, and UI
  substrate already exists; the remaining work is integration, hardening, and stabilization, not
  building from scratch.
- Reader collection sync and collection-event wiring require reliability passes and schema cleanup
  before stable use.
- Cross-plugin command/event resilience in larger vaults and automation-heavy environments.

## Between beta and `1.0.0`

After the beta foundations above are stable, `1.0.0` readiness additionally requires:

- Completion, hardening, and documentation of the supported public/in-app integration API.
- User ergonomics and onboarding work: settings, commands, interaction consistency, discoverability,
  feedback states, accessibility, and related usability work.
- Compatibility, upgrade/migration, documentation, performance, and regression hardening appropriate
  to a stable release boundary.

## Later / exploratory

Ideas in this section are not yet committed directions. They are published only as exploration scope,
not promised features.

- Investigate additional reader workflow ideas that stay compatible with current architecture boundaries.
- Expand advanced collection analytics and workspace orchestration after the 1.0.0 reliability baseline.
- Continue architecture, security, and perf work from the private implementation repo; publish only outcomes
  that are suitable for public API and user documentation.

## How Amnesia is different

This is a category/workflow-level comparison, not a feature scorecard or benchmark claim.

- **Reading stays inside Obsidian.** Amnesia keeps EPUB/PDF reading and source-linked research inside
  Obsidian rather than treating Obsidian as a downstream export target for a standalone reader app.
- **One Obsidian-native research workflow.** Source passages, selections, annotations, notes,
  wikilinks, Canvas/Bases/Workspaces, and ordinary Markdown participate in a single vault-native
  workflow.
- **Durable routes back to sources.** Notes link back to exact source locations rather than only
  clipping or importing excerpts out of context.
- **Collections belong to the reading model.** Collections are part of reading/research workflows
  inside the vault, not a separate external library database.
- **Local data integrity is a release gate.** Persistence, integrity, migration, and recoverability
  of user-created state are treated as gating requirements, not afterthoughts.
- **Interop over lock-in.** The documented in-app integration API exists so other Obsidian plugins and
  agent tooling can interoperate with Amnesia; it is not a closed hosted reading service.

No unsupported superiority claims, benchmark comparisons, or competitor pricing claims are made here.
Detailed product design, prior-art research, and comparative evidence remain in the private
`jjjjguevara/amnesia` repository; this page publishes only reviewed product-level status.