Skip to content

Developers · Build with AI

Working on Several Sites

Last updated 18 November 2026

How CloudShell picks the site for each request, so several AI sessions can work on different sites at once.

You can work on more than one site at once with CloudShell: several AI sessions, each on its own site, or one session that moves between sites. This page explains how CloudShell decides which site a request acts on, so a change never lands on the wrong one. It describes CloudShell 1.2.2.

Each Session Has Its Own Selected Site

When your AI selects a site with insites_select_instance, the selection belongs to that AI session only. A second session, such as another Claude Code window or an agent running beside you, keeps its own selection. Selecting a site in one session never moves another.

A session keeps its selection for 30 days. After that, select the site again.

An AI assistant that does not identify its sessions to CloudShell shares one selection for your whole sign-in. In that case, selecting a site in one window changes it for every window, so use the per-request site described below.

Naming the Site in Each Request

Every tool that works on a site takes an optional site UUID. When your AI passes it, that one request acts on the named site and the session's selection does not change. This is the safest way to work when more than one session or agent may be active, because nothing can change the target between two requests.

Uploads are the one difference. An upload link is made for one site, so insites_commit_upload and insites_upload_asset deploy to the site the link was requested for, and refuse a different one.

Checking Where a Change Went

Every tool result ends with the site it acted on: its UUID, its name and its address. Your AI can compare that with the site you asked for. insites_list_instances lists every site you can work on, with your role on each and the site currently selected.

Access Is Checked on Every Request

Naming a site does not get around your access. CloudShell checks each request against your role on the named site, the same way it checks a selection. If you cannot use the site, the request is refused with the same message insites_select_instance gives.

Example Prompts

  • Which sites can I work on, and which one is selected in this session?
  • Deploy the header partial to my staging site, and then to production.
  • Read the logs on the production site without changing the selected site.

Related Pages