@astrofoundry/pi-astro 0.23.1 → 0.23.2

package/extensions/astro-subagents/index.test.ts

@@ -70,6 +70,16 @@ describe("astro-subagents extension", () => {
         expect(notify).toHaveBeenCalledWith(expect.stringContaining("depth limit"), "warning");
     });
 
+    it("posts the /run result without a model turn and names the model in the footer", async () => {
+        const pi = makePi();
+        astroSubagents(pi as unknown as Parameters<typeof astroSubagents>[0], { dirs, env: {} });
+        const setStatus = vi.fn();
+        const ctx = { ui: { notify: vi.fn(), setStatus }, hasUI: true, cwd: root, model: { provider: "openai-codex", id: "gpt-6-astra" } };
+        await pi.commands.get("run")?.handler("astro.nobody -- x", ctx);
+        expect(setStatus).toHaveBeenCalledWith("subagent", expect.stringContaining("astro.nobody on openai-codex/gpt-6-astra"));
+        expect(pi.sendMessage).toHaveBeenCalledWith(expect.objectContaining({ customType: "astro-subagents", content: expect.stringContaining("Unknown agent") }), { triggerTurn: false });
+    });
+
     it("removes legacy loader copies on session start", async () => {
         writeFileSync(join(dirs.userAgents, "astro.arcane.md"), "old copy");
         writeFileSync(join(dirs.userAgents, "mine.md"), "---\nname: mine\ndescription: keep\n---\n");

package/extensions/astro-subagents/index.ts

@@ -139,6 +139,12 @@ export default function astroSubagents(pi: ExtensionAPI, options: GateOptions =
         });
     }
 
