overview

How It Works

From Remote Host pairing to a recoverable agent session.

The mental model

Manifoldone is a Local and Cloud Workspaces around coding-agent CLIs. A Remote Host you manage performs cloud-session execution, while Manifoldone keeps the session transcript and Git checkpoints recoverable across clients. Local desktop sessions remain available as a secondary workflow.

1. Pair a Remote Host

Connect an Apple-silicon Mac with the one-time pairing command. Public Personal Remote Host support uses an isolated Linux VM on that Mac; pairing does not by itself make provider credentials available to collaborators.

2. Prepare an agent profile

Prepare Claude Code or Codex in the Remote Host’s isolated profile home. Credentials are stored in an envelope-encrypted Vault and materialized only into that dedicated runtime profile when execution needs them. Grok remains a compatible local-desktop provider, not a core Remote Host promise.

3. Open a project

Choose a local project. The sidebar keeps the project, worktree or branch, and its persistent sessions in one hierarchy so it is clear where each agent runs.

4. Start a session

Select a prepared provider profile and send a prompt. Manifoldone launches the real provider CLI on the Remote Host and renders output, tool activity, waiting states, and errors in a structured session surface.

5. Checkpoint and resume

After a successful turn, confirm that its transcript and Git checkpoint were recorded. You can then leave the original terminal and reopen that Agent thread from the desktop, web, or mobile web client. A failed checkpoint is shown as a failure and is not counted as a durable success.

6. Invite a teammate carefully

The project owner can search for an existing registered Manifoldone account or create a seven-day invite link for a member or viewer. Invite tokens are random, stored only as hashes, expire, and can be accepted only once. A new user signs in and returns to the pending invite automatically.

That teammate can review authorized transcripts, artifacts, and diffs. A member can also send the next turn to the same server-side Agent session; a viewer cannot execute. The command records the requesting human and Remote Host execution identity separately, and the provider credential never enters the member’s client.

7. Make the result explicit

The useful loop is not simply “run more agents.” It is: preserve work in a known Git context, let another authorized person understand it, then continue the same Agent session. Turns run in queue order; a member uses an explicit commit, push, pull request, or checkpoint fork when the result needs to become a durable Git action or a separate branch.

Where data and execution live

  • cloud provider execution and working files live in the Remote Host’s isolated runtime; local sessions still execute on the desktop client;
  • provider traffic follows the selected provider CLI and account;
  • connected collaboration sends the session and control data required to render the shared surface;
  • the web surface does not independently execute a local provider CLI.

See the FAQ for the current platform and trust boundaries. For assisted setup, see the private beta.