agent-relay-server 0.105.0 → 0.105.2

package/src/prompt-template-defaults-runner.ts

@@ -1,136 +0,0 @@
-import type { SeedTemplate } from "./db/prompt-templates";
-
-function lines(...parts: string[]): string {
-  return parts.join("\n");
-}
-
-export const RUNNER_PROMPT_TEMPLATE_DEFAULTS = [
-  {
-    slug: "relay.manual.claude",
-    category: "runner",
-    title: "Claude Relay Manual",
-    description: "Bundled CLAUDE.md relay manual written into provisioned Claude homes.",
-    template: lines(
-      "# Agent Relay",
-      "",
-      "- Agent Relay messages may come from humans, channels, or other agents.",
-      "- Read the delivered message body and do the requested work.",
-      "- Reply through Relay only when the sender still needs an answer.",
-      "- Prefer the inline MCP tools `relay_reply` or `relay_send_message` for the actual answer to an incoming Relay message.",
-      "- Do not send `/message` with the useful answer and then a separate `/reply` that only says it was sent.",
-      "- If multiple Relay messages arrive together, answer once to the latest relevant message and cover the current request. Do not separately acknowledge stale greetings or context.",
-      "- If the useful response was already delivered through Relay, do not send an extra \"sent\", \"done\", or \"drafts sent\" confirmation unless the user explicitly asked for one.",
-      "- No reply is needed for pure info messages, passive acknowledgements, or reactions that do not ask for action.",
-      "- NEVER reply to a notification-class message. The server marks these and renders a single `↪ Notification — no reply needed.` line instead of the reply reminder — it is a fire-and-forget signal (a merge notice, lifecycle event, or FYI). Act on the information if relevant, but do not send any reply, status confirmation, or reaction back.",
-      "- Use `agent-relay /react <messageId> <emoji>` instead of a text reply for lightweight acknowledgement, approval, thanks, or \"good job\" after a completed work update.",
-      "- Good reaction uses: acknowledge praise with 👍 or ❤️, mark a completed handoff as seen, approve a proposed next step, or acknowledge a passive FYI.",
-      "- Do not use reactions when the user asked a question, gave a new task, reported a bug, or needs a textual result.",
-      "- A thumbs-up reaction to your question means approval to proceed. A thumbs-up reaction to your completed status means no further action.",
-      "- Use `agent-relay get-message <id>` when a delivered preview is truncated.",
-      "- Use `agent-relay /status --json` to inspect your current Relay identity and `agent-relay /guide` for command details.",
-    ),
-    defaultTemplate: lines(
-      "# Agent Relay",
-      "",
-      "- Agent Relay messages may come from humans, channels, or other agents.",
-      "- Read the delivered message body and do the requested work.",
-      "- Reply through Relay only when the sender still needs an answer.",
-      "- Prefer the inline MCP tools `relay_reply` or `relay_send_message` for the actual answer to an incoming Relay message.",
-      "- Do not send `/message` with the useful answer and then a separate `/reply` that only says it was sent.",
-      "- If multiple Relay messages arrive together, answer once to the latest relevant message and cover the current request. Do not separately acknowledge stale greetings or context.",
-      "- If the useful response was already delivered through Relay, do not send an extra \"sent\", \"done\", or \"drafts sent\" confirmation unless the user explicitly asked for one.",
-      "- No reply is needed for pure info messages, passive acknowledgements, or reactions that do not ask for action.",
-      "- NEVER reply to a notification-class message. The server marks these and renders a single `↪ Notification — no reply needed.` line instead of the reply reminder — it is a fire-and-forget signal (a merge notice, lifecycle event, or FYI). Act on the information if relevant, but do not send any reply, status confirmation, or reaction back.",
-      "- Use `agent-relay /react <messageId> <emoji>` instead of a text reply for lightweight acknowledgement, approval, thanks, or \"good job\" after a completed work update.",
-      "- Good reaction uses: acknowledge praise with 👍 or ❤️, mark a completed handoff as seen, approve a proposed next step, or acknowledge a passive FYI.",
-      "- Do not use reactions when the user asked a question, gave a new task, reported a bug, or needs a textual result.",
-      "- A thumbs-up reaction to your question means approval to proceed. A thumbs-up reaction to your completed status means no further action.",
-      "- Use `agent-relay get-message <id>` when a delivered preview is truncated.",
-      "- Use `agent-relay /status --json` to inspect your current Relay identity and `agent-relay /guide` for command details.",
-    ),
-    variables: [],
-  },
-  {
-    slug: "relay.context.claude",
-    category: "runner",
-    title: "Claude Relay Context",
-    description: "One-line relay context note for Claude sessions.",
-    template: "[agent-relay] Relay is available. Follow the Agent Relay rules in CLAUDE.md when present, or run agent-relay /guide. Reply through Relay only when a response is needed; do not send status-only follow-ups after the useful Relay response was already delivered.",
-    defaultTemplate: "[agent-relay] Relay is available. Follow the Agent Relay rules in CLAUDE.md when present, or run agent-relay /guide. Reply through Relay only when a response is needed; do not send status-only follow-ups after the useful Relay response was already delivered.",
-    variables: [],
-  },
-  {
-    slug: "relay.context.claude.readonly",
-    category: "runner",
-    title: "Claude Relay Context (Read Only)",
-    description: "Read-only relay context note for Claude sessions.",
-    template: lines(
-      "[agent-relay] Relay is available. Follow the Agent Relay rules in CLAUDE.md when present, or run agent-relay /guide. Reply through Relay only when a response is needed; do not send status-only follow-ups after the useful Relay response was already delivered.",
-      "",
-      "This Claude session is running with restricted read-only Relay permissions. Do not invoke Agent Relay skills. If you need to reply, use this Bash command shape:",
-      "",
-      "agent-relay /reply <messageId> \"<your reply>\"",
-    ),
-    defaultTemplate: lines(
-      "[agent-relay] Relay is available. Follow the Agent Relay rules in CLAUDE.md when present, or run agent-relay /guide. Reply through Relay only when a response is needed; do not send status-only follow-ups after the useful Relay response was already delivered.",
-      "",
-      "This Claude session is running with restricted read-only Relay permissions. Do not invoke Agent Relay skills. If you need to reply, use this Bash command shape:",
-      "",
-      "agent-relay /reply <messageId> \"<your reply>\"",
-    ),
-    variables: [],
-  },
-  {
-    slug: "relay.context.codex",
-    category: "runner",
-    title: "Codex Relay Context",
-    description: "Relay context note injected into Codex sessions.",
-    template: "[agent-relay] You are connected to Agent Relay, a real-time message bus between agents and users. When you receive a relay message: read it, do what it asks, and reply through the relay when a text response is needed. Use agent-relay /react <messageId> <emoji> for lightweight acknowledgement or approval. If Relay MCP tools are available, prefer relay_reply, relay_get_message, relay_get_thread, relay_send_message, relay_upload_artifact, relay_attach_artifact, relay_agent_status, relay_find_agents, relay_compact_and_resume, relay_recall, relay_spawn_agent, and relay_shutdown_agent. You never need to know or pass your own agent id — relay fills it from your token; use relay_whoami only if you need to reason about yourself. relay_compact_and_resume is for clean-seam self-resume after a context advisory: pass workingState and optional ruledOut; Relay owns the objective envelope. relay_recall searches your own archived pre-compaction segments by keyword when a discarded detail is needed. relay_spawn_targets / relay_spawn_agent / relay_shutdown_agent only appear if your profile grants spawning (a live-children quota); when present, call relay_spawn_targets FIRST for the live host/provider/model matrix + your quota, then stand up long-living child agents and shut down your own — find them later with relay_find_agents spawnedBy:me. For replies, prefer relay_reply or relay_send_message; CLI fallback: agent-relay /reply <messageId> \"<your reply>\". If a delivered message says it was truncated, fetch the full body with: agent-relay get-message <messageId>. For command details, run: agent-relay /guide",
-    defaultTemplate: "[agent-relay] You are connected to Agent Relay, a real-time message bus between agents and users. When you receive a relay message: read it, do what it asks, and reply through the relay when a text response is needed. Use agent-relay /react <messageId> <emoji> for lightweight acknowledgement or approval. If Relay MCP tools are available, prefer relay_reply, relay_get_message, relay_get_thread, relay_send_message, relay_upload_artifact, relay_attach_artifact, relay_agent_status, relay_find_agents, relay_compact_and_resume, relay_recall, relay_spawn_agent, and relay_shutdown_agent. You never need to know or pass your own agent id — relay fills it from your token; use relay_whoami only if you need to reason about yourself. relay_compact_and_resume is for clean-seam self-resume after a context advisory: pass workingState and optional ruledOut; Relay owns the objective envelope. relay_recall searches your own archived pre-compaction segments by keyword when a discarded detail is needed. relay_spawn_targets / relay_spawn_agent / relay_shutdown_agent only appear if your profile grants spawning (a live-children quota); when present, call relay_spawn_targets FIRST for the live host/provider/model matrix + your quota, then stand up long-living child agents and shut down your own — find them later with relay_find_agents spawnedBy:me. For replies, prefer relay_reply or relay_send_message; CLI fallback: agent-relay /reply <messageId> \"<your reply>\". If a delivered message says it was truncated, fetch the full body with: agent-relay get-message <messageId>. For command details, run: agent-relay /guide",
-    variables: [],
-  },
-  {
-    slug: "workspace.lifecycle",
-    category: "runner",
-    title: "Runner Workspace Lifecycle Note",
-    description: "Lifecycle note injected by the runner for isolated workspaces.",
-    template: lines(
-      "[agent-relay] Isolated workspace: you are in a git worktree on branch {{branch}}, based on {{baseRef}} — NOT the main checkout. Other agents may work in parallel and land to {{baseRef}}, so {{baseRef}} will move under you. That is expected; don't fight it.",
-      "Do NOT push this branch yourself — not with `git push`, not with `tl push` or any other push wrapper, and do not manually rebase or merge. A steward may be auto-rebasing this branch in the background; pushing concurrently races it and can leave the worktree mid-rebase. Just commit your work here. When the task is done, run `agent-relay workspace ready` — Relay rebases onto the latest {{baseRef}}, lands your work, and pushes for you. If the installed `agent-relay` binary is stale and says the workspace command is unknown, run the repo-local fallback: `bun src/index.ts workspace ready`.",
-      "After `ready`, the status becomes `review_requested` — this is the NORMAL, healthy hand-off state, NOT an escalation or a stall. Relay auto-merges clean rebases roughly every 2 minutes; a steward agent is spawned (after a short delay) ONLY if it can't land deterministically, so seeing no steward means it's working, not stuck. Stop your turn after `ready` and go idle; do NOT wait or poll the steward queue. Relay wakes you with `landed-success` when your branch lands and refreshes, or `landed-failure` if landing fatally fails. On success you'll be on a fresh rebased branch whose name gains a `--N` suffix — expected, keep working there. Never `cd` into the main checkout, and never merge/push/resolve conflicts yourself — Relay and the steward own all of that. `agent-relay workspace status` anytime shows your current state and the exact next step.",
-    ),
-    defaultTemplate: lines(
-      "[agent-relay] Isolated workspace: you are in a git worktree on branch {{branch}}, based on {{baseRef}} — NOT the main checkout. Other agents may work in parallel and land to {{baseRef}}, so {{baseRef}} will move under you. That is expected; don't fight it.",
-      "Do NOT push this branch yourself — not with `git push`, not with `tl push` or any other push wrapper, and do not manually rebase or merge. A steward may be auto-rebasing this branch in the background; pushing concurrently races it and can leave the worktree mid-rebase. Just commit your work here. When the task is done, run `agent-relay workspace ready` — Relay rebases onto the latest {{baseRef}}, lands your work, and pushes for you. If the installed `agent-relay` binary is stale and says the workspace command is unknown, run the repo-local fallback: `bun src/index.ts workspace ready`.",
-      "After `ready`, the status becomes `review_requested` — this is the NORMAL, healthy hand-off state, NOT an escalation or a stall. Relay auto-merges clean rebases roughly every 2 minutes; a steward agent is spawned (after a short delay) ONLY if it can't land deterministically, so seeing no steward means it's working, not stuck. Stop your turn after `ready` and go idle; do NOT wait or poll the steward queue. Relay wakes you with `landed-success` when your branch lands and refreshes, or `landed-failure` if landing fatally fails. On success you'll be on a fresh rebased branch whose name gains a `--N` suffix — expected, keep working there. Never `cd` into the main checkout, and never merge/push/resolve conflicts yourself — Relay and the steward own all of that. `agent-relay workspace status` anytime shows your current state and the exact next step.",
-    ),
-    variables: ["branch", "baseRef"],
-  },
-  {
-    slug: "workspace.deps.symlink",
-    category: "runner",
-    title: "Runner Workspace Deps Symlink Note",
-    description: "Symlinked node_modules caveat injected by the runner.",
-    template: "[agent-relay] Isolated workspace: this is a git worktree, and its node_modules are SYMLINKED from the main checkout — dependencies are already installed and ready to use. Do NOT run a clean dependency install (`bun install` / `npm install` / `pnpm install`): it writes through the symlink and mutates the main checkout's shared node_modules. Build caches written under node_modules are shared too. If typecheck/build fails on a missing module (a dependency added to the base AFTER this worktree was created), run `agent-relay workspace deps` — it re-provisions only the stale dirs with a real isolated install, safely, without touching the shared node_modules. If you genuinely need to change dependencies in isolation, ask the host to spawn with AGENT_RELAY_WORKSPACE_DEPS=install.",
-    defaultTemplate: "[agent-relay] Isolated workspace: this is a git worktree, and its node_modules are SYMLINKED from the main checkout — dependencies are already installed and ready to use. Do NOT run a clean dependency install (`bun install` / `npm install` / `pnpm install`): it writes through the symlink and mutates the main checkout's shared node_modules. Build caches written under node_modules are shared too. If typecheck/build fails on a missing module (a dependency added to the base AFTER this worktree was created), run `agent-relay workspace deps` — it re-provisions only the stale dirs with a real isolated install, safely, without touching the shared node_modules. If you genuinely need to change dependencies in isolation, ask the host to spawn with AGENT_RELAY_WORKSPACE_DEPS=install.",
-    variables: [],
-  },
-  {
-    slug: "workspace.deps.none",
-    category: "runner",
-    title: "Runner Workspace Deps None Note",
-    description: "Missing dependency provisioning caveat injected by the runner.",
-    template: "[agent-relay] Isolated workspace: dependencies were not provisioned (AGENT_RELAY_WORKSPACE_DEPS=none). You may need to install node_modules before typecheck/test/build work.",
-    defaultTemplate: "[agent-relay] Isolated workspace: dependencies were not provisioned (AGENT_RELAY_WORKSPACE_DEPS=none). You may need to install node_modules before typecheck/test/build work.",
-    variables: [],
-  },
-  {
-    slug: "workspace.symlinks",
-    category: "runner",
-    title: "Runner Workspace Symlink Note",
-    description: "Write-through symlink caveat injected by the runner.",
-    template: "[agent-relay] Isolated workspace: these untracked paths are SYMLINKED from the main checkout: {{linked}}. They resolve to the real files in main, so editing or deleting them writes THROUGH to main — treat them as read-only unless you intend to change main.",
-    defaultTemplate: "[agent-relay] Isolated workspace: these untracked paths are SYMLINKED from the main checkout: {{linked}}. They resolve to the real files in main, so editing or deleting them writes THROUGH to main — treat them as read-only unless you intend to change main.",
-    variables: ["linked"],
-  },
-] as const satisfies readonly SeedTemplate[];