@bridge4dev/runner 0.39.0 → 0.40.0

package/dist/adapters/claude.js

@@ -287,6 +287,15 @@ class ClaudeSession {
     mcpFallbackNotice = null;
     /** Guards against overlapping capability probes. */
     capabilitiesInFlight = false;
+    /**
+     * Has the first main-loop answer of this process already asked for the
+     * context window? (ticket #223)
+     *
+     * `q` is `readonly` — one adapter per CLI process — so this never needs
+     * resetting: a restarted process is a new instance with the flag back to
+     * false, which is exactly the moment the meter needs a fresh number.
+     */
+    contextProbedAfterFirstReply = false;
     mode;
     /**
      * A launch-time mode this workspace does not allow, remembered so the feed
@@ -559,6 +568,13 @@ class ClaudeSession {
         // message would otherwise show no model list at all — while the control
         // requests themselves work as soon as the CLI is up.
         this.refreshCapabilities();
+        // Same reasoning for the context meter (ticket #223). It used to be asked
+        // for only at the END of a turn, so a session that had not finished its
+        // first one had no numbers at all and the gauge did not exist — worst in a
+        // session that parked a question, which can sit there for hours. This probe
+        // costs one control round-trip and gives the meter its denominator (the
+        // model's window) from the moment the process is up.
+        this.refreshContextUsage();
     }
     /**
      * Write this session's MCP config to a 0600 file and return its path, or null
@@ -623,10 +639,14 @@ class ClaudeSession {
         this.output.push(maskSecrets(event));
     }
     /**
-     * How full the context window is, after a finished turn. Fire-and-forget with
-     * a timeout on purpose: this is one more control round-trip on a channel that
-     * can hang, and it must never be able to stall the event loop that carries the
-     * conversation.
+     * How full the context window is. Fire-and-forget with a timeout on purpose:
+     * this is one more control round-trip on a channel that can hang, and it must
+     * never be able to stall the event loop that carries the conversation.
+     *
+     * Called from four places, each answering a different gap: process start and
+     * first main-loop reply (ticket #223 — otherwise a session shows no gauge at
+     * all until its first turn ends), model change (the window's size differs 5x
+     * between 200k and 1M), and end of turn.
      */
     refreshContextUsage() {
         if (this.stopped)
@@ -1845,6 +1865,17 @@ class ClaudeSession {
                                 });
                             }
                         }
+                        // Ticket #223. The startup probe fires before the CLI has read
+                        // anything, so its number is the empty window; this one lands after
+                        // the agent has actually said something and is the first figure
+                        // worth showing. Once per process, and only for the main loop: it is
+                        // a control round-trip on a channel that can hang, subagent chatter
+                        // is not this session's context, and the end-of-turn probe covers
+                        // everything after.
+                        if (!fromSubagent && !this.contextProbedAfterFirstReply) {
+                            this.contextProbedAfterFirstReply = true;
+                            this.refreshContextUsage();
+                        }
                         break;
                     }
                     case 'user': {

package/dist/attachments.js

@@ -18,9 +18,32 @@ const execFileAsync = promisify(execFile);
  */
 /** Directory inside the worktree; also the line written to info/exclude. */
 export const ATTACHMENT_DIR = '.devbridge/attachments';
-/** Hard ceiling per file; the API allows 10 MB for images and 25 MB otherwise. */
-const MAX_ATTACHMENT_BYTES = 26 * 1024 * 1024;
-const DOWNLOAD_TIMEOUT_MS = 60_000;
+/**
+ * Hard ceiling per file; the API allows 10 MB for images and 50 MB otherwise.
+ *
+ * Mirror of `MAX_DOCUMENT_ATTACHMENT_SIZE_BYTES` in `@devbridge/shared` plus a
+ * megabyte of slack — the runner cannot import that package (see
+ * `recipe-schema.ts`: the published tarball would not resolve it). The slack is
+ * what keeps the two halves from disagreeing on a rounding: the API refuses
+ * first, with an error the person actually sees, and this only catches bytes
+ * that no upload path should have produced.
+ *
+ * Raise the API side and this one in the SAME runner release. A ceiling that
+ * moves only in DevBridge lets a file upload and then vanish: the refusal below
+ * is a warning line in the session, not something the uploader is shown.
+ */
+const MAX_ATTACHMENT_BYTES = 51 * 1024 * 1024;
+/**
+ * A minute was plenty while the ceiling was 26 MB; at 50 MB it is a coin flip.
+ *
+ * The whole file is buffered by the API and pushed through nginx in one
+ * response, so this timeout covers the entire transfer, not idle time between
+ * packets. 60 s for 50 MB demands ~7 Mbit/s sustained end to end — ordinary for
+ * two VPSes, not ordinary for a dev server on a home uplink or behind a
+ * throttled proxy. Three minutes covers ~2.3 Mbit/s, and the cost of being
+ * generous is nil: a stalled download fails the same way, just later.
+ */
+const DOWNLOAD_TIMEOUT_MS = 180_000;
 /**
  * A file name that is safe to write and unambiguous to read.
  *
@@ -153,9 +176,16 @@ export async function saveAttachments(input) {
     pruneAttachmentDir(dir);
     return { saved, failed };
 }
-/** Keep at most this much history in one worktree's attachment folder. */
+/**
+ * Keep at most this much history in one worktree's attachment folder.
+ *
+ * Sized in files, not in bytes: 512 MB was twenty attachments at the old 25 MB
+ * ceiling and would be ten at the new one — an afternoon of work, after which
+ * the folder starts evicting documents a running session may still be told to
+ * open. A gigabyte restores the same twenty-file depth.
+ */
 const ATTACHMENT_RETENTION_MS = 14 * 24 * 60 * 60 * 1000;
-const ATTACHMENT_DIR_BUDGET_BYTES = 512 * 1024 * 1024;
+const ATTACHMENT_DIR_BUDGET_BYTES = 1024 * 1024 * 1024;
 /**
  * Delete old attachments from a session worktree.
  *

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const RUNNER_VERSION = "0.39.0";
+export declare const RUNNER_VERSION = "0.40.0";
 //# sourceMappingURL=version.d.ts.map

package/dist/version.js

@@ -1,3 +1,3 @@
 // Kept in sync with package.json by the release script (manual for now).
-export const RUNNER_VERSION = '0.39.0';
+export const RUNNER_VERSION = '0.40.0';
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bridge4dev/runner",
-  "version": "0.39.0",
+  "version": "0.40.0",
   "description": "DevBridge dev runner — connects a dev server to DevBridge and runs agent sessions (Claude Code / Codex)",
   "homepage": "https://bridge4.dev",
   "license": "MIT",