@openagents-org/agent-launcher 0.2.192 → 0.2.194

package/README.md

@@ -10,6 +10,24 @@ npm install -g @openagents-org/agent-connector
 
 ## CLI Usage
 
+### Shared thread context
+
+Before each triggered agent turn in a workspace thread, the connector reads
+recent messages from all participants, including human-to-human discussion.
+It includes up to 30 chat messages from the latest 100 events before the
+trigger, in chronological order with speaker names. The transcript is bounded
+to 16,000 characters, with long messages shortened to 2,000 characters each.
+Status updates and the triggering message are excluded from the transcript;
+the current request remains separate. Older messages remain available through
+the workspace history tool.
+
+This does not change mention or response-mode rules. Direct messages keep
+their existing conversation handling. If history cannot be fetched within
+five seconds, the connector logs the failure and continues with the request.
+Existing installations need the updated connector and an agent restart.
+
+### Commands
+
 ```bash
 # Browse available agents
 agent-connector search
@@ -32,8 +50,14 @@ agent-connector status
 # View logs
 agent-connector logs
 
-# Connect to a workspace
-agent-connector connect my-agent <token>
+# Connect this device (formerly "node") to a workspace with a pairing code
+# from Workspace → Devices → Connect a device. Pair once; agents created on
+# this device can then join without a token. `agn node ...` still works.
+agent-connector device connect XXXX-XXXX
+agent-connector device status
+
+# Connect an agent to a paired workspace
+agent-connector connect my-agent --workspace <slug>
 
 # Stop
 agent-connector down
@@ -41,6 +65,12 @@ agent-connector down
 
 Run `agent-connector help` for the full command list.
 
+Only the person who connected a device controls it from the workspace
+(remote add/start/stop of its agents); a workspace admin can only unpair it.
+Every request the connector makes for an agent carries `X-Agent-Name`, so the
+workspace applies that agent's permissions rather than treating the call as an
+anonymous machine.
+
 ## Library Usage
 
 ```js

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openagents-org/agent-launcher",
-  "version": "0.2.192",
+  "version": "0.2.194",
   "description": "OpenAgents Launcher \u2014 install, configure, and run AI coding agents from your terminal",
   "main": "src/index.js",
   "bin": {

package/registry.json

@@ -329,7 +329,7 @@
     },
     "check_ready": {
       "binary": "agent",
-      "not_ready_message": "Cursor is installed but not signed in — run `cursor-agent login` on the device, or set a CURSOR_API_KEY from cursor.com/settings. Third-party or relay API keys do not work with Cursor.",
+      "not_ready_message": "Cursor is installed but not signed in — run `cursor-agent login` on the device (this is separate from signing in to the Cursor editor), or set a CURSOR_API_KEY from cursor.com/settings. Third-party or relay API keys do not work with Cursor.",
       "env_vars": [
         "CURSOR_API_KEY"
       ],
@@ -337,7 +337,11 @@
       "creds_key": "authInfo",
       "creds_no_parse": true,
       "unverifiable": true,
-      "login_command": "cursor-agent login"
+      "login_command": "cursor-agent login",
+      "status_args": [
+        "status"
+      ],
+      "logged_out_pattern": "not logged in|not signed in|not authenticated|unauthenticated|logged out|signed out|login required|partially authenticated"
     },
     "env_config": [
       {
@@ -1323,9 +1327,11 @@
       "env_vars": [
         "GEMINI_API_KEY"
       ],
+      "credential_target": "gemini:antigravity",
+      "unverifiable": true,
       "saved_env_key": "GEMINI_API_KEY",
       "login_command": "agy",
-      "not_ready_message": "Needs sign-in — run `agy` to sign in with Google, or set GEMINI_API_KEY.",
+      "not_ready_message": "Sign-in not confirmed. Run `agy` in a terminal to sign in with Google, or set GEMINI_API_KEY. On Windows the sign-in is detected once it lands in Credential Manager; elsewhere agy keeps it out of reach, so it is confirmed when you run a task.",
       "auth_detected_labels": {
         "cli_login": "Google account sign-in detected",
         "api_key": "API key detected"

package/src/adapters/antigravity-stream.js

@@ -158,7 +158,21 @@ class AgyRunState {
   }
 }
 
-const AUTH_RE = /authentication (required|failed)|not authenticated|sign[ -]?in|log[ -]?in required|no valid credentials|GEMINI_API_KEY/i;
+// Auth phrasings agy and the Gemini API behind it actually produce. The
+// underscored API status codes are spelled out rather than matched as plain
+// English ("permission denied" alone is just as likely to be a file a tool
+// couldn't read), and an expired/missing token counts as auth because the fix
+// is the same sign-in either way.
+const AUTH_RE =
+  /authentication (required|failed)|not authenticated|unauthenticated|sign[ -]?in|log[ -]?in required|no valid credentials|credentials? (not found|missing|expired|invalid)|(access|auth|refresh|id) token (expired|invalid|missing)|permission_denied|GEMINI_API_KEY/i;
+// agy 1.2.2, verbatim, on an account Antigravity will not serve:
+//   Eligibility check failed: Your current account is not eligible for
+//   Antigravity, because it is not currently available in your location.
+// It is checked BEFORE the auth patterns because it is the one failure a
+// sign-in cannot fix — the account is signed in, which is exactly why telling
+// the user to sign in again is the wrong answer.
+const ELIGIBILITY_RE =
+  /eligibility check failed|not (currently )?available in your (location|country|region)/i;
 const PROVIDER_RE = /modelProvider|model provider/i;
 const MODEL_RE = /unknown model|invalid model/i;
 const TIMEOUT_RE = /print-timeout|timed? ?out/i;
@@ -177,6 +191,17 @@ function classifyAgyFailure({ code, stderr, error } = {}) {
     typeof error === 'string' ? error : [err.type, err.message].filter(Boolean).join(' ');
   const text = [errText, stderr].filter(Boolean).join('\n');
 
+  if (ELIGIBILITY_RE.test(text)) {
+    return {
+      kind: 'eligibility',
+      message:
+        'Antigravity CLI refused the run because this Google account is not ' +
+        'eligible for Antigravity — agy reports it is not available in your ' +
+        'location. Signing in again will not change that. The other path this ' +
+        'agent supports is GEMINI_API_KEY, which runs it against the Gemini API ' +
+        'instead.',
+    };
+  }
   if (AUTH_RE.test(text)) {
     return {
       kind: 'auth',
@@ -206,15 +231,50 @@ function classifyAgyFailure({ code, stderr, error } = {}) {
   if (TIMEOUT_RE.test(text)) {
     return { kind: 'timeout', message: 'Antigravity CLI timed out before producing a response.' };
   }
-  const detail = (errText || (stderr || '').trim().split('\n').pop() || '').slice(0, 200);
+  const detail = errText || stderrTail(stderr);
+  if (!detail) {
+    return {
+      kind: 'unknown',
+      message: `Antigravity CLI exited with code ${code ?? '?'} without a response.`,
+    };
+  }
+  // Unclassified, so the CLI's own words lead — but they are often a bare
+  // "Agent execution terminated due to error.", which tells the user nothing
+  // they can act on. Name the first thing worth checking without claiming to
+  // know it is the cause; agy says nothing more specific when it has no usable
+  // credentials, and that is far and away the most common way a run reaches
+  // here.
   return {
     kind: 'unknown',
-    message: detail
-      ? `Antigravity CLI failed (exit ${code ?? '?'}): ${detail}`
-      : `Antigravity CLI exited with code ${code ?? '?'} without a response.`,
+    message:
+      `Antigravity CLI failed (exit ${code ?? '?'}):\n${detail}\n\n` +
+      'If that does not say why, check the sign-in first — run `agy` once in a ' +
+      'terminal to sign in with Google, or set GEMINI_API_KEY for this agent.',
   };
 }
 
+/**
+ * The tail of a CLI's stderr, as a short quotable block.
+ *
+ * The last line alone used to be it, which threw away the informative half of
+ * every multi-line failure: agy prints its detail above a generic closing line,
+ * so what survived was exactly the part that says nothing. Colour codes are
+ * stripped — agy writes them even into a pipe, and they arrive as mojibake in a
+ * chat message.
+ */
+function stderrTail(stderr, { lines = 3, limit = 600 } = {}) {
+  // eslint-disable-next-line no-control-regex
+  const plain = String(stderr || '').replace(/\u001B\[[0-9;?]*[ -\/]*[@-~]/g, '');
+  const kept = plain
+    .split('\n')
+    .map((l) => l.trimEnd())
+    .filter((l) => l.trim())
+    .slice(-lines)
+    .join('\n')
+    .trim();
+  return kept.length > limit ? kept.slice(-limit) : kept;
+}
+
 /**
  * Filesystem candidates for the agy binary, beyond a PATH lookup. The install
  * script targets ~/.local/bin on macOS/Linux and %LOCALAPPDATA%\agy\bin on