Repository navigation
Releases
SlateOS 0.2.2
Connecting the agent is a step of the installation, a model API key of your own works beside a Claude subscription, a tutorial shows how to work with the agent, and an installation with the minimal applications needs no network.
- Connecting the agent is part of installing. The installer has a new step, between the account and the options: how the agent reaches a model. It does not go on without an answer, because SlateOS without an agent is a desktop that does not answer. The choices are a Claude subscription (Claude Code's own sign-in, done in the live session and carried over to the installed system) and an API key of your own. Systems that were not installed this way (the module on an existing NixOS,
slateos-installfrom a console) get the same question from a welcome at first login (slate-welcome,services.slate.desktop.welcome), which comes back at every login until the agent is connected. Settings, AI shows the connection and changes it. - An API key of your own, in OpenAI's or Anthropic's format. An address, a key and a model name are enough: OpenAI, Anthropic, OpenRouter, DeepSeek, a relay, a model on your own network. The form asks the service for its models and tries the connection before it accepts it. The agent stays Claude Code, so approvals, the audit log and undo work as with a subscription: slash points it at a gateway of its own on this computer (the new
slate-gateway), which passes Anthropic-format requests through and rewrites the others for chat completions and back, tool calls and streaming included. The key stays in slash and in~/.config/slate/provider.toml(readable by you alone); the commands the agent runs see a token that is only good for that gateway, and slated asks before the agent reads the file.slate provider show,testandmodelsdo the same from a terminal; slash's banner names the model and the service, and/modelpicks another of the service's models. With another service the agent has no web search (Anthropic's servers do that) and Claude Code's telemetry is off. docs/agent-connection.md has the details and the limits, docs/decisions/0008 the reasons. Tested with the real Claude Code against a scripted endpoint (tests/e2e/mock_openai.py), not yet against each provider's own. - A tutorial. Six short pages on working with the agent: asking with Super+S, its own screen, approvals, undo, the terminal, the rest of the desktop. The installer shows them while it installs, the welcome after the agent is connected, and Settings, AI on request (
slate-welcome --tour). - slated asks before the agent reads a file that is a key or a sign-in (
provider.toml, the agent CLIs' credentials, private SSH keys); reading anything else stays free. - Fix: installations built most of the system again on the person's machine, and failed without a network although the "Minimal" set says it needs none. Three causes. The SwayFX build named sway's patches as strings inside the nixpkgs tree, so the image (built from the flake's copy of nixpkgs) and an installation (evaluated from the installer's copy) asked for two different compositors, and each installation compiled its own. NixOS marks its small generated files as never to be copied from elsewhere, so some three hundred that the image already held were built again, a few of them wanting a C compiler. And the installed system is not a subset of the live one (another boot loader, an encrypted initrd), nor was the nixpkgs tree its configuration is locked to on the image. Now the patches are copied by content;
slateos-installlets Nix copy what the image holds; the image carries the closure of the system an installation builds, evaluated with placeholder answers; and the desktop profile no longer builds NixOS's manual (documentation.nixos.enable, a default). What is left to build are the few dozen files with the person's names in them. On the CI runner an installation went from about 350 s to about 200 s, and the image test now installs its plain run without a network card. - Speech synthesis is off by default (
services.speechd.enable): NixOS turns it on for graphical systems, with 450 MB of voices, and SlateOS has no screen reader to use it yet. The image is 200 MB smaller. - Fix: the installer still said that some virtual machines cannot show an encrypted disk's passphrase prompt; 0.2.1 fixed that.
Upgrading from 0.2.1:
- The welcome opens once at the next login. Where Claude Code is signed in already, it shows the tutorial and asks nothing; where it is not, it asks for the connection at every login until there is one.
services.slate.desktop.welcome = falseturns the welcome off. - Speech synthesis is no longer enabled by the desktop profile. A configuration that uses it sets
services.speechd.enable = true.
Known limitations, where they differ from 0.2.1's:
- An API connection has been run with the real Claude Code against a scripted OpenAI-format endpoint, and against no provider's own service yet. Services differ in the parameters they accept and in how they stream tool calls; the gateway learns the former from their error messages, and a fault in the latter shows as a tool call the agent does not make.
- With a model other than Claude the agent works from prompts and tool descriptions written for Claude, and Claude Code assumes Claude's context window. docs/agent-connection.md lists what differs.
- The installer's new step and the welcome have been run on the development system (the installer without writing to a disk), not yet in a live session started from the image. The image test carries a connection into the new home with
slateos-install --home-files.
SlateOS 0.2.1
SlateOS follows the NixOS release it is developed on, the image is installed and booted in virtual machines on both architectures, and an encrypted disk asks for its passphrase on the screen.
- SlateOS follows NixOS 26.05. The flake pinned nixos-unstable (a revision of late September), while SlateOS is developed and tested on the stable release: the image and what it installed ran packages the end-to-end suites never saw, and got no security updates. The flake now follows
nixos-26.05, the same revision the development system runs, and later 0.2.x releases move along that branch. A system installed from the 0.2.0 image changes to it when its copy of Slate (/etc/slateos/slate) is replaced. - The image is installed and booted before a minor release.
tests/image/install_test.pystarts the image in QEMU the way a person does, installs to an empty disk withslateos-installthrough a console of the live system, boots the disk without the image, types the disk's passphrase on the keyboard when the installation is encrypted, logs in and checks the desktop. A workflow (.github/workflows/image.yml) builds the x86_64 image and runs it, on a plain and on an encrypted disk, for the commit that prepares a minor release and on request; patch releases keep to the evaluation of both images. - slash shows a Markdown table as aligned columns, its header bold; it printed the rows with their pipes.
- The system names itself with SlateOS's version: the boot menu's generations, the console greeting and
slateos-versiongave NixOS's ("26.11.20260926.e158d9e" on a system installed from the 0.2.0 image), which stays inVERSION_IDand, in brackets, inslateos-version. - The image no longer carries ZFS's kernel module, which SlateOS does not install on.
- Fix: an encrypted disk's passphrase prompt did not show on ARM computers whose firmware names a serial port as the console (UTM, QEMU, servers): the kernel then used that port alone, the screen stayed black until the desktop started, and the passphrase could only be typed blind or on the serial port. The screen is now the console (
console=tty0), on every architecture. - Fix: the dock could start with GTK's default icons at login, when it came up before the settings portal answered; it now sets the icon theme itself, as it does the colours.
- Fix: each restart of the dock or the Slate prompt left a
swaymsgprocess behind until the next window event. Both now read sway's events from its socket themselves. - Firefox no longer aborts when the agent reads its session-restore page (0.2.0's known limitation): not reproduced with Firefox 159, with and without a session to restore.
Known limitations, where they differ from 0.2.0's:
- Both images now install and boot in QEMU: x86_64 in CI, aarch64 on the development system under emulation. No image has been tried on real hardware, and the graphical installer has not been run on x86_64 (the test installs with
slateos-install). - A system installed from the 0.2.0 image does not move to this release by itself; a software update that does is planned for 0.3.0.
- On a very slow machine (an emulated one) the session's first terminal may not open; Super+Return opens one.
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 window...
SlateOS 0.1.1
Window buttons on every title bar, and fixes from living with 0.1.0.
- Window buttons. Every title bar has minimize, maximize and close buttons at the right, round and in the title's colour like libadwaita's (the SwayFX the module builds carries a SlateOS patch for them; sway has none). Apps that draw their own title bar, Settings and Firefox among them, show the same three: the compositor now advertises maximize and minimize to them, and handles their requests instead of ignoring them. Maximize fills the space between the menu bar and the dock and gives the window its size back when pressed again; a double click on a title bar does the same, and moving or resizing a maximized window by hand makes it an ordinary one. A minimized window waits in sway's scratchpad: its dock icon brings it back when the app has no other window on your screen.
- The dock no longer lifts an icon under the pointer; the grey highlight stays.
- The agent sees minimized windows as
minimizedindesktop_windows(they were reported as on the screen), anddesktop_focusordesktop_showbrings one back on your screen. When it clicks a title bar to focus a window, it keeps clear of the buttons. - Fix: after the agent clicked or scrolled on your screen, its cursor stayed there as a second pointer until its next action somewhere else. It now goes back to the agent's own screen once it has rested for five seconds. The desktop daemon also serves each client on its own connection, so a command-line call no longer waits behind the agent's open connection.
- Fix: switching between dark and light, or choosing a wallpaper, showed a black screen for a moment (sway ends its background program before the new one has drawn). The new background now covers the screen before sway swaps its own.
- Fix: in Thunar's side pane the Trash icon was smaller than the others, blurred and off-centre on HiDPI screens (Thunar drew it from the trash folder instead of the icon theme); a patch gives it the themed icon the other places use.
SlateOS 0.1.0
The first milestone. SlateOS runs as a daily desktop on the development machine: you and an AI agent share the computer, the agent works through a seat and a screen of its own, and its work is approved, audited and undoable. This release marks what the 0.0.x snapshots built, and gives the desktop a finished look: rounded, shadowed, frosted windows, a dock, a menu bar, a lock screen and a session menu. Everything the agent relies on works the same on the new compositor (the e2e suites pass on it).
What is in it:
- slash, the login shell: plain language goes to the agent,
!runs your real shell on a pty,/commands control the session. Claude Code and Codex backends with session resume, model choice and an identity prompt that makes the agent operate this machine rather than write code. - The Slate prompt (Super+S): one exchange at a time over whatever you are doing, approvals as buttons, a message queue with edit, steer and delete, and answers that come back when a background task finishes.
- The agent seat: its own Wayland input seat, so it never moves your cursor or types into your window; its own background screen, with the AI workspace as a live view of it and
desktop_show/desktop_hideto move windows between the two; applications read and driven through the accessibility tree (AT-SPI2) first and the pointer second. - Task controls: an approval broker for Claude Code's tool calls with a policy you can edit, an audit log, a btrfs snapshot before the first change of every task, scoped
/undowith a preview, memories, and root only with your consent through a password dialog. - The desktop: a SwayFX session (rounded corners, soft shadows, frosted translucency, short animations) with a menu bar, a dock, the AI workspace, a lock screen and a session menu, dark and light themes that switch everything live, a settings app (display, sound, network, appearance, AI, memories) and an application suite (Firefox, Thunar, LibreOffice, Thunderbird, Mousepad, zathura, mpv, imv).
- The distribution: a NixOS module (
services.slate.enable), SlateOS branding and system commands (slateos-rebuildand friends), OS Skills kept in step with the installed version, and a live/installer image (nix build .#iso).
Changes since 0.0.19:
- A new look. Windows have rounded corners and soft shadows, translucent surfaces are frosted, and windows fade in and out: the session runs SwayFX 0.6 (sway 1.12 with effects; the module builds it, nixpkgs has 0.5.3, which cannot capture single windows) when
services.slate.desktop.effectsis on, the default, and falls back to plain sway if it does not start. Title bars are centred, in the apps' own header colours; GTK3 apps use adw-gtk3, icons are Colloid and the cursor Bibata Modern Classic. New wallpapers, one per appearance, follow it unless you pick your own. - A dock of its own (
slate-dock): pinned and open apps in one row, a dot under the ones with a window on your screen, a ◆ on the ones Slate has a window of on its background screen (a click brings the window over), right-click menus and the trash. The panel is now a translucent menu bar, the launcher (Super+Space) opens like Spotlight, and notifications are frosted. - Lock screen and session menu. Super+L locks the screen: the desktop blurred, a clock, a ring that answers your typing. Super+Escape, or a right click on the menu bar's ◆, offers lock, log out, restart and shut down; before the last three it asks every window to close, so apps save their state and ask about unsaved work instead of finding at the next start that they crashed.
- Volume and brightness pop-up (swayosd) for the media keys, above the dock; the brightness keys work for the desktop user.
- Reduce transparency in Settings, Appearance (
slate-theme transparency reduced): nearly opaque surfaces, for legibility and for machines without a GPU. - The application list is tidier (
slate-apps, at login and after upgrades): developer tools, terminal programs and the NixOS manual are hidden, and a few apps have plain names (Files, Terminal, Document Viewer, Videos, Text Editor). Only files it wrote are touched. - os-release names SlateOS and its version (
SlateOS 0.1.0 (26.05)), BenchGrid as the vendor, SlateOS's logo and links; the NixOS release stays inVERSION_ID, andID_LIKE=nixos. - Fix: Firefox opened taller than the space between the menu bar and the dock, its bottom under the dock (its size was fixed in pixels for a larger screen). Firefox now opens at a share of the free area and the terminal at a size small screens fit, both centred.
- Fix: in a terminal narrower than slash's banner, the terminal wrapped it mid-word; slash now breaks it between its notes.
- Fix: GTK4 applications without libadwaita (Volume Control) stayed light in the dark appearance: GTK 4.22 does not infer the dark style from the portal's colour scheme. slate-theme now sets
gtk-application-prefer-dark-themein GTK4'ssettings.ini, keeping the rest of the file. - Fix: per-user copies of the desktop's files (mako, fuzzel, waybar, foot) were written once and did not follow system updates; the theme is re-applied at login.
- Fix: the first terminal of a session opened on Slate's background screen (sway opens a window on the workspace focused when its command runs); it now opens after workspace 1 has the focus.
- Fix:
desktop_readright after a page loaded often returned only the browser's own buttons: Firefox shows the new title before the page's content is on the accessibility bus (more often with the effects on a machine without a GPU). Reading and listing elements now wait up to three seconds for a page on screen that is still loading or has no content yet. - Fix: the panel and the dock run as the supervised
slate-paneluser service, so a waybar crash (it can crash while reloading its style on a theme switch) no longer leaves the session without them until the next login.
Known limitations:
- Codex runs under its own sandbox without Slate's approvals (Claude Code goes through them).
- GTK4/libadwaita applications need the user-seat fallback for pointer and keyboard input; Qt, Chromium/Electron and Flatpak applications are untested.
- Undo covers the snapshot root, which must be a btrfs subvolume the user owns; changes outside it cannot be undone.
- The image builds and boots, but a full installation with
slateos-installhas not been exercised end to end, and there is no graphical installer. - Firefox 156 aborted once right after an accessibility walk of its session-restore page; not reproduced.
- There is no graphical login screen; installs log in automatically.
- Without a GPU the frosted translucency costs CPU; Settings, Appearance, "Reduce transparency" turns it down.
0.0.19
- Fix: every program the agent opened with
desktop_launchran inside slate-desktop.service's cgroup, so stopping or restarting the desktop daemon (an upgrade restarts it) killed all of them, including windows already handed to the user, with whatever was unsaved. Each program now runs in a systemd scope of its own (app-slate-*.scopeinapp.slice), and the daemon reaps programs that exit instead of leaving zombies. - Fix: undo restored nothing when the task had worked in a directory above the snapshot root (the prompt's tasks run in the home directory; on a machine whose snapshot root is a subvolume inside it, every scope was "outside the snapshot root"). A scope that contains the root now covers all of it, outermost scopes first so nothing is compared twice.
- Fix: a background
desktop_launchof an application that was already running (Firefox, Mousepad, Thunar, LibreOffice open new windows from the running process) put the window, or for Firefox a new tab, on the user's screen. Firefox now gets--new-windowand Mousepad--opening-mode=window, and while a background launch is pending the daemon moves that application's new window to the background as it appears and gives the user their focus back. - Fix: the agent's OS Skills were linked once, to the store path of whatever version ran
slate skills install, and never followed upgrades: skills added later (appearance, display-brightness) never reached the agent, the ones it had were out of date, and a renamed skill stayed under its old name. The NixOS module now runsslate skills installas a user service at login and after every upgrade, and the command removes links to skills the installed version no longer ships. - Fix: after slated restarted (every upgrade restarts it), a running slash, including the one behind the Slate prompt, kept its dead connection and printed "slated: Broken pipe" on every task, which then ran without approvals, audit or undo. slash now reconnects and resends the request.
- Fix: a terminal task ended twice, so the desktop showed "Slate finished" and "Slate stopped with an error" for the same answer: slash detached from slated before reporting the end, and slated took the detach for a shell that died mid-turn. slash now reports the end first, and slated ignores a second end. The notification offers undo only when the task took a snapshot.
- Fix: in the Slate prompt,
/undo(and other commands answered with notes only) showed nothing: the notes went to the activity line, which the end of the command cleared. They are now the reply. - Fix: opening a window on the user's screen carried the agent's cursor along (sway gives a new window the focus of every seat on its workspace and warped the agent seat's cursor to it), leaving a second cursor in the middle of the new window. The desktop now sets
mouse_warping none. - Fix: the agent's idle pointer sat in the middle of the user's screen as a second cursor; the desktop daemon parks it on the agent's own screen when it starts.
- Fix: a window from a process the agent started long ago (a browser it opened from its shell an hour earlier) is the user's; only windows of processes the agent started in the last 20 seconds are moved to the background.
- slash: answers in the terminal are styled instead of showing Markdown markers (
**bold**,`code`, headings, fenced blocks), also when a marker arrives split across two streamed pieces. - Tests: the serve and slash end-to-end suites use a private config directory, so a user's "bypass approvals by default" no longer fails the approval checks.
0.0.18
- Desktop: windows the agent opens in the background no longer flash on the user's screen first (they map straight onto the background screen). A program the agent's engine starts from the shell is moved to the background as it appears, unless
desktop_launchasked for it on the user's screen.desktop_focuson a background window brings it to the user instead of pulling the user's focus onto the background screen, and the user's seat refuses to type there. - Panel: workspace 1 is always shown, also when it has no windows.
- CLI:
slate-desktop type | key | clicktake--window W. - Fix: focusing a window for the agent's seat clicked the middle of its title bar, which could belong to a window stacked above it; the click now lands where the window is visible, and a covered background window is moved to a free spot for that click (which raises it) and put back.
0.0.17
- Slate prompt: messages typed while Slate works are queued under the current exchange, each with edit, send-now (steer: the current turn is interrupted and the message follows) and remove; they go out one by one as turns end.
slash --servegains acancelop that interrupts the running agent. - Slate prompt: after sending, clicking another window puts the prompt away (it follows the person's focus); the colours follow
slate-theme's choice directly. - Desktop: a dock at the bottom (pinned launcher, files, browser, terminal, settings, then the open windows; click to activate, middle-click to close) and an AI workspace left of 1 (Super+grave or Super+0): a live, read-only view of the agent's background screen. Logging in lands on workspace 1.
0.0.16
- Fix: with the background screen in the layout, absolute input devices (tablets, touch, a virtual machine's pointer) mapped onto the whole layout and the cursor vanished past a fraction of the visible screen. The desktop daemon maps the person's pointer, touch and tablet devices to the region the real outputs cover.
0.0.15
- Appearance:
slate-theme dark | light | wallpaper PATHswitches the whole desktop live (GTK/libadwaita through the colour-scheme key, sway colours and background, waybar, foot, mako, fuzzel, the Slate prompt) and remembers the choice; Settings → Appearance exposes it with a file chooser; theappearanceskill lets the agent do it. - Fix: the person's focus and cursor can no longer end up on the agent's background screen (the daemon pulls them back; a window mapped there at login is brought over).