Follow the output
Compositor-aware geometry and fractional scaling across Wayland outputs.
splinterm
Stable 0.1.0 · Arch / Omarchy · x86_64
A native Wayland terminal where the window can close and the work keeps running.
Stable 0.1.0 · Enter the Lair
Your shell should outlive its window.
Splinterm keeps your work below the surface: Lairs hold projects, Dojos hold working sessions, and Splints keep their shells alive when graphical clients disappear.
Built in Rust from Foot’s terminal behavior. Quietly disciplined for Omarchy.
beneath every windowsplinterdowns processes + state
Lairproject atlas
Dojo 01editor
Dojo 02services
The work lives in the Lair.
Windows only visit.
splinterd keeps the topology underground. A Lair gathers the work, each Dojo holds a focused session, and every Splint carries a running shell. Windows are temporary views in.
- 01EnterOpen a Lair and gather the work.
- 02TrainShape a Dojo from tabs, panes, and Splints.
- 03ReturnLeave the window; find the same Dojo later.
No XWayland in the middle
Native where you look.
Persistent where you work.
Splinterm speaks directly to the Wayland compositor for input, scaling, clipboard, IME, and frame timing. The window stays lightweight and disposable; the work remains with splinterd below it.
01CompositorHyprland / Wayland
↓02Disposable viewsplinterm window
↓03Persistent ownersplinterd topology
↓04Living workshells · layouts · scrollback
Meet text where it enters
Native keyboard, pointer, clipboard, compose, and IME/preedit handling.
Draw only what changed
Damage-driven rendering and compositor frame scheduling avoid blind full-window redraws.
Close the glass, not the work
The Wayland client can disappear while daemon-owned sessions continue below it.
Native does not mean GPU-rendered or universally compatible. Splinterm currently uses CPU/Wayland-SHM composition and is validated for the documented Omarchy/Arch and Hyprland target.
One Lair.
Two deliberate ways in.
Human hands and bounded automation can enter the same topology without inheriting the same authority.
Humannative client
Hands on the Dojo
Local or SSH-backed Wayland windows, tabs, panes, presets, vi copy mode, and explicit control transfer.
- Typed keymaps and trusted chrome
- Native Recent Dojos picker
- Visible authority state
Automationbounded client
Allowed in, never unleashed
JSON/NDJSON, an SSH stdio relay, and MCP—always subject to explicit policy.
- Exact executable identity
- Resource and scope limits
- Revocable controller leases
Discipline is structural: terminal output remains data, never authority or automatic instruction.
One topology, closed authority
Useful enough to act.
Narrow enough to revoke.
Tools can inspect and operate the same Lairs, Dojos, and Splints visible to people—without inheriting human graphical trust. Policy-controlled machine operations meet explicit identity, scope, resource, and limit checks at the daemon.
ClientMCP host · JSON/NDJSON · SSH relay
↓Policy identityexact executable path + digest where required
↓Policy-controlled operations
↓- exact path + SHA-256
- closed operation scopes
- explicit resources
- deadlines + result limits
Authorized surfacetopology · terminal · control
Discover topology, snapshots, scrollback, search results, authorization, and body-free audit metadata.
Create, split, launch, input, resize, restore, rename, or close only when the exact operation is authorized.
Follow topology, terminal, and control streams; stop and fetch fresh state when a resync is required.
33fixed MCP tools
18closed policy scopes
0daemon network listeners by default
Terminal output is untrusted data. It cannot grant authority, approve consent, alter policy, or become an instruction to call another tool.
Measured, not mythologized
Foot-class light.
Built to multiply.
Splinterm keeps panes inside one native topology instead of stacking a separate multiplexer onto every terminal window. The payoff shows up most clearly as the workspace grows.
Idle footprint52.9 MiB
Comparable to Foot at 50.9 MiB—and 76–85% below the tested Alacritty, Ghostty, and Kitty builds.
Comparable to Foot, and faster than the tested Alacritty, Kitty, and Ghostty launches.
Less memory than Foot + tmux at 122 MiB, four Foot windows at 197 MiB, or Foot + Zellij at 204 MiB.
Medians from randomized, checksum-verified runs on one Linux/Wayland host. Splinterm used its prestarted daemon; peer terminals used standalone launches. These are measured results for the recorded hardware and builds—not a universal ranking.
The doors are open.
The edges stay marked.
Splinterm 0.1.0 is stable for x86_64 Omarchy/Arch Linux with native Wayland under Hyprland. Source, documentation, GitHub releases, and AUR packages are public. Broader platform compatibility and a support lifetime are not promised; newer release candidates are prereleases.
01Native Wayland terminalImplemented
02Persistent sessionsValidated
03Panes, tabs, and restoreValidated
04Bounded automationValidated
05Versioned public buildsAvailable
06AUR packagesAvailable
The ordinary path into the Lair
Leave the window.
Return to the Dojo.
Install Splinterm, open a Splint, then use the Dojo picker whenever you want the running work back. AUR may offer release candidates; the installation guide explains how to choose stable 0.1.0 specifically.
$
yay -S splinterm-bin$
splinterm dojoschoose a running Dojo$
splinterm reopenreturn to the last oneKnow the passages
Go as deep as the work requires.
Start using SplintermInstall, launch, detach, and return.↗Configure the terminalFonts, themes, typed keymaps, vi copy mode, and migration.↗Build a Dojo from a presetAtomic Omarchy layouts, strict catalogs, and collision-safe shell helpers.↗Understand persistenceLairs, Dojos, Splints, windows, and lifecycle.↗Enter a remote LairNative SSH-backed windows and separately bounded machine relay.↗Why native WaylandDirect compositor integration, practical benefits, and honest limits.↗Automate safelyMachine contracts, policy gates, controller ownership, and untrusted output.↗Connect an MCP hostInstall the adapter, authorize only what it needs, validate, and revoke.↗Follow the product roadmapDaily-driver confidence, supported 1.0, connected workspaces, and gated expansion.↗Develop and contributeWorkspace structure, checks, and architecture.↗