LLM chat in a haunted crypt, as a desktop app: creatures of pixel art
(the Haunt bestiary), the spirit hub, Kiro the mascot ghost, apparitions
that react to the chat, horror effects (vignette, fog, lightning), a
header fear gauge (fear, % of the model's context window), and a
global token counter. Port of the kiro-horror-tui terminal app to
Tauri v2 (Rust backend) + Svelte 5 (web frontend), same features,
same crypt palette.
Screens: Chat, Settings, Vps, Haunt, plus the inter-agent panel (bus + mailbox) and the 3D project space (F7/F8).
Releases : https://github.com/Tradoooo/Crypte/releases (bundles Tauri
Windows .msi, macOS .dmg, Linux .AppImage, plus the terminal build
kiro-horror-tui for Linux/macOS).
# macOS : right-click the app > Open (unsigned build)
open crypte_1.0.0_universal.dmg
# Linux
chmod +x crypte_1.0.0_amd64.AppImage && ./crypte_1.0.0_amd64.AppImage
# Windows : installer .msi (SmartScreen : More info > Run anyway)- Clone your project from GitHub.
- Launch Crypt inside that folder (the folder is the project drawn in the 3D crypt).
- Press F7 — the 3D crypt turns on and pulls back over every project you run. F8 toggles the background, F5 is a scare, F9 plays Haunt.
Without a release binary: npm install && npm run tauri dev in this
repository (needs Rust stable, Node 22+ and the Tauri system libs).
- Backend: Rust 2021, Tauri v2 (
src-tauri/, libcrypte_lib+cryptebin) - Frontend: SvelteKit 2 in static SPA mode (
ssr=false), Svelte 5 runes, Vite, TypeScript strict, Vitest - Bridge: ~75
#[tauri::command]s + 2 event channels (crypte-event,crypte-ui) — contracts insrc/lib/contracts.ts
Prerequisites: Rust stable, Node 22+, Tauri v2 system libs
(libwebkit2gtk-4.1-dev libgtk-3-dev libayatana-appindicator3-dev librsvg2-dev on Debian).
npm install
npm run tauri dev # desktop app with hot reload
npm run check # svelte-check (types)
npm run test # vitest
npm run build # static frontend -> build/
cd src-tauri && cargo test # backend tests (447)Gates (must stay green): cargo fmt --check, cargo clippy --all-targets -- -D warnings, cargo test, npm run check,
npm test, npm run build.
The binary embeds the TUI's headless surface (same names, same effects):
crypte --smoke # self-check, no network, no key
crypte --sheet out.png # creature sheet (34 drawings) as PNG
crypte --apercu out.json # preview report as JSON
crypte --mbox <args...> # broadcast CLI (same files as bcast shell)
crypte --events-log f # append domain events as JSONL (KH_EVENTS_LOG)New paths under the Tauri app id (com.crypte.app):
- config:
$XDG_CONFIG_HOME/com.crypte.app(chats.json,permissions,permissions-rules,vps.toml) - data:
$XDG_DATA_HOME/com.crypte.app(providers.enc,master.key,almanac.json,checkpoints/)
First launch auto-migrates (copy-once, never overwrites) from the legacy
TUI paths (kiro-horror-tui). Shared, never migrated: the mbox broadcast
dir (BCAST_DIR), ~/.config/muse/auth.json, ~/.kiro/.
/vps keeps the remote TUI in tmux (V1).
Two layers, both ported:
- Bus (in-process): chats and sub-agents talk (
/tell,/ask,/msg,/link,/unlink,/links), queued delivery, 8-hop loop cap. - Mailbox (broadcast v2 mirror): file-backed agent mailbox —
P0/P1/P2 messages,
O-AAAAMMJJ-NNNorders + acks, tokens, throttle, digest, 15 s probe,--mboxCLI and typed commands.
- Files < 500 lines AND ≤ 30 functions; functions < 50 lines
(
grep -cE 'fn [a-zA-Z_][a-zA-Z0-9_]* *\('); zero duplication. - Secrets never logged (manual redacted
Debugs;debug_redactedtests). - CI: every job ≤ 5 min (
ci-budgetguard); checksfmt,clippy,build,testrequired by the Mergify queue.