@schlenkr/ragents 0.1.19 → 0.1.20

package/apps/web/dist/help/guide-clients.html

@@ -132,47 +132,26 @@
     <button class="nav-menu" type="button" aria-expanded="false" aria-controls="main-navigation"><span data-menu-label>Menu</span><svg viewBox="0 0 24 24" aria-hidden="true"><path d="m6 9 6 6 6-6"/></svg></button>
   </header><main class="shell" id="main"><div class="guide-layout"><aside class="guide-sidebar"><nav class="guide-chapters" aria-label="Guide navigation"><a href="guide.html">Overview</a><div class="guide-nav-group"><p>Understand</p><a href="guide-ideas.html">Core ideas</a><a href="guide-runtime.html">Actors and messages</a></div><div class="guide-nav-group"><p>Use</p><a href="guide-getting-started.html">Get started</a><a href="guide-clients.html" aria-current="page">Web and VS Code</a><a href="guide-distributed.html">Distributed work</a></div><div class="guide-nav-group"><p>Build</p><a href="guide-functions.html">Work with TypeScript</a><a href="guide-programs.html">Build mini-apps</a><a href="guide-plugins.html">Plugins and skills</a></div><div class="guide-nav-group"><p>Access</p><a href="guide-access.html">Assign permissions</a></div></nav></aside><details class="guide-mobile-nav"><summary>Guide: Web and VS Code</summary><nav class="guide-chapters" aria-label="Guide navigation"><a href="guide.html">Overview</a><div class="guide-nav-group"><p>Understand</p><a href="guide-ideas.html">Core ideas</a><a href="guide-runtime.html">Actors and messages</a></div><div class="guide-nav-group"><p>Use</p><a href="guide-getting-started.html">Get started</a><a href="guide-clients.html" aria-current="page">Web and VS Code</a><a href="guide-distributed.html">Distributed work</a></div><div class="guide-nav-group"><p>Build</p><a href="guide-functions.html">Work with TypeScript</a><a href="guide-programs.html">Build mini-apps</a><a href="guide-plugins.html">Plugins and skills</a></div><div class="guide-nav-group"><p>Access</p><a href="guide-access.html">Assign permissions</a></div></nav></details><article class="guide-body"><header class="guide-title"><p class="eyebrow"><a href="guide.html">Guide</a></p><h1>Web and VS Code</h1><p>Use the same runs in the browser and in the VS Code extension; automate them through the API and command-line tools.</p></header><details class="guide-page-nav"><summary>On this page</summary><nav aria-label="On this page"><a href="#run-panel-and-vs-code-extension">Run panel and VS Code extension</a><a href="#control-ragents-as-an-agent">Control RAgents as an agent</a><a href="#drive-runs-from-external-clients">Drive runs from external clients</a></nav></details><h2 id="run-panel-and-vs-code-extension">Run panel and VS Code extension</h2>
 <p>The run panel is also available in the browser. <code>http://localhost:4710/run-panel.html?run=&lt;id&gt;</code>
-shows a run in a narrow layout with mini-app chips, the selected app, actor chips, chat, and the
-tab bar on the right. Without <code>run</code>, it shows the run list with &quot;New run&quot; as the first
-card. <code>run-panel.html?layout=app&amp;run=&lt;id&gt;&amp;element=&lt;app-id&gt;</code> shows one mini-app without the tab bar.
-Run-panel state, including the selected app and actor, view mode, chat width, collapsed chat
-height, open tab, and tab-area height, is stored per run in the browser.</p>
+shows chat with an addressee selector, mini-app tabs, and the inspection bar on the right.
+Without <code>run</code>, it shows the shared Start page.
+<code>run-panel.html?layout=app&amp;run=&lt;id&gt;&amp;element=&lt;app-id&gt;</code> shows one mini-app without the tab bar.
+The selected app and addressee are stored per run in the browser.</p>
 <p>With write rights, the menu at the top right of an open run offers &quot;Run script&quot;: it lists the run
 scripts you may start, each with its description, and greyed out with the reason when it cannot
 join this run, because its <code>RUN.md</code> does not set <code>embeddable: true</code> or because it fixes a start
 option to a value the run does not have. A click starts it inside the run without a start value;
-the primary actor stays, a repeated start reuses the script, its main view is placed next to the
-tiles, and its output and summary appear in the chat as <code>@handle: ...</code>. If the start is refused,
+the primary actor stays, a repeated start reuses the script, its main view becomes available as an app, and its output and summary appear in the chat as <code>@handle: ...</code>. If the start is refused,
 the menu shows why. The same menu works in the VS Code run panel.</p>