+    /** Footer label: the agent and the model it will run on. */
+    function runLabel(ctx: ExtensionContext, agents: AgentConfig[], agentName: string): string {
+        const model = agents.find((a) => a.name === agentName)?.model ?? (ctx.model ? `${ctx.model.provider}/${ctx.model.id}` : undefined);
+        return model ? `${agentName} on ${model}` : agentName;
+    }
+
     if (canDelegate) {
         const initial = listAgents(process.cwd(), "user");
         pi.registerTool({
@@ -152,7 +158,13 @@ export default function astroSubagents(pi: ExtensionAPI, options: GateOptions =
             ],
             parameters: Params,
             async execute(_id, params, signal, onUpdate, ctx) {
-                const label = params.chain?.length ? `chain of ${params.chain.length}` : params.tasks?.length ? `${params.tasks.length} agents` : (params.agent ?? "subagent");
+                const label = params.chain?.length
+                    ? `chain of ${params.chain.length}`
+                    : params.tasks?.length
+                      ? `${params.tasks.length} agents`
+                      : params.agent
+                        ? runLabel(ctx, listAgents(ctx.cwd, params.agentScope ?? "user").agents, params.agent)
+                        : "subagent";
                 const stopTicker = startTicker(ctx, label);
                 try {
                     return await runTool(params, signal, onUpdate, ctx);
@@ -260,7 +272,7 @@ export default function astroSubagents(pi: ExtensionAPI, options: GateOptions =
                 return;
             }
             const agents = listAgents(ctx.cwd, "user").agents;
-            const stopTicker = startTicker(ctx, parsed.agent);
+            const stopTicker = startTicker(ctx, runLabel(ctx, agents, parsed.agent));
             let result: RunResult;
             try {
                 result = await runOne(ctx, agents, parsed.agent, parsed.task, undefined, undefined, undefined, undefined);
@@ -269,10 +281,8 @@ export default function astroSubagents(pi: ExtensionAPI, options: GateOptions =
             }
             const status = isFailed(result) ? "failed" : "done";
             if (isFailed(result)) ctx.ui.notify(`${parsed.agent} failed`, "warning");
-            pi.sendMessage(
-                { customType: "astro-subagents", content: `Result from /run ${parsed.agent} (${status}). Task: ${parsed.task}\n\n${resultOutput(result)}`, display: true },
-                { deliverAs: "followUp", triggerTurn: true },
-            );
+            // No turn: the result joins the context for the next prompt without the parent model restating it.
+            pi.sendMessage({ customType: "astro-subagents", content: `Result from /run ${parsed.agent} (${status}). Task: ${parsed.task}\n\n${resultOutput(result)}`, display: true }, { triggerTurn: false });
         },
     });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrofoundry/pi-astro",
-  "version": "0.23.1",
+  "version": "0.23.2",
   "description": "Personal pi customizations (extensions, subagents, skills, prompts, themes) for the pi coding agent.",
   "keywords": [
     "pi-package"

package/specialists/README.md

@@ -105,7 +105,7 @@ Check: `sudo -n -u specialist -H /usr/local/bin/specialist-cli arcane --caller t
 
 The `astro-discord` extension gives Discord users access to the specialists from a channel. It runs in a headless Pi host on Cortex (LaunchAgent `com.astrofoundry.astro-discord`, user `cortex`), never in interactive sessions.
 
-- Channels are configured one by one (`channels.<id>`): `trigger` is `always` (every message that names a specialist counts) or `mention` (only messages that start with `@Cortex` or reply to the bot); `specialists` is `*` or a list. A channel with one specialist needs no prefix: every message there is a task for it. In a channel with several, `dns list the zones` names the specialist; an addressed message without a name gets a reply asking for one. Threads inherit their parent channel's entry; unlisted channels are ignored. Reactions on your message: ⏳ running, 🔒 waiting for an owner's approval, ✅ done, ❌ failed. `help` shows what you may use in that channel; `status` lists running tasks. Long answers arrive as a `.md` attachment.
+- Channels are configured one by one (`channels.<id>`): `trigger` is `always` (every message that names a specialist counts) or `mention` (only messages that start with `@Cortex` or reply to the bot); `specialists` is `*` or a list. A channel with one specialist needs no prefix: every message there is a task for it. In a channel with several, `dns list the zones` names the specialist; an addressed message without a name gets a reply asking for one. Threads inherit their parent channel's entry; unlisted channels are ignored. The bot replies at once with "<specialist> is working on your task" and shows the typing indicator until the answer replaces that reply. Reactions on your message: ⏳ running, 🔒 waiting for an owner's approval, ✅ done, ❌ failed. `help` shows the specialists you may use in that channel and the commands (`status` lists running tasks; owners in the admin channel also see the `config` commands). Long answers arrive as a `.md` attachment.
 - Access: `owners` may use every specialist and decide approvals; `access.<specialist>` lists extra users for that specialist; everyone else gets no reply. Owners change the configuration from the admin channel (`adminChannelId`) without a shell: `config show`, `config channel <#channel> <always|mention> <*|dns,edge>`, `config channel <#channel> remove`, `config access <specialist> add|remove <@user>`; the bot writes `~/.config/astro-discord/config.json` on Cortex, which is also editable by hand and re-read on every message. Deny the bot's role View Channel on channels it must never read; that is the boundary the map cannot provide.
 - Approvals: a risky call (anything with `--confirm`, plus writes such as record or zone deletes, Zitadel changes, Pomerium deploys, Arcane redeploys, service restarts) pauses the specialist and posts Approve/Deny buttons; only owners' clicks count; no decision within `approvalTimeoutMinutes` denies it. The specialist then reports the denial. Ambiguous tasks get a question back instead of an action.
 - Setup, as `cortex`: `d=$(mktemp -d) && cp ~/.pi/agent/npm/node_modules/@astrofoundry/pi-astro/extensions/astro-discord/*.ts "$d" && node --disable-warning=ExperimentalWarning "$d/setup.ts"` (Node does not strip types inside `node_modules`, so the files are copied first) prompts for the bot token and the ids, checks each against Discord, and writes `~/.config/astro-discord/{token,config.json,run.sh}` and the LaunchAgent; it prints the `launchctl bootstrap` line. After a pi-astro update restart the bridge with `launchctl kickstart -k gui/$(id -u)/com.astrofoundry.astro-discord`. Log: `~/Library/Logs/astro-discord.log`.