---
title: "Live Feedback"
description: "Invite a client into an isolated CloudLink worktree, collect review requests in context, and let an OpenCode agent apply changes without touching the running app."
canonical: "https://opencodecloud.link/docs/live-feedback/"
lastUpdated: "2026-11-19"
---
Live Feedback lets a reviewer open a running preview, describe a change in
context, and have an OpenCode agent apply it in an isolated Git worktree. The
project you are sharing keeps running untouched. Live Feedback is available in
the desktop app. The macOS and Windows downloads include the tray UI; the Linux
download on this site is headless.

## Before you start

- The desktop app is installed and the machine is paired.
- The OpenCode integration is enabled.
- The project has started successfully at least once.
- The project route is enabled with a **Password protected** access policy.
- The project uses a local Git repository with a base branch.
- You accept that preflight and review sessions use your selected OpenCode model
  and may consume model usage.

Live Feedback is not available in services-only mode. Starting and exposing a
project does not require OpenCode; the reviewer workflow does.

## Set up the profile

1. Open the project in **Settings → Projects**.
2. Choose **Set up Live Feedback** after the app has run successfully.
3. Choose the local base branch and the OpenCode model. An agent and extra
   preview instructions are optional.
4. Confirm the project folder and foreground setup script.
5. Choose **Save and test**.

The preflight creates a disposable Git worktree, checks the model and agent, and
tests generation with a fixed prompt. It then runs the setup script with your
permissions and network access and checks the app's HTTP readiness. The test
session and worktree are deleted. A failed test leaves the saved setup available
for editing.

Cloud Link runs at most one preflight per installation. When a reviewer redeems
an invitation, the review needs a spare HTTPS service port; if every port is
occupied, the invitation stays unused until one is free.

## Enable and invite

1. Make sure the project route uses **Password protected** access.
2. Enable the tested profile. The tested Git commit is pinned.
3. Open the Invitations section.
4. Set a reviewer label and a link lifetime: 1 hour, 24 hours, or 48 hours.
5. Create the invitation and copy the one-time link.

Send the link and the project service password through separate channels. The
connector stores only the invitation secret hash. Replacing or revoking an
invitation ends the old link and any active review.

## What the reviewer sees

The reviewer redeems the link with the service password and gets:

- a dedicated Git worktree for that review;
- the app's development server on its own public preview origin;
- a review page that embeds the app and accepts change requests;
- status updates while the agent works;
- a reload of the app preview after a successful edit.

Each review leases a separate HTTPS service port, so the app content has its own
browser origin. The preview forwards HTTP and WebSocket traffic, including
root-relative assets and development reload connections.

Reviewer requests do not enter OpenCode's native shell, plugin, MCP, or tool
execution endpoints. The connector asks the selected OpenCode session for text
generation and applies file operations through its worktree broker. The broker
permits bounded text file reads and writes under the review worktree and rejects
links, Git metadata, sensitive configuration paths, and path escapes.

Each edit has a 20-minute deadline. The connector keeps the latest 32 turns and
the reviewer can continue from the saved worktree after a partial or failed
change. Reviewer-facing results are plain outcomes; provider diagnostics and raw
summaries stay private.

## What the owner sees

The project's review list shows the reviewer, review state, worktree path, and
actions:

- **View summary** generates a short recap of completed reviewer requests.
- **Open OpenCode** opens the review session in the managed OpenCode window.
- **Push to origin** commits non-ignored worktree changes and pushes the branch
  `cloudlink-review/<review-id>` without merging it.
- **Stop** ends reviewer access and preserves the worktree.
- **Discard** removes a stopped worktree after a fresh Git cleanliness check.

Expiry, revocation, a route or password change, a profile change, or stopping the
project invalidates the reviewer session and stops its preview. The owner can
still inspect the worktree and OpenCode session.

## Security and limits

- Share only with trusted reviewers. The preview can execute edited code with
  your permissions.
- The service must remain password protected for reviewer access.
- Reviewer login attempts are rate limited and review mutations require the same
  origin.
- Detection and cleanup are local to the connector; there is no hosted review
  service.
- Live Feedback is a desktop workflow. It is not exposed through the remote
  service API or the connector MCP.
- Model usage and preview port capacity are real limits. Plan around them.

## Troubleshooting

| Symptom | Check |
| --- | --- |
| Live Feedback is hidden | Start and expose the project first, and enable OpenCode |
| Enable is refused | Save and test the exact profile; enable it only after the test passes |
| No reviewer preview | A preview port must be free; try again after one is released |
| Reviewer cannot sign in | Use the current invitation link and the current service password |
| Edit fails | Check the selected model and agent, then retry from the saved worktree |
| Push to origin fails | Confirm Git credentials and that the review branch does not conflict |
| Discard is refused | Stop the review and commit or discard tracked changes first |

## Related

- [Projects](/docs/projects/)
- [Share a local app with clients](/docs/sharing-with-clients/)
- [Exposed services](/docs/exposed-services/)
- [Security and privacy](/docs/security/)