Direction, not a deadline · Product roadmap
The work persists.
The promise grows carefully.
Splinterm has a stable 0.1.0 release on its documented platform. The roadmap works toward a broader 1.0 support contract; stable 0.1.0 does not imply those future guarantees. The horizons below describe outcomes—not dates, feature quotas, or compatibility guarantees.
Current positionStable 0.1.0
- Confidence
- Contract
- Continuity
- Expansion
x86_64 · Omarchy / Arch · native Wayland
North star / Persistent work
Splinterm should become the place terminal work lives while windows, machines, and tools come and go.
The primary human workflow remains the anchor. Automation expands the product; it does not redefine Splinterm as an “AI terminal.” Every support claim stays narrower than the evidence.
01
Now · Stable 0.1.0
Earn daily-driver confidence.
Make persistence understandable, desktop behavior coherent, and installation trustworthy on the environment Splinterm can validate today.
Product outcomes
- Intentional Lair states and lifecycle controls
- Exact theme fidelity and Omarchy integration
- Bounded local-file drop path insertion
- Trustworthy install, recovery, and diagnostics
- Continued performance and memory validation
Graduation signalA new user can leave a Window, return to the same work, and predict every destructive action without maintainer help.
02
Product outcomes
- Declared platform and compatibility boundaries
- Tested upgrade, rollback, and recovery paths
- Stable configuration and machine contracts
- Security and issue-reporting processes
- Visible resource limits and failure behavior
Graduation signalVersion 1.0 is a support contract—not a reward for accumulating features.
03
Later · Connected workspace
Keep one workspace across entry points.
Make local, remote, headless, and authorized tool access feel like ways into the same work instead of separate terminal worlds.
Product outcomes
- Productized remote profiles and recovery
- Stable integration kits and reference journeys
- Distinct human and automation activity
- Portable, non-executable workspace definitions
Graduation signalNo public daemon listener, hosted control plane, synchronized secrets, or collaborative typing is implied.
04
Product outcomes
- Nix and Home Manager workflows
- Additional validated Wayland compositors
- Coherent tertiary distribution artifacts
- A carefully bounded extension model
- Compatibility driven by real applications
Decision testEvery expansion needs a blocked user, continuous validation, a support boundary, and an honest opportunity cost.
Deliberate restraint
Not every direction becomes a promise.
- Reboot-transparent process survival
- Arbitrary
foot.ini compatibility - Unrestricted automation
- Collaborative simultaneous typing
- A hosted cloud control plane
- Broad Linux support without validation
Public product truth
Direction here.
Boundaries in the docs.
This page communicates the product path. Public documentation records strategy, current status, accepted architecture, and supported boundaries; maintainer delivery sequencing is tracked separately.
