Cross-Client Access

Cross-client access lets you continue a running Amp CLI thread from ampcode.com. Start Amp in the CLI, open the thread on the web from a desktop or mobile device, and send messages to keep working from anywhere.

Workspace Access

Workspace admins manage Cross-Client Access in Member Settings. The setting is visible for Enterprise workspaces, including self-serve Enterprise, or when access was already disabled. Access is enabled by default, and this name change does not alter existing saved values.

When access is disabled, members cannot send messages to CLI threads from the web, and they cannot start new threads on their runners from outside the CLI: the web command palette hides runners, and the create_thread tool, Puck, and automations cannot target a runner.

Passkey Authentication

To require recent passkey authentication when interacting with the agent on the web or in the app, enable Require Passkey Authentication for Web & App Interaction in your user security settings. Enterprise workspace admins can require passkey authentication for all workspace members. Only a workspace admin who has authenticated with their own passkey can turn the workspace requirement off again.

Terminal Access

If the web Terminal says terminal access is disabled, restart the CLI with --remote-control-terminal:

$ amp --remote-control-terminal

Then reload the thread page. Use --no-remote-control-terminal to explicitly disable access. When neither flag is provided, AMP_REMOTE_CONTROL_TERMINAL=1 enables access and AMP_REMOTE_CONTROL_TERMINAL=0 disables it. An explicit CLI flag takes precedence over the environment variable.