TL;DR
Grok Bot says every agent gets its own computer. True. That computer sits in xAI's datacenter.
Muse gets your mail, your photos, your shopping. Today gets your calendar, your meetings, your work
chat, and promises the memory is "readable, editable, erasable" — on their servers, on their word.
Grok Bot, Muse, Today: different logos, the same trade. They learn everything about you, and they keep
it somewhere you will never be allowed to look.
We don't think you have to accept the second half.
eta is the same product with the address changed. The thing that knows you lives on the machine under
your desk. Read its source, watch what it does, swap the model, open the database, carry the whole
thing to another machine with cp -r.
One process. One SQLite file. Zero required external services. 100% BYOK.
What it is
A workbench where one person directs a crew of always-on agents: each one has a persona, a project it
belongs to, its own tools and its own memory. You talk to them, hand them tasks, put things on a
schedule — and when something needs your OK, they stop and wait for it. Long jobs survive the
conversation that started them; wake-ups arrive only with what's new since the last time the agent
looked.
Nothing here is a black box, because there is no box:
- Every agent has its own computer — and it's yours. Run the host on your laptop and the sessions
run there. Add a second machine and the sessions move: the daemon dials out to you, shows a
fingerprint, and waits for you to approve it.
- 100% BYOK, not "supports BYOK". Your ChatGPT, Grok and Gemini subscriptions by device code, any
OpenAI-compatible endpoint, and the private model in your own rack. A first-class citizen, not a
compatibility mode. Nothing is routed anywhere you didn't point it.
- Memory is a SQLite file. One file, in the same data directory as everything else, queried per
conversation. Open it, grep it, fix a row, delete a row. Delete it and it's actually gone.
- You can see the work. Every turn and every tool call — what it read, what it ran, what it
changed — lands on a timeline instead of a spinner. When an agent wakes up, it gets the increment,
not a rewrite of the whole story.
- Nothing to cancel. No seat, no credits, no rate limit we invented. There is no account to be
banned from, because there is no account.
- The door has a lock that turns itself on. Bind anything other than loopback and the token gate
comes up on its own. A file on disk, mode 0600,
Authorization: Bearer for scripts.
And it's all there to change. Prompts are files, personas are markdown cards, tools are plugins, the
wire is documented frame by frame. If the runtime doesn't behave the way you need, it's not a feature
request away — it's right there.
The part where we disagree
Grok Bot Every agent gets its own computer — in their datacenter, on their dynamic router, which
conveniently never tells you which model actually answered.
Muse Ten million users in forty days, and the most popular thing to do with it is shopping. It's
not a workbench, it's a storefront that remembers your address.
Today "Memory you can read, edit and erase." Great. Ship me the file, then.
Claude Code Useful? Yes. Yours? Not really.
Codex The prompt, the state, the context and the storage move around while you're expected to
smile and trust the dashboard.
OpenCode If the runtime ignores your plan, that isn't autonomy, it's an argument you keep losing.
Run it
git clone https://github.com/0xfe-project/eta.git
cd eta
bun run setup # install dependencies
bun run dev # host + web
Open http://127.0.0.1:3000, add a model service in Settings — an API key, or a subscription account by
device code — then create an agent and a conversation. Data lands in $HOME/.eta, the same directory a
production install uses, so nothing you set up here is throwaway.
bun run check runs the same checks CI and the pre-commit hook run.
If that sounds like your kind of tool: clone it, inspect it, and make it yours.
Manual
Everything below is the reference: what the process is, what the flags are, how to run it on a server,
how to add a machine, where the data lives.
Layout
apps/
eta/ host: one Bun process — WebSocket pipe, cordis plugins, SQLite (main node)
daemon/ eta-daemon: a slim node on another machine, dials back to the main node, runs sessions only
web/ React UI, reads and writes over that same WebSocket
tui/ eta: terminal UI, a client of the host over that same WebSocket
packages/
eta-* kernel, harness, server floor, SSH and git plugins of upstream eta
client-wire-proto, client-contracts wire frames and product target types
docs/architecture/ design notes
Architecture notes:
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
