@yunazgr/pi-companion 0.3.0 → 0.3.1

package/README.md

@@ -2,7 +2,7 @@
 
 Lightweight, local-first remote control for Pi sessions.
 
-**New in 0.3.0:** [automations](docs/automations.md) with manual/UTC-cron runs, read-only agent sessions, run history, native agent tools and a standalone MCP surface. Disconnected sessions auto-archive after seven days; mobile Settings is now in the header.
+**New in 0.3.1:** claymorphic automation workspaces with searchable, status-filtered, paginated lists; Summary/History tabs and calendar-style run cards; sanitized Markdown/ADF/JSON results; a staged job editor with strict validation and optional failed-action retries (up to 5, default 10-second interval). Per-automation history keeps the latest 30 runs by default, with 10 per page. Automated sessions are clearly marked as answers-only. Type `/` in a normal session to discover available commands, skills, and prompt templates. See [automations](docs/automations.md).
 
 Pi Companion is deliberately not another agent runtime. Pi owns execution and conversation state. A single Rust daemon owns session discovery, pairing, temporary file exchange, browser fan-out, and the embedded web UI.
 
@@ -15,7 +15,7 @@ The UI is a static SvelteKit application. There is no Node runtime in production
   <img src="docs/mobile.webp" alt="Session detail on a phone" width="28%" />
 </p>
 
