Evidence over assumption
Facts retain their origins and confidence. Unresolved relationships, stale evidence and omissions stay visible.
Project context for coding agents
Your codebase, understood.
Workspace Atlas maintains a verified map of your project, so coding agents get the evidence a task needs without starting from scratch.
Local-first Agent-neutral Open source
Your projectA maintained map
Your repositorySource, relationships and tests
AtlasA verified project map
For this taskRelevant evidence. Explicit gaps.
Built for a changing repository.
Why Atlas exists
Stop making models relearn the repository.
A new task should build on what is already known.
Instead, coding agents repeatedly list files, follow imports, locate tests and reconstruct the same relationships. The next session starts over.
Atlas keeps that project understanding available between tasks. It narrows the search to relevant evidence and makes uncertainty visible, so an agent can spend its attention on the work.
Give them the project truth they actually need.
How it works
From repository to relevant evidence.
Keep the project map current. Build a smaller working set around the task. Verify against the source before making a change.
-
Map the workspace
Atlas records files, symbols and relationships locally. Reconciliation updates what changed.
-
Focus on the task
Return relevant code, callers, tests and known gaps within an explicit context budget.
-
Check the source
Verify the live file before change-mode use. Source, builds and tests remain authoritative.
Read the walkthrough
- An unmapped repository forces each coding session to list, search, open and follow references again.
- Atlas reads the workspace, records its structure and publishes an immutable current generation.
- Later reconciliation re-reads changed files while reusing unchanged files and reusable provider evidence.
- For a task, Atlas returns relevant symbols, callers, callees, configuration, tests, effects and known gaps.
- Before change-mode handoff, Atlas checks the live file hash against the recorded source so stale evidence cannot stand in for current code.
- The agent still verifies with source, builds, tests and runtime evidence. Atlas narrows the route; it does not replace proof.
What Atlas stands for
Useful context starts with trustworthy evidence.
A smaller working set is only valuable if an agent can understand where it came from, what is current and what is still unknown.
Your source stays authoritative
The map helps an agent find its way. It does not replace the code, the tests or the evidence from running your software.
Local control
The catalogue lives on your machine. Atlas requires no cloud service and does not edit, move or rename your project files.
Independent of the agent
Use the same evidence layer through the CLI or MCP. Keep your choice of model, editor and engineering workflow.
Explore the technical foundations
- Incremental by design
- Content-addressed revisions avoid reprocessing unchanged files. Reconciliation is explicitly caller-driven, with no background daemon required.
- Consistent generations
- Each candidate activates atomically. Failed candidates never partially replace the last valid generation.
- Bounded context
- DIRECT, ATLAS_LIGHT and ATLAS_DEEP distinguish context depth. Task compilation records selection reasons, costs and omissions.
- Live-source verification
- Before returning change-mode source, Atlas checks the live file hash and blocks stale content.
Start with your own repository
Open source. Ready to inspect.
Atlas v2.0.0 is available as a source release, under MIT or Apache-2.0. Build it locally and explore the evidence behind your own project.
Build Atlas locally
For open source users and developers, the source is the starting point. You’ll need Git and Rust 1.94 or newer, including Cargo.
The commands build the pinned release and map the Atlas checkout itself. Then use a path to your own repository.
On Windows, use .\target\release\atlas.exe in place
of ./target/release/atlas.
Build and explore
git clone --branch v2.0.0 --depth 1 https://github.com/Zerolitter/Workspace-Atlas.git
cd Workspace-Atlas
cargo build --release --locked
./target/release/atlas init .
./target/release/atlas reconcile .
./target/release/atlas status .Source release No prebuilt binaries
Engineering teams
Connect Atlas to your agent through MCP, or use the CLI in your workflow. Start with one repository and inspect how context is selected.
Commercial and research partners
Explore an integration or a pilot around a real engineering question: how much context does a task need to produce a correct result?
Development
Built in the open.
Measured with care.
Smaller context is the research direction. Correctness is the standard. Performance claims need evidence from real tasks.
Follow the project- ReleasedWorkspace Atlas v2.0.0
- The first public source release, with verified project mapping, bounded task context and shared CLI/MCP operations.
- Current focusReliable local evidence
- Storage-safe audits, portable benchmark results and small Atlas OFF / ON comparisons. Evidence for the next decision.
- Research horizonWorking-set qualification
- Study how far task context can be narrowed without losing useful evidence. A research question, not a promised performance gain.
Workspace Atlas
Better context.
A clearer starting point.
Bring a maintained understanding of your project to the next task.