-<p>The narrow tab bar on the right contains the same tabs as the full web view: files, documents,
-functions, executions, and language-server diagnostics, depending on the run and the user&#39;s
-permissions. The tab name appears in a tooltip. A small counter sits at the top right of its
-button, while a dot at the bottom right indicates new activity since the last view. Clicking a
-button opens that tab below the chat with its name and an X in the header. Clicking the same
-button or the X closes it; another button switches tabs. Drag the top handle or use the up and
-down arrow keys to change the area&#39;s height. At least 160 pixels remain for the chat. The open
-tab and height are stored per run in the browser, per VS Code window, and independently from the
-full web view.</p>
-<p>Once a mini-app is selected, three header buttons control the run-panel view: &quot;Chat only&quot;
-(speech bubble), &quot;Chat below&quot; (a sheet over the app), and &quot;Chat right&quot; (beside the app).
-&quot;Chat right&quot; is the default. While the panel is narrower than the
-configured width, that option is disabled and the chat stays below. &quot;Chat only&quot; gives the chat the
-entire panel: the mini-app
-recedes, nothing slides in or out, and an open sheet closes cleanly. Switching back rebuilds the
-mini-app, so unsaved input in it is lost. The choice is stored per run and survives a restart.
-The extension can also open a mini-app as an editor tab in the center, which works well with
-&quot;Chat only&quot; in the run panel.</p>
-<p>In &quot;Chat below&quot;, the handle controls the expanded chat height. Dragging up makes it taller;
-dragging down makes it shorter. The chosen height is stored per run. The collapsed chat shows the
-handle, status, and complete input, including multiple input lines. An open question sits
-completely above the input there as well: the collapsed chat grows by its height, up to half of
-the panel, and the status line reads &quot;Waiting for input&quot;. Hovering or
-writing opens the chat to the chosen height (90 percent of the panel by default). Dragging leaves
-the chat open at its new height. Clicking the handle opens or closes it. With
-keyboard focus on the handle, up and down change the height, Home and End select its limits, and
-Escape cancels an active drag.</p>
-<p>The collapsed chat keeps its rounded border, background, and shadow. The compact handle row
-shows keyboard focus on the small grip itself.</p>
+<p>The inspection rail on the right contains files, documents, functions, executions, and
+language-server diagnostics according to the run and your permissions. Clicking an icon opens
+a panel over the current view. The same icon, Escape, X, or the backdrop closes it. The open
+inspection tab is stored per run. Visited persistent panels keep their state while closed.</p>
+<p>In the browser panel, select Chat or a mini-app in the tab row. Only that view is visible;
+visited apps keep their local input when you switch away. A new app appears without taking focus,
+and an unavailable selected app returns you to Chat. In VS Code, click an app entry to open or
+focus its single editor tab; moving that tab between editor groups does not create a second one.
+The panel stays on chat. Questions and news stay in the chat, and unsent drafts stay with their
+addressee when you switch actors.</p>
 <p>The chip at the left of the chat input names the addressee, the actor your messages go to.
 Clicking it opens the addressee list as a tree of who created whom, like the agent tree of a
 coding assistant: the coordinator at the top, below it the agents and TypeScript actors it
@@ -185,9 +164,8 @@ with their shared handle prefix, their number, and a count per state; click it t
 it. A group that contains the current addressee opens by itself. With more than twelve actors a
 search field appears above the tree; it matches every word against handle, display name, and
 description and keeps the creators of each hit visible. Clicking an entry makes it the addressee
