Repository navigation
feat: run durable Harness workspaces with browser and terminal clients - #32
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Kinfe123
marked this pull request as ready for review
October 23, 2026 05:45
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Local Tress previously lost its conversation on exit and could not expose that local run to a browser. This source preview starts or reconnects to a background machine host: Harness owns the saved conversation, the machine owns project files and tools, and browser/terminal clients control the same work.
The local host uses atomic Harness snapshots, the Rust/WASM agent, and Tress's existing browser UI. Release builds bundle the host and browser assets; Node 22+ is still required. Managed mode uses HarnessCloud and its backend tunnel with service credentials kept on the host. Optional ANTHROPIC_WORKSPACE_ID is forwarded to model requests, including after a CLI-driven host restart.
Existing assistant-ui applications are an independent integration path. They keep their UI, agent, identity, and hosting, expose an authorized thread list and thread endpoints through a discovery manifest, and let
tress attach <app-origin>list every permitted conversation, including archived threads. API-key, explicitly anonymous, and custom-header access are supported. No Tress UI installation is required in those apps.Documentation now leads with the machine-backed workspace. Added Run on your machine and Embedding and runtimes guides, clarified VM and managed storage, corrected outdated setup/hosting/roadmap claims, and kept released v0.3.0 separate from source-preview capabilities. Markdown exports and deployment checks include the new pages.
Validation on the updated branch:
Release limits: not published in v0.3.0; no new CLI release. Live managed account/tunnel deployment and the release platform matrix remain unverified. One standalone thread per project, loopback-only access, no automatic interrupted-tool recovery, no per-command approval dialog, and no embedded V8 executable. Full history pagination, generic browser login, automatic token refresh, thread creation, and stable public embedding packages remain future work. Full fx.sh parity is not claimed. Supersedes draft #31's custom conversation-store approach; npm packaging #24 remains separate.