docs: update documentation for OpenHands v1.11.0

openhands/usage/agent-canvas/conversations.mdx

@@ -5,6 +5,22 @@
 
 A conversation is a single agent session on the active backend. It has its own message history, tool calls, file changes, selected agent profile, and conversation-specific plugins.
 
+## Child Conversations
+
+When an agent uses `launch_child_conversation`, Agent Canvas can launch a child conversation on a local or Cloud target. Local children can use either an isolated worktree or the parent's shared workspace. Cloud children use the repository and branch selected for the launch.
+
+The child remains linked to its parent, and its result is returned to the parent conversation. Agent Canvas validates the launch inputs before creating the child conversation.
+
+## Conversation List Controls
+
+Use the conversation list controls to manage automation runs and visible tags:
+
+- Choose `All`, `Hide`, or `Only` to include, exclude, or show only automation-run conversations. You can further select individual automation names, including unnamed automations.
+- Pinned conversations remain visible when automation-run filtering would otherwise hide them.
+- Enable the `Tags` preference to show conversation tag chips. Tags are off by default; when there are more tags than fit, Agent Canvas shows a `+N` chip with the remaining count.
+
+Agent Canvas omits reserved tags and raw automation IDs from the chips. LLM metadata is also hidden by default.
+
 ## Follow Agent Activity
 
 While an agent is running, the composer shows a live activity chip for its current unresolved action, such as reading a file or running a command. If no action-specific label is available, it shows `Thinking`. The chip disappears when the agent pauses or completes its work.

openhands/usage/agent-canvas/customize-and-settings.mdx

@@ -12,8 +12,8 @@ Agent Canvas separates **Customize** from **Settings**.
 
 Open the top-level `Customize` area to manage:
 
-- [Skills](/overview/skills)
 - [MCP Servers](/openhands/usage/settings/mcp-settings)
+- [Skills](/overview/skills)
 - [Plugins](/openhands/usage/agent-canvas/plugins)
 
 Use the section navigation inside `Customize` to switch between these pages.
@@ -56,9 +56,10 @@ The `Settings` area currently includes the following sections:
 | `Application` | UI-level preferences and app behavior |
 | `Secrets` | Stored secrets used by the active backend |
 
-On local backends, the `LLM` page also includes an `Available Profiles` area for saved profiles.
 
-In `Settings > Application`, the **Conversation titles** setting selects the LLM profile used to generate conversation titles. **Automatic** uses the active local LLM profile; you can choose another saved profile, like a small, cheap LLM, when you want titles generated independently from the model selected for agent work. The same page shows the installed Agent Canvas version, update availability, and a **Check for updates** button.
+In `Settings > Application`, the **Conversation titles** setting selects the LLM profile used to generate conversation titles. **Automatic** uses the active local LLM profile; you can choose another saved profile, like a small, cheap LLM, when you want titles generated independently from the model selected for agent work.
+
+The main settings nav also shows the installed version of Agent Canvas with a manual **Check for updates** button. When an update is available click on the tile to view details and update information.
 
 Use `Settings > Agent` to choose the active Agent Profile for new conversations. OpenHands profiles reference LLM profiles from `Settings > LLM`; ACP profiles use the external agent's own model configuration.
 

openhands/usage/agent-canvas/managing-automations.mdx

@@ -1,17 +1,17 @@
 ---
 title: Managing automations
 description: Browse, export, import, enable, disable, and run automations from the Agent Canvas Automate view.
 ---
 
 The **Automate** view in Agent Canvas is the in-app control center for your automations. From here you can see all automations on the active backend, inspect their configuration and run history, and manage their lifecycle without leaving the app.
 
 <Note>
   Automations run on the active backend. Switch backends from [Connect and Manage Backends](/openhands/usage/agent-canvas/backends) to see automations on a different backend.
 </Note>
 
 ## Browse and inspect automations
 
-Open the **Automate** tab in the sidebar to see all automations on the active backend. Each row shows the automation name, trigger type, and enabled state.
+Open the **Automate** tab in the sidebar to see all automations on the active backend. Each row shows the automation name, trigger type, and enabled state. When the active backend is healthy but has no automations, the Automate pane remains available and includes an option to add one.
 
 Click an automation to open its detail view. The detail view shows:
 
@@ -24,9 +24,15 @@
 
 A run can be `PENDING`, `RUNNING`, `COMPLETED`, `FAILED`, `CANCELLED`, or `SKIPPED`. A `SKIPPED` run can occur when the backend reaches its concurrency limit. Future backend statuses appear as a neutral status badge so they do not prevent you from viewing the automation.
 
+### Activity Log Costs and Exports
+
+The Activity Log displays a completed run's reported LLM cost in USD to four decimal places. A measured zero cost appears as `$0.0000`; when the backend does not report a cost, no cost appears in the log.
+
+Use the Activity Log export controls to download run data as CSV or JSON. Both formats include a raw numeric `cost` field for every run. An unavailable cost is exported as `null`.
+
 ## Enable and disable automations
 
 Toggle an automation on or off from the kebab menu (⋮) on the automation row, or from the detail view. Disabled automations do not fire on their scheduled trigger or in response to events, but their configuration is preserved.
 
 ## Run an automation manually
 
@@ -86,7 +92,7 @@
 4. Review the preview — it shows the automation's name, trigger type, and prompt.
 5. Confirm to create the automation.
 
 Imported automations are created **disabled**. After importing, open the automation from the list, review its configuration, and enable it when ready.
 
 ## Related guides