# Roadmap

What Reliquary does today, what is being built, and what may come next.

Reliquary is pre-alpha: things change and may break; data is backed up daily. The same list, in columns, is at [/roadmap](https://reliquary.redmage.cc/roadmap). To suggest something, email [andres@redmage.cc](mailto:andres@redmage.cc?subject=Reliquary%20feature%20suggestion). What changed in each release is in the [changelog](https://reliquary.redmage.cc/docs/changelog.md).

Milestones are built in order, and each starts only after the one before has held for a week of real use.

## Shipped

- **Vaults, files and folders.** Shared vaults of versioned text files for people and their agents, with search. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/vaults-and-files.md))
- **Canon and open files with rules and quorum.** Canon files change only when enough people approve; open files are written directly. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/canon-and-rules.md))
- **Proposals and review.** Approve, request changes, reject or edit then approve, with diffs, threads and snooze. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/proposals-and-review.md))
- **Remote MCP endpoint with OAuth.** One MCP URL for Claude Code, Claude.ai, ChatGPT, Cursor and any MCP client. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/reference/mcp-tools.md))
- **Scoped, expiring access tokens.** Tokens and connections limited to chosen vaults, read-only or read-write, always expiring. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/connections.md))
- **The agent ceiling, enforced in the database.** Agents act as their person but can never approve, manage members, reveal secrets or delete. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/agents.md))
- **Activity and history.** An append-only log of every change, filterable, across vaults or per file. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/activity.md))
- **Vault settings, export, delete and erase.** Rename a vault, export it as a tar.gz, delete it at once, or erase one file's text. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/export-delete-erase.md))
- **Members and invites.** Invite by email with a role, change roles, remove members, leave a vault. (milestone 1, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/members.md))
- **Environment variables.** Encrypted variables per environment, revealed only to people and logged on every access. (milestone 2, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/variables.md))
- **The Reliquary CLI.** reliquary run and env pull deliver variables to a process or a gitignored .env. (milestone 2, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/reference/cli.md))
- **.env imports.** Paste a .env or push one from the CLI; a person applies it in the web app. (milestone 2, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/imports.md))
- **Key rotation and custom environments.** Rotate the encryption key without downtime; owners add their own environments. (milestone 2, in 0.1.0, [docs](https://reliquary.redmage.cc/docs/concepts/variables.md))
- **Versioned releases.** Each release is tagged with a changelog; the footer and /version say which one is running. (in 0.1.0, [docs](https://reliquary.redmage.cc/docs/changelog.md))
- **Public docs and roadmap.** Docs for people and agents at /docs, with llms.txt and every page as Markdown. ([docs](https://reliquary.redmage.cc/docs/index.md))
- **Onboarding templates.** Start a vault as a client engagement, personal projects or a product team, with folders, rules and a README for agents. (milestone 1, [docs](https://reliquary.redmage.cc/docs/concepts/templates.md))
- **OS keychain for the CLI.** CLI sign-ins in the macOS Keychain, the Secret Service on Linux or DPAPI on Windows, else a file. (milestone 2, [docs](https://reliquary.redmage.cc/docs/reference/cli.md))
- **The CLI on Windows and macOS.** reliquary run starts npm, npx and pnpm shims on Windows, and the CLI's tests run on Linux, macOS and Windows. (milestone 2, [docs](https://reliquary.redmage.cc/docs/reference/cli.md))
- **Rate limits on sign-in and MCP.** Limits per address, email, session, client, token and CLI sign-in on sign-in, OAuth, invites, MCP, the env API and forms. ([docs](https://reliquary.redmage.cc/docs/reference/limits.md))
- **Plans and limits.** Account plans limit the vaults you own; each vault's tier limits its people and storage, with usage in Account and Settings. ([docs](https://reliquary.redmage.cc/docs/concepts/plans-and-limits.md))

## In progress

- **A week of real use for the core.** One vault used from ChatGPT, Claude Code and Hermes for a week, canon approved in the browser. (milestone 1)
- **A week of real use for variables.** Projects run with reliquary run and no local .env for a week. (milestone 2)
- **Move to reliquary.redmage.cc.** The website and docs at reliquary.redmage.cc, the web app at app.reliquary.redmage.cc and MCP at mcp.reliquary.redmage.cc; clients sign in again once.
- **Email from the product domain.** Sign-in codes and invites sent by email from Reliquary's own domain.

## Planned

- **Publish the CLI to npm.** @reliquary-ai/cli on npm, so npx works everywhere without a checkout.
- **Shared connections.** A vault holds connections to remote MCP servers; agents use their tools and never see the key. (milestone 3)
- **Tool grants per connection.** Each connection's tools allowed per role, with writes off until an owner turns them on. (milestone 3)
- **Routines.** Declarative automations on a schedule or a change, running with nobody's machine on. (milestone 4)
- **Routine watchdog.** Missed, failed and timed-out runs are recorded and their owner is told. (milestone 4)
- **Per-member variable grants.** Choose which members may use which environments, beyond their role. (milestone 5)
- **Credential requests.** Ask a client for named credentials; they fill a form instead of emailing them. (milestone 5)
- **Emergency access.** A trusted member can request owner access, granted after a waiting period unless declined. (milestone 5)
- **Git mirror.** Every canon change committed to a git remote you choose, one way by default. (milestone 6)
- **Version history and restore.** Browse a file's earlier versions and restore one. (milestone 6)
- **Fuller export.** Exports with the log, earlier versions and proposals, and reliquary export from the CLI. (milestone 6)
- **Chat surfaces.** Use a vault from a group chat, starting with Telegram, showing only what everyone present may see. (milestone 7)

## Considering

- **Billing and plans.** Paying for a bigger plan or a Pro vault through a merchant of record. Plans and limits exist; for now the operator grants them by hand.
- **Public status page.** Uptime of the web app, the MCP endpoint and the database, in public.
- **Client-side encrypted variables.** Values only your members' keys can open, so the operator can't decrypt them.
- **Semantic search.** Find files by meaning, not only by shared words.
- **Approver groups.** Quorums like one approval from legal and one from engineering.
- **Member names over MCP.** Let agents address co-members by display name, without learning email addresses.
- **Service agents.** Headless agents with their own grants that belong to the vault, not a person.
- **SSO.** Sign in through your company's identity provider.