@astrofoundry/pi-astro 0.32.0 → 0.33.1

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

@@ -45,6 +45,7 @@ You are the Arcane specialist.
         const minimal = parseAgentFile("---\nname: scout\ndescription: Recon\n---\nBody", "/a.md", "user");
         expect(minimal).toMatchObject({ tools: undefined, skills: [], systemPromptMode: "replace", inheritProjectContext: false, inheritSkills: false });
         expect(minimal?.maxSubagentDepth).toBeUndefined();
+        expect(parseAgentFile("---\nname: reviewer\ndescription: d\ntools: none\n---\nBody", "/r.md", "user")?.tools).toEqual([]);
         expect(parseAgentFile("---\nname: x\n---\nBody", "/b.md", "user")).toBeNull();
         expect(parseAgentFile("---\nname: 'bad name!'\ndescription: d\n---\n", "/c.md", "user")).toBeNull();
     });

package/extensions/astro-subagents/agents.ts

@@ -14,6 +14,7 @@ export interface AgentConfig {
     /** Name callers use: `astro.<name>` for bundled agents, `<name>` otherwise. */
     name: string;
     description: string;
+    /** Strict allowlist; undefined means Pi's defaults and an empty list means no tools at all (`tools: none`). */
     tools?: string[];
     skills: string[];
     model?: string;
@@ -101,7 +102,7 @@ export function parseAgentFile(content: string, filePath: string, source: AgentS
     return {
         name: source === "bundled" ? `${BUNDLED_NAMESPACE}.${localName}` : localName,
         description: frontmatter.description.trim(),
-        tools: tools.length > 0 ? tools : undefined,
+        tools: tools.length === 1 && tools[0] === "none" ? [] : tools.length > 0 ? tools : undefined,
         skills: parseList(frontmatter.skills),
         model: typeof frontmatter.model === "string" ? frontmatter.model : undefined,
         thinking: typeof frontmatter.thinking === "string" ? frontmatter.thinking : undefined,

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

@@ -53,6 +53,12 @@ describe("child arguments", () => {
         expect(args).toEqual(["--mode", "json", "-p", "--no-session", "--model", "anthropic/claude-x", "--thinking", "high", "--append-system-prompt", "/tmp/p.md", "--", "Task: t"]);
     });
 
+    it("disables every tool for an agent declared with tools: none", () => {
+        const args = buildChildArgs({ agent: { ...agent, tools: [] }, task: "t", promptFile: null, defaults: {} });
+        expect(args).toContain("--no-tools");
+        expect(args).not.toContain("--tools");
+    });
+
     it("does not pass the parent's thinking level to an agent that pins its own model", () => {
         const pinned: AgentConfig = { ...agent, model: "m" };
         expect(buildChildArgs({ agent: pinned, task: "t", promptFile: null, defaults: { thinkingLevel: "high" } })).not.toContain("--thinking");

package/extensions/astro-subagents/child.ts

@@ -104,7 +104,8 @@ export function buildChildArgs({ agent, task, promptFile, defaults, session, fil
     if (model) args.push("--model", model);
     const thinking = agent.thinking ?? (agent.model ? undefined : defaults.thinkingLevel);
     if (thinking) args.push("--thinking", thinking);
-    if (agent.tools && agent.tools.length > 0) args.push("--tools", agent.tools.join(","));
+    if (agent.tools?.length === 0) args.push("--no-tools");
+    else if (agent.tools) args.push("--tools", agent.tools.join(","));
     if (!agent.inheritProjectContext) args.push("--no-context-files");
     if (!agent.inheritSkills) args.push("--no-skills");
     if (promptFile) args.push(agent.systemPromptMode === "append" ? "--append-system-prompt" : "--system-prompt", promptFile);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrofoundry/pi-astro",
-  "version": "0.32.0",
+  "version": "0.33.1",
   "description": "Personal pi customizations (extensions, subagents, skills, prompts, themes) for the pi coding agent.",
   "keywords": [
     "pi-package"
@@ -49,10 +49,10 @@
     "typebox": "*"
   },
   "devDependencies": {
-    "@earendil-works/pi-agent-core": "^0.85.1",
-    "@earendil-works/pi-ai": "^0.85.1",
-    "@earendil-works/pi-coding-agent": "^0.85.1",
-    "@earendil-works/pi-tui": "^0.85.1",
+    "@earendil-works/pi-agent-core": "^1.3.0",
+    "@earendil-works/pi-ai": "^1.3.0",
+    "@earendil-works/pi-coding-agent": "^1.3.0",
+    "@earendil-works/pi-tui": "^1.3.0",
     "@eslint/js": "^10.0.1",
     "@types/node": "^26.5.1",
     "@vitest/coverage-v8": "^5.0.0",

package/specialists/README.md

@@ -133,7 +133,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. 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). Each channel and specialist has one conversation: a reply to the bot's answer, or another task for that specialist within 30 minutes, continues it with everything the specialist saw before; otherwise a new one starts, and a task beginning with `new` forces that. Replied-to and forwarded messages (text, embeds, attachment names) travel with the task, so "check this" on a forwarded alert works. Image attachments on the message or on what it quotes (up to 4, 8 MiB each) are downloaded and passed to the specialist, which sees them; other file types are named only. Sessions live under `~/.config/astro-discord/sessions/<specialist>/` and are deleted after 7 days. Long answers arrive as a `.md` attachment. When the bridge restarts, open approval requests are marked cancelled and running tasks interrupted in Discord; ask again. With `dailyReport` in the config, the bridge posts an "Arcane Daily Report:" message every morning in that channel: each service with an update as current to target version, from a fresh `update-report`; replying to it asks the arcane specialist with the report as context.
+- 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). Each channel and specialist has one conversation: a reply to the bot's answer, or another task for that specialist within 30 minutes, continues it with everything the specialist saw before; otherwise a new one starts, and a task beginning with `new` forces that. Replied-to and forwarded messages (text, embeds, attachment names) travel with the task, so "check this" on a forwarded alert works. Image attachments on the message or on what it quotes (up to 4, 8 MiB each) are downloaded and passed to the specialist, which sees them; other file types are named only. Sessions live under `~/.config/astro-discord/sessions/<specialist>/` and are deleted after 7 days. Long answers arrive as a `.md` attachment. When the bridge restarts, open approval requests are marked cancelled and running tasks interrupted in Discord; ask again. Scheduled reports are a list in the config, one entry per report: `"reports": [{ "report": "arcane", "channelId": "<id>", "time": "06:00", "timeZone": "Europe/Madrid" }, { "report": "tools", "channelId": "<admin channel id>", "time": "06:00", "timeZone": "Europe/Madrid" }]` (the earlier single `dailyReport` key is refused; move it into the list). The Arcane report posts an "Arcane Daily Report:" message every morning: each service with an update as current to target version, from a fresh `update-report`; replying to it asks the arcane specialist with the report as context. The tools report posts "Cortex Tools Report:": every tool on Cortex with a newer version (Homebrew packages installed on request and casks, Pi, pi-astro, and through `specialist-install` the wrappers, arcane-cli at the Arcane server's version, trendarr, and the specialist Node at the latest LTS), a release-notes verdict from `astro.release-reviewer` for the tools the specialists build on, an Update button per line, and one Upgrade everything for Homebrew. Only owners can press them; nothing is installed otherwise. After an update that needs it, the bridge, herdr, or Astrogate restarts as soon as nothing runs on it; after a day of waiting, a Restart now button appears. The bridge calls `sudo -n /usr/local/sbin/specialist-install` through the sudoers rule from step 4.
 - Media: where the `media` specialist is present (`config channel <#channel> always media`), `/trending [type] [min_rating] [count]`, `/search <title> [type]`, and `/downloads <status|pause|resume|unpause>` run the wrapper without a model. Lists arrive as two messages, Movies and Series, each title with a button beside it: **Add** adds it at once and turns into Added, In library, or Not found (Retry after a failure); a greyed-out In library or No IMDb ID button needs nothing. Notes such as "downloads are paused" go only to the user who clicked. Owners and `access.media` users may use them; anyone else gets a refusal only they see, and in a channel without `media` the bot names the channels that have it. Plain messages in the channel still go to the agent, for requests by name ("add the new Dune"). At startup the bridge sets the three commands as the application's global commands (servers only).
 - 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, service restarts, and on Arcane only destructive actions: `down`, deletes, prunes, image, volume, or network removal, `system upgrade`, `gitops delete`; help lookups never ask) 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.

package/themes/astro.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://raw.githubusercontent.com/badlogic/pi-mono/main/packages/coding-agent/src/modes/interactive/theme/theme-schema.json",
+    "$schema": "https://pi.dev/schemas/theme.schema.json",
     "name": "astro",
     "vars": {
         "bg": "#0D1117",