@polygraph/opencode-plugin 0.4.28 → 0.4.30

package/agent-capture-mapping.mjs

@@ -0,0 +1,90 @@
+// Agent-capture mapping writer for the OpenCode plugin.
+// Exported from this sibling module (NOT from server.js) so it can be tested
+// independently. See server.js for the constraint on why server.js itself must
+// stay export-free beyond its plugin entry.
+//
+// Records the (agentSessionId ↔ polygraphSessionId) mapping file so the
+// Polygraph CLI can bind parent-log capture deterministically. Written on
+// every session start and compaction; the CLI reader looks for mapping-*.json
+// files in the per-session sidecars directory.
+//
+// File contract:
+//   ~/.polygraph/sidecars/<POLYGRAPH_SESSION_ID>/mapping-opencode-<sessionId>.json
+//
+// Behaviour:
+//   - Silent no-op when POLYGRAPH_SESSION_ID is unset or POLYGRAPH_CHILD_AGENT is set.
+//   - Atomic write via tmp-file rename.
+//   - Refresh: preserves firstSeenAt when a valid prior mapping exists.
+//   - All failures are silently swallowed.
+
+import { existsSync, mkdirSync, readFileSync, renameSync, writeFileSync } from 'node:fs';
+import { homedir } from 'node:os';
+import path from 'node:path';
+
+function sanitizeMappingFilename(str) {
+  return str.replace(/[^A-Za-z0-9._-]/g, '_');
+}
+
+/**
+ * Write (or refresh) the agent-capture mapping for an OpenCode session.
+ * Reads POLYGRAPH_SESSION_ID and POLYGRAPH_CHILD_AGENT from process.env.
+ *
+ * @param {string} agentSessionId  The OpenCode session id (input.sessionID).
+ * @param {string} [home]          Override HOME for testing.
+ */
+export function writeAgentCaptureMapping(
+  agentSessionId,
+  home = process.env.HOME?.trim() || homedir()
+) {
+  try {
+    const polygraphSessionId = process.env.POLYGRAPH_SESSION_ID;
+    if (!polygraphSessionId) return;
+    if (process.env.POLYGRAPH_CHILD_AGENT) return;
+    if (!agentSessionId) return;
+
+    const sidecarDir = path.join(home, '.polygraph', 'sidecars', polygraphSessionId);
+    mkdirSync(sidecarDir, { recursive: true });
+
+    const filenamePart = sanitizeMappingFilename(`opencode-${agentSessionId}`);
+    const finalPath = path.join(sidecarDir, `mapping-${filenamePart}.json`);
+    const tmpPath = `${finalPath}.tmp-${process.pid}`;
+
+    const now = Date.now();
+    let firstSeenAt = now;
+
+    if (existsSync(finalPath)) {
+      try {
+        const existing = JSON.parse(readFileSync(finalPath, 'utf8'));
+        if (
+          existing.version === 1 &&
+          existing.polygraphSessionId === polygraphSessionId &&
+          existing.agentSessionId === agentSessionId &&
+          Number.isFinite(existing.firstSeenAt)
+        ) {
+          firstSeenAt = existing.firstSeenAt;
+        }
+      } catch {
+        // ignore — treat as missing
+      }
+    }
+
+    const mapping = {
+      version: 1,
+      polygraphSessionId,
+      agentType: 'opencode',
+      agentSessionId,
+      cwd: process.cwd(),
+      // OpenCode transcripts are resolved by the CLI from its own storage by
+      // session id, so we omit transcriptPath here.
+      pid: process.pid,
+      source: 'hook',
+      firstSeenAt,
+      lastSeenAt: now,
+    };
+
+    writeFileSync(tmpPath, JSON.stringify(mapping, null, 2) + '\n');
+    renameSync(tmpPath, finalPath);
+  } catch {
+    // Silent — a broken plugin hook must never break the agent session.
+  }
+}

package/agents/polygraph-init-subagent.md

@@ -15,7 +15,7 @@ These tools are available via MCP and CLI. Use whichever is available in your en
 
 | MCP Tool | CLI Equivalent | Description |
 | --- | --- | --- |
