Skip to Content
Latch Docs

Cloud sessions

Find the simplest way to run Latch in your hosted coding environment.

Install Latch 0.1.6 or later on your machine, run your harness’s setup command in the project, and commit the file it updates. Latch adds its hooks alongside your existing settings. Running setup again keeps the file unchanged. The first cloud prompt downloads and verifies the Latch binary.

Where your session runsStart hereLatch verification
Claude Code cloud, one repository outside Projectslatch install cloud claudeVerified. Edit failures reach the model immediately. Turn-end failures reach it on the next prompt or automatically with continue_once.
Claude Projects or Anthropic-hosted multi-repo sessionsUse Remote Control or run the check directly.Repository command hooks do not load on these surfaces.
GitHub Copilot cloud agentlatch install cloud copilotLinux fixture passed. GitHub denied cloud agent access for the test account or repository. Hosted feedback is unverified.
Codex CloudRun the CLI in the checkout or in CI.Managed orchestration does not run Latch command hooks.
OpenHands Cloud, remote Canvas, or Enterpriselatch install cloud openhandsLinux fixture and local Canvas verified. Hosted feedback is unverified.
OpenCode, Pi, Kimi, or Grok Build on a host you controlInstall where the agent runs.Local integration verified. Managed-service delivery unverified.

Check local compatibility · Verify a hosted session

Claude Code

Single-repository cloud session

latch install cloud claude

Commit .claude/settings.json and start a single-repository cloud session outside Claude Projects.

In hosted tests using the v0.1.6 installer, a read-only turn skipped checks and an edit ran each configured check once. Claude quoted the edit failure in the same turn and the turn-end failure on the next prompt. With turn_end_feedback: "continue_once", Claude quoted the turn-end failure without another user message. Claude cloud settings

Claude Projects and multi-repository sessions

Anthropic-hosted Project threads and multi-repo sessions skip repository hooks. Use Remote Control with your regular Claude Code plugin, or run the check directly in the hosted checkout or in CI. Claude Projects

GitHub Copilot

latch install cloud copilot

Commit .github/hooks/latch.json to the default branch, then start a new cloud task. Your GitHub account and repository need access to Copilot cloud agent. Choose Actions if your checks need dependencies installed before the session. GitHub cloud hooks · Dependency setup

Codex

In managed Codex Cloud, install the CLI and run latch run turn_end in the checkout or in CI. For automatic checks, install the plugin in a Codex CLI session running on the machine with the checkout. Codex cloud hook support

OpenHands

If you control the Canvas backend, use Customize → Plugins. For a hosted workspace, run:

latch install cloud openhands

Commit .openhands/hooks.json and start a conversation with the repository root as the working folder. OpenHands repository hooks

Install in the environment

For manual checks or CI, use the standalone binary in the environment setup and run latch run turn_end in the checkout. The first prompt needs access to GitHub release assets. For restricted networks, allow the release download or run your checks in CI. Standalone downloads

Other integrations

Use the regular plugin install when the harness itself runs alongside the checkout on a VM or container you control.

HarnessWhere to install
OpenCodeInstall on the OpenCode server, even if you connect from a separate desktop app or TUI. OpenCode plugin loading
PiInstall on the machine running Pi and start Pi in the project. You can also commit the project package declaration and trust the workspace on that machine. Pi package scope
Kimi CodeInstall on the host running Kimi Code. Browser and Remote Control use that host. A local CLI with remote tools runs hooks beside the CLI, so use a CLI hosted with the checkout for automatic checks. Kimi Remote Control · Hook location
Grok BuildInstall into Grok Build on the machine you connect to. Remote sign-in
Cursor, Devin, KiroPreview adapters cover local CLI setups. Use the project’s check directly or in CI on managed cloud services.

Verify a new environment

Use either the repository hooks or the native Latch plugin in a session to avoid running checks twice.

  1. In a fresh agent session, try a read-only turn and then a real edit that fails a check. With defaults, the read-only turn should skip and the edit or changed turn should run its configured check once.
  2. Confirm where the report lands, then restore the file and try a passing change. Passing checks are quiet by default. Report timing and continue_once

On this page