217 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
DuProcess	d2fd7ee346	Make post-submit input gate command agnostic	2026-06-27 18:36:45 -04:00
DuProcess	acd22b93e8	Gate manual TUI launch input	2026-06-27 18:05:29 -04:00
DuProcess	ef712a79ee	Gate startup command input before TUI readiness	2026-06-27 17:53:59 -04:00
DuProcess	48a59496b2	Expose build identity in version output	2026-06-27 13:45:48 -04:00
DuProcess	606fad72e3	Respect update prebuilt override	2026-06-27 11:48:06 -04:00
DuProcess	9d0396dbf9	Fix reconnect stale keys and TUI status rendering	2026-06-27 11:46:26 -04:00
DuProcess	f71cd975bc	Make update build current source	2026-06-26 19:34:10 -04:00
DuProcess	4842a129f2	Fix startup command and holder fallback	2026-06-26 19:31:33 -04:00
DuProcess	60d73df5be	Support cross Windows release packaging	2026-06-22 17:19:16 -04:00
DuProcess	f9a378a9cd	Harden release readiness gates	2026-06-22 17:14:59 -04:00
DuProcess	fb6cf4e7c2	Warn on client server version mismatch	2026-06-22 01:52:34 -04:00
DuProcess	c0d83c9133	Add Dosh server restart command	2026-06-22 01:50:39 -04:00
DuProcess	a4b3e7c89b	Add Dosh status command	2026-06-22 01:48:16 -04:00
DuProcess	44717e4956	Harden release upload scripts	2026-06-22 01:42:17 -04:00
DuProcess	149ea07edf	Automate Gitea release publishing	2026-06-22 01:41:34 -04:00
DuProcess	6f40ff9e25	Prefer direct Gitea release assets	2026-06-21 15:52:42 -04:00
DuProcess	b21c2eed9d	Slim release packaging	2026-06-21 11:21:05 -04:00
DuProcess	29d894b43b	Read Gitea release token from config	2026-06-21 11:02:22 -04:00
DuProcess	fcc21c7aef	Make restart reconnect persistent	2026-06-21 10:51:12 -04:00
DuProcess	a029564d80	Add Mosh parity hardening	2026-06-21 10:23:06 -04:00
DuProcess	689d2a9575	Buffer input across reconnect	2026-06-21 09:44:39 -04:00
DuProcess	38e70611c5	Clarify Dosh positioning	2026-06-20 19:44:40 -04:00
DuProcess	6adcdc01e8	Tighten README	2026-06-20 19:43:54 -04:00
DuProcess	742477bf6e	Add Windows client packaging and recovery tools	2026-06-20 19:40:33 -04:00
DuProcess	a202f97704	Quiet missing release lookup v0.1.1	2026-06-20 19:20:55 -04:00
DuProcess	f6ead86db4	Add setup selftest and diagnostics polish	2026-06-20 19:19:29 -04:00
DuProcess	013d653f99	Quiet Gitea prebuilt fallback v0.1.0	2026-06-20 18:10:15 -04:00
DuProcess	4e7e4cff10	Update release artifact checksums	2026-06-20 18:09:25 -04:00
DuProcess	fbad776441	Resolve Gitea release downloads	2026-06-20 18:08:13 -04:00
DuProcess	90d9b583c0	Try prebuilt installers by default	2026-06-20 18:03:11 -04:00
DuProcess	f7c4ebaaf7	Add macOS release artifact evidence	2026-06-20 18:00:56 -04:00
DuProcess	27419f4ca8	Fix Gitea release id parsing	2026-06-20 17:51:36 -04:00
DuProcess	ec2422bc3e	Remove personal host aliases from defaults	2026-06-20 17:50:26 -04:00
DuProcess	d51cc248e7	Add release evidence and audit packet	2026-06-20 10:45:55 -04:00
DuProcess	b44ff8e773	Improve release and benchmark tooling	2026-06-20 10:37:26 -04:00
DuProcess	7884ea2796	Add prebuilt update path	2026-06-19 16:40:58 -04:00
DuProcess	774da7371e	Chunk terminal output below MTU	2026-06-19 16:30:51 -04:00
DuProcess	41cdb0f54f	Add optional command extensions	2026-06-19 16:17:38 -04:00
DuProcess	90e53f4b68	Add reliable stream retransmission	2026-06-19 16:00:51 -04:00
DuProcess	d0d6f59cdf	Add launch hardening gates	2026-06-18 09:45:27 -04:00
DuProcess	25d9a6aefa	Expand native auth and benchmark gates	2026-06-18 09:29:06 -04:00
DuProcess	2835da76b0	Persist only named/prewarmed sessions, not implicit ones ... Implicit sessions (dosh host with no --session) get a random term-<millis>-<pid> name you can never reattach to, so persisting them just left unreattachable holder processes lingering across restarts. The server now only uses a persistent holder for prewarmed or explicitly-named sessions; implicit ones use the in-process shell that dies on restart and reaps on disconnect, as before. Adds a shared protocol::{generate,is}_implicit_session_name as the single source of truth for the name shape, used by both client (generate) and server (detect). Server-only behavior change; wire VERSION unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 22:46:10 -04:00
DuProcess	eec8ef0a02	Fall back to xterm-256color when the client TERM isn't on the server ... dosh propagates the client's TERM, but a server lacking that terminal's terminfo (e.g. xterm-ghostty, xterm-kitty) made tmux/vim fail with "missing or unsuitable terminal". build_shell_command now keeps the requested TERM only when its terminfo exists on this host, otherwise falls back to xterm-256color so remote apps always work. Affects both the in-process and holder-spawned shells. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 17:03:06 -04:00
DuProcess	41256b66b7	persist_sessions: default off (opt-in until stress-tested) ... Restart-survivable sessions change the core model (per-session holder processes + SCM_RIGHTS fd passing). Keep them OFF by default so deploying the build can't flip the daily driver's session model unproven; enable with persist_sessions = true after stress-testing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 14:23:48 -04:00
DuProcess	14b7e75025	Merge persistence: server-restart-survivable sessions (holder + SCM_RIGHTS fd passing)	2026-06-14 14:21:17 -04:00
DuProcess	8b1af51bc6	Persist sessions across server restarts via per-session holders ... Make dosh terminal sessions survive a dosh-server restart (crash/upgrade/systemctl restart): a reattaching client lands on the SAME shell with screen state intact, instead of a fresh one. Design: when persist_sessions is on (new config, default true) each terminal session's shell runs in a small detached per-session holder process (the dosh-server binary re-exec'd as `dosh-server hold`). The holder double-forks + setsid into its own session, opens the PTY, spawns the shell as ITS child, and serves the PTY master fd over a per-session Unix socket via SCM_RIGHTS. The server adopts that fd to build a PtyHandle that DETACHES (does not kill the shell) on drop, so a server exit leaves holder + shell alive. On startup the server scans the runtime dir under sessions_dir/run, reconnects to each live holder, receives the master fd again, restores the persisted vt100 screen, and rebuilds the Session. Screen/scrollback (server-memory only) is mirrored to disk atomically: byte-throttled on the output hot path plus a 2s periodic flush, and restored on re-adoption so reattach repaints. Truly-abandoned persistent sessions are still reaped per the existing grace logic by asking the holder to shut down. Anything in the persistent path failing degrades gracefully to the original in-process shell. PtyHandle gains an Owned (kill-on-drop, unchanged default) vs Adopted (detach-on-drop) backing; resize on an adopted master uses TIOCSWINSZ. No wire-format change, so protocol::VERSION stays 3. New deps: libc (direct). New config: persist_sessions (default true); existing integration tests pin it false to keep exercising the non-persistent path unchanged. Adds tests/integration_smoke.rs::session_survives_server_restart_same_ shell_and_screen: attaches, sets `cd /tmp; export MARK=...`, paints a screen marker, KILLs the server, restarts it on the same config, reattaches and asserts same shell pid + MARK + PWD + restored screen. Plus persist.rs unit tests (name round-trip, screen save/load, dead-holder scan cleanup, SCM_RIGHTS fd round-trip). cargo fmt --check and cargo test green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 14:19:09 -04:00
DuProcess	a88d912d2b	Client: instant SIGWINCH-driven terminal resize (mosh-style) ... The client only polled crossterm size() every 250ms, so window resizes (esp. in VSCode/terminals that signal rather than expecting polling) lagged or felt unresponsive. Add a SIGWINCH select branch that resizes the instant the signal fires, matching mosh (which reacts to SIGWINCH + TIOCGWINSZ). Keep the 250ms poll as a fallback. Client-only; wire VERSION unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 14:02:08 -04:00
DuProcess	683c3cd01d	Merge Wave 2: disconnect status line, prediction tick-policy fix, SSH-agent forwarding (VERSION 3)	2026-06-14 11:11:42 -04:00
DuProcess	9a52d65beb	Add opt-in, security-gated SSH-agent forwarding ... Item 3: SSH-agent forwarding, double-gated (client -A/forward_agent AND server allow_agent_forwarding) and off by default on both ends. Wire: new ForwardingKind::Agent (appended, existing bincode discriminants unchanged). Bumped protocol VERSION 2 -> 3 so a pre-agent peer answers with a clear version-mismatch reject instead of a deserialize error. Client: -A / --forward-agent flag; requires local SSH_AUTH_SOCK. Requests an Agent forwarding during native auth (agent forwarding requires native auth) and, on a server-initiated StreamOpen carrying the reserved @dosh-agent sentinel, splices the stream into the local agent unix socket (separate agent_writers map, TCP forwarding paths untouched). Rejects agent StreamOpens unless it opted in, so a server cannot reach the agent without consent. Server: when the client opted in and allow_agent_forwarding is set, binds a per-session proxy unix socket (dir 0700, socket 0600) before the shell spawns, exports its path as the session's SSH_AUTH_SOCK, and tunnels each connection back to the client over the agent sentinel stream. Applies only to freshly spawned shells (documented). Socket cleaned up on auth/forward failure and when the accept loop ends. SECURITY rationale documented in comments. Tests: 2 end-to-end integration tests (full chain identities round-trip via a PTY-hosted client + looping fake agent; and "no -A => no proxy socket"). Docs updated (README forwarding + disconnect-status note, spec §12.1). fmt + full test suite green (122 tests). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 11:10:44 -04:00
DuProcess	6b2933eb05	Add non-destructive disconnect status line and tick-driven prediction policy ... Item 1: mosh-style disconnect status line. When UDP packets stop arriving, paint a single reverse-video cyan "[dosh] last contact Ns ago — reconnecting…" on the terminal's bottom row using save/restore cursor (ESC7/ESC8) so the app cursor never moves and full-screen TUIs are not corrupted. Cleared the instant a packet resumes and refreshed on the status timer tick. Configurable via client.toml `disconnect_status` (default on) and `DOSH_DISCONNECT_STATUS` env override. State machine and rendered escape sequences are pure and unit-tested. Item 2: re-evaluate the prediction display policy on the select-loop status tick via `Predictor::refresh_policy`, so a latency spike flips speculation on (or off on recovery) promptly instead of waiting for the next keystroke. Repaints only when the on-screen result would change, so idle ticks are no-ops. Tests: 8 new client unit tests (status state machine + overlay bytes, predictor spike/recovery/idle). fmt + full test suite green. No wire-format change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-14 10:57:40 -04:00