ATLAS

inferstepAGPL-3.0活跃维护

本地优先的编码 Agent 框架,让大模型在测试时自适应学习并自主专精,适合自托管、注重隐私的开发者。

Adaptive Test-time Learning and Autonomous Specialization

v3.1.7发布于 2026-10-25 18:10 UTC2,111star201fork同步于 2026-11-10 11:45 UTC

怎么上手

由 README 提炼,执行前请确认
curl -fsSL https://raw.githubusercontent.com/inferstep/ATLAS/main/scripts/atlas-bootstrap.sh | bash
硬件要求按 README 说明

README 说明可在单张消费级 GPU 上本地推理,支持 NVIDIA CUDA、AMD ROCm、Apple Metal(macOS 混合)、Vulkan,以及 CPU 支持的硬件;Intel SYCL 在路线图中。README 未给出具体显存数值。

支持 Apple Silicon需要 CUDA支持 ROCm / AMD多卡 / 张量并行有 Docker 镜像
下载:源码 zip·GitHub Releases(安装包)本站不镜像安装包

项目说明

由 README 自动翻译提炼

本地编码智能体,用小模型完成真实软件任务,无需托管 API

本地优先的编码 Agent 框架,让大模型在测试时自适应学习并自主专精,适合自托管、注重隐私的开发者。

核心能力

  • 围绕模型加规划、候选生成、评分、沙箱验证与修复
  • V3 多阶段流水线:PlanSearch 规划、DivSampling 多样候选
  • Geometric Lens 用模型自身嵌入做能量打分,无需外部裁判
  • 沙箱内编译、跑测试并迭代修复生成代码
  • 支持 GGUF 本地模型,含 TUI、代理与 llama-server

容易踩的坑

项目标注为实验状态,3.1 线验证存在已知缺口,不要直接信任其“已验证”结论;需自备兼容的 GGUF 模型,README 未说明是否随安装下载;沙箱命令默认有外网访问,需设 ATLAS_SANDBOX_NET_INTERNAL=true 关闭。

内容由模型根据 README 生成,可能不完整或不准确,以官方文档为准。看原文 README

最近发版

