XDOS 0.4 · Windows command workspace
A command workspace that remembers what you did.
Windows and WSL terminals, docked native windows, a public room, and Trose — a hash-linked memory of every session. It runs on your machine and documents exactly what each feature does, and what it doesn't.
Requires Windows and Python 3.10+ with Tk. WSL optional.
Eleven tabs, one desktop
Everything you run, docked in one place.
Windows & WSL terminals
Run real PowerShell and Bash jobs inside XDOS, or open full interactive consoles that live on their own.
Native window docking
Pick any visible app window and dock it over the XDOS viewport. Input goes straight to the app. Detach restores it.
Trose memory
Commands, panel switches and window changes are recorded locally in a SQLite Merkle ledger you can verify.
Time
Step back through checkpoints and restore your tasks, sources, current folder and identity from before or after any point.
Automation
Turn an observed event into a rule that runs a safe local action. Rules start paused and stop after ten runs a session.
Public room
Join the global XDOS chat as a guest from inside the app. Leave anytime; nothing about your machine is posted.
Private organizations
Administrator sign-in through the moneyless.win operator, verified by a one-time email code. No XDOS password exists.
Sentinel & cloak
A loopback gate with HMAC, replay nonces and rate limits. Cloak hides the screen while work keeps running.
How Trose works
Every event becomes a leaf. Every session links to the last.
Each recorded event gets its own SHA-256 leaf. Changed branches and the tree head update in the same database transaction, and each new launch anchors to the previous session's final root — so old sessions stay exactly as they were.
01
Event
A command, panel switch or window change.
02
Leaf
An ordered, domain-separated SHA-256 hash.
03
Tree head
Updated live and shown in the Live tree tab.
04
Next session
Anchors to the final root and count.
hashes status · hashes verify · hashes steps · hashout
Straight answers
What XDOS doesn't do.
Every feature ships with its limits written down. Here are the ones people ask about most.
A virtual label isn't a route.
::f1 and other identities are metadata. They never change your source IP.
Local history isn't encrypted.
Command arguments can contain secrets. Treat the AIML folder like any private file.
Time doesn't undo the world.
It restores XDOS state, not deleted files or completed shell, disk and network effects.
HMAC isn't encryption.
The sentinel gate authenticates its own socket. It is a prototype, not an audited firewall.
No online gateway ships in 0.4.
The WSL WireGuard option needs your own server and config. You still need a real uplink.
Hashes verify. They don't store bandwidth.
Local verification catches inconsistencies, not someone rewriting the whole unsigned history.
Quick start
Up and running in three steps.
1
Extract the folder
Unzip the whole XDOS folder somewhere writable.
2
Run Start-XDOS.cmd
The desktop opens with eleven tabs. Start-Terminal.cmd opens the console instead.
3
Type help
Then try id, task, curl and hashes verify in Workspace mode.
Get XDOS 0.4.
Free for Windows. The public room lives inside the app — chat.moneyless.win is an API, not a browser page, so open XDOS to say hello.