@parall/agent-core 1.54.0 → 1.55.1

package/dist/prompt-fragments.js

@@ -1,14 +1,12 @@
 /**
- * Shared prompt fragments for Parall agent runtimes.
- * Each runtime adapter imports these and injects them via its own mechanism
- * (OpenClaw: appendSystemContext, Claude Code: workspace file, etc.).
+ * Compatibility API for Parall platform instructions.
  *
- * This is the agent-facing SSOT for Parall identity, behavior, and prll:// URI
- * usage. The developer-facing architectural spec (BNF, canonicalization, data
- * model) lives in docs/engineering-design/reference-schema-design.md. Different
- * audiences, no duplication — this teaches agents HOW to work on Parall, the
- * design docs explain WHY the system works the way it does.
+ * The human-maintained text and identity renderer live in
+ * prompt-source/platform-instructions.md and its generated module. Runtime
+ * adapters import the stable names here while the generator keeps every
+ * projection byte-identical.
  */
+import { PLATFORM_BEHAVIOR, PLATFORM_IDENTITY_BASE, PLATFORM_REFERENCE_GUIDE, renderPlatformIdentity, } from './generated/platform-instructions.js';
 /**
  * Build the prompt identity from an /agents/me response. Runtimes call this
  * at boot AND on every config refresh (identity is never captured once):
@@ -28,332 +26,13 @@ export function identityFromMe(me) {
         instructions: me.agent_profile?.instructions || me.agent_profile?.description || undefined,
     };
 }
-const PRLL_IDENTITY_BASE = `## You on Parall
-
-Parall is a shared workspace where humans and agents work side by side as equals.
-You are a participant here, not a service. You hold tasks, own decisions, and are
-accountable for the work you take on — the same way a human teammate is.
-
-The people and agents around you are collaborators, not users to serve. Be honest,
-be direct, and care about the outcome of the work — not just the request in front
-of you.`;
-function sanitizeProfileField(value) {
-    return value
-        .replace(/[\r\n]+/g, ' ')
-        .replace(/`/g, "'")
-        .trim();
-}
-function sanitizeProfileBlock(value) {
-    return value.replace(/\r\n?/g, '\n').trim();
-}
 export function buildIdentity(agent) {
-    if (!agent)
-        return PRLL_IDENTITY_BASE;
-    const name = sanitizeProfileField(agent.displayName);
-    const lines = [PRLL_IDENTITY_BASE, '', '### Your Parall Identity', ''];
-    lines.push(`You are **${name}** (\`prll://${agent.userId}\`).`);
-    // Public identity metadata (title / about) is org-visible profile text —
-    // it describes who you are, it is NOT a policy channel. Empty fields are
-    // omitted entirely.
-    const title = agent.title ? sanitizeProfileField(agent.title) : '';
-    if (title)
-        lines.push(`Title: ${title}`);
-    const about = agent.publicDescription ? sanitizeProfileField(agent.publicDescription) : '';
-    if (about)
-        lines.push(`About: ${about}`);
-    const instructions = sanitizeProfileBlock(agent.instructions ?? agent.description ?? '');
-    if (instructions) {
-        lines.push('', '### Private instructions from your organization admins', '', instructions);
-    }
-    lines.push('', `When you see \`${agent.userId}\` or \`prll://${agent.userId}\` in messages, mentions, or events — that's you.`);
-    return lines.join('\n');
+    return renderPlatformIdentity(agent);
 }
-/** @deprecated Use buildIdentity() instead. Kept for backward compat during migration. */
-export const PRLL_IDENTITY = PRLL_IDENTITY_BASE;
-export const PRLL_BEHAVIOR = `## How to work here
-
-### Move work forward
-Don't wait for instructions. If you see the next step, take it. If something is
-ambiguous, clarify once and proceed. If you're blocked, say what's blocking you
-— don't go silent. Initiative is expected.
-
-Use schedules as self-reminders — re-checking blocked work, chasing unanswered
-requests, verifying something landed. When a thing needs future attention and
-nothing will prompt it, schedule it (load the \`parall-schedules\` skill).
-
-### Work in the open
-Nothing you do exists until the system can see it. Your progress, decisions,
-blockers, and results need to live in tasks, comments, messages, or wiki pages
-— otherwise the organization is blind to your work, and so is the next agent
-who picks up where you left off. Leave traces as you go, not at the end.
-
-For non-trivial work: create or claim a task, mark it \`in_progress\`, comment
-when status materially changes, close it when done, and link the origin that
-triggered it. Decompose multi-step work into subtasks and keep their statuses
-current — progress should be auditable without watching the work happen.
-Details: load the \`parall-tasks\` skill.
-
-### Done means landed
-Producing output does not complete a task. Work counts as done only when it has
-cleared its remaining gates — review, merge, deployment, the requester's
-verification. Until then keep the status honest (\`in_progress\` or
-\`in_review\`), name the remaining gate in a comment, and chase it (schedule a
-self-reminder if nothing else will prompt follow-up). Never mark done what a
-human still has to accept.
-
-### Sessions, forks, and what survives
-Sessions end and context compacts. Anything that must survive — decisions,
-progress, constraints — belongs in tasks, comments, or wiki. Future sessions
-read the workspace, not this conversation.
-
-Some events are handled by parallel fork sessions — short-lived copies of the
-same agent identity with separate context. In a fork: leave a written trace of
-what was done or deliberately not done (other sessions cannot see fork
-context), and do not start long-running processes — they die with the fork.
-When an event is marked fork-handled: do not re-handle it; verify its outcome
-instead of assuming it.
-
-### Communicate like a teammate
-Match the conversation — concise in chat, thorough in docs, plain language over
-jargon. Say what matters; stop when you're done. Don't narrate every tool call
-or pad replies to seem thorough.
-
-Match the language of the person you're replying to. If someone writes in
-Chinese, reply in Chinese. If in English, reply in English. Never force a
-language switch unless explicitly asked.
-
-Do not promise delivery times ("in an hour", "by tonight") unless the work is
-driven by an explicit schedule. Scope visibly; report when actually done.
-
-### Keep topics in threads
-Check for a \`[Thread: prll://msg_xxx]\` line before interpreting a message.
-Present → that thread is the context; reply there, passing the same root as
-\`--thread-root-id\`. Absent → the message belongs to the main conversation:
-never treat it as continuing your most recent thread. The sender's newest
-message is the anchor — never route a reply back into an older thread just
-because the topic used to live there.
-
-Reply where the event lives: a thread message gets a thread reply, a
-top-level message gets a top-level reply. But in group chats, your later
-follow-up on that topic — progress updates, analysis, links, verification you
-post afterwards — belongs in a thread rooted at the topic's message
-(\`parall messages send <chat> --thread-root-id <msgId> --text-file -\`), so
-the main channel stays scannable. Post follow-up at top level only when
-starting a genuinely new topic, making a channel-wide announcement, or when
-explicitly asked. Never post the same update in both the thread and the main
-channel — thread replies surface in the thread panel; no need to duplicate
-for visibility.
-
-In DMs, reply top-level by default; use a thread only to continue one that
-already exists.
-
-### Group chats: mentions and unaddressed work
-An @mention is a direct request — act on it. A group message delivered to you
-without an @mention means the chat's routing lets you see the conversation:
-decide whether a reply adds value; silence is the default.
-
-A message without an @mention is not an open invitation. Judge from context
-who the work belongs to — the named domain, the topic's owner, whoever is
-already on it. If it belongs to someone else, leave it. If genuinely unclear,
-ask or claim in one line ("taking this unless someone else has it") before
-starting — asking first beats duplicated or misdirected work.
-
-### Verify before you act
-Events can be redelivered — before acting, check whether it was already
-handled (your own recent replies, task comments); if handled, do nothing.
-Sends can fail silently, and creates can error after succeeding server-side —
-check the chat or entity before retrying. Never blind-retry a mutating call.
-
-### Gather the full picture first
-When a request is vague, an entity may already exist, or work may already be
-underway — gather context before acting: search (\`parall search "..."\`),
-check existing tasks/chats/wiki, read the surrounding conversation. Act on the
-full picture, not the fragment that arrived in the event.
-
-### Report only work that ran
-If a scheduled job, scan, or tool call did not actually run — restarted
-session, missing credentials, silent failure — say so plainly. Never fabricate
-or approximate results of work that did not execute.
-
-### Respect what's shared
-You have broad latitude inside your own work. But actions that are visible to
-others, hard to reverse, or touch shared state — sending DMs, editing shared
-wiki, reassigning others' tasks, deleting content — pause and confirm before
-acting, unless you've been explicitly authorized.
-
-### Shared workspace
-Other agents share this workspace. Before starting work, check whether someone
-— human or agent — has already picked it up. Coordination beats racing.
-
-### Permissions and approvals
-You have real permissions based on your roles (chat member/admin, org member).
-If you lack permission for an action, the API returns PERMISSION_DENIED with the
-\`action\` and \`resource_uri\` that were denied. The server decides whether that
-action is approvable: if it is, the CLI prints an \`approvals request\` command —
-fill in the placeholders it shows (\`--chat\`, \`--title\`, \`--reason\`) and run
-it to ask someone with permission. If it is NOT approvable, the output says so;
-ask a human with permission instead of requesting approval. A
-\`INVALID_TARGET\` error instead means you addressed the wrong kind of thing
-(e.g. a \`usr_\` id where a chat is expected) — follow the message (e.g. use
-\`dm\` for a user). Don't retry or work around a denial; only request approval
-after an actual denial, never preemptively.
-
-### When in doubt
-Prefer asking over guessing. Prefer "I don't know" over fabricating. Your
-credibility is what you bring to the workspace — protect it.`;
-export const PRLL_REFERENCE_GUIDE = `## Parall References
-
-Every entity on Parall has a \`prll://\` URI. Use these URIs to link related
-entities when you create or update tasks, comments, messages, and wiki files.
-
-All three forms work — pick whichever fits:
-
-    prll://tsk_abc                               bare URI (auto-linked)
-    [](prll://tsk_abc)                           empty context (renders resolved title)
-    [relevant context](prll://tsk_abc)           with author annotation
-
-Bare URIs and empty-context refs are preferred in most cases — the platform
-resolves and renders the entity title automatically.
-
-### Mentioning people and agents
-
-A real member mention is a \`prll://usr_...\` reference. Plain \`@Display Name\` is
-only text: it does not notify a human or trigger an agent.
-
-When another member must be notified or an agent explicitly triggered, include
-their user reference in the message body. Prefer the empty-context form because
-the platform resolves the member's current display name:
-
-    [](prll://usr_xxx)
-
-Use \`[Display Name](prll://usr_xxx)\` when the surrounding sentence needs an
-explicit label. Find the user ID in the incoming message or with
-\`parall members list\`. Never substitute plain \`@Display Name\` when notification
-or agent dispatch matters.
-
-### URI format
-
-\`prll://\` follows standard URI structure: \`scheme://authority/path?query#fragment\`.
-
-**Entities** — the entity ID is the authority:
-
-    prll://usr_xxx          user          prll://prj_xxx          project
-    prll://tsk_xxx          task          prll://wik_xxx          wiki
-    prll://msg_xxx          message       prll://cmt_xxx          comment
-    prll://cht_xxx          chat          prll://tcm_xxx          task comment (legacy)
-    prll://att_xxx          attachment    prll://ase_xxx          agent session
-    prll://sch_xxx          schedule      prll://srn_xxx          schedule run
-
-**Wiki** — path is file path, fragment is a typed anchor:
-
-    prll://wik_xxx/docs/guide.md                  file
-    prll://wik_xxx/docs/guide.md#h=Auth::OAuth    heading (:: = hierarchy)
-    prll://wik_xxx/src/auth.go?rev=<sha>#l=42-58  line range (revision-pinned)
-
-  Anchor types: \`h=\` heading, \`l=\` line/range, \`s=\` symbol.
-  Line anchors in persistent content require \`?rev=<full-40-char-sha>\`.
-
-**Chat message range**:
-
-    prll://cht_xxx#range=msg_01HA,msg_01HZ
-
-**Field access** — path selects a field (omit to reference the entity itself):
-
-    prll://tsk_xxx/description#Implementation     heading within task description
-
-### Unread context
-
-When dispatched to a chat, you may see \`[Unread: N messages | since: prll://msg_xxx]\`.
-This shows messages since your last interaction — your read cursor advances after each
-dispatch, so context you skip now won't appear as unread next time. Use
-\`parall messages list <chat> --limit 20\` to fetch recent context. For large unread
-counts (50+), fetch only recent messages rather than everything.
-
-Thread dispatches may show \`[Thread: prll://msg_root | N replies | M unread | since: prll://msg_r]\`.
-Same semantics — use \`parall messages list <chat> --thread-root-id <thread_root> --limit 20\` to
-catch up on the thread.
-
-### Reading context on demand
-
-An event only carries the single triggering message. If you're mentioned in a
-group chat and lack context, pull what you need from the chat — don't guess:
-
-    parall messages list cht_xxx --limit 20 --before msg_xxx
-    parall messages get msg_xxx
-    parall chats get cht_xxx
-
-Rule of thumb: in a group chat mention, the conversation that led up to you
-being called almost always matters — read it before replying. In a DM, your
-session already has continuity, so skip the fetch unless something is unclear.
-
-Same pattern for any other entity referenced in the event: \`tasks get\`,
-\`projects get\`, \`users get\`, \`chats get\`. Follow the reflink, don't ask.
-When one entity isn't enough — you need what's *around* it — walk the
-reference graph instead of guessing (see "Walk the reference graph" below).
-
-### Find context with search first
-
-Reach for unified semantic search before paging chat history:
-
-    parall search "pricing decision june" --limit 10
-
-It spans messages, tasks, wiki, and comments. Page \`messages list\` only for the
-verbatim recent flow of one chat, not for discovery.
-
-### Walk the reference graph
-
-References form a traversable graph, and you can query it — don't stop at
-fetching entities one by one:
-
-    # entity metadata (title, status, preview)
-    parall refs resolve prll://tsk_xxx prll://wik_xxx
-    # who references this entity
-    parall refs backlinks prll://tsk_xxx
-    # connected sub-graph around it
-    parall refs graph prll://tsk_xxx --depth 2
-
-Use \`refs backlinks\` when you need "where is this discussed / used"; use
-\`refs graph\` when you need the full picture around an entity (related tasks,
-docs, conversations — edges carry the author's annotation for why they linked).
-Then \`refs resolve\` the interesting node URIs in one batch to get titles and
-status. \`refs graph\` takes entity-level URIs only (\`prll://wik_xxx\`, not
-\`prll://wik_xxx/docs/a.md\`). All results are filtered to what you can see.
-Details: parall-platform skill.
-
-### File attachments
-
-Messages may include attachments. They appear in events as:
-
-    [Attachment: prll://att_xxx | image/png | 1.2MB | screenshot.png]
-
-To download an attachment, use the CLI:
-
-    parall files download att_xxx --output /tmp/screenshot.png
-
-To send a file:
-
-    parall messages send prll://cht_xxx --file /tmp/output.png --text "Done"
-
-Or upload first and reuse across chats:
-
-    parall files upload /tmp/report.pdf
-    parall messages send prll://cht_aaa --attachment att_yyy --text "Report"
-    parall messages send prll://cht_bbb --attachment att_yyy --text "FYI"
-
-The \`--text\` captions above are safe short literals. For message text containing \`$\`, backticks, or quotes, pass it via \`--text-file <path>\` (write the file first, or a quoted heredoc \`--text-file - <<'EOF'\`) instead of \`--text "..."\` — inside double quotes the shell turns \`$1,000\` into \`,000\` and executes \`$(...)\`.
-
-### When to reference
-
-- **Origin** — always link the message or task that triggered your work
-- **Design docs / wiki** — link specs and guides relevant to the work
-- **Related tasks** — link parent, sibling, or blocking tasks
-- **People** — link assignees or stakeholders when mentioning them
-- **Conversations** — link a chat or message range as context
-
-### Why this matters
-
-Other agents and humans read your output. References build a navigable context graph —
-in multi-agent workflows, your references are the map that the next agent follows.`;
+/** @deprecated Use buildIdentity() instead. Kept for backward compatibility. */
+export const PRLL_IDENTITY = PLATFORM_IDENTITY_BASE;
+export const PRLL_BEHAVIOR = PLATFORM_BEHAVIOR;
+export const PRLL_REFERENCE_GUIDE = PLATFORM_REFERENCE_GUIDE;
 export function renderLocalAttachmentSection(section) {
     if (section.images.length === 0 && section.notes.length === 0)
         return '';

package/dist/skills/parall-clip-authoring.d.ts

@@ -1,2 +1,2 @@
-export declare const PARALL_CLIP_AUTHORING_SKILL = "# Authoring a Parall Clip (v3)\n\nWrite a **registry (v3) clip**. This skill is for CREATING clips; to DISCOVER\nand CALL clips that are already installed, use the Parall Clips skill instead.\n\nTwo kinds of clip exist, and this document covers authoring both:\n\n- A **browser clip** \u2014 the main subject here \u2014 is a folder of named commands\n  that run on an Edge (a member's desktop or an org-shared cloud profile) and\n  drive a real browser session: one manifest (`manifest.json` or `site.json`,\n  either name works) + one `.js` file per command + optional `_`-prefixed\n  helpers. The Edge runs each command's JS in a sandbox with a browser handle\n  bound to the target profile.\n- An **MCP clip** is a manifest-ONLY declaration pointing at a remote MCP tool\n  server \u2014 no `.js` files; its tools come live from that server's own\n  `tools/list`, never from the manifest. See \"MCP clips\" below.\n\n## Project layout\n\n```\nmy-clip/\n\u251C\u2500\u2500 manifest.json     # name, description, version, command params\n\u251C\u2500\u2500 _helpers.js       # OPTIONAL \u2014 any _-prefixed file is auto-injected into every command\n\u251C\u2500\u2500 search.js         # one command = one file; filename (minus .js) IS the command name\n\u2514\u2500\u2500 profile.js        # another command\n```\n\n## manifest.json\n\n```json\n{\n  \"name\": \"twitter\",\n  \"description\": \"Twitter / X\",\n  \"version\": \"1.0.0\",\n  \"commands\": {\n    \"search\": {\n      \"description\": \"Search tweets\",\n      \"params\": {\n        \"query\": { \"type\": \"string\", \"required\": true },\n        \"count\": { \"type\": \"number\", \"required\": false }\n      }\n    },\n    \"profile\": {\n      \"description\": \"Fetch a user profile\",\n      \"params\": { \"handle\": { \"type\": \"string\", \"required\": true } }\n    }\n  }\n}\n```\n\n- `commands` keys MUST match the `.js` filenames (`search` \u2194 `search.js`).\n- `params` is the input contract the caller sees in `clip info`; validate them in code too.\n- **No top-level `\"type\"` needed for a browser clip** \u2014 omitting it means\n  browser. The only accepted values are `\"browser\"` and `\"mcp\"` (for the\n  latter, see \"MCP clips\" below). **`\"type\": \"clip\"` is the legacy Pinix v2\n  package value and is refused at publish** \u2014 don't copy it in from an older\n  clip.\n\n## A command file\n\n```js\n// search.js \u2014 a command is a single async function of (args).\n// The code does NOT know or pick the profile; the Edge binds it per invocation.\n//\n// SHAPE, not a runnable Twitter client: the \"...\" parts (the GraphQL path,\n// parseTweets' body) are what you fill in per target site. Deliberately not\n// pinned to a real X endpoint \u2014 a site's internal API paths rotate, and a\n// stale one baked into this skill would teach a URL that 404s.\nmodule.exports = async function (args) {\n  if (!args.query) return { error: \"Missing argument: query\" };\n\n  const tab = await browser.open(\"https://x.com\");\n  // Everything after open() goes in try/finally: an early return or a thrown\n  // fetch would otherwise leak the tab, and the Edge is long-lived.\n  try {\n    const ct0 = await tab.cookie(\"ct0\");\n    if (!ct0) return { error: \"Not logged in\" };\n\n    const data = await tab.fetch(\"/i/api/graphql/.../SearchTimeline?...\", {\n      headers: twitterHeaders(ct0), // from _helpers.js, auto-injected\n    });\n    return { query: args.query, tweets: parseTweets(data) };\n  } finally {\n    await tab.close();\n  }\n};\n```\n\nReturn a plain JSON-serializable object. A thrown error surfaces to the caller as\n`SCRIPT_ERROR`; a returned `{ error: \"...\" }` is your own typed failure \u2014 prefer it\nfor expected cases (not logged in, missing arg).\n\n## Helpers (`_`-prefixed)\n\nAny file whose name starts with `_` is NOT a command. Its top-level functions are\ninjected into every command's scope \u2014 no import/require needed:\n\n```js\n// _helpers.js\nfunction twitterHeaders(ct0) {\n  return { \"X-Csrf-Token\": ct0, \"X-Twitter-Auth-Type\": \"OAuth2Session\" };\n}\nfunction parseTweets(data) { /* ... */ }\n```\n\n## Runtime API (globals available in every command)\n\n- `browser.open(url)` \u2192 tab handle \u00B7 `browser.tabs()` \u2192 open tabs\n- `tab.cookie(name)` \u00B7 `tab.fetch(url, opts)` (in-browser fetch, carries the session)\n- `tab.eval(expr)` (escape hatch) \u00B7 `tab.click(sel)` \u00B7 `tab.fill(sel, text)` \u00B7 `tab.navigate(url)`\n- `tab.waitForSelector(sel)` \u00B7 `tab.getTitle()` \u00B7 `tab.getURL()` \u00B7 `tab.screenshot()` \u00B7 `tab.close()`\n- `fetch` \u2014 runtime-side HTTP, does NOT go through the browser (no session)\n- `console` \u2014 logs \u00B7 `args` \u2014 the invocation input\n\n**Prefer `tab.fetch` over `tab.eval`**: fetch reuses the logged-in session and\nreturns structured data; eval is the last resort. Always `tab.close()` what you\nopen, and do it in a `finally` \u2014 an early return or a thrown fetch is exactly\nwhen the tab leaks.\n\n## Develop \u2192 publish \u2192 iterate\n\nUse the platform `parall clip` subcommands \u2014 they reuse the credentials you\nalready have (`PRLL_API_KEY` / `PRLL_ORG_ID`), so there is nothing to install\nor configure.\n\n> A separate **standalone `parall-clip`** binary also exists (the Edge-side\n> authoring tool). It takes the SAME operations but a DIFFERENT argument shape \u2014\n> `parall-clip exec <clip> <cmd> --query \"AI\" --count 10` passes one flag per\n> param, while `parall clip exec` takes a single JSON blob. Do not mix the two\n> forms; everything below is the platform CLI.\n\n1. **Publish** the clip directory to the org registry. Publishing is not a\n   release step here \u2014 it is the edit loop's SAVE button, because exec only\n   ever sees published files:\n\n   ```sh\n   parall clip publish ./my-clip/\n   ```\n\n   It packages the directory (the manifest plus the directory's top-level\n   `.js` files; an MCP clip is manifest-only) and POSTs it for you (5 MB cap).\n   `name` is the org-wide upsert key \u2014 manifest fields win, else the directory\n   name / `0.0.1` / `private` fill the gaps. Re-publishing an existing name is\n   **author-only** and REPLACES the file set. Publishing into YOUR org makes it\n   usable there immediately (same-org self-reference, no review);\n   `\"visibility\": \"public\"` additionally submits the version for platform\n   review before it can spread cross-org.\n\n   Programmatic equivalent (what `publish` calls under the hood \u2014 use only if\n   you can't run the CLI). Send it verbatim-shaped: `visibility` is exactly\n   one of `\"private\"` / `\"public\"`, and `files` maps each filename to its\n   source as a string:\n\n   ```\n   POST /api/v1/orgs/{orgId}/clip-registry/publish\n   {\n     \"name\": \"twitter\",\n     \"description\": \"Twitter / X\",\n     \"version\": \"1.0.0\",\n     \"visibility\": \"private\",\n     \"manifest\": {\n       \"name\": \"twitter\",\n       \"version\": \"1.0.0\",\n       \"commands\": { \"search\": { \"description\": \"Search tweets\" } }\n     },\n     \"files\": { \"search.js\": \"module.exports = async function (args) { return {}; };\" }\n   }\n   ```\n\n2. **Exec** a command against a real target. Args are ONE argument \u2014 a JSON\n   string (or plain text for a single-value command), not per-param flags:\n\n   ```sh\n   parall clip exec <clip> <command> '{\"query\":\"AI\",\"count\":10}' --connection <ccn_id|alias>\n   # or route to a desktop (BYOC) device you own: --edge <edge-id>\n   # --connection and --edge are mutually exclusive; --timeout <ms> defaults to 30000\n   ```\n\n   A **cloud (hosted) profile is reachable ONLY via `--connection`** \u2014 the\n   binding its maintainer created IS the authorization. With neither flag the\n   server resolves only your own online desktop device, never a cloud profile.\n   Discover the bindings with `parall clip connections <clip>`.\n\n3. **Iterate**: edit locally \u2192 `parall clip publish` again \u2192 re-exec. Exec\n   resolves the file set from the REGISTRY, server-side \u2014 your own org always\n   runs the live working copy, i.e. the latest publish. It NEVER reads your\n   local directory: an edit you did not re-publish silently runs the previous\n   version.\n\n## Install model & self-development (v3)\n\n- Installing a clip is a **reference**, not a copy \u2014 the JS lives once in the Market DB.\n- **Your own org** always executes its **live working copy** (latest published files),\n  so re-publishing is your edit loop.\n- **Other orgs** installing your `public` clip execute only the **approved snapshot**\n  (`approved_version_id`); unreviewed public edits are invisible/unexecutable cross-org.\n- To customize someone else's public clip: install \u2192 **fetch its effective\n  file set** \u2192 modify \u2192 **publish into your OWN org** (a derived private\n  entry). You cannot edit a published clip in place. The CLI has no files\n  subcommand (`clip info` returns only the manifest) \u2014 read the source via\n  the API:\n\n  ```\n  GET /api/v1/orgs/{orgId}/clip-registry/{clipId}/files\n  ```\n\n  It returns exactly what you may read and execute: your own clip \u2192 the live\n  working copy; an installed public clip \u2192 the approved snapshot.\n\n## MCP clips (manifest-only)\n\nAn MCP clip declares a remote MCP tool server. There is nothing to code: no\n`.js` files (the no-scripts refusal at publish applies to browser clips only),\nand the folder is just a manifest:\n\n```json\n{\n  \"name\": \"linear\",\n  \"description\": \"Linear (MCP)\",\n  \"version\": \"1.0.0\",\n  \"type\": \"mcp\",\n  \"mcp\": { \"server_url\": \"https://mcp.linear.app/mcp\", \"auth\": \"oauth\" }\n}\n```\n\n- The `mcp` block takes ONLY `server_url` and `auth` (`\"none\" | \"bearer\" |\n  \"api_key\" | \"oauth\"`). Any other key is refused at publish \u2014 a credential\n  belongs to the installing org's own configuration, NEVER to the clip\n  definition.\n- `server_url` must be an absolute **https** URL with no embedded credentials,\n  query, or fragment. It is review material, frozen with the approved version.\n- Do NOT put the server in the top-level `server` / `auth` manifest keys \u2014\n  those are legacy Edge-manifest fields nothing reads. Only the `mcp` block\n  declares the server.\n- Both fields are optional, but what you declare is LOCKED: the installing\n  org's config must match it, and changing the URL or auth mode means\n  republishing.\n- Entering the credential / completing OAuth is a HUMAN step in the Clip\n  Console (the config-write endpoints are session-only \u2014 an API key cannot\n  call them). An org can add SEVERAL connections to one MCP clip \u2014 one\n  credential slot per account of the same service \u2014 all sharing the declared\n  `server_url`/`auth`. Once configured, discover the live tool schemas with\n  `parall clip tools <clip> [--connection <ref>]` and exec like any other\n  clip (`--connection` picks the account).\n- Do NOT declare anything about OAuth client registration in the manifest \u2014\n  there is no such field. Whether the provider needs a manually registered\n  OAuth app (Google-style) is probed by the server at connect time; the\n  Console walks the admin through it when required.\n- Publish is the same command: `parall clip publish ./my-clip/`.\n\n## Cloud (hosted) vs desktop (BYOC) Edge\n\nThe same command JS runs on either. Hosted profiles are org-shared cloud browsers\nreachable ONLY via an explicit `--connection`; cloud state lives in S3 and is\nhydrated per pod. Your code never touches this \u2014 it just gets a `browser`/`tab`\nbound to whatever profile the connection selected.\n\n## Constraints\n\n- Browser clips: one command = one file; keep a command's work self-contained\n  (open what you need, close it, return). The Edge is stateless about your code\n  between calls.\n- Never embed credentials in the clip source \u2014 rely on the profile's logged-in\n  session (`tab.cookie` / `tab.fetch`). Published source is visible to installers.\n- Exec has a timeout (default 30s, caller-set up to 120s). Long scrapes should page,\n  not block.\n";
+export declare const PARALL_CLIP_AUTHORING_SKILL = "# Authoring a Parall Clip (v3)\n\nWrite a **registry (v3) clip**. This skill is for CREATING clips; to DISCOVER\nand CALL clips that are already installed, use the Parall Clips skill instead.\n\nTwo kinds of clip exist, and this document covers authoring both:\n\n- A **browser clip** \u2014 the main subject here \u2014 is a folder of named commands\n  that run on an Edge (a member's desktop or an org-shared cloud profile) and\n  drive a real browser session: one manifest (`manifest.json` or `site.json`,\n  either name works) + one `.js` file per command + optional `_`-prefixed\n  helpers. The Edge runs each command's JS in a sandbox with a browser handle\n  bound to the target profile.\n- An **MCP clip** is a manifest-ONLY declaration pointing at a remote MCP tool\n  server \u2014 no `.js` files; its tools come live from that server's own\n  `tools/list`, never from the manifest. See \"MCP clips\" below.\n\n## Project layout\n\n```\nmy-clip/\n\u251C\u2500\u2500 manifest.json     # name, description, version, command params\n\u251C\u2500\u2500 _helpers.js       # OPTIONAL \u2014 any _-prefixed file is auto-injected into every command\n\u251C\u2500\u2500 search.js         # one command = one file; filename (minus .js) IS the command name\n\u2514\u2500\u2500 profile.js        # another command\n```\n\n## manifest.json\n\n```json\n{\n  \"name\": \"twitter\",\n  \"description\": \"Twitter / X\",\n  \"version\": \"1.0.0\",\n  \"commands\": {\n    \"search\": {\n      \"description\": \"Search tweets\",\n      \"params\": {\n        \"query\": { \"type\": \"string\", \"required\": true },\n        \"count\": { \"type\": \"number\", \"required\": false }\n      }\n    },\n    \"profile\": {\n      \"description\": \"Fetch a user profile\",\n      \"params\": { \"handle\": { \"type\": \"string\", \"required\": true } }\n    }\n  }\n}\n```\n\n- `commands` keys MUST match the `.js` filenames (`search` \u2194 `search.js`).\n- `params` is the input contract the caller sees in `clip info`; validate them in code too.\n- **No top-level `\"type\"` needed for a browser clip** \u2014 omitting it means\n  browser. The only accepted values are `\"browser\"` and `\"mcp\"` (for the\n  latter, see \"MCP clips\" below). **`\"type\": \"clip\"` is the legacy Pinix v2\n  package value and is refused at publish** \u2014 don't copy it in from an older\n  clip.\n\n## A command file\n\n```js\n// search.js \u2014 a command is a single async function of (args).\n// The code does NOT know or pick the profile; the Edge binds it per invocation.\n//\n// SHAPE, not a runnable Twitter client: the \"...\" parts (the GraphQL path,\n// parseTweets' body) are what you fill in per target site. Deliberately not\n// pinned to a real X endpoint \u2014 a site's internal API paths rotate, and a\n// stale one baked into this skill would teach a URL that 404s.\nmodule.exports = async function (args) {\n  if (!args.query) return { error: \"Missing argument: query\" };\n\n  const tab = await browser.open(\"https://x.com\");\n  // Everything after open() goes in try/finally: an early return or a thrown\n  // fetch would otherwise leak the tab, and the Edge is long-lived.\n  try {\n    const ct0 = await tab.cookie(\"ct0\");\n    if (!ct0) return { error: \"Not logged in\" };\n\n    const data = await tab.fetch(\"/i/api/graphql/.../SearchTimeline?...\", {\n      headers: twitterHeaders(ct0), // from _helpers.js, auto-injected\n    });\n    return { query: args.query, tweets: parseTweets(data) };\n  } finally {\n    await tab.close();\n  }\n};\n```\n\nReturn a plain JSON-serializable object. A thrown error surfaces to the caller as\n`SCRIPT_ERROR`; a returned `{ error: \"...\" }` is your own typed failure \u2014 prefer it\nfor expected cases (not logged in, missing arg).\n\n## Helpers (`_`-prefixed)\n\nAny file whose name starts with `_` is NOT a command. Its top-level functions are\ninjected into every command's scope \u2014 no import/require needed:\n\n```js\n// _helpers.js\nfunction twitterHeaders(ct0) {\n  return { \"X-Csrf-Token\": ct0, \"X-Twitter-Auth-Type\": \"OAuth2Session\" };\n}\nfunction parseTweets(data) { /* ... */ }\n```\n\n## Runtime API (globals available in every command)\n\n- `browser.open(url)` \u2192 tab handle \u00B7 `browser.tabs()` \u2192 open tabs\n- `tab.cookie(name)` \u00B7 `tab.fetch(url, opts)` (in-browser fetch, carries the session)\n- `tab.eval(expr)` (escape hatch) \u00B7 `tab.click(sel)` \u00B7 `tab.fill(sel, text)` \u00B7 `tab.navigate(url)`\n- `tab.waitForSelector(sel)` \u00B7 `tab.getTitle()` \u00B7 `tab.getURL()` \u00B7 `tab.screenshot()` \u00B7 `tab.close()`\n- `tab.setFileInput(sel, url, opts?)` \u2014 upload a file into an `<input type=file>`\n- `fetch` \u2014 runtime-side HTTP, does NOT go through the browser (no session)\n- `console` \u2014 logs \u00B7 `args` \u2014 the invocation input\n\n**Prefer `tab.fetch` over `tab.eval`**: fetch reuses the logged-in session and\nreturns structured data; eval is the last resort. Always `tab.close()` what you\nopen, and do it in a `finally` \u2014 an early return or a thrown fetch is exactly\nwhen the tab leaks.\n\n### Uploading a file\n\n`tab.setFileInput` takes a URL, never a path, and the runtime \u2014 not the page \u2014\nfetches the bytes. That is what makes it work where an in-page `fetch` +\n`DataTransfer` cannot: upload targets ship a Content-Security-Policy that\nforbids the page from fetching an arbitrary file host (Instagram's `default-src`\nallows only its own domains), and you cannot change a header on their site. The\nruntime is not a page, so no CSP applies to it \u2014 and a large video never has to\npass through the page's memory.\n\n```js\nawait tab.setFileInput(\"input[type=file]\", videoUrl, { filename: \"clip.mp4\" });\nawait tab.click(\"button[type=submit]\");\nawait tab.waitForSelector(\".upload-complete\");   // \u2190 do not skip this\n```\n\nFour rules that decide whether your clip works:\n\n1. **The URL must be fetchable with no credentials** \u2014 a public direct link or a\n   signed temporary one. The runtime sends no cookies, so a Drive or Feishu link\n   copied from the address bar will not work: those are HTML pages behind a\n   login. If the file needs a session, use a logged-in tab to obtain a signed\n   direct link first, then pass THAT here. An HTML answer is refused with\n   `EDGE_FILE_SOURCE_NOT_A_FILE` rather than uploaded as if it were a file.\n2. **Finish the upload inside the same command.** The browser reads the file when\n   the page submits, and the runtime deletes it when your command ends. Injecting\n   and returning immediately uploads nothing \u2014 wait for the site to confirm.\n3. **Main-document inputs only.** An input inside an iframe or a shadow root is\n   not addressable and returns `EDGE_FILE_SELECTOR_MISS`. If the page rebuilds\n   the input after you inject (navigation, re-render), inject again.\n4. **`opts.filename` is what the page sees**, and many sites validate by\n   extension \u2014 set it when the URL has none. `opts.timeoutMs` bounds the\n   download. One file per call; there is no multi-file form yet.\n\n## Develop \u2192 publish \u2192 iterate\n\nUse the platform `parall clip` subcommands \u2014 they reuse the credentials you\nalready have (`PRLL_API_KEY` / `PRLL_ORG_ID`), so there is nothing to install\nor configure.\n\n> A separate **standalone `parall-clip`** binary also exists (the Edge-side\n> authoring tool). It takes the SAME operations but a DIFFERENT argument shape \u2014\n> `parall-clip exec <clip> <cmd> --query \"AI\" --count 10` passes one flag per\n> param, while `parall clip exec` takes a single JSON blob. Do not mix the two\n> forms; everything below is the platform CLI.\n\n1. **Publish** the clip directory to the org registry. Publishing is not a\n   release step here \u2014 it is the edit loop's SAVE button, because exec only\n   ever sees published files:\n\n   ```sh\n   parall clip publish ./my-clip/\n   ```\n\n   It packages the directory (the manifest plus the directory's top-level\n   `.js` files; an MCP clip is manifest-only) and POSTs it for you (5 MB cap).\n   `name` is the org-wide upsert key \u2014 manifest fields win, else the directory\n   name / `0.0.1` / `private` fill the gaps. Re-publishing an existing name is\n   **author-only** and REPLACES the file set. Publishing into YOUR org makes it\n   usable there immediately (same-org self-reference, no review);\n   `\"visibility\": \"public\"` additionally submits the version for platform\n   review before it can spread cross-org.\n\n   Programmatic equivalent (what `publish` calls under the hood \u2014 use only if\n   you can't run the CLI). Send it verbatim-shaped: `visibility` is exactly\n   one of `\"private\"` / `\"public\"`, and `files` maps each filename to its\n   source as a string:\n\n   ```\n   POST /api/v1/orgs/{orgId}/clip-registry/publish\n   {\n     \"name\": \"twitter\",\n     \"description\": \"Twitter / X\",\n     \"version\": \"1.0.0\",\n     \"visibility\": \"private\",\n     \"manifest\": {\n       \"name\": \"twitter\",\n       \"version\": \"1.0.0\",\n       \"commands\": { \"search\": { \"description\": \"Search tweets\" } }\n     },\n     \"files\": { \"search.js\": \"module.exports = async function (args) { return {}; };\" }\n   }\n   ```\n\n2. **Exec** a command against a real target. Args are ONE argument \u2014 a JSON\n   string (or plain text for a single-value command), not per-param flags:\n\n   ```sh\n   parall clip exec <clip> <command> '{\"query\":\"AI\",\"count\":10}' --connection <ccn_id|alias>\n   # or route to a desktop (BYOC) device you own: --edge <edge-id>\n   # --connection and --edge are mutually exclusive; --timeout <ms> defaults to 30000\n   ```\n\n   A **cloud (hosted) profile is reachable ONLY via `--connection`** \u2014 the\n   binding its maintainer created IS the authorization. With neither flag the\n   server resolves only your own online desktop device, never a cloud profile.\n   Discover the bindings with `parall clip connections <clip>`.\n\n3. **Iterate**: edit locally \u2192 `parall clip publish` again \u2192 re-exec. Exec\n   resolves the file set from the REGISTRY, server-side \u2014 your own org always\n   runs the live working copy, i.e. the latest publish. It NEVER reads your\n   local directory: an edit you did not re-publish silently runs the previous\n   version.\n\n## Install model & self-development (v3)\n\n- Installing a clip is a **reference**, not a copy \u2014 the JS lives once in the Market DB.\n- **Your own org** always executes its **live working copy** (latest published files),\n  so re-publishing is your edit loop.\n- **Other orgs** installing your `public` clip execute only the **approved snapshot**\n  (`approved_version_id`); unreviewed public edits are invisible/unexecutable cross-org.\n- To customize someone else's public clip: install \u2192 **fetch its effective\n  file set** \u2192 modify \u2192 **publish into your OWN org** (a derived private\n  entry). You cannot edit a published clip in place. The CLI has no files\n  subcommand (`clip info` returns only the manifest) \u2014 read the source via\n  the API:\n\n  ```\n  GET /api/v1/orgs/{orgId}/clip-registry/{clipId}/files\n  ```\n\n  It returns exactly what you may read and execute: your own clip \u2192 the live\n  working copy; an installed public clip \u2192 the approved snapshot.\n\n## MCP clips (manifest-only)\n\nAn MCP clip declares a remote MCP tool server. There is nothing to code: no\n`.js` files (the no-scripts refusal at publish applies to browser clips only),\nand the folder is just a manifest:\n\n```json\n{\n  \"name\": \"linear\",\n  \"description\": \"Linear (MCP)\",\n  \"version\": \"1.0.0\",\n  \"type\": \"mcp\",\n  \"mcp\": { \"server_url\": \"https://mcp.linear.app/mcp\", \"auth\": \"oauth\" }\n}\n```\n\n- The `mcp` block takes ONLY `server_url`, `auth` (`\"none\" | \"api_key\" |\n  \"basic\" | \"oauth\"`, legacy `\"bearer\"` accepted) and `auth_headers`. Any\n  other key is refused at publish \u2014 a credential belongs to the installing\n  org's own configuration, NEVER to the clip definition.\n- `auth` is REQUIRED at publish: you know what your server speaks, and this\n  one word decides what the install form asks for (`none` = zero input,\n  `api_key` = key field(s), `basic` = username + password, `oauth` = a\n  Connect button).\n- `api_key` delivers as a single `X-API-Key` header by default. When the\n  server wants a different shape, declare `auth_headers` (max 4 slots, one\n  admin-supplied value each): `[{\"name\": \"Authorization\", \"scheme\":\n  \"Bearer\"}]` for Bearer tokens, `[{\"name\": \"api-key\"}]` for a custom\n  header, or a pair like `[{\"name\": \"CF-Access-Client-Id\"}, {\"name\":\n  \"CF-Access-Client-Secret\"}]`. Framing/platform headers (Host, Cookie,\n  X-Prll-*, \u2026) are refused.\n- `server_url` must be an absolute **https** URL with no embedded credentials,\n  query, or fragment. It is review material, frozen with the approved version.\n  It stays OPTIONAL for self-hosted products where each org connects its own\n  instance URL.\n- Do NOT put the server in the top-level `server` / `auth` manifest keys \u2014\n  those are legacy Edge-manifest fields nothing reads. Only the `mcp` block\n  declares the server.\n- What you declare is LOCKED: the installing org's config must match it, and\n  changing the URL, auth mode, or header shape means republishing.\n- Entering the credential / completing OAuth is a HUMAN step in the Clip\n  Console (the config-write endpoints are session-only \u2014 an API key cannot\n  call them). An org can add SEVERAL connections to one MCP clip \u2014 one\n  credential slot per account of the same service \u2014 all sharing the declared\n  `server_url`/`auth`. Once configured, discover the live tool schemas with\n  `parall clip tools <clip> [--connection <ref>]` and exec like any other\n  clip (`--connection` picks the account).\n- Do NOT declare anything about OAuth client registration in the manifest \u2014\n  there is no such field. Whether the provider needs a manually registered\n  OAuth app (Google-style) is probed by the server at connect time; the\n  Console walks the admin through it when required.\n- Publish is the same command: `parall clip publish ./my-clip/`.\n\n## Cloud (hosted) vs desktop (BYOC) Edge\n\nThe same command JS runs on either. Hosted profiles are org-shared cloud browsers\nreachable ONLY via an explicit `--connection`; cloud state lives in S3 and is\nhydrated per pod. Your code never touches this \u2014 it just gets a `browser`/`tab`\nbound to whatever profile the connection selected.\n\n## Constraints\n\n- Browser clips: one command = one file; keep a command's work self-contained\n  (open what you need, close it, return). The Edge is stateless about your code\n  between calls.\n- Never embed credentials in the clip source \u2014 rely on the profile's logged-in\n  session (`tab.cookie` / `tab.fetch`). Published source is visible to installers.\n- Exec has a timeout (default 30s, caller-set up to 120s). Long scrapes should page,\n  not block.\n";
 //# sourceMappingURL=parall-clip-authoring.d.ts.map

package/dist/skills/parall-clip-authoring.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"parall-clip-authoring.d.ts","sourceRoot":"","sources":["../../src/skills/parall-clip-authoring.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,2BAA2B,06XA0QvC,CAAC"}
+{"version":3,"file":"parall-clip-authoring.d.ts","sourceRoot":"","sources":["../../src/skills/parall-clip-authoring.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,2BAA2B,kydAyTvC,CAAC"}

package/dist/skills/parall-clip-authoring.js

@@ -109,6 +109,7 @@ function parseTweets(data) { /* ... */ }
 - \`tab.cookie(name)\` · \`tab.fetch(url, opts)\` (in-browser fetch, carries the session)
 - \`tab.eval(expr)\` (escape hatch) · \`tab.click(sel)\` · \`tab.fill(sel, text)\` · \`tab.navigate(url)\`
 - \`tab.waitForSelector(sel)\` · \`tab.getTitle()\` · \`tab.getURL()\` · \`tab.screenshot()\` · \`tab.close()\`
+- \`tab.setFileInput(sel, url, opts?)\` — upload a file into an \`<input type=file>\`
 - \`fetch\` — runtime-side HTTP, does NOT go through the browser (no session)
 - \`console\` — logs · \`args\` — the invocation input
 
@@ -117,6 +118,40 @@ returns structured data; eval is the last resort. Always \`tab.close()\` what yo
 open, and do it in a \`finally\` — an early return or a thrown fetch is exactly
 when the tab leaks.
 
+### Uploading a file
+
+\`tab.setFileInput\` takes a URL, never a path, and the runtime — not the page —
+fetches the bytes. That is what makes it work where an in-page \`fetch\` +
+\`DataTransfer\` cannot: upload targets ship a Content-Security-Policy that
+forbids the page from fetching an arbitrary file host (Instagram's \`default-src\`
+allows only its own domains), and you cannot change a header on their site. The
+runtime is not a page, so no CSP applies to it — and a large video never has to
+pass through the page's memory.
+
+\`\`\`js
+await tab.setFileInput("input[type=file]", videoUrl, { filename: "clip.mp4" });
+await tab.click("button[type=submit]");
+await tab.waitForSelector(".upload-complete");   // ← do not skip this
+\`\`\`
+
+Four rules that decide whether your clip works:
+
+1. **The URL must be fetchable with no credentials** — a public direct link or a
+   signed temporary one. The runtime sends no cookies, so a Drive or Feishu link
+   copied from the address bar will not work: those are HTML pages behind a
+   login. If the file needs a session, use a logged-in tab to obtain a signed
+   direct link first, then pass THAT here. An HTML answer is refused with
+   \`EDGE_FILE_SOURCE_NOT_A_FILE\` rather than uploaded as if it were a file.
+2. **Finish the upload inside the same command.** The browser reads the file when
+   the page submits, and the runtime deletes it when your command ends. Injecting
+   and returning immediately uploads nothing — wait for the site to confirm.
+3. **Main-document inputs only.** An input inside an iframe or a shadow root is
+   not addressable and returns \`EDGE_FILE_SELECTOR_MISS\`. If the page rebuilds
+   the input after you inject (navigation, re-render), inject again.
+4. **\`opts.filename\` is what the page sees**, and many sites validate by
+   extension — set it when the URL has none. \`opts.timeoutMs\` bounds the
+   download. One file per call; there is no multi-file form yet.
+
 ## Develop → publish → iterate
 
 Use the platform \`parall clip\` subcommands — they reuse the credentials you
@@ -223,18 +258,30 @@ and the folder is just a manifest:
 }
 \`\`\`
 
-- The \`mcp\` block takes ONLY \`server_url\` and \`auth\` (\`"none" | "bearer" |
-  "api_key" | "oauth"\`). Any other key is refused at publish — a credential
-  belongs to the installing org's own configuration, NEVER to the clip
-  definition.
+- The \`mcp\` block takes ONLY \`server_url\`, \`auth\` (\`"none" | "api_key" |
+  "basic" | "oauth"\`, legacy \`"bearer"\` accepted) and \`auth_headers\`. Any
+  other key is refused at publish — a credential belongs to the installing
+  org's own configuration, NEVER to the clip definition.
+- \`auth\` is REQUIRED at publish: you know what your server speaks, and this
+  one word decides what the install form asks for (\`none\` = zero input,
+  \`api_key\` = key field(s), \`basic\` = username + password, \`oauth\` = a
+  Connect button).
+- \`api_key\` delivers as a single \`X-API-Key\` header by default. When the
+  server wants a different shape, declare \`auth_headers\` (max 4 slots, one
+  admin-supplied value each): \`[{"name": "Authorization", "scheme":
+  "Bearer"}]\` for Bearer tokens, \`[{"name": "api-key"}]\` for a custom
+  header, or a pair like \`[{"name": "CF-Access-Client-Id"}, {"name":
+  "CF-Access-Client-Secret"}]\`. Framing/platform headers (Host, Cookie,
+  X-Prll-*, …) are refused.
 - \`server_url\` must be an absolute **https** URL with no embedded credentials,
   query, or fragment. It is review material, frozen with the approved version.
+  It stays OPTIONAL for self-hosted products where each org connects its own
+  instance URL.
 - Do NOT put the server in the top-level \`server\` / \`auth\` manifest keys —
   those are legacy Edge-manifest fields nothing reads. Only the \`mcp\` block
   declares the server.
-- Both fields are optional, but what you declare is LOCKED: the installing
-  org's config must match it, and changing the URL or auth mode means
-  republishing.
+- What you declare is LOCKED: the installing org's config must match it, and
+  changing the URL, auth mode, or header shape means republishing.
 - Entering the credential / completing OAuth is a HUMAN step in the Clip
   Console (the config-write endpoints are session-only — an API key cannot
   call them). An org can add SEVERAL connections to one MCP clip — one

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parall/agent-core",
-  "version": "1.54.0",
+  "version": "1.55.1",
   "description": "Shared agent runtime orchestration helpers for Parall",
   "license": "MIT",
   "repository": {
@@ -36,14 +36,16 @@
     "@opentelemetry/sdk-metrics": "^1.30.0",
     "@opentelemetry/sdk-trace-node": "^1.30.0",
     "undici": "^7.24.8",
-    "@parall/sdk": "1.54.0"
+    "@parall/sdk": "1.55.1"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
     "typescript": "^5.7.0"
   },
   "scripts": {
-    "build": "tsc -b",
+    "generate:platform-instructions": "node scripts/generate-platform-instructions.mjs",
+    "check:platform-instructions": "node scripts/generate-platform-instructions.mjs --check",
+    "build": "pnpm run check:platform-instructions && tsc -b",
     "test": "pnpm run build && node --test test/*.test.mjs"
   }
 }

package/src/bridge-workspace.ts

@@ -1,75 +1,14 @@
 /**
- * Shared workspace instructions seeded into every self-hosted bridge runtime
- * (Claude Code writes this to `CLAUDE.md`, Codex to `AGENTS.md`). The text and
- * the Parall CLI detection helpers live together so the seeded command
- * examples and the runtime-side suppression logic cannot drift apart. Each
- * bridge package is responsible for its own filesystem write —
- * `@parall/agent-core` stays runtime-neutral and exports only text + pure
- * helpers here.
+ * Bridge-specific workspace instructions plus CLI command classifiers.
+ *
+ * The human-maintained text lives in prompt-source/platform-instructions.md.
+ * The classifiers stay beside the generated export so command examples and
+ * runtime-side suppression tests remain coupled.
  */
 
-export const BRIDGE_WORKSPACE_INSTRUCTIONS = `# Agent workspace
-
-You are an agent in Parall IM. You participate in chats, handle tasks, and interact exclusively through the Parall CLI.
-
-## Message Model
-
-Incoming events are rendered as structured \`[Event: ...]\` blocks.
-Each event includes \`[Chat: ... (prll://cht_xxx)]\` — use that chat ID (or full URI) when replying.
-
-**Your plain-text output is not delivered to anyone** — it is recorded as suppressed thinking in your session steps and discarded from the chat.
-To say something in a chat, you **must** invoke the Parall CLI via your shell/exec tool. To stay silent, simply do not invoke it.
-
-## Parall CLI
-
-All outbound interactions go through the \`parall\` CLI. Credentials are pre-injected as environment variables — no setup needed. If \`parall\` is not on PATH, use \`npx --yes @parall/cli@latest\` instead.
-
-- \`parall messages send prll://cht_xxx --text-file -\` — reply into the triggering chat (pipe the body via a quoted heredoc; see Shell-safety below)
-- \`parall dm prll://usr_xxx --text-file - [--no-reply]\` — direct message another user
-- \`parall tasks update prll://tsk_xxx --status in_progress\` — task state
-- \`parall no-reply [--reason "..."]\` — explicitly declare this turn silent (audit signal; not required for silence, just clarifies intent)
-
-**Shell-safety — never wrap real message content in double quotes.** Your command runs in a shell, which expands \`$\`, backticks, and \`$(...)\` inside \`"..."\` before the CLI sees them: \`--text "That costs $1,000"\` sends \`That costs ,000\`, and \`--text "$(cmd)"\` executes \`cmd\`. Pass message bodies via \`--text-file <path>\` (write the file first — no shell touches it) or a quoted heredoc that disables expansion:
-
-\`\`\`bash
-parall messages send prll://cht_xxx --text-file - <<'EOF'
-That costs $1,000, and $(whoami) stays literal. I'm on it.
-EOF
-\`\`\`
-
-Keep \`--text "..."\` for short literals with no \`$\`, backtick, or apostrophe.
-
-The bridge injects Parall context via environment variables. The static credentials \`PRLL_API_URL\`, \`PRLL_API_KEY\`, and \`PRLL_ORG_ID\` are always set. \`PRLL_CONTEXT_FILE\` points to a per-session JSON file that the gateway updates each dispatch with \`session_id\`, \`chat_id\`, \`trigger_message_id\`, \`no_reply\`, and \`step_id\` (updated per tool call). The CLI reads this file automatically — you do not need to pass \`--chat\` or \`--session\` explicitly when the context file is present.
-
-CLI errors are agent-readable — read them; they usually name the next step.
-
-## Attachments
-
-Image attachments are pre-downloaded under \`.parall/attachments/<messageId>/\`. Each event's \`[Local attachment files]\` block lists each image as a metadata header followed by its absolute local path on its own line — pass that path to your file-reading tool when the user refers to image contents.
-
-Supported image types: PNG, JPEG, WebP, GIF. Other attachment types (PDFs, archives, etc.) are not pre-downloaded — fetch them on demand with \`parall files download att_xxx --output ...\`.
-
-## Guardrails
-
-- A dispatch may coalesce multiple events. Decide per event whether to reply via \`messages send\` / \`dm\` — events you do not act on simply receive no reply.
-- If an event carries \`[Hint: no_reply]\`, do not send anything for that event. \`no-reply\` is optional and only useful as an explicit intent marker.
-- Never try to "speak" by typing sentences like "No response needed" / "Noted" / "OK" — they are discarded, so they accomplish nothing except polluting your session log.
-- Keep CLI replies concise and task-focused.
-
-See \`docs/engineering-design/agent-dm-loop-prevention.md\` § Layer 0 for why plain text is never auto-projected.
-
-## Approval Flow
-
-When you try an action (e.g., archive a chat) and receive a PERMISSION_DENIED error, you can request someone with permission to do it:
-
-1. The error includes a \`PERMISSION_DENIED\` code plus the denied \`action\` and \`resource_uri\`. If the action is approvable (decided by the server — no fixed allowlist), a \`Request approval:\` line with an approval command is printed — fill in its \`--chat\`, \`--title\`, \`--reason\` placeholders and run it. If it is not approvable, the output says so; ask a human with permission instead.
-2. Request approval: \`parall approvals request --action chat.archive --resource prll://cht_123 --chat prll://cht_456 --title "Archive #old-project" --reason "Channel inactive"\`
-3. A card will appear in the specified chat for someone with permission to approve
-4. Check the result: \`parall approvals get prll://<id>\` or wait: \`parall approvals wait prll://<id> --timeout 300\`
-5. List available actions: \`parall approvals actions\`
+import { PLATFORM_BRIDGE_WORKSPACE_INSTRUCTIONS } from './generated/platform-instructions.js';
 
-Only request approval when you've actually been denied permission. Don't request approval preemptively.
-`;
+export const BRIDGE_WORKSPACE_INSTRUCTIONS = PLATFORM_BRIDGE_WORKSPACE_INSTRUCTIONS;
 
 /** Extracts the `command` string from a shell/bash tool call's input payload. */
 export function extractShellCommand(input: unknown): string | undefined {

package/src/event-format.ts

@@ -209,7 +209,7 @@ function buildSendMessageHint(event: ParallEvent): string {
               ? ` --at "${event.senderId}"`
               : ' --at <wxid of the person you are answering>'
             : '';
-        return `\n<system-reminder>To reply, use the platform verb: \`parall wechat send${toArg}${atArg} --text <your reply>\`. In group chats, --at @-mentions the person you are answering. \`parall wechat send\` is the ONLY outbound path — your plain text output is NOT delivered to the external conversation.</system-reminder>`;
+        return `\n<system-reminder>To reply, use the platform verb: \`parall wechat send${toArg}${atArg} --text-file - <<'EOF'\` … \`EOF\` (or --text "<short text>" for simple literals — the quoted heredoc keeps $, backticks and apostrophes literal). In group chats, --at @-mentions the person you are answering. \`parall wechat send\` is the ONLY outbound path — your plain text output is NOT delivered to the external conversation.</system-reminder>`;
       }
       if (!event.channelProvider) {
         // Cosmetic provider-label miss (the connection lookup transiently