5 个版本v3.1.7
  1. v3.1.7V3.1.7 "Maia"最新正式版2026-10-25 · 2026-10-25 18:10 UTC

    A security release, with installer and build fixes. 3.1.7 fixes four defects with an advisory and several more without one; the advisories are GHSA-543g-qfqh-q498, GHSA-f7jr-f255-59p6, GHSA-cjfr-rrgx-2g38 and GHSA-62cf-6h99-6cv9. Please upgrade.

    Security

    • The service token could go to an address outside the stack. Each service now adds it only to a request for one of the stack's own addresses, checks every step of a redirect again, and drops the token on a redirect to another origin. The Hugging Face token goes only with a download from huggingface.co. (GHSA-543g-qfqh-q498)
    • The proxy could read project files outside the workspace. Eight of its own reads of project files, and the steering status, now read through one confined reader, as the file tools do. (GHSA-f7jr-f255-59p6)
    • The TUI wrote control characters from the proxy to the terminal. It now shows each control character and direction mark marked; the stored text does not change. (GHSA-cjfr-rrgx-2g38)
    • A tool could use a path the workspace check had not passed. The workspace check and a tool could read different values from one tool call, so the tool could use a path the check had not passed. The check now reads a call's arguments once and hands the tool that one reading; a call it cannot read that way is refused before the tool runs. (GHSA-62cf-6h99-6cv9)

    Security fixes without an advisory

    • The lens and the V3 service could not read the token file that atlas init makes, so they ran without the token check. They now run as the installing user, every service stops with a message when the token file is there but cannot be read, and atlas doctor reports it.
    • atlas rollback checks the target images' signatures before it changes .env or pulls anything, as atlas upgrade does.
    • atlas lens check reads cost_field.pt only in torch's restricted mode, as the lens service does.
    • The proxy refuses a POST whose body is not JSON (415) and a request from a web origin that is not on the new ATLAS_ALLOWED_ORIGINS setting (403). The TUI and the CLI send neither, so they are not affected.
    • A workspace's .atlas/config.toml can no longer make run_command run on the host: only the operator chooses the host, with ATLAS_VERIFY_IN=host together with ATLAS_TRUST_MODE=fully-trusted.

    Fixes

    • Each build of the model server names the processor level of its CPU part, so the image runs on every amd64 processor with AVX2, whatever processor built it. (#427)
    • uninstall.sh --data names every folder it removes, the projects folder included, and refuses an empty setting. (#414)
    • The bootstrap script tries a failed download again (#406), and the installer keeps its downloads and logs in a temporary folder of its own (#409). The bootstrap's TUI build runs the Go that the script found (#535).
    • The proxy image and the TUI build with Go 1.26.10, which has the fixes of the Go standard library. The TUI's modules move to their fixed versions: x/net v0.60.0 and x/text v0.42.0 (#542), and goldmark v1.7.17.

    Known issues in 3.1.x (fixes planned for 3.2.0)

    Review what ATLAS writes and run your project's own tests before you rely on a "done".

    • A failing V3 candidate can be written as verified (3.1.0 to 3.1.7). When the V3 pipeline handles an edit and no candidate passes its tests, even after repair, ATLAS writes the best-scoring candidate anyway and tells the model the edit was verified. The fix is on dev (e8112d3).
    • C, C++, Swift, JSX, Vue and Svelte files are checked as Python (3.1.6 and 3.1.7). Their candidates fail, and the issue above then applies.
    • **The lens gives no
  2. v3.1.6V3.1.6 "Maia"2026-10-01 · 2026-10-01 20:21 UTC
    查看更新说明

    A security release. 3.1.6 fixes a way for a command behind a prefix or a nested shell to skip ATLAS's command policy: GHSA-m9w4-p32x-chx9. Please upgrade. Thanks to @Rendegou, who reported and fixed it.

    Security

    • The command policy now looks past command prefixes and checks the command each nested shell, eval or env -S layer would run, up to 16 layers.
    • A command whose quoting or layers can't be checked completely is refused, with a message saying so.
    • One rarely used form is now refused: eval of generated command text with nested quoting. Run the generated command directly instead.

    Known issues in 3.1.x (fixes planned for 3.2.0)

    Review what ATLAS writes and run your project's own tests before you rely on a "done".

    • A failing V3 candidate can be written as verified (3.1.0 to 3.1.6). When the V3 pipeline handles an edit and no candidate passes its tests, even after repair, ATLAS writes the best-scoring candidate anyway and tells the agent the edit was verified. The fix is on dev (e8112d3).
    • C, C++, Swift, JSX, Vue and Svelte files are checked as Python (3.1.6). Their candidates fail, and the issue above then applies.
    • The lens gives no usable signal (3.1.3 to 3.1.6). It reports calibrated and interventions active, but its per-token scoring cannot run under the default settings, so it cannot veto or alert, and its scores barely change between inputs (#281).

    Upgrade

    • Existing install: in your ATLAS folder, run git pull first, then atlas upgrade. Or re-run the install command.
    • New install: curl -fsSL https://raw.githubusercontent.com/inferstep/ATLAS/main/scripts/atlas-bootstrap.sh | bash

    Verify

    • The tag v3.1.6 is SSH-signed by a key in .github/allowed_signers (in a checkout: git -c gpg.ssh.allowedSignersFile=.github/allowed_signers verify-tag v3.1.6).
    • The images are signed by the inferstep/ATLAS build workflow:
      cosign verify --certificate-identity https://github.com/inferstep/ATLAS/.github/workflows/build-images.yml@refs/tags/v3.1.6 \
        --certificate-oidc-issuer https://token.actions.githubusercontent.com ghcr.io/inferstep/atlas-proxy:3.1.6
      

    To hear about releases only, choose Watch → Custom → Releases on the repository page.

    Full list: CHANGELOG.md.

  3. v3.1.5V3.1.5 "Maia"2026-09-29 · 2026-09-29 23:56 UTC
    查看更新说明

    A security release. 3.1.5 fixes a way to skip ATLAS's workspace check with an argument name in another letter case: GHSA-c3p6-m657-h629. Please upgrade.

    Security

    • Tool argument names must now be lowercase, as every tool's names are. A name in another letter case (for example "PATH") or with non-ASCII letters is refused. Before, such a name skipped the workspace check, and in 3.1.4 a "Command" argument also skipped the destructive-command deny-list.
    • insert_after's path is now checked at dispatch, like every other write.

    Upgrade

    • Existing install: in your ATLAS folder, run git pull first, then atlas upgrade. Or re-run the install command.
    • New install: curl -fsSL https://raw.githubusercontent.com/inferstep/ATLAS/main/scripts/atlas-bootstrap.sh | bash

    Verify

    • The tag v3.1.5 is SSH-signed by a key in .github/allowed_signers (in a checkout: git -c gpg.ssh.allowedSignersFile=.github/allowed_signers verify-tag v3.1.5).
    • The images are signed by the inferstep/ATLAS build workflow:
      cosign verify --certificate-identity https://github.com/inferstep/ATLAS/.github/workflows/build-images.yml@refs/tags/v3.1.5 \
        --certificate-oidc-issuer https://token.actions.githubusercontent.com ghcr.io/inferstep/atlas-proxy:3.1.5
      

    To hear about releases only, choose Watch → Custom → Releases on the repository page.

    Full list: CHANGELOG.md.

  4. v3.1.4V3.1.4 "Maia"2026-09-27 · 2026-09-27 22:32 UTC
    查看更新说明

    The first release from ATLAS's new home, inferstep/ATLAS. It carries the security fixes below, the move to the new image owner, and the new contributor setup, on top of the changes on main since 3.1.3 (see the end of these notes).

    Security: commands ran without approval, and file search read credential files

    • run_background started any command without the approval prompt in the default and accept-edits modes, and was checked against a narrower deny-list than run_command (env rm -rf / and (rm -rf /) passed it). Outside yolo, every tool that runs a command now asks, and one command policy covers both. It looks where a command can start: behind env, nohup, nice, time, timeout or exec, in a subshell and in a command substitution. grep mkfs notes.txt is no longer refused.
    • search_files returned the contents of credential files that read_file refuses (.env, keys, cloud credentials) and followed symlinks out of the workspace. It now skips both and reports how many credential files it skipped (skipped_credential_files). move_file refuses to move a credential file to another name, and insert_after gets the write deny-list. The rules follow what a tool does, and a test fails when a new tool is outside them. Shell commands are not covered, and the docs now say so.
    • Approval prompts cut a command at 100 characters, so the end of a chain was never shown. The proxy sends the whole command, and stop_background names its job.
    • In the TUI, one "allow for session" answer on a deletion approved every later deletion without showing which file, and the proxy honoured delete_file in session_allowed_tools from any client. Each deletion is now asked about on its own: the TUI never auto-answers or sends a session approval for delete_file, the proxy ignores one, and a new session starts with no approvals. The TUI prompt shows the whole command, wrapped; one too long for the screen keeps its first and last lines in view and says how many are not shown.
    • The TUI's chat stream, events stream, raw demo lane and feedback calls never sent the service token, so on an install with one they failed with 401. Every request to the proxy now sends it, ahead of an api-keys token.

    Moved to inferstep/ATLAS

    • The repository is now github.com/inferstep/ATLAS. Old links, git remotes and the install one-liner redirect.
    • Images are published under ghcr.io/inferstep/atlas-* and signed by the inferstep/ATLAS build workflow. ghcr.io/itigges22/atlas-* stays published for existing installs but gets no new versions.
    • Existing installs: re-run the install command, or git pull and then atlas upgrade. atlas upgrade, atlas config migrate and a bootstrap re-run move ATLAS_GHCR_OWNER=itigges22 in .env to inferstep. A failed upgrade or a rollback puts it back. An install pinned to a release from before the move keeps the old owner until it upgrades, and an owner set in the shell is left alone.

    Fixed

    • golang.org/x/net in the TUI is now v0.55.0 (GHSA-5cv4-jp36-h3mw).

    Contributors

    • New issue forms for bugs, features, tasks, docs, spikes and RFCs, and a fuller pull request template. CONTRIBUTING is rewritten as the path from an issue to a release. GOVERNANCE describes the trust ladder and the RFC flow. New TRIAGE and INCIDENT_RESPONSE guides.
    • The public Roadmap board has a Start Here view. The atlas-bot handles /claim and /unclaim, reminds and releases stale claims, adds area labels and welcomes newcomers.
    • Pull requests now also need the dependency review and a conventional tit
  5. v3.1.3V3.1.3 "Maia"2026-07-06 · 2026-07-06 18:58 UTC
    查看更新说明

    The production-platform release: the machinery around running, upgrading, and trusting an ATLAS install.

    Highlights

    • Staged upgrade & rollback — atlas upgrade records a restore point (tag + image digests + .env backup), verifies cosign signatures on the target images, waits for readiness, runs a smoke check, and automatically restores the previous release if any step fails. atlas rollback returns to the restore point on demand; atlas diagnostics collect produces a shareable, secret-filtered support bundle.
    • SQLite state store (ADR 0007, core implementation from #128 by @HarshalPatel1972) — the lens's pattern cache, co-occurrence graph, router posteriors, task queue, and metrics now live in one WAL-mode SQLite file on the lens-state volume. The Redis service and its configuration are gone; one less dependency, and state backup is a single file.
    • Signed artifact manifests — atlas artifact verify | snapshot | rollback: SSH-signed provenance manifests over lens/ASA bundles with per-file SHA-256 verification, plus one-generation bundle rollback.
    • Observability — structured JSON logs (ATLAS_LOG_FORMAT=json) with X-ATLAS-Request-ID correlation across proxy → llama/v3/lens/sandbox; a stable error-code taxonomy and OpenAPI 3.1 spec for the proxy surface; command-execution trust modes (ATLAS_TRUST_MODE).
    • Interactive permissions & sessions — destructive tool calls prompt for approval in default/accept-edits modes; the TUI saves sessions and atlas --continue / --resume picks them back up.
    • Typed configuration — atlas config validate | migrate: schema-checked .env with forward migration (deprecated keys, including the removed ATLAS_REDIS_*, are cleaned up automatically).
    • Install trust — release-pinned installs: ATLAS_BOOTSTRAP_REF=v3.1.3 pins the checkout to this signed tag and the images to the matching cosign-signed digests. A review-before-running variant is documented beside the one-shot install.
    • Two adversarial review sweeps fixed 33 confirmed bugs across the proxy, CLI, services, and CI — including a trust-mode bypass, several restore-path failures, and CI gates that could never fail.

    Upgrading

    atlas upgrade --to v3.1.3
    

    Existing installs: the Redis container and redis-data volume are no longer used after this upgrade (docker volume rm <project>_redis-data reclaims the space). Learned lens state starts fresh in SQLite and rebuilds through use.

    Full details in CHANGELOG.md.

用户点评

登录用户的真实使用记录,可按版本和硬件筛选
共 0 条

    还没有人点评。第一个说出真实体验的人最有价值。

    README 原文

    未翻译

    Status: experimental. The 3.1 line's verification has known gaps, listed under Known Limitations below. The fixes are planned for 3.2.0. Until then, do not rely on a "verified" or "completed" from ATLAS: review what it writes and run your own tests.

    🌎 What is ATLAS?

    ATLAS is a local coding agent that brings frontier-style reasoning and verification to compact open models. It puts more intelligence in the system around the model (planning, candidate generation, quality scoring, sandboxed testing, and repair) so smaller models can tackle real software work entirely on your own hardware, without a hosted API or per-token fees.

    💡 Why ATLAS?

    • Get more from smaller models. ATLAS adds planning, candidate selection, verification, and repair around the model instead of depending on a single generation.
    • Verify before accepting. Generated code can be compiled, tested, and corrected inside an isolated execution environment.
    • Spend compute where it matters. Straightforward edits take a shorter path, while harder tasks receive more candidates, reasoning, and validation.
    • Run your own model. Use a compatible GGUF model on NVIDIA, AMD, Apple Silicon, Vulkan, or CPU-supported hardware.
    • Keep control local. ATLAS does not intentionally upload your repository or prompts to a hosted model or ATLAS-operated service. Sandbox commands have outbound network access by default; set ATLAS_SANDBOX_NET_INTERNAL=true to disable it.
    • Own the full stack. ATLAS is open source and self-hosted. It requires no hosted model or third-party model-provider API key; a local per-installation service token authenticates ATLAS services.

    📰 Latest News

    • 2026-10-24 - V3.1.7 "Maia" released - security fixes for the service token, the proxy's file reads, the TUI's terminal output, the tool-call path check, where commands run, rollback signatures, the lens check's file loading and the proxy's requests, and installer fixes (advisories). Please upgrade.
    • 2026-10-01 - V3.1.6 "Maia" released - security fix for the command policy (GHSA-m9w4-p32x-chx9, reported and fixed by @Rendegou). Please upgrade.
    • 2026-09-29 - V3.1.5 "Maia" released - security fix for tool argument names (GHSA-c3p6-m657-h629). Please upgrade.
    • 2026-09-27 - V3.1.4 "Maia" released - the move to inferstep/ATLAS, security fixes (GHSA-5hvw-59r4-7rcq), and the contributor setup.
    • 2026-07-06 - V3.1.3 "Maia" released - production-platform pass: staged upgrade/rollback with auto-restore, SQLite state store (no more Redis), signed artifact manifests, structured logs + correlation IDs, interactive permissions, session resume, and two adversarial bug-fix sweeps
    • 2026-06-17 - V3.1.2 "Maia" released - broader hardware reach (ROCm / Metal / Vulkan), bring-your-own-model Lens + ASA training, in-the-loop lens retraining from your own workloads, and an agent-reliability pass
    • 2026-05-12 - V3.1.0 "Maia" released - native Bubbletea TUI, one-command bootstrap, streaming Lens + ASA activation steering, AST-aware surgical edits
    • 2026-03-26 - Hacker News front page - 489 points, 285 comments
    • 2026-03-05 - V3.0 released - the multi-phase V3 pipeline on frozen Qwen3-14B. The 74.6% LiveCodeBench figure published with this release is withdrawn: the benchmark runner never ran LiveCodeBench's hidden tests, and it counted a task as passed when any of three candidates, or a repair shown the failing output, passed the examples printed in the problem (withdrawal notice). ATLAS will be re-measured once the current product is re-verified.
    • 2026-02-18 - V2.0 released - benchmark infrastructure, HumanEval/MBPP/LiveCodeBench/GPQA/SciCode evaluation suite

    ⭐ Star History

    Updated weekly (Mondays, via GitHub Actions).


    🧱 What ATLAS Does

    1. atlas-tui - native Bubbletea terminal UI; the canonical chat client. Type atlas in any project directory to launch it.

    2. atlas-proxy - Go agent loop that orchestrates the system.

      • Tool-call routing - classifies file operations by complexity tier
      • Grammar enforcement - GBNF schemas strongly steer output toward the expected JSON shapes, with proxy-side recovery for malformed or truncated output
      • BiasBusters - four composed mitigations (descriptions, grammar bans, system notes, ASA steering) that push the model toward structural_edit for structural code edits
      • Safety limits - turn caps, token budgets, timeouts
    3. V3 Pipeline - multi-phase code generation; turns a single prompt into a verified candidate.

    4. Geometric Lens - energy-based scoring over the model's own embeddings, no external oracle. (What is a "Geometric Lens"?)

      • C(x) Cost Field - model-hidden-dim→512→128→1 MLP that scores candidate quality
      • G(x) Quality Prediction - XGBoost ensemble used for selection
      • Per-step scoring - per-token C(x)/G(x) scoring of writes, with per-model calibrated thresholds driving interventions
      • Pattern cache - lessons from previous sessions, injected into new runs
    5. Sandbox - isolated execution for build verification.

      • Multi-language execution: Python, Rust, Go, C, Shell, others
      • Compilation and linting before scoring
      • Runs both generated and existing test suites
    6. llama-server - local LLM inference on one consumer GPU.

      • GPU-accelerated quantized inference (Q6_K / Q4_K_M) - NVIDIA CUDA, AMD ROCm, Apple Metal (macOS hybrid), and Vulkan; Intel SYCL on the roadmap
      • Grammar-constrained decoding at the token level
      • Self-embeddings, so the lens doesn't need a second model

    Full documentation (setup, architecture, configuration, troubleshooting, benchmark reports, and the research behind each component) lives in the docs/ directory.


    🚀 Get Started

    One-shot install:

    curl -fsSL https://raw.githubusercontent.com/inferstep/ATLAS/main/scripts/atlas-bootstrap.sh | bash
    

    Prefer not to pipe a moving script into bash? Same installer, two more careful ways to run it:

    # Pinned to a release: script, checkout, and images all at the signed tag
    curl -fsSL https://raw.githubusercontent.com/inferstep/ATLAS/v3.1.7/scripts/atlas-bootstrap.sh \
      | ATLAS_BOOTSTRAP_REF=v3.1.7 bash
    
    # Review before running
    curl -fsSL -o atlas-bootstrap.sh https://raw.githubusercontent.com/inferstep/ATLAS/main/scripts/atlas-bootstrap.sh
    less atlas-bootstrap.sh
    bash atlas-bootstrap.sh
    

    The script detects your distro (Ubuntu, Debian, RHEL, Fedora, Rocky, Alma) and your GPU vendor (NVIDIA → nvidia-container-toolkit; AMD → ROCm device passthrough), installs the appropriate runtime, downloads the model weights, builds the ASA steering vector, and starts the stack. Expect 10-30 minutes; the model download is the bottleneck.

    Then in any project directory, run atlas.

    Requirements

    GPU16 GB+ VRAM. NVIDIA (CUDA, Supported), AMD (ROCm, Community-tested), or Apple Silicon (Metal, macOS hybrid, Supported); Vulkan (Preview) covers most other GPUs. The prebuilt CUDA image targets Blackwell (RTX 50xx); older NVIDIA GPUs need a one-time local rebuild (see SETUP.md § CUDA Compute Capability). Levels: SUPPORT_MATRIX.md; GPU list: SETUP.md § Supported GPUs. To size a specific model to your card, see What fits on my GPU?.
    RuntimeDocker (NVIDIA: + nvidia-container-toolkit; AMD: standalone Docker is enough) or Podman
    Python3.9+
    Disk~20 GB CUDA / ~22 GB ROCm (model weights + container images)

    Apple Silicon runs natively through the macOS hybrid Metal path (native llama-server + Docker for the rest - see SETUP_MACOS.md); Intel Arc (SYCL) is on the roadmap. For the manual install path (Docker Compose, bare-metal, K3s) and the full set of bootstrap flags, see SETUP.md.


    ⚠️ Known Limitations

    • Linux Docker stack, plus a native macOS path. NVIDIA (Supported), AMD ROCm (Community-tested), and Vulkan (Preview) Docker paths exist today; Apple Silicon (Supported) runs via the native macOS hybrid Metal path (#32). Intel Arc / SYCL is Roadmap. Level definitions: SUPPORT_MATRIX.md.
    • ATLAS has no current benchmark result. The V3.0 LiveCodeBench figure is withdrawn (see Latest News), and no capability or reliability figure has been measured for the current release. Numbers will be published only after a re-measurement on held-out tasks; model-specific results are tracked in #28.
    • Known issues in 3.1.x (fixes planned for 3.2.0). Review what ATLAS writes and run your project's own tests before you rely on a "done".
      • A failing V3 candidate can be written as verified (3.1.0 to 3.1.7). When the V3 pipeline handles an edit and no candidate passes its tests, even after repair, ATLAS writes the best-scoring candidate anyway and tells the agent the edit was verified. The fix is on dev (e8112d3).
      • C, C++, Swift, JSX, Vue and Svelte files are checked as Python (3.1.6 and 3.1.7). V3 handles these files but tests their candidates as Python, so the candidates fail, and the issue above then applies.
      • The lens gives no usable signal (3.1.3 to 3.1.7). It reports calibrated and interventions active, but with the default settings its per-token scoring cannot run, so it cannot veto a candidate or raise an alert, and its scores barely change between inputs, so V3 always gets three candidates. The calibration files in the repository were also fit to a different cost field than the published one (#281).
    • Complex feature additions can be inconsistent. Compact models sometimes spend agent turns exploring an unfamiliar codebase before writing code.
    • Grammar-constrained decoding is slower than unconstrained decoding.

    🗺️ Roadmap

    V3.1.3 "Maia" - Current release. Production-platform pass on top of V3.1.2: staged atlas upgrade/rollback with automatic restore, SQLite state store replacing Redis (ADR 0007), signed artifact manifests, structured JSON logs with cross-service correlation IDs, interactive permission prompts, session resume, typed config validation/migration, and two adversarial bug-fix sweeps (33 confirmed fixes).

    V3.1.2 "Maia" - Broader hardware reach, bring-your-own-model training, and an agent-reliability pass on top of the V3.1.0 base (TUI, one-command install, streaming Lens + ASA).

    • Hardware reach: AMD ROCm via llama.cpp incl. RDNA4 / RX 9070 (gfx1200/gfx1201) (#26); Apple Silicon native macOS hybrid Metal path (#32, see SETUP_MACOS.md); Vulkan universal fallback covering AMD / Intel / Snapdragon / Apple-via-MoltenVK / CPU (#114).
    • Bring-your-own-model: local Lens training pipeline (atlas lens build / retrain, #100) and ASA per-model calibration parity (atlas asa check/build/publish, #113) - train Lens + ASA artifacts for additional GGUFs, with per-model operating thresholds that ship with the lens.
    • In-the-loop lens training: rate passes in the TUI (/good · /bad · /review · /deny) → collected, weighted samples → atlas lens retrain on your own workloads.
    • Agent reliability: tool-result visibility fix, read-dedup, traceback → directed-edit, move_file, pip-install / case-mismatch steers, sandbox shell policy + host-sized cgroup limits.
    • Structural call-graph reasoning (#39 / #125, thanks @yogthos); ARCHITECTURE.md translated to zh-CN / ja / ko (#25).

    V3.2 - Next milestone: deeper code reasoning.

    • RPG-style architecture-first planning was built (#120), A/B-measured, and removed: no improvement on the reference model at ~10x planning latency. #148 is the record; the design study is docs/reports/RPG_WAVELET_PLANNING_V3_2.md.
    • Structural code reasoning (tail) - deepen the shipped call-graph layer (#39).
    • Reasoning with sampling - efficiency and quality gains (#9).
    • Deferred infra: automated HuggingFace submission pipeline (#102); ROCm on K3s / Kubernetes; formal registry-model benchmarks - LiveCodeBench, GPQA Diamond, SciCode (#28).

    Backlog / help wanted

    • Hardware: ARM64 multi-arch builds (#115), multi-GPU for larger models (#34), Intel oneAPI / SYCL (#27).
    • Tooling: VS Code / JetBrains extension (#35).
    • Sandbox languages: Java / Kotlin (#29), Ruby / PHP (#30).
    • Architecture: model-agnostic platform (#66).

    ❤️ Support ATLAS

    ATLAS is built by a single college student in his free time on a single consumer GPU (the story behind ATLAS). If the project has been useful to you and you want to help keep it sustainable, please consider sponsoring on GitHub.

    Sponsorship directly funds:

    • Compute & hardware - more GPUs for faster benchmark iteration, access to architectures the maintainer can't afford (AMD ROCm, higher VRAM cards, cloud rentals for larger-model experiments).
    • Contributor bounties - meaningful compensation for external contributors who put real time into substantive PRs, so ATLAS can grow faster than a single-person pace allows.
    • Research - continued academic engagement around the architecture, from future workshop and conference submissions to paper writing and collaborations that validate and extend the approach.
    • Community - continued support for the community and platforms ATLAS runs on, including documentation, user-facing channels, and educational content that help ATLAS reach more developers and better serve the ones already using it.

    Every sponsor is credited in the release notes of the version they helped fund.


    🤝 Contributing

    ATLAS is developed in the open and welcomes contributors and core maintainers. Bug fixes, accelerator support, and larger subsystem work are all welcome.

    Found a bug or hit a wall? Open an issue - you don't need to submit a fix. Bug reports and feedback help just as much as code.

    See CONTRIBUTING.md for guidelines and the repository map for an overview of the codebase layout.


    📄 License

    Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).