CLI & Build
Aephoron doesn't ship a separate command-line tool for identity or credential operations — the "CLI" here is mach, the Servo-heritage build orchestrator used to compile and launch the browser itself.
Build commands
Clone the Aephoron repository (see /contact for source access):
bash
git clone <your-aephoron-checkout>
cd aephoron-main
# Development build
./mach build
./mach run aephoron-desktop
# Release build
./mach build --release
./mach run aephoron-desktop --releaseKnown issue on this pre-release
./mach build can finish the actual compile successfully but fail at its own post-build step (BuildNotFound). If that happens, the binary was still built — run it directly:
bash
./target/debug/aephoron-desktop
# or ./target/release/aephoron-desktop for --release buildsConformance testing
bash
./mach test-wptRuns the Web Platform Tests suite against the Kinetoor engine.
Configuration rules
- Never commit private keys, API secrets, or production credentials.
- Use environment variables for local secrets, never shell history.
- Wallet keys live in the OS secure enclave (Keychain / Credential Guard) — the build tooling never touches them.
See Getting Started for full platform prerequisites, and Web3 & Wallet for the in-browser window.aephoron API that dApps use instead of a CLI.