THE DISANCHOR DEVLOG
Devlog
Notes from building Disanchor: the thinking behind it, what we’ve finished and what comes next.
Disanchor is in development. These posts describe our direction and progress, not features available today.
-
Early November: idle PCs, files and your edits
We’re teaching a PC to notice when nobody is using it, moving files in and out, and keeping your own edits when the assistant resumes. All in local development.
-
Checking the assistant’s work
We started measuring how an experimental assistant handles everyday tasks on a local Linux desktop. So far, its mistakes teach us the most.
-
Late October: build notes and a new community
What changed since we chose Linux: email sign-ups, a local desktop experiment, preparing a small first test and a new Discord community.
-
Starting with Linux
Disanchor’s first version will be a Linux PC you open in your browser. Here’s what changes and what stays.
-
October progress: the parts you don’t see
An October snapshot of Disanchor’s Cloud PC controls in simulated testing. The first release now targets Linux in a browser.
-
Why we’re building Disanchor
A laptop that ran out of room, a game that streamed better than expected, and the question that followed.
-
Clarity is part of the product.
Knowing what is running, what you’re paying for and what happens to your saved work should feel straightforward.
-
Power should follow the work.
Some moments ask for more from your PC. Choosing more performance should be a deliberate, understandable decision.
-
A PC is more than a processor.
The apps you choose, the files you save, the way you work. That’s what makes a computer feel personal.
-
DirectN is now Disanchor
How DirectN became Disanchor, our personal Cloud PC project. The first version is a Linux PC you open in a desktop browser.
JOIN THE COMMUNITY
Build it with us on Discord.
Talk with the people building Disanchor, share what you’d want from a personal Linux PC in the cloud, and see announcements as they happen.
Free to join. It doesn’t grant early access.