[Kinfe123]

Draft: architecture correction required. The requested foundation is a server-owned Harness SDK thread shared by all clients. This implementation uses a native Tress engine and custom thread state, so it does not yet meet that requirement. Reuse the existing Harness host/client integration and attach machine-backed execution/artifact storage to that thread before considering this release-ready.

Tress can run locally, but that process cannot host a browser or persist a shared native conversation. tress serve now runs the existing agent/tools on a local machine or VM and embeds a small browser client. Artifacts remain ordinary workspace files; browser and terminal chat control the same process through Statewire.

• Save admission before executing work, checkpoint completed model/transcript history, lock private state outside the project, and report interrupted turns without replaying tools.
• Browse/download scoped machine files and preview text/raster images. File writes and native shell are separate opt-ins; each shell command needs browser approval.
• Keep this first host single-owner and loopback-only, with SSH forwarding for remote machines. Existing hosted/client commands are unchanged.
• Add real-binary integration checks to CI and every release target. Documentation labels the command as a source preview until published.

Validation passed on macOS ARM64: formatting, Clippy with warnings denied, all 85 Rust tests, optimized release build, four host integration scenarios, CLI release smoke, setup PTY checks, 13 installer tests, JS syntax, documentation links, and browser keyboard/preview/approval checks at wide and narrow viewports. Model responses were scripted; no live model, remote VM, production sandbox, or other release platforms were tested locally. Full repository CI passed on Linux, including the machine-host scenarios, existing-app/access tests, PostgreSQL relay, WASM/workspace tests, TypeScript, production/development host integration, and deployment checks. Browser artifact download was verified byte-for-byte against disk, and a raster image preview was verified.

Limits: one project/conversation per host; browser file previews/approvals, terminal chat; text previews 1 MiB, downloads 32 MiB. Partial output from interrupted runs may be lost, and an already-started shell subprocess may outlive the host. This does not add public multi-user hosting, automatic provisioning, or automatic run recovery. No version tag, release, production deployment, or merge is part of this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
tress	Ready	Preview	Oct 22, 2026 8:05pm UTC