Install
Atlas installs with one line. The installer brings everything it needs, its own Python, Node and tools, each checked against a pinned hash, then builds the desktop app and opens it.
Windows
In PowerShell:
irm https://gist.githubusercontent.com/marqueskaio/4e04aef1d784d6d6518f12e466621266/raw/install.ps1 | iexmacOS and Linux
In a terminal:
curl -fsSL https://gist.githubusercontent.com/marqueskaio/4e04aef1d784d6d6518f12e466621266/raw/install.sh | bashThe first time it opens
- The app asks for an API key from a model provider: OpenAI, Anthropic, Google Gemini or OpenRouter. Atlas checks the key without spending anything and keeps it in its encrypted vault.
- Start talking. Each conversation can switch models.
- To use your coding agents, open Settings, then Executors: it lists the harnesses on this computer, Claude Code, Codex, the Gemini CLI and DeepSeek’s. Turn on the ones you use; each one shows up in the Executors tab of the sidebar, and one not installed shows the command that installs it.
Updating
Run the same line again, or type:
atlas updateIf a step of the update fails, Atlas goes back to where it was.
In a container
Atlas also runs with Docker Compose. From a clone of the repository:
git clone https://github.com/marqueskaio/atlas.git && cd atlasdocker compose up -d --builddocker compose exec atlas atlas secrets set OPENAI_API_KEYdocker compose exec atlas atlas server tokenThe third line asks for the key without showing it; use GEMINI_API_KEY or another provider’s name for another provider. The last line prints the token the desktop app needs: open the app with ATLAS_DESKTOP_URL=ws://127.0.0.1:18790/ws and ATLAS_DESKTOP_TOKEN set to that token.
The container listens only on the host’s loopback, and your data lives in a named volume. A backup leaves on standard output, never with the keys:
docker compose exec -T atlas atlas backup -o - > atlas.zipatlas restore puts a backup into any home.