· OneNess TOR

real files · real commands · real preview

DarkWeb App Builder + Rust Program Builder

Two workbenches on this node: web (HTML / CSS / JS / Node) and rust (a real cargo project). Every prompt becomes real files, and every button is a real API call — read, create, write, delete, run, install dependencies, start the app and watch it in the preview window. Sign in at /wallet — your own wallet owns what you build here (create, read, write, run, install, AI-edit, serve and deploy). No admin token is involved. Nothing is charged here: deploy performs a real ADD_ONION and returns the onion URL.

model …

project

new project name

kind

—

Files

no project yet

new file path

Editor

no file

—

Prompt the builder

ai edit

model for this surface

what should it do?

Every answer is a JSON file plan applied to the project — keep prompting to edit the app.

Run & dependencies

command (argv, no shell)

Allowed: cargo, rustc, python, pip, node, npm, npx, git, make, dotnet, go, java, pytest. No shell operators (; | && >) — one command per call.

install dependencies

$ ready

Preview window

not running

—

process log (real stdout / stderr)

—

web → ADD_ONION · rust → cargo build + owner-only program

Deploy

Deploy a DarkWeb app to get a real .onion URL, or a Rust program to compile it and register an owner-only program on the chain.

DarkWeb: Tor's control port performs ADD_ONION and points /builds/<id>/ at this node — the answer is the onion URL, or the exact Tor error. Rust: cargo build --release runs for real; the binary is sha3-hashed and stored as a program owned by the deploying wallet (only that wallet sees its source, state and build, and only it can manage/run it). The chain charges no transaction fee; nodes and platforms add their own fees.