Repository navigation
v0.1.0 — the first download
The first build of deepnest you can download and open. It is the app, not a promise of one: it starts, opens a page in your browser, and an agent writes a working application on your own machine — React front end, Rust back end, SQLite storage — reloading the page while it writes.
Install
- Download
Deepnest-0.1.0-arm64-mac.dmgbelow. Apple silicon only, macOS 12 or newer. - Open the disk image and drag
Deepnestout of it. - The first launch will be refused: this build is ad-hoc signed and not notarized, because there is no Developer ID identity behind the project. Right-click the app → Open → Open again. macOS remembers the decision for that copy.
sha256 is attached beside the image as Deepnest-0.1.0-arm64-mac.dmg.sha256.
Before your first build, deepnest checks for the platform's C toolchain — Xcode Command Line Tools on macOS (xcode-select --install) — and walks you through installing it, rather than failing halfway through a compilation.
What works
- The binary is self-contained: it carries a minimal Rust toolchain (1.95.0) and the JavaScript runtime (Bun 1.2.21), and unpacks them on first launch, so an app can be built on a machine with nothing installed but the OS and its C toolchain.
http://127.0.0.1:4270/serves the page and opens it in your desktop browser. The control token is written to~/.deepnest/deepnest.token, mode0600.- Every app is a directory under
~/.deepnest/apps/<slug>/: source, config, SQLite database and build output together. There is no remote build server and no cloud account. - Every app has its own agent, in a dialog beside it. It generates and modifies the code, and the page reloads while it works.
- Every tool call runs inside an OS-level sandbox — Seatbelt on macOS — with three modes; protected files are unwritable in all of them.
- A model endpoint over
httpsworks, verified against the machine's own certificate store. Skills load from~/.deepnest/skills/<name>/SKILL.md.
What does not work yet
- macOS arm64 only. There is no Windows build and no Linux build. Both back ends are in the repository and both are exercised in CI on every change; what is missing is the packaging, not the platform. Building from source works on all three today.
- No Developer ID, no notarization, no secure timestamp. The bundle is ad-hoc signed, which is why the first open needs a right-click. A signed build needs a certificate and an app-specific password that no runner holds yet.
- A model endpoint is required. Nothing is built until
base_url/key/modelare filled in on the first-run form. The binary carries the toolchain, not a model, and there is no bundled local model. - No auto-update, no crash reporting, no telemetry of any kind. Nothing leaves your machine except what you send to the endpoint you configured yourself.
What is inside the app
The toolchain travels inside the binary rather than beside it: a packed archive (138,749,755 bytes; Rust toolchain compressed from 486 MB, JavaScript runtime from 60 MB) is embedded at build time and unpacked to the app's own directory on first use. The executable is 145,616,912 bytes; the disk image is ~136 MB.
Built from tag v0.1.0 on a CI runner — never from a laptop.