@tbrandenburg/node-red-agents 0.1.4 → 0.2.0

package/nodes/agent/agent.html

@@ -475,6 +475,12 @@
             the id of the execution to kill, as returned by an earlier run in
             <code>msg.agentExecution.id</code> or an Events message's
             <code>executionId</code>.</dd>
+        <dt class="optional">concurrency <span class="property-type">number</span></dt>
+        <dd>Overrides the Concurrency field at runtime, applied before this
+            message is submitted -- no redeploy needed. Raising it starts any
+            already-queued messages immediately; lowering it only affects
+            future scheduling (already-running executions are never
+            cancelled). Non-numeric/non-positive values are ignored.</dd>
     </dl>
     <h3>Outputs</h3>
     <ol class="node-ports">
@@ -509,7 +515,9 @@
        complete in a different order than the messages arrived; ordering is
        not guaranteed above concurrency 1. On redeploy/removal, queued
        messages are cancelled (a <code>cancelled</code> event plus a Node-RED
-       error) and any still-running agent processes are terminated.</p>
+       error) and any still-running agent processes are terminated. Send
+       <code>msg.concurrency</code> to change the bound at runtime without a
+       redeploy -- see Inputs below.</p>
     <p><b>Terminating a specific execution on demand</b>: send a message with
        <code>msg.operation = "terminate"</code> and <code>msg.executionId</code>
        set to the id to kill (from a prior run's <code>msg.agentExecution.id</code>

package/nodes/agent/agent.js

@@ -342,6 +342,15 @@ module.exports = function (RED) {
         return;
       }
 
+      // Optional per-message override of the deploy-time Concurrency
+      // field, applied before this message is submitted so a raised
+      // bound can immediately start any items already queued from
+      // earlier messages. Invalid values (non-numeric/non-positive)
+      // are ignored -- see ExecutionScheduler.setConcurrency.
+      if (msg.concurrency !== undefined) {
+        node.scheduler.setConcurrency(Number(msg.concurrency));
+      }
+
       let resolved;
       try {
         resolved = {

package/nodes/agent/lib/execution/scheduler.js

@@ -27,6 +27,20 @@ class ExecutionScheduler {
     return this.active.size;
   }
 
+  // Runtime override of the concurrency bound (e.g. from a per-message
+  // msg.concurrency), as opposed to the fixed value passed into the
+  // constructor. Invalid input (non-finite/non-positive) is ignored
+  // rather than falling back to 1 -- an in-flight bound should never be
+  // silently reset by a bad message. Raising the bound immediately
+  // drains eligible queued items via _advance(); lowering it only
+  // affects future scheduling -- already-active items are never
+  // cancelled by this call.
+  setConcurrency(concurrency) {
+    if (!Number.isFinite(concurrency) || concurrency <= 0) return;
+    this.concurrency = Math.floor(concurrency);
+    this._advance();
+  }
+
   get queuedCount() {
     return this.queue.length;
   }

package/nodes/agent-server/agent-server.html

@@ -194,7 +194,7 @@
         <label for="node-input-maxInstances"><i class="fa fa-tasks"></i> Max instances</label>
         <input type="text" id="node-input-maxInstances" placeholder="5" style="width:80px">
         <i class="fa fa-info-circle" style="color:#888; cursor:help; margin-left:4px;"
-           title="Maximum number of daemons this node may have spawned at once. A new no-session-id trigger errors immediately once reached (no queueing). 0 = unlimited."></i>
+           title="Maximum number of daemons this node may have spawned at once. A new no-session-id trigger errors immediately once reached (no queueing). 0 = unlimited. Overridable at runtime via msg.maxInstances."></i>
     </div>
     <div class="form-row agent-server-row-spawn">
         <label for="node-input-startupTimeoutMs"><i class="fa fa-clock-o"></i> Startup timeout</label>
@@ -340,6 +340,12 @@
        configured Operation for a single trigger -- e.g. to ask a message-sending node
        instance for its own current status, without needing a second node pointed at
        nothing.</p>
+    <p>Set <code>msg.maxInstances</code> to override the Max instances field at
+       runtime, without a redeploy -- 0 keeps meaning "unlimited", and
+       negative/non-numeric values are ignored. Lowering it below the current
+       number of tracked daemons never kills any of them; it only blocks
+       <em>future</em> spawns until the count naturally drops back under the
+       new cap.</p>
     <h3>Outputs</h3>
     <ol class="node-ports">
         <li>Result

package/nodes/agent-server/agent-server.js

@@ -464,6 +464,18 @@ module.exports = function (RED) {
         return;
       }
 
+      // Optional per-message override of the deploy-time Max instances
+      // field, applied before spawnNewInstance()'s guard clause reads it
+      // -- no redeploy needed. 0 stays "unlimited" (same as the
+      // constructor's semantics above); negative/non-numeric values are
+      // ignored. Lowering the limit below the current registry size
+      // never evicts already-spawned daemons -- it only blocks *future*
+      // spawns until the count naturally drops back under the new cap.
+      if (msg.maxInstances !== undefined) {
+        const n = Number(msg.maxInstances);
+        if (Number.isFinite(n) && n >= 0) node.maxInstances = Math.floor(n);
+      }
+
       // msg.operation can override the configured default for this one
       // trigger. This matters because each node instance's registry is
       // private (per-node-instance scoping, same as the `agent` node's

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tbrandenburg/node-red-agents",
-  "version": "0.1.4",
+  "version": "0.2.0",
   "description": "Node-RED nodes for running coding agents (opencode, pi) and GitHub CLI operations from flows.",
   "keywords": [
     "node-red",