Repository navigation
Slipstream v0.1.9
Slipstream v0.1.9 rebases the byok branch onto upstream Warp a806bfb2 from May 8, 2026, while preserving Slipstream's local-first defaults and fork-specific integrations. The rebase was conflict-reviewed rather than applied blindly, with extra attention on remote-server installation, agent conversations, BYOK/local service behavior, and release packaging.
Highlights
- Updated the fork's
masterto upstream Warpa806bfb2and rebasedbyokonto that upstream base. - Preserved Slipstream's BYOK/no-cloud defaults, self-hosted session-sharing relay, local multi-agent backend, Codex/OpenCode integrations, remote-host explorer metadata, and Slipstream README/branding.
- Merged upstream remote-server installer improvements with Slipstream's configurable install URL/channel support, including typed SSH install errors, SCP fallback for hosts without
curl/wget, and bash 3.2 tilde handling. - Pulled in upstream agent and harness work, including Hermes CLI detection, third-party harness MCP/model/context support, Codex model selection, in-app auth-secret creation, local-to-cloud handoff plumbing, and named-agent API key support behind its feature flag.
- Pulled in upstream code, remote, and editor improvements, including remote-backed global buffers, linked-worktree checkout fixes,
DiffStateModellocal/remote separation, remote environment codebase-indexing handshake support, command-palette loading improvements, and notebook Markdown ToC fixes. - Included dependency and security updates from both upstream and the fork, including the upstream diesel advisory fix path and Slipstream's OpenSSL 0.10.79 bump.
Changelog
Added
- OpenCode server conversation support alongside the existing Codex app-server conversation work.
- Codex model controls and MCP OAuth loopback support after rebasing onto upstream agent/harness changes.
- Remote host vertical-tab metadata and SSH remote explorer surfacing in Slipstream.
- Release-maintenance cleanup for the rebased lockfile/import state.
Changed
- Replayed the full Slipstream BYOK/local-agent stack onto the latest upstream Warp base.
- Kept Slipstream's local/no-cloud branding and hidden hosted-account/promotional surfaces while accepting compatible upstream UI and agent-management changes.
- Kept the macOS release workflow on the tag-driven
release-macos.ymlpath for Apple Silicon DMG builds. - Normalized rebased
Cargo.lockentries and cleaned up unused imports introduced by conflict resolution.
Fixed
- Preserved Codex command output across refresh and kept cached/new child conversation refresh behavior working after the upstream conversation model changes.
- Preserved harness metadata persistence for new Codex app-server child conversations.
- Kept remote proxy command quoting for identity keys after the remote-server transport merge.
- Avoided reintroducing older TLS/lockfile entries while merging upstream dependency reductions and fork dependency bumps.
Validation
The rebased branch was validated with targeted checks:
cargo test -p remote_server install_script_with_optionscargo test -p remote_server manager::testscargo test -p warp remote_proxy_command_quotes_identity_keycargo test -p warp refresh_cached_codex_conversationcargo test -p warp start_new_child_conversation_persists_harness_metadatacargo test -p warp agent_iconcargo test -p warp remote_host --libgit diff --check- conflict-marker scan across the repository excluding
target
Release Assets
Pushing v0.1.9 starts the macOS release workflow. When the workflow finishes, this release should contain:
Slipstream.dmgSHA256SUMS
Full changelog: v0.1.8...v0.1.9