Casual Desktop · v0.0.6

The same editors, off the network.

A native binary that reuses the Casual Docs and Casual Sheets web cores verbatim. Single-user, offline. Tauri shell, Rust glue. macOS, Linux, Windows. Same shipped UX as the web, no SaaS in the loop.

macOS .dmg · Linux .deb / .AppImage · Windows .exe / .msi · checksums. Apache-2.0. Installers are unsigned in the OS sense — on macOS, right-click → Open on first launch.

Version
v0.0.6
Targets
3 OSes
Updates
signed, in-app
Shell
Tauri
The shape

Reuse the web build. Replace the chrome.

Same web cores, verbatim

Casual Docs and Casual Sheets ship as web apps first; Casual Desktop wraps the same bundle. No second code path, no "desktop-only" feature drift — fixes and features in the web cores reach the desktop on the next release.

Single-user only

Real-time co-edit stays in the Docker image where it earns its keep. The desktop binary is intentionally offline: open a file, edit it, save it. No server, no port, no port forwarding.

📁

Native file dialogs

Native macOS / Linux / Windows file pickers. Drag-and-drop from Finder / Explorer / nautilus into the window. The browser sandbox limitations on file access disappear in the desktop shell.

Signed in-app updates

The app checks GitHub Releases on launch and installs newer signed builds in place — verified against an embedded minisign key. Opt-out in Settings. Update signing, not OS code-signing.

Coming in v0.0.6

An offline AI assistant — and PDF joins the bundle.

The next desktop release brings the AI assistant to the binary and folds Casual PDF into the same shell. Both run on your machine — the model can be a local one, and your files never leave the disk.

Offline AI assistant

The same document assistant that ships in Casual Docs, running against a local model — llama.cpp with Metal on Apple Silicon, CUDA on NVIDIA, CPU fallback everywhere — or your own cloud key. Cloud requests are dispatched natively from Rust over system TLS, and the key can come from an environment variable so it stays out of the renderer. Every edit lands as a tracked change you accept or reject; nothing is rewritten behind your back.

PDF in the same binary

Casual PDF joins Docs and Sheets in the desktop shell — the same PDFium-WASM core: annotate, forms, in-place text edit, certified PKCS#7 digital signing, and true byte-level redaction, all offline. One download, three editors.

Installing

The builds aren’t OS-code-signed yet

Code-signing certificates cost money per OS, so the downloads are not signed in the OS sense. They’re the same binaries published on GitHub Releases, but macOS Gatekeeper and Windows SmartScreen will warn on first launch. Here’s how to get past it on each platform. (Auto-update is cryptographically signed — verified against an embedded minisign key — so updates after install are tamper-checked.)

macOS · .dmg

Gatekeeper shows “Casual Office can’t be opened because Apple cannot check it.”

  1. Drag the app to Applications.
  2. Right-click (or Ctrl-click) the app → OpenOpen.
  3. Or: System Settings → Privacy & Security → Open Anyway.
  4. Still stuck? In Terminal: xattr -dr com.apple.quarantine "/Applications/Casual Office.app"

Windows · .exe / .msi

SmartScreen shows a blue “Windows protected your PC” dialog.

  1. Click More info.
  2. Click Run anyway.
  3. Then install normally. The .exe (NSIS) and .msi are interchangeable — pick either.

Linux · .deb / .AppImage

No code-signing gate on Linux — just install or mark executable.

  1. .deb (Debian/Ubuntu): sudo apt install ./Casual.Office_*_amd64.deb — or open it in your software centre.
  2. .AppImage (any distro): chmod +x Casual.Office_*_amd64.AppImage then run it. Needs FUSE (libfuse2 on newer Ubuntu).
v0.0.6 is the latest release. On desktop, your files stay on disk — edits no longer get mirrored into browser storage (IndexedDB); the disk file and its on-disk recovery sidecar are the only source of truth. Builds on v0.0.4 (rename-on-disk, persistent theme, cleaner open) — see the changelog. Auto-update installs it in place.