ac4bf666e6
CLAUDE.md said "Rust components are guest-side: they run inside a virtual machine". That was true of every one of them until yesterday and is now false, which makes it worse than a gap -- it is instruction that would send someone looking for nesdoctor in the wrong half of the system. Records the two things about it that hold nowhere else in this tree. Its dependency list is part of its interface, because it is handed to strangers and asked to be trusted. And it cannot be verified on the development machine alone: both bugs it has shipped were Windows-only, found by users, in code paths Linux never executes -- so prefer a property test that runs everywhere over a platform check that runs nowhere, and read what the Windows and macOS runners print.
4.2 KiB
nestri
Open-source cloud gaming: a control plane and the guest components that run inside a box. This repository is public. That is the single most important fact about it and most of the rules below follow from it.
Layout
Split by what a thing is, not by what language it is written in.
apps/ what runs api, auth (TS) · nescope, neswire, nescapture, neshub (Rust, guest-side)
nesdoctor (Rust, runs on the user's own machine)
crates/ shared Rust nesprotocol
packages/ shared TS core, auth
docs/ long-form alchemy.md
Both toolchains live at the root: package.json is the Bun workspace,
Cargo.toml the Cargo one.
bun install |
dependencies |
bun dev |
local Cloudflare dev via Alchemy |
cargo build --workspace · cargo test --workspace |
the Rust half |
bun run deploy:sandbox |
deploy a stage |
Two rules that are not style preferences
Nothing closed may enter this repo. Not source, not a dependency, not a directory that "looked convenient". Before adding a top-level directory, know which component it is and that the component is open. This has already been caught once, in a commit that was never pushed.
Versions are pinned once, centrally. A Cargo member writes
tokio.workspace = true and never a version; a TS package uses the root
catalog. Two packages in one tree must not disagree about a dependency.
Where the detail is
These load automatically when you work in the directory they describe — read them there rather than duplicating them here.
packages/core/CLAUDE.md— domain modules: the.sql.ts/index.tspair,fn(), the serialization boundary, ids, the actor model, the error type, auth flow.apps/api/CLAUDE.md— route modules, registration,.meta()vs.openapi(), error flow.docs/alchemy.md— infrastructure: stages, bindings, secrets, service bindings, the CLI.
Things worth knowing before you start
This tree is mid-rewrite. The Rust components arrived recently, one commit
each, imported as trees rather than as history — so git log on them starts at
the import and their own past is not here. Docs for that half are thin and
being written.
The TypeScript half predates the Rust half, so the guides above describe it in much more depth. That is a gap in the writing, not a statement about which half matters.
Most Rust components are guest-side: they run inside a virtual machine, not
on the control plane. nescope composites, nescapture captures and encodes
frames from inside the workload's own process, neswire handles audio, and
neshub muxes all of it into one connection to the client. nesprotocol is
the wire format they share. None of them talk to the API.
nesdoctor is the exception to all of the above. It runs on a stranger's
own machine, on Linux, Windows and macOS, and is the only thing here that a
person outside the project can operate. Two consequences that do not apply
anywhere else in the tree: its dependency list is part of its interface,
because it is handed to people and asked to be trusted — everything doable with
std is done with std; and it cannot be tested on the development
machine alone. Both bugs it has shipped were Windows-only, found by users, in
code paths Linux never executes. Prefer a property test that runs everywhere
over a platform check that runs nowhere, and read what the Windows and macOS CI
runners print.
None of the guest components depend on what they are running. The box starts a payload that
the open components are not allowed to understand, so no code here may branch on
which one it is. nescope does mention Steam and Proton in comments — it
implements public Wayland and Vulkan protocols that gamescope also implements,
and those comments say which real case motivated a workaround. That is the
allowed kind: a name in prose, never a dependency in code.
Conventions
Conventional commits. Explain why in the body — the diff already shows what. Comments earn their place by saying something the code cannot; a comment restating the line below it is noise.