Vessel Agent Cloud · private early access

Bring your Harness.
Leave your laptop.

Publish a portable Harness, pin an immutable Harness Revision, and launch a persistent Git-backed cloud Worktree with a retained Session. Agents are designed to continue remotely after your laptop or browser disconnects.

Request early access Explore Harness

Invite-only · pre-launch · no production availability claim

Harness

The environment is the product, not just the prompt.

A Harness is the portable definition of an agent environment. Publishing creates an immutable Harness Revision, and each Session is pinned to exactly one revision.

Harness manifest

agent adapter
OpenCode (first intended Adapter)
revision
immutable after publication
secret names
declared; values excluded

The current MVP supports harness.json and skills. Broader MCP and runtime declarations are Harness product direction, not a claim of availability.

Session continuity

Agents are designed to continue after your laptop goes away.

Agent Cloud keeps the Git-backed Worktree and retained Session remote. Closing a browser or laptop does not make the cloud checkout belong to a local machine.

  1. 01Publish a Harnessan immutable Harness Revision
  2. 02Select connected Git sourcean exact remote commit
  3. 03Create a Worktreepersistent cloud checkout
  4. 04Launch a Sessionpinned to its Adapter and Revision
  5. 05Disconnect and returnthe retained Session is designed to continue remotely

Git-backed Worktree

Start from an exact commit. Keep the checkout for the work ahead.

Agent Cloud resolves a selected connected Git remote to an immutable initial remote commit. Local-only files and unpushed commits are excluded.

connected remote → exact initial commit → persistent Worktree

Shared Worktree

One mutable checkout, several active Session Trees.

Sessions observe the same filesystem and Git concurrency. Vessel does not promise conflict-free writes.

Isolated Worktree

A checkout reserved for one active root Session Tree.

Use it when autonomous work needs separation from other active work.

Product direction

Extend the terminal-first workflow; do not replace it with another chatbot.

Local workflow

  • Developer-owned source and setup
  • Native agent workflow
  • Available while the laptop is available

Agent Cloud direction

  • Portable Harness and immutable Revision
  • Persistent Git-backed Worktree
  • Retained remote Session
  • OpenCode is the first intended Agent Adapter

Private early access

Bring your Harness. Leave your laptop.

Vessel Agent Cloud is pre-launch. We are shaping the product with developers who already have an agent workflow worth keeping.

Request early access