ontology-atlas

English | 한국어 | 日本語 | 简体中文

Why

Coding agents now change code faster than a team can keep a picture of it in their heads. Atlas keeps that picture beside the code: what each part is for, which files implement it, what depends on what, and what nobody knows yet. Your agent reads it before a task and proposes updates after; you keep, correct or reject each change as a Markdown diff.

• Your agent starts with context. Claude Code, Codex, Cursor and Antigravity read the concepts, code paths, dependencies and open questions a task touches, over MCP.
• You own the record. One Markdown file per concept in an atlas/ folder, versioned and reviewed in Git like the code.
• You decide what is true. Agent proposals stay proposals until you accept them.
• It says what it does not know. A line on the map is a declared relationship, not proof of runtime impact; missing evidence shows as unknown, never as safe. Compact task handoffs preserve whole uncertainty statements or report omissions with the document reads needed to inspect them. Initial analysis also excludes literal Markdown examples and marks truncated document evidence for review with a hash-bound original-source follow-up. Task matching and navigation use authored evidence; code examples, hidden comments and blockquotes cannot supply capability claims or work coordinates.

See it

Flat maps show domain labels with spaced outward capability branches and thin directed dependencies. Mark sizes and detail fade with the available row spacing as you zoom. Implementation elements form compact groups beside their capability, with readable names and membership stems. The overview limits crossing lines; inspecting an endpoint reveals its recorded connections and explicitly labelled bundle counts. Gentle local curves and screen-sized arrows keep direction legible. Individual relationship explanations and declaring documents remain available in relation review. A persistent bright outline distinguishes the selection, while amber exclamation marks mean evidence needs rechecking; the map key explains both marks and direction. Larger maps keep the same branch grammar with shorter previews and stable column groups. More/collapse controls disclose actual capabilities; focused areas keep that grammar and a labelled return to the full map. The Concepts panel separates searching, selecting and expanding the tree. Below 1280 px it temporarily folds beside an inspector and returns when that inspector closes; it can still be reopened explicitly. Project details keep dated source checks under Check record.

Empty folders and concepts without relationships reveal their start actions when returning to Map from another screen. Starter creation keeps a persistent retry action after a write failure, including partial creation. Retrying preserves existing files and writes the missing starter files; completion produces one success notification. Popup tours are retired. Folder opening guidance, contextual help and keyboard help remain. Returning from a concept's full reading view keeps that concept selected on the map. Returning through primary navigation restores the selected map concept and Concepts search for the same opened folder, in memory for this session. Ordinary unsent chat text survives screen changes in memory for the same opened folder; restoring it never sends a request.

Library service setup is app-only: Atlas confirms folder and keychain saves before activation. A browser offers the app or Add files without collecting service tokens. Local setup does not verify service access. Library check history lists executed checks first; recorded sleep gaps are available through an explicit display control.

Quick start

1. Install the app from the download page, or open the browser version.
2. Open a folder. Atlas reads its Markdown in place, or starts an atlas/ folder in your repository, and shows the path before it writes anything.
3. Connect your agent. In Agents › MCP, press Connect for your tool, restart the agent, and ask about your next task.

macOS (Apple Silicon) is signed and notarized and carries the MCP server inside the app. Windows x64 is an unsigned beta. On Linux, use the browser version or run the CLI and MCP server from a source checkout. Releases list each version's files and checksums.

How it works

your-repo/
├── src/
└── atlas/                 ← cloned, branched and reviewed with the code
    ├── project.md
    ├── domains/  capabilities/  elements/
    ├── sources/           documents kept exactly as they arrived
    └── wiki/              pages written from those sources, every fact cited

A Markdown file whose frontmatter has kind: is one concept. Its uid never changes, its slug is its current address, and its path names the code it describes. The map, documents, Library, Insights and Git screens all read these files.

Your agent reaches the folder two ways:

• MCP: the agent starts the Atlas MCP server, which reads and writes the folder on disk, even with the app closed. Connect an agent · MCP reference
• ACP: Claude Agent and Codex also run in the app's own chat; each write waits until you allow it. Agents

A project's source-path repair opens the affected concept and recorded relative path; stale or missing targets require remeasurement.

Project checks distinguish a document changed since its last meaning review from malformed input. They ask for review and explicit re-finalization; supported code paths and saved changes do not accept the meaning. Analysis filters capabilities by changed, missing or unchecked source evidence while keeping the selected claim open.

Analysis compares recorded dependencies between responsibilities, then opens the exact concepts and declaring document beside the selected claim. Implementation records, unchecked source and missing explanations stay distinct. In the macOS app, documents and cited files can be dated in their respective bound Git repositories; missing access or history stays unknown, and a folder chosen for reading must match the existing connection. Analysis

Local-first

The installed app's Changes prototype reads a chosen Git repository without requiring an ontology. Public GitHub PR reading is the recommended first step; commit-only explanations remain an explicitly limited alternative. Failed PR refreshes keep previously read versions and explanations with a freshness warning. Explicitly read public PR originals have bounded local copies that can reopen after restart, labelled with their original read time and unchecked current GitHub state. Saved copies can be cleared in Changes even without a source folder. Known GitHub rate limits show a retry time and pause PR reads while local sources remain usable. Select daily, weekly, monthly, yearly or custom local dates; inspect full commit messages, touched file