What Zeus does. Each feature is described in the Zeus specifications and implemented in the source. Release 0.0.1a ships the daemon, the command line, the MCP server and the clients; the browser extension is in the source only.
Pre-alpha. Zeus is in pre-alpha. Release 0.0.1a can be tried in the browser on a hosted sandbox or downloaded for Windows and Linux. The binaries are unsigned and many parts are still being tested. See the roadmap.
After a dropped connection, a crash or a reboot, Zeus keeps the bytes it has already saved. It records every saved part in a crash-safe journal and continues from the last committed byte, as long as the server supports resuming.
When a server allows it, Zeus fetches a large file in several parts at once over a limited number of connections, so one slow connection does not hold up the whole file and the site is not flooded with requests.
When a download fails in Chrome or Edge, the Zeus extension offers to hand it to Zeus, which continues from the bytes the browser already saved when the server supports it.
Some files are behind a login. Zeus can use that website session, but only for a site you approve and for the time you choose. Cookies are held in memory for at most 15 minutes and are never written to disk or sent anywhere else.
Each finished file gets SHA-256 and BLAKE3 fingerprints and a receipt that records where it came from and when. If a file does not match a checksum you supplied, Zeus reports the mismatch.
Zeus offers its download tools through MCP, the open standard for giving AI apps tools, so assistants such as Claude Code, Cursor and Codex can call it. The assistant sends a request and Zeus reports the result.
Your AI can request a permission but cannot approve it. Every sensitive step waits for you in the extension or your terminal, and the kill switch withdraws every permission at once.
Zeus runs locally. There is no account, no cloud relay and no telemetry. Nothing leaves your machine except the downloads you asked for.
The app, the engine and the browser extension are licensed under Apache-2.0. The source is public on GitHub, so anyone can read what Zeus does with a login before using it.
You do not need any of this to use Zeus. It is here because a tool that handles logins should explain itself.
| Language | Rust; unsafe code only in small platform modules |
|---|---|
| Transfers | HTTP/1.1 and HTTP/2 over TLS (rustls); range requests with validator checks; parallel parts over a bounded number of connections |
| Crash safety | A transactional journal (redb) written in a fixed order, with a tested kill-and-resume path |
| Integrity | SHA-256 and BLAKE3 for every file; a hash-chained audit log; a provenance record for each file |
| Browser link | Manifest V3 extension; the browser’s native messaging; optional, per-site permissions |
| AI interface | 13 MCP tools named zeus_*, over stdio; one local JSON-RPC API for everything else |
| Footprint | One background process (zeusd) with one local connection point and no network listener; optional bridges, such as zeus-web-bridge, are separate programs |
These parts are implemented in the source and have automated tests, but they are less complete than the features above.
Workflow plans for paginated public pages: Zeus extracts the links, shows what it would fetch in a dry run, and runs only after you approve the plan. Pages behind a login are not supported yet.
Rename and move files by a fixed set of rules, with a dry run first, an approval, and an undo. Format conversion is planned.
Adapters for OpenAI-compatible, Anthropic and local models, off by default and limited to metadata unless you opt in. Today a model can only draft page selectors for a workflow; file classification is planned.
Delivery to Google Drive, Yandex Disk, Baidu Netdisk and rclone remotes after an approval in your terminal. Not yet tested against live accounts.
A restricted desktop client shows real downloads and reports but cannot take approvals. A Firefox build of the extension and a local agent-to-agent (A2A) bridge exist and still need testing.
Zeus 0.0.1a is a pre-alpha release: try it in your browser on a private sandbox, or download it for Windows or Linux. Expect rough edges.
