Repository navigation
SlateOS 0.2.0
The second milestone. SlateOS can be tried and installed from its image, with a graphical installer, and has what a computer needs day to day: Wi-Fi, Bluetooth, the battery and power modes, printers, input methods, apps from Flathub, and a screen that locks when you are away. The agent gets more of its own: Chromium-based apps it opens take its keyboard and pointer, you choose what it may do while the screen is locked, and a request from the Slate prompt arrives with what you are looking at. It is also the first release whose image builds; 0.1.0 and 0.1.1 had none.
Upgrading from 0.1:
- The screen now locks after 10 minutes without input and before the computer sleeps (0.1 locked only on Super+L);
services.slate.desktop.screenLock = falseturns that off. - With the desktop enabled, the module turns on NetworkManager, BlueZ, UPower, power-profiles-daemon, CUPS with Avahi and ipp-usb, polkit, Flatpak, AppImage, nix-ld, zram swap and redistributable firmware. Each is a default (
lib.mkDefault, polkit excepted) that a configuration can turn off. NetworkManager cannot run alongsidenetworking.wireless: a configuration that uses it setsnetworking.networkmanager.enable = falseor moves its networks to NetworkManager.
Changes since 0.1.1:
- Try or install, like other systems. The image's boot menu is SlateOS's own (it showed nixpkgs' NixOS logo) and starts "Try or Install SlateOS 0.2.0"; the live desktop opens a window to try SlateOS or install it, and Install SlateOS stays in the dock. Installing is now graphical: choose the disk, your user name and password, the computer name, time zone, applications and disk encryption, review, confirm, and follow the progress (
slateos-installer, which runsslateos-install). The Memtest86+ entry is gone on ARM, where the image has no Memtest and it only reported an error, and the text consoles no longer speak of a "nixos" account. - The basics of a computer. Settings has new pages: Network lists Wi-Fi networks and asks for their password (the password goes to NetworkManager over D-Bus, never on a command line; a failed attempt is not kept), Bluetooth pairs devices (it answers pairing requests with the code to confirm or type) and connects or forgets them, Power shows the battery and the power mode, and Printers lists printers and the default one. The menu bar shows the battery and Bluetooth when the computer has them, and its icons open their page (
slate-settings network,bluetooth,power). The module now enables what these need on real hardware: redistributable firmware, zram swap, NetworkManager, BlueZ, UPower, power-profiles-daemon, CUPS with Avahi and ipp-usb (driverless printers work without being added; cups-browsed stays off), and a polkit agent (soteria). A notification warns when the battery reaches 10 % and 5 %. - The screen locks when you are away: after 10 minutes without input, and before the computer sleeps; it turns off after 15 (Settings, Power). What the agent does on its own screen does not count as activity. What the agent may do in windows while the screen is locked is yours to choose, in Settings, AI: look but not use them (the default), also press buttons, fill in fields and open and close windows through accessibility, or keep working with its keyboard and pointer behind the lock (a SwayFX patch exempts its seat from the lock; its input never reaches the lock screen, and it cannot unlock). You can also let the screen stay unlocked while the agent works; it then locks a minute after the agent stops. Loosening either asks you to confirm what it allows, and every change asks for your password, so the agent cannot change them itself (
slateos-settings set agent-while-locked,lock-while-agent-works;services.slate.desktop.agentWhileLocked,lockWhileAgentWorks). A tool the choice does not allow explains why; none of them types into the lock screen. - Electron and Chromium apps the agent opens take its own keyboard and pointer. Chromium binds one Wayland seat, the first, so the agent had to borrow yours to type in VS Code, Obsidian or Chrome. A Chromium-based app it opens in the background now connects to a Wayland socket of the agent's (a security context), and a SwayFX patch shows it the agent's seat and no other (measured with Obsidian). Your mouse and keyboard do not reach such a window, so the agent is told to close it when done and to open apps you will use on your screen (
where: "here"). Like Flatpak's, these apps get no privileged protocol. GTK 4 apps turned out not to need this: GTK 4.22 takes the agent seat's input when the seat existed before the app, as the desktop daemon makes sure (the slate-desktop README's table is corrected). - Input methods, installed from Settings. Settings, Keyboard adds Chinese (Pinyin or Rime), Japanese (Mozc) or Korean (Hangul): it asks for your password and updates the system; Ctrl+Space then switches. None is installed by default. The choice lives in
/etc/slateos/settings.json(services.slate.settingsFile), whichslateos-settingswrites before it rebuilds;services.slate.desktop.inputMethodssets the same in the configuration. Each seat has its own input method state, so what the agent types is never converted by your Pinyin. - Apps from Flathub. Flatpak is set up with Flathub in each person's own installation, so installing an app needs no password, and Bazaar, a store for Flathub, is on the dock. AppImages run when opened, and downloaded Linux programs find the usual libraries (nix-ld). A new skill tells the agent where an app should come from.
- Installer.
slateos-install --encryptputs the system inside LUKS2 and asks for the passphrase at every boot;--apps minimalinstalls the smaller application set. A complete encrypted install has now been run and booted (in QEMU, from the development system). - Windows that open larger than the space between the menu bar and the dock are fitted into it (a SwayFX patch); they were centred on the whole screen, their title bar under the menu bar.
- New OS Skills: bluetooth, printing, power-battery and apps-flatpak; the system skill knows
slateos-settings, and the windows skill the locked screen and input methods. - Fix: the screen lock did not lock when a seat's keyboard had no keymap: swaylock exited instead. The agent seat's keyboard on your seat had none after the desktop daemon restarted, and an input method's has none until it first forwards a key; Super+L then did nothing. slate-desktop now gives its keyboards a keymap at once, and the lock is swaylock-effects with a patch that ignores such a seat.
- Fix: the configuration the installer wrote loaded the Slate flake from
/etc/slateos/slate, which does not exist whilenixos-installruns on the live system, so an install could not finish. It now loads it from next to the configuration, and keeps Settings' choices there too (an install took those of the machine it ran on). - Fix: the agent did not see a dialog that a GTK4 application had just opened (GTK4 caches its accessibility tree only as far as an assistive tool has asked); parts the cache lists fewer children of than they have are now read directly.
- Fix: the agent did not find the accessibility tree of most Flatpak apps (Obsidian among them): it matches an app to its window by process, and the bus sees the D-Bus proxy of the app's sandbox instead. It now matches them by Flatpak instance. Measured with Flatseal (GTK4), Obsidian (Electron) and WeChat (no accessibility tree: screenshots and clicks); the slate-desktop README lists them.
- Fix (SwayFX patch): any
seatcommand at run time,swaymsg reloadincluded, moved the agent's virtual pointer and keyboard to your seat, leaving the agent seat without input until the desktop daemon restarted. Devices a client created for its own transient seat now stay on it. - Fix: installing a Flatpak app after the first reported "Permission denied" for hicolor's
index.theme(Flatpak's icon cache trigger copies it read-only out of the store). - The Slate prompt sends what you are looking at. When you open it, it notes the window you had in front of you, and while you type, slash reads your screen; your request then reaches the agent with the windows you can see (and those on its own screen), with ids it can use at once, and, when the request is about what is on screen ("summarize this page", "翻译这段"), that window's text and your text selection. The agent no longer spends turns listing windows and reading the page first: summarizing the page in Firefox went from three turns and 10 s to one turn and 3.6 s. Requests that are not about the screen carry only the window list. Desktop tools also take an 8-digit id prefix.
- Deleting what undo cannot bring back asks first. A command that deletes or moves files was allowed after a snapshot even when the snapshot did not hold them: files outside the snapshot root (with
snapshotRootset to a folder inside the home directory), in caches undo leaves alone, or on a system without snapshots were gone for good, and/undoreported nothing to restore. slated now asks before such a command and says which path undo could not restore (docs/policy.md). - Apps the agent opens in the background no longer take your keyboard for a moment. A program started through a wrapper (LibreOffice's
soffice, many Nix wrappers) opened its window on your screen, with your keyboard focus, for up to a second and a half before it was moved: what you typed meanwhile went into the agent's document. The processes such a program starts now get the same placement rule, so the window opens on the agent's screen, and a window that still lands on yours is moved before slate-desktop asks sway anything else. A dialog an app opens while the agent works in it on its screen ("Save Document?") stays there too, anddesktop_closesays when an app asks something before it closes instead of reporting it closed. - The agent no longer pulls windows over from your other workspaces. Asked to put "Firefox and the terminal" side by side, it took the terminal on another workspace, and sway brought it over.
desktop_windowsnow gives each window on your screen its workspace and marks those on one you are not looking at (on_hidden_workspace), a window named by app or title is the one you can see when there are several, anddesktop_arrangewithout a list arranges only what you can see. - A click on Allow or Deny in an approval that appeared on its own now answers it; the first click only woke the prompt up, so it took two.
- The desktop prompt shows bullet lists and italics in answers (they were shown as
-and*), and slash says "1 turn". - Opening an app is quicker and says what went wrong. The desktop and Slate tools are loaded with the agent instead of on first use (Claude Code's
alwaysLoad), which saves the agent a round trip for every desktop tool it first uses in a session.desktop_launchwaits up to 15 s for a program that is still starting (a first Flatpak start can take longer than the 8 s it waited), says so if it is still starting after that, and places its window where it was asked when it does appear; a program that exits before it shows a window is reported at once with its last output. Launched programs now write their output to the journal under their name (journalctl --user -t com.tencent.WeChat). A Flatpak app opened in the background is recognised by its window's name (wechatforcom.tencent.WeChat) and moved there as soon as the window opens; it stayed on your screen until the launch was done waiting. - slash shows the agent's tool calls more plainly: desktop tools by their short names (
desktop_launch), their arguments ascommand: …, where: hereinstead of JSON, window ids by their first eight digits, skills by name, and no line for Claude Code loading a tool's definition (ToolSearch). - The password dialog says who asks when Settings needs root, and the dock shows it with a padlock.
- The session now holds
graphical-session.targetwhile it runs (slateos-session.target, stopped when sway exits), so units that start with a graphical session work, and the session's own services stop at logout. - Fix: the image could not be built since SwayFX 0.6 (0.1.0 and 0.1.1 had none): the override passed an argument the flake's newer nixpkgs no longer takes. CI now evaluates both images.
- Fix: the live session locked itself after ten minutes away, and its user, who has no password, could not unlock it. The live image no longer locks the screen (
services.slate.desktop.screenLock). - Fix: changing the resolution or scale in Settings could leave the screen unusable. When the confirmation ran out (or was closed), Settings went back without
--customto a mode the display does not list (UTM's 2560x1600), so sway fell back to another mode at the old scale: a quarter of the working area, every window larger than the screen, the dialog out of reach. It now restores the exact mode, closes the dialog, and answers once. The person's absolute pointer (a virtual machine's) is also mapped to the new screen size at once instead of up to 5 s later, so clicks land where the pointer is. Dialogs of Settings no longer show in the dock as an unknown app. - Fix: in a virtual machine (virtio-gpu: UTM, QEMU) the screen stayed dark once it had turned off after 15 minutes away, whatever you pressed. The display misses the first power on after a power off and still reports success;
slate-screensnow asks again until every screen is on. - Fix: installations failed while building the new system (
path '/mnt/etc/slateos/settings.json' does not exist). The module copiedservices.slate.settingsFileinto the store to name it in/etc/slate/system-settings.json, and a new system has nosettings.jsonyet; it now writes the path as text. Running the installer from the image itself also found three more faults, now fixed: the copied Slate source was a link into the image's read-only store,nixos-installbuilt the live system's configuration instead of the new one ("no build method found"), and a second attempt found the disk still mounted. On the image,slateos-installis now the disk installer; the system tools' front end of the same name had taken the name, so the command the consoles suggest did not work. While it installs, the installer keeps the screen on and the computer awake, also with a laptop's lid closed, and writes its output to/tmp/slateos-install.log.
Known limitations:
- Only the aarch64 image has been booted and installed from, in QEMU on the development machine. The x86_64 image is evaluated in CI but has not been booted, and no installation on real hardware, nor its Wi-Fi or Bluetooth, has been tried.
- The image is not attached to the release: it is larger than the 2 GiB GitHub allows a file. Build it on Linux with
nix build github:BenchGrid-dev/slate#iso. - An encrypted installation asks for its passphrase at boot through the firmware's framebuffer or a GPU driver in the initrd. In UTM and QEMU (virtio-gpu) the prompt does not show, so do not encrypt there.
- A Chromium-based app the agent opens in the background takes only the agent's input; your mouse and keyboard do not reach its window.
- Some apps have no accessibility tree (WeChat); the agent uses screenshots and clicks there.
- Codex runs under its own sandbox without Slate's approvals (Claude Code goes through them).
- Undo covers the snapshot root, a btrfs subvolume the user owns; slated asks before deleting what it cannot restore.
- Firefox can abort when the agent reads the accessibility tree of its session-restore page.
- There is no graphical login screen; installs log in automatically.
- On a slow machine the dock can show default icons at login, when it starts before the icon theme is ready.