You ask
A task, in plain words β from the terminal or Telegram.
It runs on your machine, drives your real tools, and keeps every session on your own disk.
$curl -fsSL https://atomicagent.io/install | sh -:::::::--
-::::::::-
-:::::::::-
-::::::::::-
-:::::::::::-
-:::::::::::::-
-::::::::::::::::-
-::::::::::::::::::::::::::::::::-
::::::::::::::::::::::::::::::::::
::::::::::::::::::::::::::::::::::
-:::::::::::::::::::::::::::::::::
=------------:::::::::::::::::---=
@@@@@@@@@@@*-::::::::::::-=+#%%@
-:::::::::::-+#@
-::::::::::=#@
-:::::::::=#
-::::::::-*
-::::::::=
+--------*
%%%%%% βββ βββ βββ βββββ β βββ βββ βββ βββ ββββ βββ βββ βββ βββ βββββ β βββ βββ βββ βββ ββββ βββ
Hermes Agent GAIA Level 1 β 53 real-world tasks on the same model and same machine
Accuracy Β· GAIA Level 1
Hermes Agent 37/53 solved. Grammar-constrained decoding (GBNF) forces structurally-valid tool calls; bounded tails keep reasoning on-budget.
217s vs 351s. cache_prompt + slot_id reuse across steps, plus parallel read-only batches that overlap I/O after a single inference.
Grammar-locked actions and step-by-step checks mean Atomic Agent rarely walks into an unrecoverable wrong answer.
β» the loop repeats β KV-cache keeps each step cheap, nothing re-sent to a server
A task, in plain words β from the terminal or Telegram.
One pass on your own GPU returns a list of next actions β grammar-locked, always valid.
Browser, files and shell β in parallel. Pauses for approval on risky steps.
Loops with cached context, so each step stays fast β until it replies or you stop it.
the engineering that keeps it fast, private, and running on your own machine
A byte-stable prompt prefix means every turn reuses the same cached compute. Nothing is re-encoded, and nothing leaves your machine.
prefix ββββββββββ cachedtail βββ re-computedββββββββββββββββββββstep N KV-cache HIT β
Grammar-constrained decoding forces structurally valid actions, even from tiny local models.
root ::= "[" call ("," call){0,15} "]"call ::= { "tool":β¦, "args":{β¦} }
Curated Q4 GGUF quants fit a long window on an everyday GPU.
fp16 ββββββββ ~24 GBq4 ββ ~6.7 GB
Recall injected in the tail, a few hundred tokens, cache intact.
SELECT content FROM memories_fts ORDER BY rankβ ~320 tokens
It pulls the backend and model for you. No accounts, no bills.
$ atomic-agent models startchat: started, healthyβ on port 8080
Bring your daily tools into one assistant
Local-first agent in one app. Same engine, zero setup. Join the waitlist to get in first!
macOS β’ Linux β’ Windows
Everything you need to know about running a local-first agent.
Atomic Agent is an open-source, local-first AI agent runtime that runs entirely on your own machine. It uses llama.cpp to serve a local model, GBNF grammars to keep tool calls structurally valid, the Model Context Protocol (MCP) to connect external tools, and a SQLite-backed memory. It's built by AtomicBot and released under the MIT license on GitHub at github.com/AtomicBot-ai/atomic-agent.
Yes. Atomic Agent is free and open source under the MIT license, and there's no token bill because the model runs locally on your own hardware. You bring your own llama-server (or let the CLI manage one), so the work runs where you do and the metered cost stays at zero.
Yes β by default the agent loop, the model, and your data all run locally on your own machine, so it works without sending your data to the cloud. Cloud providers are used only if you deliberately configure them. This makes Atomic Agent a strong fit for private, air-gapped, or compliance-sensitive workflows.
On the GAIA Level 1 benchmark (53 tasks, run on the same model and the same hardware for a fair head-to-head), Atomic Agent scored 69.8% versus Hermes' 58.5% β that's +11.3 percentage points more accurate, solving 37 of 53 tasks. It was also about 1.6x faster per task (roughly 217 seconds versus 351 seconds on average). Unlike cloud-first agents, Atomic Agent is local-first and open source, so you keep both the accuracy and full control of your data.
Atomic Agent works with any model your local llama-server can serve via llama.cpp, so you're free to choose the open-weight model that fits your hardware and task. GBNF grammars constrain the model's output so tool calls stay valid regardless of which model you pick. The published GAIA Level 1 benchmark was run on the same model and hardware as Hermes to keep the comparison fair.
Atomic Agent is currently in Developer Preview (v0.1.65) and runs on macOS, Linux, and Windows today. You can follow progress and see current requirements on GitHub at github.com/AtomicBot-ai/atomic-agent.
Yes. Atomic Agent is released under the permissive MIT license, with open weights, open source, and open traces β software you can read and audit all the way down. The full code is on GitHub at github.com/AtomicBot-ai/atomic-agent.
Yes. You can connect external tools through the Model Context Protocol (MCP), teach it repeatable workflows with skills, and even drive it remotely from Telegram. Because it's MIT-licensed and open source, you can also modify the runtime itself.
$curl -fsSL https://atomicagent.io/install | sh Great news,
you are in!
You've joined the waitlist
We'll email you at launch π