@evandu/super-pi 0.1.32 → 0.1.34

package/README.md

@@ -74,6 +74,10 @@ Super Pi includes Hermes-style active memory. It saves only durable information,
 
 Open **Settings → 主动记忆** to inspect, edit, delete, or approve pending changes; the same panel controls the automatic review interval. Primary Agents can use `memory`, `skill_manage`, and `session_search`. Sub Agents can read relevant material but cannot write it.
 
+### Composer references
+
+Messages may include `@worktree:<name>` to attach the matching Git worktree path from the current workspace, or `@session:<id-or-title>` to attach the recent transcript of another session in the same workspace. These references are expanded into explicit context before the turn is sent to Pi, so an agent repairing a harness can inspect the session where it behaved poorly without switching away from the current session.
+
 After the configured number of completed user turns (10 by default), Super Pi starts a separate, restricted review run. It can only use the three memory tools: it cannot read or modify project files, execute shell commands, or dispatch agents. New facts may be saved automatically; changing or deleting existing facts is staged for approval. A new message or stop cancels that conversation's review.
 
 The feature is on by default. Set `SUPER_PI_MEMORY_ENABLED=0` to disable it, or set `SUPER_PI_MEMORY_REVIEW_INTERVAL=0` to keep manual memory while disabling automatic review. See [the design](docs/ACTIVE_MEMORY_DESIGN.md) for storage limits, lifecycle, and security boundaries.

package/agents/super-pi-task/index.ts

@@ -45,6 +45,7 @@ const Parameters = Type.Object({
   task_id: Type.Optional(Type.String({ description: "Resume a previous task when supported" })),
   background: Type.Optional(Type.Boolean({ description: "Run asynchronously and deliver the result as a follow-up message" })),
 });
+const QuestionParameters = Type.Object({ question: Type.String(), options: Type.Array(Type.String(), { minItems: 1 }), multiple: Type.Optional(Type.Boolean()), extraNote: Type.Optional(Type.Boolean()) });
 
 /**
  * The `todowrite` parameter schema, OpenCode's `tool/todo.ts:6-8` in the TypeBox dialect this adapter
@@ -109,6 +110,7 @@ const WorkflowParameters = Type.Object({
 type ExtensionApi = { registerTool(tool: ExtensionToolDefinition): void };
 
 const extension = (pi: ExtensionApi): void => {
+  pi.registerTool({ name: "question", label: "Question", description: "Ask the user a blocking single or multiple choice question with an optional extra note.", parameters: QuestionParameters, execute: async (_id, raw) => { const endpoint = process.env.SUPER_PI_QUESTION_ENDPOINT; const conversationId = process.env.SUPER_PI_TASK_CONVERSATION; if (!endpoint || !conversationId) return { error: "Interactive question is unavailable" }; const p = raw as { question: string; options: string[]; multiple?: boolean; extraNote?: boolean }; const response = await fetch(endpoint, { method: "POST", headers: { "content-type": "application/json" }, body: JSON.stringify({ conversationId, ...p }) }); return await response.json(); } });
   // Read ONCE at load, not per call: the environment cannot change under a running Pi, and `prepareLoadout`
   // is synchronous - it cannot await a fetch for a roster - so the roster has to already be here.
   const config = readTaskConfig(process.env);
@@ -147,6 +149,8 @@ const extension = (pi: ExtensionApi): void => {
       await executeTask(params as TaskParams, context, config, { signal: signal ?? undefined }),
   });
 
+
+
   /**
    * `todowrite`, registered SECOND and for one reason: order in the tool list is the order a model reads
    * them in, and a plan is worth more in front of the eye than a dispatcher is. Nothing depends on the