@schlenkr/ragents 0.1.7 → 0.1.9

package/apps/web/dist/assets/{runPanel-BJEFQ__w.js → runPanel-ZT6TPDLM.js}

@@ -1,4 +1,4 @@
-import{a as M,I as H,u as Z,r as i,j as e,B as y,J as De,K as Ae,w as ze,l as Fe,m as Te,v as _e,k as Me,P as He,H as ce,L as Ue,q as K,s as de,i as Be,N as ue,O as re,T as Ve,V as $e,A as ie,Y as qe,Z as Ke,_ as Ze,$ as Ge,t as Je,a0 as We,e as Qe,a1 as Ye,a2 as Xe,y as et,z as tt,a3 as nt,a4 as st,a5 as rt,F as it,Q as ot,a6 as at,a7 as lt,G as ct}from"./mermaid-HWGCJPDP-kxkB991i.js";/**
+import{a as M,I as H,u as Z,r as i,j as e,B as y,J as De,K as Ae,w as ze,l as Fe,m as Te,v as _e,k as Me,P as He,H as ce,L as Ue,q as K,s as de,i as Be,N as ue,O as re,T as Ve,V as $e,A as ie,Y as qe,Z as Ke,_ as Ze,$ as Ge,t as Je,a0 as We,e as Qe,a1 as Ye,a2 as Xe,y as et,z as tt,a3 as nt,a4 as st,a5 as rt,F as it,Q as ot,a6 as at,a7 as lt,G as ct}from"./mermaid-HWGCJPDP-DfsU5ofC.js";/**
  * @license lucide-react v1.46.0 - ISC
  *
  * This source code is licensed under the ISC license.

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

@@ -204,11 +204,14 @@ a checkout. <code>ragents.hostPath</code> remains an override pointing to a chec
 The status bar shows the number of connected servers and opens the start page when clicked. See
 the root <code>README.md</code> for details.</p>
 <p>Install the extension from the Marketplace as <code>purestate.ragents-vscode</code> using &quot;Extensions:
-Install Extension&quot; or <code>code --install-extension purestate.ragents-vscode</code>. To install a locally
-packaged file, run <code>pnpm package:vscode</code>, which builds
-<code>dist/ragents-vscode-&lt;version&gt;.vsix</code>, then use &quot;Extensions: Install from VSIX&quot; or
-<code>code --install-extension dist/ragents-vscode-&lt;version&gt;.vsix --force</code>. <code>scripts/vscode/install-local.sh</code>
-performs both steps, rebuilds the built-in plugins, and
+Install Extension&quot; or <code>code --install-extension purestate.ragents-vscode</code>. The Marketplace
+delivers the build for your platform, which carries ripgrep for the <code>bash</code> tool (see
+<a href="guide-distributed.html#work-on-windows">Work on Windows</a> for the Windows bash). To install a locally
+packaged file, run <code>pnpm package:vscode</code>, which builds the universal
+<code>dist/ragents-vscode-&lt;version&gt;.vsix</code> and one <code>dist/ragents-vscode-&lt;platform&gt;-&lt;version&gt;.vsix</code> per
+platform, such as <code>darwin-arm64</code>, then use &quot;Extensions: Install from VSIX&quot; or
+<code>code --install-extension dist/ragents-vscode-darwin-arm64-&lt;version&gt;.vsix --force</code>. <code>scripts/vscode/install-local.sh</code>
+performs both steps with the file for this machine, rebuilds the built-in plugins, and
 rebuilds the web interface if it no longer matches its sources, so that hosts from this checkout
 start again. The script then restarts manually launched
 servers (<code>scripts/start.sh</code>, identified by <code>RAGENTS_LAUNCH=start.sh</code> in their environment, with logs under
@@ -263,7 +266,12 @@ server has locked, for example because its journal uses an older format, shows a
 tooltip names the cause; it does not open, but the selection mode deletes it.</p>
 <p><strong>Server</strong> is the configuration page. You can add, edit, sign in, sign out, connect,
 disconnect, and remove servers with confirmation, then open <code>settings.json</code> from the link
-at the bottom.</p>
+at the bottom. If a connected server does not accept this window&#39;s folders as a workstation, its
+entry says &quot;Arbeitsplatz nicht angemeldet&quot; (workstation not registered) with the cause. When the
+extension and the server carry different workspace executor versions, the cause names both and
+what to update: the extension if it is older, the server if it is newer. The same applies when the
+host the extension uses lacks a plugin bundle the server&#39;s executor carries, such as a language
+server, or carries it in another version: the cause names the plugin and the host to update.</p>
 <p>Every status uses a colored icon and a tooltip with the same vocabulary everywhere. A run is
 &quot;läuft&quot; (running), &quot;wartet auf Eingabe&quot; (waiting for input, with the number of open inputs),
 &quot;ruht&quot; (idle), &quot;beendet&quot; (ended), &quot;fehlgeschlagen&quot; (failed), or &quot;abgebrochen&quot; (cancelled). A

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

@@ -84,11 +84,14 @@ The status bar shows the number of connected servers and opens the start page wh
 the root `README.md` for details.
 
 Install the extension from the Marketplace as `purestate.ragents-vscode` using "Extensions:
-Install Extension" or `code --install-extension purestate.ragents-vscode`. To install a locally
-packaged file, run `pnpm package:vscode`, which builds
-`dist/ragents-vscode-<version>.vsix`, then use "Extensions: Install from VSIX" or
-`code --install-extension dist/ragents-vscode-<version>.vsix --force`. `scripts/vscode/install-local.sh`
-performs both steps, rebuilds the built-in plugins, and
+Install Extension" or `code --install-extension purestate.ragents-vscode`. The Marketplace
+delivers the build for your platform, which carries ripgrep for the `bash` tool (see
+[Work on Windows](guide-distributed.html#work-on-windows) for the Windows bash). To install a locally
+packaged file, run `pnpm package:vscode`, which builds the universal
+`dist/ragents-vscode-<version>.vsix` and one `dist/ragents-vscode-<platform>-<version>.vsix` per
+platform, such as `darwin-arm64`, then use "Extensions: Install from VSIX" or
+`code --install-extension dist/ragents-vscode-darwin-arm64-<version>.vsix --force`. `scripts/vscode/install-local.sh`
+performs both steps with the file for this machine, rebuilds the built-in plugins, and
 rebuilds the web interface if it no longer matches its sources, so that hosts from this checkout
 start again. The script then restarts manually launched
 servers (`scripts/start.sh`, identified by `RAGENTS_LAUNCH=start.sh` in their environment, with logs under
@@ -150,7 +153,12 @@ tooltip names the cause; it does not open, but the selection mode deletes it.
 
 **Server** is the configuration page. You can add, edit, sign in, sign out, connect,
 disconnect, and remove servers with confirmation, then open `settings.json` from the link
-at the bottom.
+at the bottom. If a connected server does not accept this window's folders as a workstation, its
+entry says "Arbeitsplatz nicht angemeldet" (workstation not registered) with the cause. When the
+extension and the server carry different workspace executor versions, the cause names both and
+what to update: the extension if it is older, the server if it is newer. The same applies when the
+host the extension uses lacks a plugin bundle the server's executor carries, such as a language
+server, or carries it in another version: the cause names the plugin and the host to update.
 
 Every status uses a colored icon and a tooltip with the same vocabulary everywhere. A run is
 "läuft" (running), "wartet auf Eingabe" (waiting for input, with the number of open inputs),

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

@@ -287,9 +287,14 @@ After transfer, inspect the journal with <code>pnpm driver journal &lt;runId&gt;
 <li><strong>The VS Code extension for Windows</strong> brings its own bash. The Marketplace delivers a
 <code>win32-x64</code> or <code>win32-arm64</code> build that contains a slim bash with the GNU tools (coreutils,
 <code>grep</code>, <code>sed</code>, <code>awk</code>, <code>find</code>, <code>diff</code>, <code>patch</code>, <code>tar</code>, <code>unzip</code>, <code>cygpath</code> and more), taken from
-a fixed Git for Windows release. The <code>bash</code> tool uses only this bash, for the workspace and for
-the local host; an installed Git Bash or a <code>bash.exe</code> on <code>PATH</code> is never used. PowerShell and
-<code>cmd.exe</code> are not used either.</li>
+a fixed Git for Windows release, plus <code>rg.exe</code> (ripgrep) from a fixed ripgrep release. The
+<code>bash</code> tool uses only this bash, for the workspace and for the local host; an installed Git
+Bash or a <code>bash.exe</code> on <code>PATH</code> is never used. PowerShell and <code>cmd.exe</code> are not used either.</li>
+<li><strong>Code search</strong> runs through <code>rg</code>, which skips <code>node_modules</code>, <code>bin</code>, <code>obj</code> and everything else
+<code>.gitignore</code> excludes. The extension builds for macOS and Linux carry <code>rg</code> as well and put it at
+the front of the <code>bash</code> tool&#39;s <code>PATH</code>, on the workstation and for the local host. The system
+prompt tells the model to search with <code>rg</code> only when the machine running <code>bash</code> has one;
+otherwise it tells the model to exclude dependency and build folders from <code>grep -r</code>.</li>
 <li><strong>Git</strong> is your own <code>git.exe</code> on <code>PATH</code>, for example from Git for Windows. The bundled bash
 contains no git, so your login works as usual: Git Credential Manager, <code>~/.gitconfig</code> and
 <code>~/.ssh</code>. On your own machine the bash inherits your whole environment, except the variables of
@@ -297,7 +302,10 @@ VS Code itself and <code>BASH_ENV</code>/<code>ENV</code>.</li>
 <li><strong>Without the extension</strong> (<code>ragents start</code> or <code>ragents workspace-client</code> from the npm package)
 set <code>RAGENTS_BASH</code> to the <code>bash.exe</code> of such a bundle, for example
 <code>&lt;extension folder&gt;\dist\bash\win32-x64\usr\bin\bash.exe</code>. Without it every <code>bash</code> call fails
-and names what is missing.</li>
+and names what is missing. <code>RAGENTS_RG</code> names an <code>rg</code> in the same way, for example
+<code>&lt;extension folder&gt;\dist\rg\win32-x64\rg.exe</code>, on every platform; without it, an <code>rg</code> on
+<code>PATH</code> is used if there is one. A <code>RAGENTS_RG</code> that points to a missing file stops the server
+start or the workstation&#39;s registration.</li>
 <li><strong>Node.js</strong> is enough with <code>@schlenkr/ragents</code>. A checkout additionally needs <strong>pnpm</strong>, and
 <code>pnpm install</code>, <code>pnpm build:agent</code>, and <code>scripts/start.sh</code> need a bash of your own, such as
 Git Bash.</li>

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

@@ -191,9 +191,14 @@ The local host and workspace also run on Windows. Requirements are:
 - **The VS Code extension for Windows** brings its own bash. The Marketplace delivers a
   `win32-x64` or `win32-arm64` build that contains a slim bash with the GNU tools (coreutils,
   `grep`, `sed`, `awk`, `find`, `diff`, `patch`, `tar`, `unzip`, `cygpath` and more), taken from
-  a fixed Git for Windows release. The `bash` tool uses only this bash, for the workspace and for
-  the local host; an installed Git Bash or a `bash.exe` on `PATH` is never used. PowerShell and
-  `cmd.exe` are not used either.
+  a fixed Git for Windows release, plus `rg.exe` (ripgrep) from a fixed ripgrep release. The
+  `bash` tool uses only this bash, for the workspace and for the local host; an installed Git
+  Bash or a `bash.exe` on `PATH` is never used. PowerShell and `cmd.exe` are not used either.
+- **Code search** runs through `rg`, which skips `node_modules`, `bin`, `obj` and everything else
+  `.gitignore` excludes. The extension builds for macOS and Linux carry `rg` as well and put it at
+  the front of the `bash` tool's `PATH`, on the workstation and for the local host. The system
+  prompt tells the model to search with `rg` only when the machine running `bash` has one;
+  otherwise it tells the model to exclude dependency and build folders from `grep -r`.
 - **Git** is your own `git.exe` on `PATH`, for example from Git for Windows. The bundled bash
   contains no git, so your login works as usual: Git Credential Manager, `~/.gitconfig` and
   `~/.ssh`. On your own machine the bash inherits your whole environment, except the variables of
@@ -201,7 +206,10 @@ The local host and workspace also run on Windows. Requirements are:
 - **Without the extension** (`ragents start` or `ragents workspace-client` from the npm package)
   set `RAGENTS_BASH` to the `bash.exe` of such a bundle, for example
   `<extension folder>\dist\bash\win32-x64\usr\bin\bash.exe`. Without it every `bash` call fails
-  and names what is missing.
+  and names what is missing. `RAGENTS_RG` names an `rg` in the same way, for example
+  `<extension folder>\dist\rg\win32-x64\rg.exe`, on every platform; without it, an `rg` on
+  `PATH` is used if there is one. A `RAGENTS_RG` that points to a missing file stops the server
+  start or the workstation's registration.
 - **Node.js** is enough with `@schlenkr/ragents`. A checkout additionally needs **pnpm**, and
   `pnpm install`, `pnpm build:agent`, and `scripts/start.sh` need a bash of your own, such as
   Git Bash.

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

@@ -156,15 +156,19 @@ that exact environment variable. Startup fails if it is missing. Existing enviro
 take precedence over profile values; no <code>.env</code> file is loaded. Startup reports a missing
 referenced variable as an error. Configured models and reasoning levels must be valid in the
 available model catalog.</p>
-<p>A profile can also name its models by alias: <code>MODEL_ALIASES</code> in the <code>host</code> section lists
-<code>alias=provider/model</code> or <code>alias=provider/model@thinking</code>, and <code>AGENT_PROVIDER: &quot;alias&quot;</code> makes the
-product use them. The interface, the chat, and the journal then show only the alias names.</p>
+<p>A profile can also name its models by alias: <code>MODEL_ALIASES</code> in the <code>host</code> section lists objects
+with <code>alias</code>, <code>model</code> as <code>provider/model</code>, an optional default <code>thinking</code> level, and the model&#39;s
+<code>compaction</code> values: the context size in tokens at which an agent compacts (<code>threshold</code>), how much
+recent context stays verbatim (<code>keepRecentTokens</code>), and the summary budget (<code>summaryTokens</code>).
+<code>AGENT_PROVIDER: &quot;alias&quot;</code> makes the product use them. The interface, the chat, and the journal then
+show only the alias names.</p>
 <p>Alternatively, a profile can obtain its models from another RAgents server running the
-<code>ragents.model-relay</code> plugin, which offers that server&#39;s <code>MODEL_ALIASES</code>: set
-<code>AGENT_PROVIDER: &quot;relay&quot;</code>, point <code>RELAY_URL</code> to that server, use <code>RELAY_TOKEN: env(&quot;...&quot;)</code> with a
-user&#39;s personal token there, and use relay aliases for every model key. Only the relay server can
-see which model is behind an alias. Its log at <code>plugins/ragents.model-relay/relay.log</code> records the
-user, alias, target, and token count for each request.</p>
+<code>ragents.model-relay</code> plugin, which offers that server&#39;s <code>MODEL_ALIASES</code> with their compaction
+values: set <code>AGENT_PROVIDER: &quot;relay&quot;</code>, point <code>RELAY_URL</code> to that server, use
+<code>RELAY_TOKEN: env(&quot;...&quot;)</code> with a user&#39;s personal token there, and use relay aliases for every model
+key. Only the relay server can see which model is behind an alias. Its log at
+<code>plugins/ragents.model-relay/relay.log</code> records the user, alias, target, and token count for each
+request.</p>
 <p>Then start the neutral profile:</p>
 <pre><code class="language-sh">scripts/start.sh core
 </code></pre>

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

@@ -35,16 +35,20 @@ take precedence over profile values; no `.env` file is loaded. Startup reports a
 referenced variable as an error. Configured models and reasoning levels must be valid in the
 available model catalog.
 
-A profile can also name its models by alias: `MODEL_ALIASES` in the `host` section lists
-`alias=provider/model` or `alias=provider/model@thinking`, and `AGENT_PROVIDER: "alias"` makes the
-product use them. The interface, the chat, and the journal then show only the alias names.
+A profile can also name its models by alias: `MODEL_ALIASES` in the `host` section lists objects
+with `alias`, `model` as `provider/model`, an optional default `thinking` level, and the model's
+`compaction` values: the context size in tokens at which an agent compacts (`threshold`), how much
+recent context stays verbatim (`keepRecentTokens`), and the summary budget (`summaryTokens`).
+`AGENT_PROVIDER: "alias"` makes the product use them. The interface, the chat, and the journal then
+show only the alias names.
 
 Alternatively, a profile can obtain its models from another RAgents server running the
-`ragents.model-relay` plugin, which offers that server's `MODEL_ALIASES`: set
-`AGENT_PROVIDER: "relay"`, point `RELAY_URL` to that server, use `RELAY_TOKEN: env("...")` with a
-user's personal token there, and use relay aliases for every model key. Only the relay server can
-see which model is behind an alias. Its log at `plugins/ragents.model-relay/relay.log` records the
-user, alias, target, and token count for each request.
+`ragents.model-relay` plugin, which offers that server's `MODEL_ALIASES` with their compaction
+values: set `AGENT_PROVIDER: "relay"`, point `RELAY_URL` to that server, use
+`RELAY_TOKEN: env("...")` with a user's personal token there, and use relay aliases for every model
+key. Only the relay server can see which model is behind an alias. Its log at
+`plugins/ragents.model-relay/relay.log` records the user, alias, target, and token count for each
+request.
 
 Then start the neutral profile:
 

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

@@ -312,6 +312,7 @@ the built-in plugins live under <code>plugins/&lt;id&gt;/</code>:</p>
   contract.ts        import-free contract shared by both halves, when present
   prompt.hbs         assets at the plugin root, alongside prompts/, skills/,
                      run-scripts/, provision.ts
+  executor.ts        contribution to the workspace executor, when present
 </code></pre>
 <p><code>server/index.ts</code> exports exactly one entry point:</p>
 <pre><code class="language-ts">export const plugin: PluginModule = {
@@ -379,7 +380,8 @@ loads plugin sources; it loads finished bundles, and the author builds them. The
 <code>@schlenkr/ragents</code> carries everything this needs, so an empty folder and the package are enough.</p>
 <p><strong>Source folder.</strong> One folder per plugin, named after its ID, such as <code>acme.tickets</code>. It holds
 <code>ragents-plugin.json</code>, <code>server/index.ts</code> exporting <code>plugin</code>, optionally <code>provision.ts</code> for tools the
-plugin installs, <code>web/index.tsx</code> exporting <code>webPlugin</code> when there is an interface, and assets such
+plugin installs and <code>executor.ts</code> for work that runs on the machine of a workspace, such as a
+language server, <code>web/index.tsx</code> exporting <code>webPlugin</code> when there is an interface, and assets such
 as <code>prompt.hbs</code>, <code>prompts/</code>, <code>skills/</code>, and <code>run-scripts/</code> at the root. <code>ragents-plugin.json</code>
 names the ID, the files other plugins may import (per half, as paths without extension), and
 additional assets that go into the bundle:</p>
@@ -422,7 +424,9 @@ so does a host with the same number that lacks one of the names, as an older hos
 changes only when the host API changes incompatibly, not with every host release.</p>
 <p><strong>Ship.</strong> A bundle is a plain folder without <code>node_modules</code> or native binaries and runs wherever a
 host offers the same host API with the names it uses. Native tools such as language servers come through the plugin&#39;s
-provisioning. To hand a profile together with its bundles to other machines, a server adds
+provisioning. The contribution to the workspace executor becomes one self-contained file that
+imports only Node modules, so every machine can load it, the VS Code extension included; a
+workstation loads it from the bundles of its own host, in exactly the version the server uses. To hand a profile together with its bundles to other machines, a server adds
 <code>ragents.profile-distribution</code>; <code>ragents connect</code> fetches the profile and its bundles and starts
 them with the local host (<a href="guide-distributed.html">Distributed work</a>). The client
 profile names such bundles relative to itself (<code>./</code> or <code>../</code>); the client resolves an absolute or

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

@@ -174,6 +174,7 @@ plugins/ragents.actor-programs/
   contract.ts        import-free contract shared by both halves, when present
   prompt.hbs         assets at the plugin root, alongside prompts/, skills/,
                      run-scripts/, provision.ts
+  executor.ts        contribution to the workspace executor, when present
 ```
 
 `server/index.ts` exports exactly one entry point:
@@ -257,7 +258,8 @@ loads plugin sources; it loads finished bundles, and the author builds them. The
 
 **Source folder.** One folder per plugin, named after its ID, such as `acme.tickets`. It holds
 `ragents-plugin.json`, `server/index.ts` exporting `plugin`, optionally `provision.ts` for tools the
-plugin installs, `web/index.tsx` exporting `webPlugin` when there is an interface, and assets such
+plugin installs and `executor.ts` for work that runs on the machine of a workspace, such as a
+language server, `web/index.tsx` exporting `webPlugin` when there is an interface, and assets such
 as `prompt.hbs`, `prompts/`, `skills/`, and `run-scripts/` at the root. `ragents-plugin.json`
 names the ID, the files other plugins may import (per half, as paths without extension), and
 additional assets that go into the bundle:
@@ -310,7 +312,9 @@ changes only when the host API changes incompatibly, not with every host release
 
 **Ship.** A bundle is a plain folder without `node_modules` or native binaries and runs wherever a
 host offers the same host API with the names it uses. Native tools such as language servers come through the plugin's
-provisioning. To hand a profile together with its bundles to other machines, a server adds
+provisioning. The contribution to the workspace executor becomes one self-contained file that
+imports only Node modules, so every machine can load it, the VS Code extension included; a
+workstation loads it from the bundles of its own host, in exactly the version the server uses. To hand a profile together with its bundles to other machines, a server adds
 `ragents.profile-distribution`; `ragents connect` fetches the profile and its bundles and starts
 them with the local host ([Distributed work](guide-distributed.html)). The client
 profile names such bundles relative to itself (`./` or `../`); the client resolves an absolute or

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

@@ -200,7 +200,8 @@ copy of the current model context, and a new turn does not mean the model starts
 conversation memory.</p>
 <p>When the context grows too large, the agent compacts it: older parts are replaced by a summary
 written by the model, and recent parts are kept. A compaction is recorded in the journal as well,
-and the chat shows a short system note.</p>
+and the chat shows a short system note. When it starts, how much recent context stays verbatim,
+and how long the summary may be are values of the model; a profile sets them for each model alias.</p>
 <h2 id="interrupting-a-turn-stopping-an-actor-stopping-a-run-and-shutting-down-the-server">Interrupting a turn, stopping an actor, stopping a run, and shutting down the server</h2>
 <p>All stop paths follow the same principle: block new work first, then cancel, wait for running
 work, and only then release resources. The exact boundary differs:</p>

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

@@ -84,7 +84,8 @@ conversation memory.
 
 When the context grows too large, the agent compacts it: older parts are replaced by a summary
 written by the model, and recent parts are kept. A compaction is recorded in the journal as well,
-and the chat shows a short system note.
+and the chat shows a short system note. When it starts, how much recent context stays verbatim,
+and how long the summary may be are values of the model; a profile sets them for each model alias.
 
 ## Interrupting a turn, stopping an actor, stopping a run, and shutting down the server