-and closes the list. Hidden actors, as chosen with &quot;Show&quot; in the footer, sit in their own tree
-behind &quot;Hidden actors&quot;; picking one of them also shows it again. In runs recorded before
-actors had descriptions, the description falls back to the first assignment or the display name.</p>
+and closes the list. All actors permitted by your access rights are available, including stopped
+actors. TypeScript actors require inspection rights.</p>
 <p>The extension lives under <code>apps/vscode</code>. It works with all configured <strong>servers at the same
 time</strong>; there is no single active connection. A server in the <code>ragents.connections</code> setting is
 either a server (<code>name</code> and <code>url</code>; it connects automatically when activated and its card asks
@@ -308,8 +286,8 @@ confirmation; to stop a single actor for good, use &quot;Stop&quot; on its actor
 been stopped, the input is replaced by <code>@handle stopped: &lt;reason&gt;</code> and, with permission to operate
 and inspect the run, &quot;Restart&quot;. Restarting the former primary actor makes it the
 primary actor again, and the run chat continues.</p>
-<p>The arrow on a mini-app in the run-panel stage opens it as a central editor tab; &quot;Back to panel&quot;
-closes the tab. Text artifacts and the journal open as read-only documents, while other artifacts
+<p>Click a mini-app in the run panel to open or focus its editor tab. Move and close that tab with
+VS Code; opening it again reuses its current group or creates one editor after it was closed. Text artifacts and the journal open as read-only documents, while other artifacts
 open in the browser. <code>RAgents: New run</code> uses a Quick Pick grouped by server and template.
 The first entry for each server is its default, marked &quot;Default&quot;, or the free task without
 a template. The commands <code>RAgents: Disconnect</code>, <code>RAgents: Connect</code>, and
@@ -317,7 +295,9 @@ a template. The commands <code>RAgents: Disconnect</code>, <code>RAgents: Connec
 <p>When the run chat or a hosted mini-app input has focus, VS Code shortcuts such as Cmd/Ctrl+P
 and Cmd/Ctrl+Shift+P still work using your keybindings, including key chords. This also applies
 to nested hosted mini-app frames. Text entry, selection, undo, and clipboard actions remain in
-the input field. Dictation tools that paste their result, such as HEX, use the same input path.
+the input field. After pasting, focus stays in that input, including in nested mini-apps and
+when the clipboard is empty. You can continue typing or undo without clicking the input again.
+Dictation tools that paste their result, such as HEX, use the same input path.
 Keys already handled by the chat or mini-app are not also executed as VS Code commands.
 In a regular browser, native keyboard and clipboard behavior remains in use.</p>
 <p>To make RAgents smaller or larger independently of VS Code&#39;s window zoom, set <code>ragents.zoom</code>

package/apps/web/dist/help/guide-clients.md

@@ -5,52 +5,29 @@ Use the same runs in the browser and in the VS Code extension; automate them thr
 ## Run panel and VS Code extension
 
 The run panel is also available in the browser. `http://localhost:4710/run-panel.html?run=<id>`
-shows a run in a narrow layout with mini-app chips, the selected app, actor chips, chat, and the
-tab bar on the right. Without `run`, it shows the run list with "New run" as the first
-card. `run-panel.html?layout=app&run=<id>&element=<app-id>` shows one mini-app without the tab bar.
-Run-panel state, including the selected app and actor, view mode, chat width, collapsed chat
-height, open tab, and tab-area height, is stored per run in the browser.
+shows chat with an addressee selector, mini-app tabs, and the inspection bar on the right.
+Without `run`, it shows the shared Start page.
+`run-panel.html?layout=app&run=<id>&element=<app-id>` shows one mini-app without the tab bar.
+The selected app and addressee are stored per run in the browser.
 
 With write rights, the menu at the top right of an open run offers "Run script": it lists the run
 scripts you may start, each with its description, and greyed out with the reason when it cannot
 join this run, because its `RUN.md` does not set `embeddable: true` or because it fixes a start
 option to a value the run does not have. A click starts it inside the run without a start value;
-the primary actor stays, a repeated start reuses the script, its main view is placed next to the
-tiles, and its output and summary appear in the chat as `@handle: ...`. If the start is refused,
+the primary actor stays, a repeated start reuses the script, its main view becomes available as an app, and its output and summary appear in the chat as `@handle: ...`. If the start is refused,
 the menu shows why. The same menu works in the VS Code run panel.
 
-The narrow tab bar on the right contains the same tabs as the full web view: files, documents,
-functions, executions, and language-server diagnostics, depending on the run and the user's
-permissions. The tab name appears in a tooltip. A small counter sits at the top right of its
-button, while a dot at the bottom right indicates new activity since the last view. Clicking a
-button opens that tab below the chat with its name and an X in the header. Clicking the same
-button or the X closes it; another button switches tabs. Drag the top handle or use the up and
-down arrow keys to change the area's height. At least 160 pixels remain for the chat. The open
-tab and height are stored per run in the browser, per VS Code window, and independently from the
-full web view.
-
-Once a mini-app is selected, three header buttons control the run-panel view: "Chat only"
-(speech bubble), "Chat below" (a sheet over the app), and "Chat right" (beside the app).
-"Chat right" is the default. While the panel is narrower than the
-configured width, that option is disabled and the chat stays below. "Chat only" gives the chat the
-entire panel: the mini-app
-recedes, nothing slides in or out, and an open sheet closes cleanly. Switching back rebuilds the
-mini-app, so unsaved input in it is lost. The choice is stored per run and survives a restart.
-The extension can also open a mini-app as an editor tab in the center, which works well with
-"Chat only" in the run panel.
-
-In "Chat below", the handle controls the expanded chat height. Dragging up makes it taller;
-dragging down makes it shorter. The chosen height is stored per run. The collapsed chat shows the
-handle, status, and complete input, including multiple input lines. An open question sits
-completely above the input there as well: the collapsed chat grows by its height, up to half of
-the panel, and the status line reads "Waiting for input". Hovering or
-writing opens the chat to the chosen height (90 percent of the panel by default). Dragging leaves
-the chat open at its new height. Clicking the handle opens or closes it. With
-keyboard focus on the handle, up and down change the height, Home and End select its limits, and
-Escape cancels an active drag.
-
-The collapsed chat keeps its rounded border, background, and shadow. The compact handle row
-shows keyboard focus on the small grip itself.
+The inspection rail on the right contains files, documents, functions, executions, and
+language-server diagnostics according to the run and your permissions. Clicking an icon opens
+a panel over the current view. The same icon, Escape, X, or the backdrop closes it. The open
+inspection tab is stored per run. Visited persistent panels keep their state while closed.
+
+In the browser panel, select Chat or a mini-app in the tab row. Only that view is visible;
+visited apps keep their local input when you switch away. A new app appears without taking focus,
+and an unavailable selected app returns you to Chat. In VS Code, click an app entry to open or
+focus its single editor tab; moving that tab between editor groups does not create a second one.
+The panel stays on chat. Questions and news stay in the chat, and unsent drafts stay with their
+addressee when you switch actors.
 
 The chip at the left of the chat input names the addressee, the actor your messages go to.
 Clicking it opens the addressee list as a tree of who created whom, like the agent tree of a
@@ -64,9 +41,9 @@ with their shared handle prefix, their number, and a count per state; click it t
 it. A group that contains the current addressee opens by itself. With more than twelve actors a
 search field appears above the tree; it matches every word against handle, display name, and
 description and keeps the creators of each hit visible. Clicking an entry makes it the addressee
-and closes the list. Hidden actors, as chosen with "Show" in the footer, sit in their own tree
-behind "Hidden actors"; picking one of them also shows it again. In runs recorded before
-actors had descriptions, the description falls back to the first assignment or the display name.
+and closes the list. All actors permitted by your access rights are available, including stopped
+actors. TypeScript actors require inspection rights.
+
 
 The extension lives under `apps/vscode`. It works with all configured **servers at the same
 time**; there is no single active connection. A server in the `ragents.connections` setting is
@@ -200,8 +177,8 @@ been stopped, the input is replaced by `@handle stopped: <reason>` and, with per
 and inspect the run, "Restart". Restarting the former primary actor makes it the
 primary actor again, and the run chat continues.
 
-The arrow on a mini-app in the run-panel stage opens it as a central editor tab; "Back to panel"
-closes the tab. Text artifacts and the journal open as read-only documents, while other artifacts
+Click a mini-app in the run panel to open or focus its editor tab. Move and close that tab with
+VS Code; opening it again reuses its current group or creates one editor after it was closed. Text artifacts and the journal open as read-only documents, while other artifacts
 open in the browser. `RAgents: New run` uses a Quick Pick grouped by server and template.
 The first entry for each server is its default, marked "Default", or the free task without
 a template. The commands `RAgents: Disconnect`, `RAgents: Connect`, and
@@ -210,7 +187,9 @@ a template. The commands `RAgents: Disconnect`, `RAgents: Connect`, and
 When the run chat or a hosted mini-app input has focus, VS Code shortcuts such as Cmd/Ctrl+P
 and Cmd/Ctrl+Shift+P still work using your keybindings, including key chords. This also applies
 to nested hosted mini-app frames. Text entry, selection, undo, and clipboard actions remain in
-the input field. Dictation tools that paste their result, such as HEX, use the same input path.
+the input field. After pasting, focus stays in that input, including in nested mini-apps and
+when the clipboard is empty. You can continue typing or undo without clicking the input again.
+Dictation tools that paste their result, such as HEX, use the same input path.
 Keys already handled by the chat or mini-app are not also executed as VS Code commands.
 In a regular browser, native keyboard and clipboard behavior remains in use.
 

package/apps/web/dist/help/guide-functions.html

@@ -163,7 +163,7 @@ permissions; plain LLMs with <code>tools: []</code> do not receive it.</p>
 <code>label</code> for people. <code>description</code> briefly explains its purpose and appears in the automatic
 overview. An optional <code>longDescription</code> adds detailed rules, prerequisites, and examples. Input
 and result types come from schemas; descriptions do not replace those contracts. Local recursive
-schema references create named TypeScript aliases, keeping nested contracts such as the tile tree
+schema references create named TypeScript aliases, keeping nested recursive contracts
 fully typed in snippets, actor programs, and the public run API. Resolution includes local
 <code>$defs</code> references; external references are not loaded.</p>
 <p>Without selected names, <code>typescript_api</code> returns the compact catalog. <code>query</code> searches names and

package/apps/web/dist/help/guide-functions.md

@@ -43,7 +43,7 @@ A function registered with `defineRunFunction` has a technical `name` for calls
 `label` for people. `description` briefly explains its purpose and appears in the automatic
 overview. An optional `longDescription` adds detailed rules, prerequisites, and examples. Input
 and result types come from schemas; descriptions do not replace those contracts. Local recursive
-schema references create named TypeScript aliases, keeping nested contracts such as the tile tree
+schema references create named TypeScript aliases, keeping nested recursive contracts
 fully typed in snippets, actor programs, and the public run API. Resolution includes local
 `$defs` references; external references are not loaded.
 

package/apps/web/dist/help/guide-getting-started.html

@@ -130,7 +130,7 @@
       <a class="nav-github" href="https://github.com/SchlenkR/RAgents" aria-label="GitHub"><svg class="gh-icon" viewBox="0 0 24 24" aria-hidden="true"><path fill="currentColor" d="M12 2a10 10 0 0 0-3.2 19.5c.5.1.7-.2.7-.5v-1.7c-2.8.6-3.4-1.3-3.4-1.3-.5-1.2-1.1-1.5-1.1-1.5-.9-.6.1-.6.1-.6 1 .1 1.5 1 1.5 1 .9 1.6 2.4 1.1 3 .9.1-.7.4-1.1.6-1.4-2.2-.3-4.6-1.1-4.6-5 0-1.1.4-2 1-2.7-.1-.3-.4-1.3.1-2.7 0 0 .8-.3 2.8 1a9.6 9.6 0 0 1 5 0c1.9-1.3 2.8-1 2.8-1 .5 1.4.2 2.4.1 2.7.6.7 1 1.6 1 2.7 0 3.9-2.4 4.7-4.6 5 .4.3.7.9.7 1.9V21c0 .3.2.6.7.5A10 10 0 0 0 12 2Z"/></svg><span class="gh-label">GitHub</span></a>
     </nav>
     <button class="nav-menu" type="button" aria-expanded="false" aria-controls="main-navigation"><span data-menu-label>Menu</span><svg viewBox="0 0 24 24" aria-hidden="true"><path d="m6 9 6 6 6-6"/></svg></button>
-  </header><main class="shell" id="main"><div class="guide-layout"><aside class="guide-sidebar"><nav class="guide-chapters" aria-label="Guide navigation"><a href="guide.html">Overview</a><div class="guide-nav-group"><p>Understand</p><a href="guide-ideas.html">Core ideas</a><a href="guide-runtime.html">Actors and messages</a></div><div class="guide-nav-group"><p>Use</p><a href="guide-getting-started.html" aria-current="page">Get started</a><a href="guide-clients.html">Web and VS Code</a><a href="guide-distributed.html">Distributed work</a></div><div class="guide-nav-group"><p>Build</p><a href="guide-functions.html">Work with TypeScript</a><a href="guide-programs.html">Build mini-apps</a><a href="guide-plugins.html">Plugins and skills</a></div><div class="guide-nav-group"><p>Access</p><a href="guide-access.html">Assign permissions</a></div></nav></aside><details class="guide-mobile-nav"><summary>Guide: Get started</summary><nav class="guide-chapters" aria-label="Guide navigation"><a href="guide.html">Overview</a><div class="guide-nav-group"><p>Understand</p><a href="guide-ideas.html">Core ideas</a><a href="guide-runtime.html">Actors and messages</a></div><div class="guide-nav-group"><p>Use</p><a href="guide-getting-started.html" aria-current="page">Get started</a><a href="guide-clients.html">Web and VS Code</a><a href="guide-distributed.html">Distributed work</a></div><div class="guide-nav-group"><p>Build</p><a href="guide-functions.html">Work with TypeScript</a><a href="guide-programs.html">Build mini-apps</a><a href="guide-plugins.html">Plugins and skills</a></div><div class="guide-nav-group"><p>Access</p><a href="guide-access.html">Assign permissions</a></div></nav></details><article class="guide-body"><header class="guide-title"><p class="eyebrow"><a href="guide.html">Guide</a></p><h1>Get started</h1><p>Install RAgents, start a profile, and create your first run.</p></header><details class="guide-page-nav"><summary>On this page</summary><nav aria-label="On this page"><a href="#install-locally">Install locally</a><a href="#configure-model-access-and-start">Configure model access and start</a><a href="#build-after-changes">Build after changes</a><a href="#create-your-first-run">Create your first run</a><a href="#use-the-surface">Use the surface</a></nav></details><h2 id="install-locally">Install locally</h2>
+  </header><main class="shell" id="main"><div class="guide-layout"><aside class="guide-sidebar"><nav class="guide-chapters" aria-label="Guide navigation"><a href="guide.html">Overview</a><div class="guide-nav-group"><p>Understand</p><a href="guide-ideas.html">Core ideas</a><a href="guide-runtime.html">Actors and messages</a></div><div class="guide-nav-group"><p>Use</p><a href="guide-getting-started.html" aria-current="page">Get started</a><a href="guide-clients.html">Web and VS Code</a><a href="guide-distributed.html">Distributed work</a></div><div class="guide-nav-group"><p>Build</p><a href="guide-functions.html">Work with TypeScript</a><a href="guide-programs.html">Build mini-apps</a><a href="guide-plugins.html">Plugins and skills</a></div><div class="guide-nav-group"><p>Access</p><a href="guide-access.html">Assign permissions</a></div></nav></aside><details class="guide-mobile-nav"><summary>Guide: Get started</summary><nav class="guide-chapters" aria-label="Guide navigation"><a href="guide.html">Overview</a><div class="guide-nav-group"><p>Understand</p><a href="guide-ideas.html">Core ideas</a><a href="guide-runtime.html">Actors and messages</a></div><div class="guide-nav-group"><p>Use</p><a href="guide-getting-started.html" aria-current="page">Get started</a><a href="guide-clients.html">Web and VS Code</a><a href="guide-distributed.html">Distributed work</a></div><div class="guide-nav-group"><p>Build</p><a href="guide-functions.html">Work with TypeScript</a><a href="guide-programs.html">Build mini-apps</a><a href="guide-plugins.html">Plugins and skills</a></div><div class="guide-nav-group"><p>Access</p><a href="guide-access.html">Assign permissions</a></div></nav></details><article class="guide-body"><header class="guide-title"><p class="eyebrow"><a href="guide.html">Guide</a></p><h1>Get started</h1><p>Install RAgents, start a profile, and create your first run.</p></header><details class="guide-page-nav"><summary>On this page</summary><nav aria-label="On this page"><a href="#install-locally">Install locally</a><a href="#configure-model-access-and-start">Configure model access and start</a><a href="#build-after-changes">Build after changes</a><a href="#create-your-first-run">Create your first run</a><a href="#use-chat-and-mini-apps">Use chat and mini-apps</a></nav></details><h2 id="install-locally">Install locally</h2>
 <p>The application is built from the repository with Node.js and pnpm. Run these commands from
 the repository root:</p>
 <pre><code class="language-sh">pnpm install
@@ -208,8 +208,7 @@ bundles or an outdated interface and names <code>pnpm build:plugins</code> or <c
 Settings opens the included help. For separate static hosting, <code>pnpm generate:homepage</code> creates
 the same website under <code>docs/homepage/dist</code>.</p>
 <h2 id="create-your-first-run">Create your first run</h2>
-<p>The top-left corner opens the run overview. Choose &quot;New run&quot; to open the start selection. It
-shows the same tiles as the start page in VS Code: &quot;New chat&quot; or the server&#39;s default
+<p>Start shows recent runs and the same templates in the browser and VS Code: &quot;New chat&quot; or the server&#39;s default
 template first, then skill templates with a prepared task and script templates with programmed
 setups. &quot;New chat&quot; opens an empty run whose task you write in its chat; a template starts with one
 click. Some templates collect values in a setup dialog first (&quot;Set up&quot;); a skill template then
@@ -217,27 +216,20 @@ continues in the preparation chat. There you can discuss the task, give a clear
 &quot;Start&quot;, or choose &quot;Create run&quot;. Merely confirming a detail does not start
 anything. In the browser a new run always works on the server; only VS Code and <code>ragents run</code>
 bind a run to a workstation.</p>
+<p>While a template starts, the panel shows its progress in the chat area and reserves the
+bottom status bar, keeping the notice in place when the run connects.</p>
 <p>Inside the run, the coordinator processes the task. Additional agents and mini-apps appear on
 the surface when the workflow creates them. The global coordinator in the header has its own
 conversation and can oversee several runs. The journal and &quot;Executions&quot; tab make events and
 TypeScript calls traceable.</p>
-<h2 id="use-the-surface">Use the surface</h2>
-<p>A run&#39;s surface consists of tiles. Each tile shows an actor or mini-app, and together they
-fill the available space. There is no panning or zooming. Tiles use flat surfaces, outlines,
-and rounded corners without depth. Mini-app content appears at its original size both in the
-tile and in full view.</p>
-<p>Drag an actor or mini-app from the header onto one of a tile&#39;s docking targets. Left and right
-create a side-by-side split; top and bottom create a vertical split. Targets at the outer edge
-split the entire surface. Before you release, a preview shows the resulting area. Drag an
-existing tile by its title bar; the X removes it from the layout. Its content remains available
-through the header. Without access to the actors view, removal and reordering are disabled: the
-X and drag handle are hidden. Dividers for adjusting size ratios remain available.</p>
-<p>Drag a divider to the desired ratio; releasing it saves the value. Escape cancels the active
-resize. With keyboard focus on a divider, arrow keys change its size while Home and End set the
-allowed limits. When space is tight, the &quot;Visible tile&quot; selector displays one item at a time
-without discarding the layout. You can also ask the coordinator: &quot;App on the left, chat on the
-right, 50:50&quot; or &quot;One tile on top, two below at a 2:1 ratio.&quot; Until a layout is specified, the
-surface arranges visible participants itself. Your changes remain saved until the program
-changes its layout. A new program layout is applied automatically so added tiles appear at
-once. &quot;Apply program layout&quot; in the status bar can reset your own layout earlier.</p>
+<h2 id="use-chat-and-mini-apps">Use chat and mini-apps</h2>
+<p>Activated visible mini-apps become available automatically, including those from an embedded setup.
+Programs cannot arrange the host interface. Runs saved with removed layout functions or placements
+are locked with an explanation; their original files are kept. Start a new run with updated programs.</p>
+<p>Browser runs have tabs: Chat, then each available mini-app. Only one view is visible. Chat
+and visited apps keep their input when you switch tabs. New apps appear without interrupting
+your current view. If a selected app becomes unavailable, the panel returns to Chat.</p>
+<p>In VS Code, clicking an app opens or focuses its editor tab. VS Code controls where that tab
+appears. Questions and news stay in chat. The selector below the input chooses the addressee;
+the run coordinator is selected by default.</p>
 <p class="guide-source">Source: <a href="https://github.com/SchlenkR/RAgents/blob/main/docs/operations.md">docs/operations.md</a>, <a href="https://github.com/SchlenkR/RAgents/blob/main/docs/usage.md">docs/usage.md</a>. <a href="guide-getting-started.md">This chapter as Markdown</a>.</p><p><a href="guide-clients.html">Use Web and VS Code</a></p><nav class="guide-next" aria-label="Continue reading"><a href="guide-runtime.html">Previous: Actors and messages</a><a href="guide-clients.html">Next: Web and VS Code</a></nav></article></div></main><footer class="shell"><p>Generated from public documentation. Rebuild with <code>pnpm generate:homepage</code>. Verify with <code>pnpm check:homepage</code>.</p><nav aria-label="More pages"><a href="index.html">Homepage</a><a href="guide.html">Guide</a></nav></footer></body></html>

package/apps/web/dist/help/guide-getting-started.md

@@ -98,8 +98,7 @@ the same website under `docs/homepage/dist`.
 
 ## Create your first run
 
-The top-left corner opens the run overview. Choose "New run" to open the start selection. It
-shows the same tiles as the start page in VS Code: "New chat" or the server's default
+Start shows recent runs and the same templates in the browser and VS Code: "New chat" or the server's default
 template first, then skill templates with a prepared task and script templates with programmed
 setups. "New chat" opens an empty run whose task you write in its chat; a template starts with one
 click. Some templates collect values in a setup dialog first ("Set up"); a skill template then
@@ -108,30 +107,24 @@ continues in the preparation chat. There you can discuss the task, give a clear
 anything. In the browser a new run always works on the server; only VS Code and `ragents run`
 bind a run to a workstation.
 
+While a template starts, the panel shows its progress in the chat area and reserves the
+bottom status bar, keeping the notice in place when the run connects.
+
 Inside the run, the coordinator processes the task. Additional agents and mini-apps appear on
 the surface when the workflow creates them. The global coordinator in the header has its own
 conversation and can oversee several runs. The journal and "Executions" tab make events and
 TypeScript calls traceable.
 
-## Use the surface
-
-A run's surface consists of tiles. Each tile shows an actor or mini-app, and together they
-fill the available space. There is no panning or zooming. Tiles use flat surfaces, outlines,
-and rounded corners without depth. Mini-app content appears at its original size both in the
-tile and in full view.
-
-Drag an actor or mini-app from the header onto one of a tile's docking targets. Left and right
-create a side-by-side split; top and bottom create a vertical split. Targets at the outer edge
-split the entire surface. Before you release, a preview shows the resulting area. Drag an
-existing tile by its title bar; the X removes it from the layout. Its content remains available
-through the header. Without access to the actors view, removal and reordering are disabled: the
-X and drag handle are hidden. Dividers for adjusting size ratios remain available.
-
-Drag a divider to the desired ratio; releasing it saves the value. Escape cancels the active
-resize. With keyboard focus on a divider, arrow keys change its size while Home and End set the
-allowed limits. When space is tight, the "Visible tile" selector displays one item at a time
-without discarding the layout. You can also ask the coordinator: "App on the left, chat on the
-right, 50:50" or "One tile on top, two below at a 2:1 ratio." Until a layout is specified, the
-surface arranges visible participants itself. Your changes remain saved until the program
-changes its layout. A new program layout is applied automatically so added tiles appear at
-once. "Apply program layout" in the status bar can reset your own layout earlier.
+## Use chat and mini-apps
+
+Activated visible mini-apps become available automatically, including those from an embedded setup.
+Programs cannot arrange the host interface. Runs saved with removed layout functions or placements
+are locked with an explanation; their original files are kept. Start a new run with updated programs.
+
+Browser runs have tabs: Chat, then each available mini-app. Only one view is visible. Chat
+and visited apps keep their input when you switch tabs. New apps appear without interrupting
+your current view. If a selected app becomes unavailable, the panel returns to Chat.
+
+In VS Code, clicking an app opens or focuses its editor tab. VS Code controls where that tab
+appears. Questions and news stay in chat. The selector below the input chooses the addressee;
+the run coordinator is selected by default.

package/apps/web/dist/help/guide-ideas.html

@@ -166,7 +166,7 @@ program again so it can assign the next actor.</p>
 the journal does not execute the recorded work again. The
 <a href="guide-runtime.html">runtime guide</a> explains how the pieces fit together.</p>
 <h2 id="mini-apps-make-the-work-interactive">Mini-apps make the work interactive</h2>
-<p>An actor can have a small interface: a mini-app on the surface. It displays the actor&#39;s data
+<p>An actor can have a small interface: a mini-app in the shared panel. It displays the actor&#39;s data
 and calls its functions. In the word game, this interface contains the start button, progress,
 and word list. On the collection board, both an AI assistant and a person can add entries to
 the same list.</p>

package/apps/web/dist/help/guide-ideas.md

@@ -51,7 +51,7 @@ the journal does not execute the recorded work again. The
 
 ## Mini-apps make the work interactive
 
-An actor can have a small interface: a mini-app on the surface. It displays the actor's data
+An actor can have a small interface: a mini-app in the shared panel. It displays the actor's data
 and calls its functions. In the word game, this interface contains the start button, progress,
 and word list. On the collection board, both an AI assistant and a person can add entries to
 the same list.

package/apps/web/dist/help/guide-plugins.html

@@ -270,7 +270,7 @@ function and the owning web-plugin contribution opens it in the correct area. Ke
 state separate from unsent input. Unchanged polling responses must not overwrite drafts, and old
 responses must not replace newer state. Keep loading and errors visible during actions, and retain
 the last valid result after a failed request. Polling must neither overlap nor continue forever
-in hidden areas. Test Enter, buttons, focus, narrow tiles, and dialogs inside the real host
+in hidden areas. Test Enter, buttons, focus, narrow views, and dialogs inside the real host
 iframe; a render test alone does not prove native interactions work there.</p>
 <h3 id="8-choose-evidence-for-what-it-proves">8. Choose evidence for what it proves</h3>
 <p>Contract tests verify inputs, state transitions, and errors. Integration tests verify real

package/apps/web/dist/help/guide-plugins.md

@@ -120,7 +120,7 @@ function and the owning web-plugin contribution opens it in the correct area. Ke
 state separate from unsent input. Unchanged polling responses must not overwrite drafts, and old
 responses must not replace newer state. Keep loading and errors visible during actions, and retain
 the last valid result after a failed request. Polling must neither overlap nor continue forever
-in hidden areas. Test Enter, buttons, focus, narrow tiles, and dialogs inside the real host
+in hidden areas. Test Enter, buttons, focus, narrow views, and dialogs inside the real host
 iframe; a render test alone does not prove native interactions work there.
 
 ### 8. Choose evidence for what it proves

package/apps/web/dist/help/guide-programs.html

@@ -161,7 +161,7 @@ include local modules, while fixed local dependencies come from the host install
 <p><code>package.json</code> contains <code>name</code>, <code>private: true</code>, <code>type: &quot;module&quot;</code>, and <code>ragents</code> metadata with a
 title, optional description, optional backend, and optional named views. Each view has an ID and
 client entry point; its title and stylesheet are optional. A view declares no size; the host sizes
-its tile. At least one backend or view must exist. The host supplies HTML with a <code>root</code> element
+its tab. At least one backend or view must exist. The host supplies HTML with a <code>root</code> element
 for each view. The authoritative schemas are in
 <code>apps/server/src/plugin-support/actor-programs/app-project.ts</code>; a violation names each path and
 its reason, for example <code>views.0 has unknown field width</code>.</p>

package/apps/web/dist/help/guide-programs.md

@@ -40,7 +40,7 @@ include local modules, while fixed local dependencies come from the host install
 `package.json` contains `name`, `private: true`, `type: "module"`, and `ragents` metadata with a
 title, optional description, optional backend, and optional named views. Each view has an ID and
 client entry point; its title and stylesheet are optional. A view declares no size; the host sizes
-its tile. At least one backend or view must exist. The host supplies HTML with a `root` element
+its tab. At least one backend or view must exist. The host supplies HTML with a `root` element
 for each view. The authoritative schemas are in
 `apps/server/src/plugin-support/actor-programs/app-project.ts`; a violation names each path and
 its reason, for example `views.0 has unknown field width`.