-Screenshots use demo sessions, not private conversation data, and are regenerated with `node tools/screenshots.mjs` (see [Running locally from source](#running-locally-from-source)). See the [session menu](docs/session-menu.webp), [desktop session rows](docs/session-list-desktop.webp) and [mobile session list](docs/session-list.webp), plus [attachment previews](docs/attachments.webp), [file-grouped changes](docs/changes.webp) and [connection recovery](docs/connection-error.webp).
+Screenshots use demo sessions, not private conversation data, and are regenerated with `node tools/screenshots.mjs` (see [Running locally from source](#running-locally-from-source)). See the [session menu](docs/session-menu.webp), [desktop session rows](docs/session-list-desktop.webp) and [mobile session list](docs/session-list.webp), plus [attachment previews](docs/attachments.webp), [file-grouped changes](docs/changes.webp) and [connection recovery](docs/connection-error.webp). Explore the new [automation list](docs/automations.webp), [summary](docs/automation-detail.webp), [run history](docs/automation-history.webp), [job editor](docs/automation-editor.webp), and [rich results](docs/automation-result.webp).
 
 ## Install
 
@@ -354,7 +354,7 @@ Clone the repository, then:
 
 `npm run serve` builds the embedded Svelte UI and starts the Rust daemon in the foreground. It prints:
 
-      Pi Companion v0.3.0
+      Pi Companion v0.3.1
 
       Console          http://127.0.0.1:43721
       Paired devices   http://127.0.0.1:43722
@@ -392,6 +392,8 @@ To regenerate the README screenshots from demo sessions (your running daemon is
     npm run ui:build && cargo build --release --manifest-path server/Cargo.toml
     node tools/screenshots.mjs
 
+The generator also refreshes automation list/detail/history/editor/results, automated session, and [slash-command suggestions](docs/slash-commands.webp) screenshots. Type `/` in a shared session to search its available extension commands, skills, and prompt templates; use ↑/↓ and Tab/Enter to choose, then send when ready. Built-in terminal-only commands and ordinary tool names are not included. Automated answers-only sessions never expose this picker.
+
 It needs Playwright and `cwebp`. Set `PLAYWRIGHT=/path/to/node_modules/playwright/index.mjs` if Playwright isn't installed in this repo, and `CHROME=/path/to/chrome` to use an existing browser.
 
 To test the same behavior as a published install, stop any development daemon first and install the package normally:

package/docs/automations.md

@@ -1,7 +1,41 @@
-# Automations (0.3.0)
+# Automations (0.3.1)
 
 Automations are persisted, named JSON scripts run by the Companion daemon. Open **Automations** in the navigation to view definitions, start/stop runs, and inspect timestamped run history. Click a run to view its captured output and Pi summary. Desktop console users can create, edit, delete, and enable/disable definitions; mobile and paired-device users can only inspect and start/stop them.
 
+## Workspace & editor
+
+The claymorphic automation collection supports name search, Enabled/Disabled filters, ten-item pagination, and its own scrollable card region. The detail workspace has **Summary** and **Run history** tabs; history is newest-first with calendar tiles, duration, status filters, and ten-item pagination over each automation’s retained history (latest 30 finished runs by default, configurable 1–1000).
+
+The job editor separates name, enablement, UTC cron, optional retry policy, preconditions, actions, and post-actions. Each step is a reorderable JSON DSL object with Command/Pi templates. Saving validates the definition, cron ranges, action types, arguments, absolute directories, timeouts, step count, and retry bounds; the daemon validates again before persistence. Only computer desktop administrators can author definitions.
+
+Run results have a formatted and raw view. Formatted results split daemon execution phases, render sanitized Markdown (including tables, links, code, and diagrams), recognise whole/fenced JSON, and render Atlassian Document Format (`type: "doc"`) or `{ "adf": ... }` documents. ADF supports headings, lists, marks, tables, panels, and safe links; unsupported nodes preserve their text, and attachments are placeholders. HTML/scripts and executable link protocols are not trusted. Raw output remains available for inspection and copying.
+
+## Screenshots
+
+Screenshots use only demo data. The same generator refreshes the existing overview, session, and mobile screenshots too.
+
+![Automations on the overview below live sessions](overview-automations.webp)
+![Searchable automation cards](automations.webp)
+![Automation cards on a phone](automations-mobile.webp)
+![Run history on a phone](automation-history-mobile.webp)
+![Automation summary and execution steps](automation-detail.webp)
+![Filtered, paginated run history](automation-history.webp)
+![Friendly staged job editor](automation-editor.webp)
+![Rich review summary with linked PR table](automation-result.webp)
+![Answers-only automated session](automation-session.webp)
+
+## History retention
+
+`historyLimit` is an optional integer **1–1000**, default **30**. Each automation retains its latest N finished runs, replacing older history as newer runs finish. Lowering the limit prunes older runs immediately on save; active runs are retained until finished. The same policy is applied on daemon startup. Deleted run results cannot be recovered from the dashboard. Run history pages show **10 items** at a time.
+
+Automations also appear below running sessions on the overview. Automated sessions are labelled **Automated · answers only** in session cards, tables, and the session workspace. Their browser controls allow question answers but not steering, planning, uploads, or code changes; backend restrictions remain authoritative.
+
+## Optional retries
+
+`maxRetries` is an optional integer **0–5** (default **0**, no retries). `retryIntervalSeconds` is an optional integer **1–86400** (default **10 seconds**). Only a failed main action is retried; completed steps do not repeat, and precondition skips and finalizers are never retried. Stop cancels an active process or retry delay. Save-time validation requires the total retry-delay budget to be shorter than the shortest daily UTC trigger gap (a conservative bound for schedules limited to selected dates). Before each wait, the daemon also skips a retry that would reach the next scheduled trigger. It cannot guarantee action duration; overlapping runs remain prohibited. Attempt diagnostics are included in run output, and finalizers execute after the final outcome unless stopped.
+
+**Retries can duplicate side effects**, including model calls and remote submissions after ambiguous failures. Enable them only for retry-safe work; the PR-review automation should keep retries off. Existing definitions without either field retain their original behavior.
+
 ## JSON DSL
 
 ```json
@@ -9,6 +43,9 @@ Automations are persisted, named JSON scripts run by the Companion daemon. Open
   "name": "Daily repository check",
   "enabled": true,
   "schedule": "0 9 * * 1-5",
+  "maxRetries": 0,
+  "retryIntervalSeconds": 10,
+  "historyLimit": 30,
   "preconditions": [
     { "type": "command", "command": "git", "args": ["rev-parse", "--is-inside-work-tree"], "cwd": "/absolute/project" }
   ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yunazgr/pi-companion",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Local-first remote control for Pi sessions: live activity feed, steering, git diff, file drop and phone pairing from a single Rust daemon.",
   "keywords": [
     "pi-package",

package/skills/companion-automations/SKILL.md

@@ -32,6 +32,8 @@ Read the current definition with `get` before `update`, `enable`, or `disable`.
 - `schedule` is a five-field **UTC** cron expression; `null` means manual only. The daemon must be running for scheduling. There is no catch-up while it is stopped.
 - Commands use executable plus argument array, **no implicit shell**. Shell syntax must never be passed as an executable. Avoid explicit shells unless the user requested and authorized them.
 - Preconditions gate execution. Actions run sequentially. Post-actions are the cleanup/finalization stage; inspect the run result to determine failures.
+- Optional `maxRetries` (integer 0–5, default 0) and `retryIntervalSeconds` (integer 1–86400, default 10) retry only the failed main action, never completed steps, preconditions, or finalizers. Stop cancels a retry delay. Retries may duplicate side effects or model usage: obtain authorization, and keep them off for non-idempotent remote submissions.
+- Optional `historyLimit` (integer 1–1000, default 30) keeps the latest N finished runs per automation. Lowering it immediately removes older history on save. Retry delays must fit before the next scheduled trigger.
 - A Pi action starts a daemon-owned, read-only Companion session: users can answer asks, but cannot steer, prompt, upload, request changes, or edit its plan. The agent itself still has ordinary Pi tool permissions.
 - Pi must be installed on PATH and configured with model credentials. Its final assistant output is saved in run history.
 

package/src/automation-mcp.ts

@@ -31,7 +31,7 @@ async function receive(line: string) {
     case "initialize": {
       const versions = ["2025-06-18", "2025-03-26", "2024-11-05"];
       const requested = message.params?.protocolVersion;
-      reply({ protocolVersion: versions.includes(String(requested)) ? requested : versions[0], capabilities: { tools: {} }, serverInfo: { name: "pi-companion-automations", version: "0.3.0" } });
+      reply({ protocolVersion: versions.includes(String(requested)) ? requested : versions[0], capabilities: { tools: {} }, serverInfo: { name: "pi-companion-automations", version: "0.3.1" } });
       return;
     }
     case "ping": reply({}); return;

package/src/automation.ts

@@ -10,6 +10,9 @@ export type AutomationDefinition = {
   preconditions: AutomationAction[];
   actions: AutomationAction[];
   postActions: AutomationAction[];
+  historyLimit?: number;
+  maxRetries?: number;
+  retryIntervalSeconds?: number;
 };
 export type AutomationParams = {
   action: "list" | "get" | "create" | "update" | "delete" | "enable" | "disable" | "start" | "stop" | "runs" | "run";
@@ -48,7 +51,10 @@ export const automationTool = {
           schedule: { type: ["string", "null"], description: "Five-field UTC cron; null for manual only." },
           preconditions: { type: "array", items: actionSchema },
           actions: { type: "array", minItems: 1, items: actionSchema },
-          postActions: { type: "array", items: actionSchema }
+          postActions: { type: "array", items: actionSchema },
+          historyLimit: { type: "integer", minimum: 1, maximum: 1000, description: "Retain latest N finished runs; default 30." },
+          maxRetries: { type: "integer", minimum: 0, maximum: 5, description: "Optional retries of the failed main action only; default 0. May repeat side effects." },
+          retryIntervalSeconds: { type: "integer", minimum: 1, maximum: 86400, description: "Optional delay between retries; default 10 seconds; total retry delay must fit before the next scheduled trigger." }
         }
       }
     }
@@ -92,8 +98,8 @@ export async function executeAutomation(params: AutomationParams, signal?: Abort
     case "enable": case "disable": {
       const current = await request(path) as AutomationDefinition;
       // PUT only definition fields, never server-generated metadata.
-      const { name, schedule, preconditions, actions, postActions } = current;
-      return request(path, "PUT", { name, schedule, preconditions, actions, postActions, enabled: params.action === "enable" });
+      const { name, schedule, preconditions, actions, postActions, maxRetries, retryIntervalSeconds, historyLimit } = current;
+      return request(path, "PUT", { name, schedule, preconditions, actions, postActions, maxRetries, retryIntervalSeconds, historyLimit, enabled: params.action === "enable" });
     }
     case "start": case "stop": return request(path + "/" + params.action, "POST");
     case "runs": return request(path + "/runs");

package/src/bridge.ts

@@ -70,7 +70,11 @@ export class CompanionBridge implements AskChannel {
       shortTitle: name?.trim() || cwd.split(/[\\/]/).filter(Boolean).pop() || "Pi",
       mainModel: ctx.model?.id ?? null,
       effort: ctx.thinkingLevel ?? this.pi.getThinkingLevel?.() ?? null,
-      telemetry: this.telemetry.snapshot(ctx)
+      telemetry: this.telemetry.snapshot(ctx),
+      // Expose only executable slash commands, not local source paths or credentials.
+      commands: (this.pi.getCommands?.() ?? []).slice(0, 500).map(command => ({
+        name: command.name, description: command.description?.slice(0, 500), source: command.source
+      }))
     };
     const patch: Partial<SessionSnapshot> = {};
     for (const key of Object.keys(next) as Array<keyof typeof next>) {

package/src/protocol.ts

@@ -61,6 +61,7 @@ export type SessionSnapshot = {
   effort?: string | null;
   telemetry?: SessionTelemetry;
   remoteEnabled: boolean;
+  commands?: { name: string; description?: string; source: 'extension' | 'prompt' | 'skill' }[];
   connectedAt: string;
   /** Questions waiting for an answer. Kept in the snapshot so late-joining browsers see them. */
   asks: AskRequest[];