-| `list_repos` | `polygraph repo list` | Discover candidate repositories with descriptions and graph relationships |
+| `list_repos` | `polygraph repo list` | Discover candidate repositories. |
 | `start_session` | `polygraph session start --repo <ids>` | Initialize a NEW session with selected repositories. Only use when no `sessionId` was provided. |
 | `add_repo` | — | Attach repositories to an EXISTING session. Use when `sessionId` was provided and the session has no repos yet, or when the user wants to add more. |
 | `show_session` | `polygraph session show <id> [--details]` | Get full session details including URL, and use details when session summary, repo IDs, PR URLs, and PR descriptions are needed |
@@ -58,16 +58,22 @@ Call `list_repos` to discover available candidate repositories:
 list_repos()
 ```
 
+`list_repos` accepts these optional parameters; set whichever apply. Refer to the tool schema for each parameter.
+
+- `connectedTo`: repo ID, name, or full name (e.g. `nrwl/ocean`); pair with `connectionType`
+- `connectionType`: `directly-upstream` | `directly-downstream` | `directly-both` (default) | `upstream` | `downstream` | `both`
+- `publishedPackages`, `consumedPackages`, `publishedApis`, `consumedApis`: arrays of package names / API paths
+- `nameFilter`: array of repo name patterns (e.g. `nrwl/*`)
+- `semanticQuery`: free-text description of the repositories you want
+
 This returns:
 
-- **`initiator`**: The current repository, or `null` if not running from a specific repo
-- **`candidates`**: Candidate account repositories, each with:
+- **`repos`**: Candidate account repositories, each with:
   - `id`: Repository ID
   - `name`: Repository name
+  - `repository`: Full repo name (e.g., `org/repo`)
+  - `provider`: VCS provider (e.g., `GITHUB`)
   - `description`: AI-generated description of what the repository does (may be null)
-  - `vcsConfiguration.repositoryFullName`: Full repo name (e.g., `org/repo`)
-  - `graphRelationship`: How this repository relates to the initiator (`distance`, `direction`, `path`), or `null` if the repository is not in the dependency graph. When `initiator` is null, `graphRelationship` will be null for all candidates.
-- **`dependencyGraph`**: Graph of repository dependency `edges` (always available, independent of initiator)
 
 ### Step 2: Select Relevant Repos
 
@@ -77,14 +83,11 @@ If `selectedRepoIds` or exact repo refs were provided by the main agent, use tho
 
 Otherwise, analyze the candidates using the `userContext` to determine which repos are relevant:
 
-1. Read each candidate's `description` and `graphRelationship`
-2. Match against the `userContext` — consider:
-   - Repository descriptions that mention relevant functionality
-   - Graph relationships (closer repos are more likely relevant); note that `graphRelationship` may be `null` for repositories not in the dependency graph — use their `description` to assess relevance
-   - When `graphRelationship` is null for all candidates (no initiator), rely on `description` fields and the raw `dependencyGraph` edges for selection instead
-   - Direction (upstream/downstream based on the nature of the change)
-3. Select only the repos that are clearly relevant to the task
-4. If uncertain which repos are relevant, include all candidates (safe default)
+1. Read each repo's `description`
+2. Match repo descriptions against the `userContext` to identify relevant repos
+3. Select the repos that are relevant to the task
+4. When uncertain, include all candidates
+5. When the user described the task in natural language and the result is large, re-query with `semanticQuery` set to that description
 
 ### Step 3: Initialize Polygraph Session or Attach Repos
 
@@ -140,11 +143,6 @@ Return a structured summary in this format:
 | Repo | Repository ID | Description | Selected |
 | --- | --- | --- | --- |
 | REPO_FULL_NAME | REPOSITORY_ID | DESCRIPTION | Yes/No |
-
-### Initiator
-(Only include this section if `list_repos` was called and `initiator` is non-null)
-- **Name:** <initiator name>
-- **Repo:** <initiator repo full name>
 ```
 
 ## Important Notes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polygraph/opencode-plugin",
-  "version": "0.4.28",
+  "version": "0.4.30",
   "description": "AI agent skills and subagents for Polygraph multi-repo coordination",
   "license": "UNLICENSED",
   "private": false,
@@ -24,6 +24,7 @@
   },
   "files": [
     "server.js",
+    "agent-capture-mapping.mjs",
     "skills/",
     "agents/",
     "README.md"

package/server.js

@@ -1,9 +1,21 @@
+// ⚠️  IMPORTANT — READ BEFORE EDITING OR ADDING CODE TO THIS FILE ⚠️
+//
+// OpenCode loads this file directly as a plugin module. Any `export` beyond
+// the plugin entry (`PolygraphPlugin` / `export default`) breaks OpenCode
+// plugin loading ENTIRELY for every user who has the plugin installed.
+//
+// DO NOT add new exports to this file. Put shared or testable logic in sibling
+// modules under source/opencode/ (e.g. agent-capture-mapping.mjs) and import
+// it here instead.
+
 import { existsSync, readFileSync, readdirSync } from 'node:fs';
 import { homedir } from 'node:os';
 import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 import yaml from 'js-yaml';
 
+import { writeAgentCaptureMapping } from './agent-capture-mapping.mjs';
+
 const __dirname = path.dirname(fileURLToPath(import.meta.url));
 const packageRoot = __dirname;
 const skillsDir = path.join(packageRoot, 'skills');
@@ -29,6 +41,9 @@ export const PolygraphPlugin = async () => {
     'shell.env': async (input, output) => {
       output.env.POLYGRAPH_AGENT_SESSION_ID = input.sessionID;
       output.env.POLYGRAPH_AGENT_TYPE = 'opencode';
+      // Record the agent-capture mapping so the Polygraph CLI can bind
+      // parent-log capture deterministically for this session.
+      writeAgentCaptureMapping(input.sessionID);
     },
 
     // OpenCode has no SessionStart hook, but the Polygraph CLI already seeds the
@@ -41,6 +56,9 @@ export const PolygraphPlugin = async () => {
       if (note) {
         output.context.push(note);
       }
+      // Refresh the mapping on compaction (same refresh semantics as Claude/Codex
+      // SessionStart hooks firing on 'compact').
+      writeAgentCaptureMapping(input.sessionID);
     },
   };
 };

package/skills/polygraph/SKILL.md

@@ -18,7 +18,7 @@ Polygraph functionality is available via both MCP tools and CLI commands. Use wh
 
 | MCP Tool | CLI Equivalent | Description |
 | --- | --- | --- |
-| `list_repos` | `polygraph repo list` | Discover candidate repositories with descriptions and graph relationships |
+| `list_repos` | `polygraph repo list` | Discover candidate repositories. |
 | `start_session` | `polygraph session start --repo <ids>` | Initialize a Polygraph session with selected repositories |
 | `spawn_agent` | — | Start a new child task or send a follow-up to an active task in another repository. Input: `{ sessionId, repo, instruction, context? }`. Output: `{ taskId, message, status: 'delegated' }`. Follow-up routing is automatic: if the repo already has an active child task, the instruction is delivered to it as a follow-up message; otherwise a new child run starts. A repo has at most one active child at a time. A session resume or reconstruction is read-only context restoration; after resuming, do not use `spawn_agent` to continue changes unless the user explicitly asks for changes. |
 | `show_agent` | — | Poll flat per-child status for the session. Output: `{ children: PolygraphChildStatusItem[] }` where each item exposes `repositoryId`, `repoFullName`, `status`, `lastOutputLines`, `durationMs`, `instruction`, `agentType?`, `inputRequiredQuestion?`. `status` is an AcpRunStatus: `'created' \| 'in-progress' \| 'input-required' \| 'permission-required' \| 'completed' \| 'failed' \| 'cancelled'` (British double-L on `'cancelled'`). `inputRequiredQuestion` is populated only when `status === 'input-required'`. |