One app
No implicit all-application loop.
Task-based documentation
Arcane keeps app ownership, shared runtime work, and native toolchains separate. Pick the guide whose boundary matches what you are changing.
Each guide begins with its authority and ends with the exact artifact or evidence it creates.
First project
Use arcane-os@latest, scaffold one browser app, install it, and let the lockfile record the exact selection.
One request
Use new AI(), supply your runtime key, and display the complete response. Includes saved-preference migration.
Try TWiN →On-device speech
Configure Kokoro, load and unmute, stream audio in exact order, and inspect the selected device.
Try speech →Independent source
Own source, tests, adapters, licensing, and one deterministic release bundle in a separate repository.
Arcane checkout
Develop one built-in app or run one exact shared/Core test through the fixed Arcane provider.
Explicit toolchain
Assemble a portable payload, understand the Windows and Mac host-archive requirements, or select checkout-backed Linux and Android providers.
Caller-selected models
Prepare explicit runtimes, retain ONNX graph sessions and use complete named tensors or local chat through Core.
Read local AI →Independent audio streams
Retain a selected Nemotron model, stream mono audio and observe timed generic speaker labels with owned cancellation.
Read diarization →Application-owned storage
Choose one writable file, preserve complete JSON values and drain accepted writes before the native host exits.
Read preferences →One fetched revision
Read complete selected text through a dedicated bare object cache while leaving the application's checkout untouched.
Read snapshots →Explicit generated ownership
Refresh selected documents and retire confirmed SDK-generated files. Use resolvePwaRetirementResponse() in an existing custom host for the disabled worker route, preserving authored workers, other routes and browser saved data.
Read PWA retirement →Independent encoder and decoder
Select the optional Windows x64 NPU encoder, keep its paired model files together and observe actual readiness through native speech.
Read NPU Whisper →Application-owned services
Compose one application dispatcher and connect a page while rendering and service startup proceed independently.
Read development Core →Explicit native session
Own a selected native process, complete live turns, originating server requests and joined shutdown.
Read native sessions →Application-owned tools
Expose authored tools and static resources with complete protocol payloads and cooperative cancellation.
Read MCP STDIO →Selected repository text
Preserve complete selected file content and diagnostics while reporting confirmed and uncertain repository outcomes.
Read repository writing →Application-selected identity
Read separate global, local and effective settings, then select child-only author fields or credential username hints without rewriting Git configuration.
Read Git identity →Explicit native activation
Score complete state, questions and options with Laya FP32 through the existing ONNX owner, retaining raw scores and every graph output.
Read native decisions →Same native owners
Obtain one dependency-ready service without a renderer, reuse its ONNX runtime and retain prepared model files through actual native cleanup.
Read service composition →Captured remote and ref
Observe existing checkout configuration and carry a selected target through pull, push and complete text writing. Select longPaths for a new Windows clone; existing repositories and other platforms retain their settings.
Per-instance presentation
Show Light / Dark / System with complete labels. Choose corner radii, label font and group background through host CSS while retaining the shared preference owner, keyboard focus and selected colors during hover. Optional Core service absence stays distinct from genuine failures.
Read theme configuration →Complete text and audio
Process every Kokoro content token in ordered engine-capacity segments. Select textFormat:'plain' to preserve supplied speech text through SDK preparation.
Application-selected dimensions
Choose logical client dimensions and resizing behavior. The matching Windows host fits initial placement to the usable screen while omitted fields keep existing defaults.
Read window configuration →One application runtime
Select native.launchContext defaults for ordinary executable launch. Resolve matching state, workspace and shared endpoint locations for native UI and MCP, retaining explicit overrides and independent connections.
Read shared hosting →One storage owner
Store the complete selected decision-runtime entry and model resources through DBOPFS, retaining reusable resources, resumable parts and activation-owned cleanup.
Read resource storage →Committed changes
Observe successful DBOPFS writes and removals across live application documents while records remain authoritative.
Read storage events →Independent preparation
Release one preparation's activation interest while preserving other active callers and complete saved audio.
Read preparation lifetime →Boundary check
| I need to… | Workspace | Guide | Result |
|---|---|---|---|
| Create my first app | New external repository | Quick start | Running browser app |
| Keep application source outside Arcane | External repository | External app | Selected app package or bundle |
| Change a built-in Arcane app | Arcane OS checkout | Integrated | One selected app check/package |
| Change shared runtime or Core | Arcane OS checkout | Integrated shared scope | One focused test or canonical check |
| Produce a portable payload or native development artifact | Installed SDK, or app plus compatible Arcane checkout | Native builds | One selected target artifact |
| Publish the SDK | Canonical SDK repository | Publishing guide | Selected package, registry release, and consumer notices |
| Adopt a published SDK release | Consuming application repository | Consumer update guide | Updated declaration, lockfile, and managed projections |
No implicit all-application loop.
No inferred format or architecture.
Every background operation surfaces its result.
Build only the selected application artifact.