opencode-routines 0.1.7 → 0.1.8

package/README.md

@@ -34,7 +34,17 @@ Add the server plugin to your OpenCode config (`~/.config/opencode/opencode.json
 
 OpenCode installs the package from npm on next start. Use `@latest` if you want new versions on restart, or pin a version such as `"opencode-routines@0.1.1"`.
 
-Optional TUI slash commands are published as a companion package, `opencode-routines-tui`. It is a **TUI plugin**, which OpenCode loads from `tui.json` — NOT from `opencode.json`'s `plugin` array (that array is for server plugins only; the server loader will reject it with `must default export an object with server()`).
+That single entry is the whole packaged experience: on load, the server plugin also installs slash commands (`/loop`, `/loops`, `/stop-loop`, `/schedule-standalone-session`) as managed OpenCode custom command files under `~/.config/opencode/commands/`. These work in **both** the terminal TUI and OpenCode Desktop. The install is idempotent and marker-guarded: only files containing the `managed-by: opencode-routines` marker are ever created or updated, so a user-edited `loop.md` (marker removed) is never touched. Restart OpenCode once after the first install for the commands to appear. Opt out with plugin options:
+
+```jsonc
+{
+  "plugin": [["opencode-routines@latest", { "commands": false }]]
+}
+```
+
+### Optional native TUI dialogs
+
+`opencode-routines-tui` is an optional companion package that replaces the prompt-based commands with native TUI dialogs (interactive loop list, prompt dialogs). It is a **TUI plugin**, which OpenCode loads from `tui.json` — NOT from `opencode.json`'s `plugin` array (that array is for server plugins only; the server loader will reject it with `must default export an object with server()`).
 
 Add it to `~/.config/opencode/tui.json` (or a project-level `.opencode/tui.json`, or a custom path via the `OPENCODE_TUI_CONFIG` env var):
 
@@ -48,7 +58,7 @@ Add it to `~/.config/opencode/tui.json` (or a project-level `.opencode/tui.json`
 
 `opencode-routines-tui` is separate so the terminal TUI can install and load the TUI plugin entrypoint (`exports["./tui"]`). The root package still ships a `./tui` export for advanced/manual loaders, but installs should use the companion package via `tui.json`.
 
-TUI slash commands currently work in the **terminal TUI** (`opencode` in a terminal). OpenCode Desktop builds its slash list from a different command registry and does not load `tui.json` TUI plugins, so these slash commands do not appear there yet.
+The TUI plugin only works in the **terminal TUI** (`opencode` in a terminal); OpenCode Desktop builds its slash list from a different command registry and does not load `tui.json` TUI plugins. Note that installing the TUI plugin alongside the managed command files shows both variants of each slash command in the terminal TUI — if that bothers you, disable the managed commands with `{ "commands": false }` (above) and rely on the TUI plugin there.
 
 ## What it provides
 

package/dist/index.js

@@ -12335,7 +12335,7 @@ function tool(input) {
 }
 tool.schema = exports_external;
 // src/index.ts
-import { createWriteStream, existsSync, mkdirSync, readdirSync, readFileSync, rmSync, writeFileSync, unlinkSync } from "fs";
+import { createWriteStream, existsSync, mkdirSync, readdirSync, readFileSync, renameSync, rmSync, writeFileSync, unlinkSync } from "fs";
 import { basename, dirname, join, resolve as resolvePath } from "path";
 import { homedir, platform } from "os";
 import { execFileSync, execSync, spawn } from "child_process";
@@ -14497,8 +14497,91 @@ function getJobLogs(job, options) {
     return null;
   }
 }
-var SchedulerPlugin = async (input) => {
+var MANAGED_COMMAND_MARKER = "managed-by: opencode-routines";
+var MANAGED_COMMANDS = {
+  "loop.md": `---
+description: Start a same-session loop (opencode-routines)
+---
+<!-- ${MANAGED_COMMAND_MARKER} -->
+
+Use the LoopCreate tool from opencode-routines to start a same-session loop.
+
+Arguments: $ARGUMENTS
+
+Rules:
+- If the first argument looks like an interval (30s, 5m, 1h), pass it as \`interval\` and the rest as \`prompt\`.
+- Otherwise start a dynamic loop with the full arguments as \`prompt\`.
+- If no arguments were provided, ask what prompt to loop.
+- Confirm the created loop id and mode in one short sentence.
+`,
+  "loops.md": `---
+description: List active same-session loops (opencode-routines)
+---
+<!-- ${MANAGED_COMMAND_MARKER} -->
+
+Call the LoopList tool from opencode-routines and show the active loops as a short table (id, mode/interval, fires, prompt). If there are none, say so in one sentence.
+`,
+  "stop-loop.md": `---
+description: Stop a same-session loop (opencode-routines)
+---
+<!-- ${MANAGED_COMMAND_MARKER} -->
+
+Stop a same-session loop using opencode-routines tools.
+
+Arguments: $ARGUMENTS
+
+Rules:
+- If an argument matches a loop id, call LoopDelete with it.
+- Otherwise call LoopList first; if exactly one loop is active, stop it; if several, list them and ask which to stop.
+`,
+  "schedule-standalone-session.md": `---
+description: Create a durable standalone scheduled opencode run (opencode-routines)
+---
+<!-- ${MANAGED_COMMAND_MARKER} -->
+
+Create a durable OS-backed standalone schedule using the ScheduleCreate tool from opencode-routines.
+
+Arguments: $ARGUMENTS
+
+Rules:
+- Derive a short job name and a 5-field cron expression from the arguments; ask if the schedule is ambiguous.
+- Use the remaining text as the prompt for the standalone run.
+- After creating, report the job name, cron, and next steps (ScheduleList / ScheduleLogs) in two sentences max.
+`
+};
+function managedCommandsDir() {
+  const xdg = process.env.XDG_CONFIG_HOME?.trim();
+  const base = xdg ? xdg : join(homedir(), ".config");
+  return join(base, "opencode", "commands");
+}
+function syncManagedCommands() {
+  const dir = managedCommandsDir();
+  ensureDir(dir);
+  for (const [filename, content] of Object.entries(MANAGED_COMMANDS)) {
+    const dest = join(dir, filename);
+    const desired = `${content.trimEnd()}
+`;
+    try {
+      if (existsSync(dest)) {
+        const current = readFileSync(dest, "utf-8");
+        if (!current.includes(MANAGED_COMMAND_MARKER))
+          continue;
+        if (current === desired)
+          continue;
+      }
+      const staged = `${dest}.opencode-routines.tmp`;
+      writeFileSync(staged, desired);
+      renameSync(staged, dest);
+    } catch (error45) {
+      console.error(`[opencode-routines] failed to install command ${filename}:`, error45);
+    }
+  }
+}
+var SchedulerPlugin = async (input, options) => {
   const client = input?.client;
+  if (options?.commands !== false) {
+    syncManagedCommands();
+  }
   async function executeTool(name, args, context) {
     const plugin = await SchedulerPlugin(input);
     const definition = plugin.tool?.[name];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-routines",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "OpenCode routines: same-session loops, cron prompts, and host-backed standalone scheduled agents",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",