docs: auto-sync cloud-agent with merged PRs (through 2026-10-15)

packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md

@@ -50,6 +50,29 @@ If a compute billing check fails, follow the recovery action next to the compose
 
 Automatic commit and push depends on your session settings. If it is disabled, review, commit, and push the changes you want to keep.
 
+## Choosing where sessions run
+
+A Cloud Agent session runs in a sandbox, the environment that provides its compute. When your account can select a sandbox, the new-session page shows a **Sandbox** field. You can set a default sandbox for your owner account (personal or organization) and override it per repository so you do not have to pick each time.
+
+Open the Cloud Agent settings dialog from the gear at the right of the top bar. It has a **General** tab for where sessions run and a **Profiles** tab for agent environment profiles.
+
+On the **General** tab:
+
+- **Default sandbox** — the sandbox for new sessions when a repository has no override. The dialog names the sandbox that **Platform default** resolves to, so you can see what a session uses when nothing else applies.
+- **Repository overrides** — set or clear a sandbox and an [agent environment profile](#agent-environment-profiles) for an individual repository.
+
+The **Profiles** tab hosts the full profile manager: the profile list on the left and a detail pane on the right with **Overview**, **Variables**, **Setup**, **Slash Cmds**, **MCP**, **Skills**, and **Agents**.
+
+Each change saves as you make it. In an organization, members see the settings read-only; only owners and admins can change them.
+
+When you start a session, the sandbox is resolved in this order: the sandbox you pick in the new-session field, then the repository override, then the owner default, then the platform default. A saved choice that is no longer offered, or that is not available for the repository, falls through to the next level. The new-session picker preselects the sandbox that applies and tags it **Default**.
+
+Vercel sandboxes are offered for GitHub repositories only. If your account cannot select a sandbox, the settings show where sessions run as plain text and the new-session page hides the picker.
+
+## Queueing follow-up messages
+
+The composer stays editable while a session is being prepared or finalized, so you can keep typing and send follow-up messages without waiting for the current turn to finish. Sent messages are queued and processed in order, and the composer shows the current phase while it waits. While a session is still loading, when its connection is unresolved, or when a chat is read-only, the composer does not accept submissions, but anything you have typed is preserved.
+
 ## Starting Tasks from the CLI
 
 Use the `kilo cloud` command to run Cloud Agent tasks without opening the browser:
@@ -105,11 +128,15 @@ Group worktrees into folders in the sidebar. Folders are private to you, not sha
 
 ## Reviewing changes
 
-Select **Changes** in the chat header to review the worktree's saved change summary, including file status and lines added and removed. The panel shows the comparison's base branch and when the summary was saved. Refresh the panel to load the latest saved summary. Large summaries can be partial, with some files or line counts omitted.
+Select **Changes** in the chat header to open the worktree's saved change summary, including file status and lines added and removed. The view shows the comparison's base branch and when the summary was saved, with the changed-file list on the left and the selected file's diff on the right. Selecting another file replaces the diff in place instead of opening a new tab. Refresh to load the latest saved summary; reloading reads the latest saved revision without starting the workspace. Large summaries can be partial, with some files or line counts omitted.
 
-Select a file to open its saved diff and, when available, full contents in a read-only tab. Reloading reads the latest saved revision without starting the workspace.
+While the change view is open, the current workspace tab is not shown as selected. Select that tab to close the view and return to it.
 
-These are saved snapshots, not a live view of the checkout. Diffs or contents may be unavailable for binary, unsupported, or large files, or when there are too many changes to save in full.
+Drag the divider between the list and the diff to resize the file list between 200 and 640 pixels. Kilo saves the width in your browser and restores it the next time you open the view. On narrow viewports the list takes the full width, the diff appears after you select a file, and the resize handle is hidden.
+
+Use the side-by-side toggle in the file viewer to switch between a unified diff and a split, side-by-side diff. The viewer starts in unified and remembers your choice for the files you open next. The markdown preview is unaffected.
+
+These are saved snapshots, not a live view of the checkout. Diffs may be unavailable for binary, unsupported, or large files, or when there are too many changes to save in full.
 
 ## Agent Environment Profiles
 
@@ -121,6 +148,8 @@ Agent environment profiles are reusable bundles of environment settings for clou
 
 Profiles are owned by either a user or an organization. Names are unique per owner, and each owner can have a single default profile. This lets teams share standard environment setups across multiple sessions and triggers.
 
+In the web app, manage profiles from the **Profiles** tab of the [Cloud Agent settings dialog](#choosing-where-sessions-run).
+
 ## Environment Variables & Secrets & Startup Commands
 
 You can customize each Cloud Agent session by also defining env vars and startup commands on the fly. These will override any Agent Environment Profile you've selected:
@@ -258,9 +287,15 @@ The trigger endpoint will return rate limit responses when the number of queued
 Open a trigger's request history to inspect recent invocations. History entries
 show the source (webhook or scheduled), status such as captured, in progress,
 success, or failed, request metadata, payload details when available, and links
-or sharing actions for the resulting session. Use this view to debug webhook
-payloads, scheduled runs, and organization handoff without changing the trigger
-configuration.
+or sharing actions for the resulting session.
+
+Expand a request row to open its **Execution Logs** panel, which shows the cloud
+agent's transcript for that run without requiring you to share the session.
+Active runs refresh automatically every 3 seconds; after a run finishes, the
+panel keeps refreshing for 30 seconds to capture the final log. Use the refresh
+control to reload manually, and enable auto-scroll to follow new output. Use
+this view to debug webhook payloads, scheduled runs, and organization handoff
+without changing the trigger configuration.
 
 ### Prompt Template Variables