Skip to content

feat: run durable Harness workspaces with browser and terminal clients - #32

Merged
Kinfe123 merged 7 commits into
mainfrom
feat/harness-runtime
Oct 23, 2026
Merged

Kinfe123 merged 7 commits into
mainfrom
feat/harness-runtime

Conversation

@Kinfe123

@Kinfe123 Kinfe123 commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

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:

  • Rust formatting, Clippy with warnings denied, all 86 Rust tests, setup PTY checks, and CLI release smoke passed.
  • Five browser-client tests and six machine-host tests passed, including real CLI embedded-runtime restart, provider workspace-header forwarding, persisted history, real files, access checks, and the managed tunnel fixture.
  • Three existing-app integration tests passed, covering shared browser/native history, run survival, app authorization/revocation, discovery of 26 permitted threads, archived threads, and thread switching.
  • Site TypeScript and production build passed. Full site host suite: 47 passed, 3 PostgreSQL cases skipped locally, and all production/connected-folder scenarios passed.
  • Isolated Vercel function verification passed for the app, docs, both new pages, and inline Markdown exports.
  • Browser verification at desktop/mobile sizes confirmed new navigation and readable content, no horizontal page overflow, and no console errors. 79 local documentation links and diff checks passed.
  • GitHub CI 39907186377 passed for b606894, including PostgreSQL, development host, and deployment checks. No outstanding review feedback.

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.

@vercel

vercel Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
tress Ready Ready Preview Oct 23, 2026 5:44am UTC

Request Review

@Kinfe123 Kinfe123 changed the title feat: persist machine workspaces with Harness SDK feat: host durable Harness workspaces with reusable Tress clients Oct 22, 2026
@Kinfe123 Kinfe123 changed the title feat: host durable Harness workspaces with reusable Tress clients feat: use durable Harness hosts for native Tress clients Oct 22, 2026
@Kinfe123 Kinfe123 changed the title feat: use durable Harness hosts for native Tress clients feat: run durable Harness workspaces with browser and terminal clients Oct 23, 2026
@Kinfe123
Kinfe123 marked this pull request as ready for review October 23, 2026 05:45
@Kinfe123
Kinfe123 merged commit 64c5c79 into main Oct 23, 2026
4 checks passed

This branch was successfully deployed

1 active deployment
Preview — b606894d Deployed Oct 23, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant