@foldrun/core 0.2.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 foldrun contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,239 @@
+# foldrun
+
+**Agents are just folders. Write them, check them, run them.**
+
+An agent is a folder. Its instructions, skills, knowledge, memory, tools and
+tests are files you can read, diff and commit. There is no SDK to learn and no
+graph to wire — the runtime reads the folder.
+
+```bash
+npx foldrun init my-desk
+cd my-desk
+foldrun check          # validate everything — costs nothing
+foldrun run publish    # run the flow
+```
+
+```
+my-desk/
+├── AGENTS.md          what every agent here should know
+├── agents/            who does the work
+│   └── writer/agent.md
+├── flows/             in what order
+│   └── publish.md
+├── skills/            how a task is done
+├── knowledge/         what you gave them
+├── memory/            what they learned
+├── tools/             what they can call
+├── scripts/           code
+└── evals/             is it any good
+```
+
+**API reference:** docs/api.md — every route, its methods, and what it takes.
+
+## Built on other people's standards
+
+Most of this format is not ours. Where an open standard exists we adopt it
+rather than compete with it:
+
+| Layer | Standard | From |
+|---|---|---|
+| `AGENTS.md` | [AGENTS.md](https://agents.md/) | Linux Foundation |
+| `skills/` | [Agent Skills](https://agentskills.io) | Anthropic |
+| documents in `knowledge/`, `memory/` | [Open Knowledge Format v0.2](https://github.com/GoogleCloudPlatform/knowledge-catalog/tree/main/okf) | Google Cloud |
+| `tools/` | [MCP](https://modelcontextprotocol.io) | Anthropic, adopted broadly |
+| `flows/`, `evals/` | none exists — ours | |
+
+A skill written for Claude Code or Cursor runs here unchanged — including one installed in the cross-client `.agents/skills/` directory, which the runtime scans alongside its own `skills/`. A knowledge
+bundle exported by any OKF producer drops straight in. Agent frontmatter also
+accepts Claude Code's subagent fields, so those files mostly run as they are.
+
+## Flows are a numbered list
+
+```markdown
+1. [[researcher]] — find one topic worth writing about
+2. [[writer]]     — draft it
+2. [[fixer]]      — fix the technical issues, in parallel
+3. [[editor]]     — review both together
+   verify: test -s outputs/post.md
+```
+
+Same number runs at the same time; different numbers run in order. Each group
+receives everything the group before it produced. `verify:` means a shell
+command has to exit 0 — *done* should mean a check passed, not that the model
+stopped talking.
+
+## Evals, because prompts regress quietly
+
+```markdown
+## writes for farmers, not gardeners
+task: Propose a topic and say who it is for.
+expect:
+  - not-contains: leverage
+  - judge: the intended reader is a working farmer
+```
+
+Deterministic checks run first; a model only judges what survives them.
+`foldrun eval` in CI is how you find out a prompt edit made things worse.
+
+Every eval runs after every deploy unless it says otherwise. An eval of a
+whole flow costs a whole run each time — and may touch real systems — so mark
+it `trigger: manual` and it runs only when a person asks — the Run button,
+the API, or `foldrun eval`.
+
+## Which model, and how hard it thinks
+
+Two knobs, set anywhere from a whole agent down to one step of one flow —
+nearest wins, and the run trace names the winner:
+
+```yaml
+model: fast        # a tier (fast | default | max), an exact id, or "@preset/…"
+effort: high       # low | medium | high | xhigh | max
+```
+
+Tiers keep files from rotting when models are renamed; an exact id pins one;
+synonyms all land (`small`, `cheap`, `large`, `best`…). Effort is the
+orthogonal axis — `fast` + `max` is the cheap model told to take its time.
+
+A `provider:` block points the runtime at any endpoint speaking the Anthropic
+Messages API — OpenRouter's Anthropic skin runs 400+ models through it, a
+LiteLLM in front covers the rest — and remaps what the tiers mean there:
+
+```yaml
+provider:
+  base_url: https://openrouter.ai/api
+  token: ${OPENROUTER_API_KEY}
+  models:
+    fast: google/gemini-2.5-flash
+```
+
+The runtime then asks the gateway what each model can actually do, and uses
+the answer three ways: a step whose agent needs tools fails **at start** on a
+model that can't call them (one line, naming the nearest that can); `effort:`
+is fitted to each model's supported levels, out loud; and step cost is priced
+from the gateway's own rates, not one vendor's table. When a claim needs
+proving, `foldrun probe <model>` runs a real tool loop against it — a nonce
+the model must fetch through a tool and echo back — through your exact
+provider config. The catalogue is the gateway's claim; the probe is ground
+truth.
+
+## The host for markdown agents
+
+**foldrun cloud** runs your agents so you don't operate them: scheduled and
+webhook triggers, durable runs with full history, a secret store, team access,
+and containers you never touch. Push the folder, it runs.
+
+The format, the CLI and the runtime are open source (Apache-2.0), and the
+hosted platform imports the same core rather than a fork. Writing and checking
+an agent locally costs nothing and needs no account — that is the on-ramp to
+the host, not a competitor to it.
+
+Where the two differ is operations, not capability. Locally a run happens in
+your terminal; hosted, it survives a restart, retries a failed step, waits days
+for an approval and tells you what it cost. Nothing is held back from the open
+version to make the hosted one worth buying.
+
+## This repo, and the others
+
+This is `foldrun-core`: the runtime, published to npm as `@foldrun/core`.
+Most people want the CLI, not this package — `npm install -g foldrun`.
+
+| Path | What |
+|---|---|
+| `src/` | the runtime: parse, run, check, evaluate |
+| `templates/` | starting points for a new workspace — see below |
+| `SPEC.md` | the agent and flow format |
+| `okf/PROFILE.md` | which parts of OKF are implemented |
+| `okf/WHITE-PAPER.md` | hosting OKF: what the spec leaves to hosts |
+| `tests/` | the runtime's tests (`npm test`) |
+
+The command-line tool is its own repository,
+[`foldrun-cli`](https://github.com/foldrun-io/foldrun-cli), and depends on
+this package. The reference documentation is at
+[docs.foldrun.io](https://docs.foldrun.io). The hosted platform's own
+repositories are private; see "Hosting it" below.
+
+### Templates and workspaces
+
+There is **one** place a workspace lives: wherever you made it. `foldrun init`
+makes one in a directory you name; the hosted platform makes one under
+`data/<tenant>/workspaces/<name>/`, which is gitignored because it holds your
+secrets, run journals and whatever your agents learned.
+
+`templates/` is not a second home for workspaces. It holds **starting points**
+— authored, committed, and shipped — and you turn one into a workspace:
+
+```bash
+foldrun init my-desk --from templates/hello
+foldrun check my-desk
+foldrun run note --workspace my-desk
+```
+
+`templates/hello` is the smaller of the two and exercises the whole format: an
+agent, a flow, a skill, a script tool as a folder (`tools/wordcount/` — a
+`tool.md` and the `run.py` it calls), knowledge it may only read, memory it
+writes back, and state it carries to the next run. `templates/blog-desk` is
+the two-agent shape of a real desk: a researcher picks the topic, a writer
+drafts it, over shared house style in `knowledge/` and an eval that holds the
+writer to it.
+
+A template ships, so it has to be correct without anyone running it: every
+bundle in `templates/` is checked for conformance on each test run, and its
+generated `index.md` is regenerated and compared against the committed one, so
+a hand-edited template cannot ship an index that disagrees with its own files.
+
+## Hosting it
+
+This package is the framework: everything needed to read a workspace and
+run it on the machine you are on. The hosted platform at
+[foldrun.io](https://foldrun.io) — a queue and its worker, one gVisor pod
+per step, a vault, metering, a team — is built on it, in a separate private
+package that plugs in through `src/platform.ts`. Nothing in this repository
+imports it, so what is here is exactly what is open. There is no
+self-hosted platform; `foldrun deploy` and `git push` move a workspace from
+your machine to the hosted one unchanged.
+
+## Requirements
+
+Node 22+. Docker or Podman if your agents run scripts. Credentials come from
+`ANTHROPIC_API_KEY` or an existing Claude Code login — `foldrun check` needs
+neither.
+
+## Status
+
+v0.1. Local and hosted runs work. Hosted runs go through a durable on-disk
+queue (survives restarts, parks at approval gates), the dashboard has
+accounts and sessions (scrypt + signed cookies; first signup is free, then
+`FOLDRUN_OPEN_SIGNUP=1`), spending lands in an append-only per-account
+ledger (`FOLDRUN_BILLING=1` makes an empty balance refuse new runs), and a
+`notify:` block in AGENTS.md webhooks you when a run fails or waits for
+approval.
+
+Teams: an account holds many users, joined by 7-day invite links minted in
+Settings. Webhook URLs rotate per-hook (generation counters — nothing
+secret stored) and every delivery, refused ones included, lands in a log.
+Card top-ups are two Stripe REST calls behind `STRIPE_SECRET_KEY`, writing
+the same ledger entry the manual API does.
+
+With `FOLDRUN_RUN_ISOLATION=container` (one box) or `=k8s` (cluster —
+native run pods, gVisor by RuntimeClass, egress-limited by NetworkPolicy)
+every step runs in a hardened throwaway sandbox: workspace copied in,
+events streamed out, changes filtered back so `knowledge/`, secrets and
+run history physically cannot come back modified. The CLI keeps in-process
+runs — on a laptop there is nothing to protect the server process from.
+
+Connections cover how services actually hand out credentials: API keys,
+API with base URL + headers, SSH (key or password — materialised as a
+ready-to-run wrapper, `"$NAME" 'uptime'`), browser OAuth with your own
+client, OAuth client-credentials, service accounts (RS256 JWT), and file
+secrets (0600). Values are encrypted at rest and never reach the model.
+
+A built-in tools gallery ships platform-maintained scripts — first entry:
+a headless browser (`fetch_rendered`) for pages that render with
+JavaScript. Assigning one copies it into your account library or a
+workspace; agents still opt in explicitly in their own markdown.
+
+Known gaps: one platform replica per data directory (the web/worker role
+split needs RWX storage), and the dashboard's run lists re-read run files
+per request (fine to thousands of runs).
+
+Apache-2.0.

package/dist/index.d.ts

@@ -0,0 +1,32 @@
+export * from "./src/paths.ts";
+export * from "./src/store.ts";
+export * from "./src/starter.ts";
+export * from "./src/runner.ts";
+export * from "./src/okf.ts";
+export * from "./src/evals.ts";
+export * from "./src/flow-lint.ts";
+export * from "./src/catalog.ts";
+export * from "./src/model-probe.ts";
+export * from "./src/providers.ts";
+export * from "./src/translator.ts";
+export * from "./src/arrange.ts";
+export * from "./src/completions.ts";
+export * from "./src/confine.ts";
+export * from "./src/platform.ts";
+export * from "./src/library.ts";
+export * from "./src/tool-programs.ts";
+export * from "./src/linkable.ts";
+export * from "./src/refs.ts";
+export * from "./src/tool-names.ts";
+export * from "./src/history.ts";
+export * from "./src/gitrepo.ts";
+export * from "./src/storage.ts";
+export * from "./src/secrets.ts";
+export * from "./src/oauth-presets.ts";
+export * from "./src/secret-files.ts";
+export * from "./src/notify.ts";
+export * from "./src/webhook.ts";
+export * from "./src/approvals.ts";
+export * from "./src/deploy.ts";
+export * from "./src/tar.ts";
+export * from "./src/git.ts";

package/dist/index.js

@@ -0,0 +1,43 @@
+// @foldrun/core — the open-source runtime.
+//
+// Everything needed to read a workspace of markdown files and run the agents
+// in it. No server, no database, no account: point it at a folder.
+//
+// The hosted platform imports these same modules. That is deliberate — if the
+// open version were a reduced copy it would rot, and self-hosting would feel
+// like a downgrade instead of a choice. What the platform adds — a queue and
+// its worker, metering and billing, pods on a cluster, per-account keys in a
+// database, previews, share links, tenancy — lives in its own private package
+// and plugs in through platform.ts. Nothing here imports it.
+export * from "./src/paths.js";
+export * from "./src/store.js";
+export * from "./src/starter.js";
+export * from "./src/runner.js";
+export * from "./src/okf.js";
+export * from "./src/evals.js";
+export * from "./src/flow-lint.js";
+export * from "./src/catalog.js";
+export * from "./src/model-probe.js";
+export * from "./src/providers.js";
+export * from "./src/translator.js";
+export * from "./src/arrange.js";
+export * from "./src/completions.js";
+export * from "./src/confine.js";
+export * from "./src/platform.js";
+export * from "./src/library.js";
+export * from "./src/tool-programs.js";
+export * from "./src/linkable.js";
+export * from "./src/refs.js";
+export * from "./src/tool-names.js";
+export * from "./src/history.js";
+export * from "./src/gitrepo.js";
+export * from "./src/storage.js";
+export * from "./src/secrets.js";
+export * from "./src/oauth-presets.js";
+export * from "./src/secret-files.js";
+export * from "./src/notify.js";
+export * from "./src/webhook.js";
+export * from "./src/approvals.js";
+export * from "./src/deploy.js";
+export * from "./src/tar.js";
+export * from "./src/git.js";

package/dist/src/agent-tools.d.ts

@@ -0,0 +1,31 @@
+import { createSdkMcpServer } from "@anthropic-ai/claude-agent-sdk";
+import { type Effort } from "./store.ts";
+export interface ConsultSpec {
+    name: string;
+    systemPrompt: string;
+    model: string;
+    /** A colleague answers at its own declared effort, not the caller's — the
+     *  point of consulting one is that it is configured differently. */
+    effort: Effort | null;
+}
+/**
+ * Read the consultable colleagues' personas, host-side. Names that don't
+ * resolve to an agent are reported, not silently dropped.
+ */
+export declare function gatherConsults(workspaceRoot: string, names: unknown): {
+    consults: ConsultSpec[];
+    missing: string[];
+};
+export interface ConsultToolResult {
+    /** Passed to the SDK as an in-process MCP server (the agent just sees tools). */
+    server: ReturnType<typeof createSdkMcpServer> | null;
+    toolNames: string[];
+    /** Model spend by the consults so far — the caller adds it to its step. */
+    drainCost: () => number;
+}
+/**
+ * The MCP server carrying one consult_<name> tool per colleague. Works in
+ * both homes — the server process and the runner container — because it
+ * takes values, not stores.
+ */
+export declare function buildConsultTools(consults: ConsultSpec[], env: Record<string, string | undefined>, emit: (type: "info" | "error", text: string) => void): ConsultToolResult;

package/dist/src/agent-tools.js

@@ -0,0 +1,99 @@
+// Agent-as-tool: consult a colleague without ending your turn.
+//
+//   agents: [researcher]        # in agent.md frontmatter
+//
+// gives the agent one tool per named colleague — consult_researcher(question)
+// — that runs that agent's persona as a one-shot, toolless model call and
+// returns its answer inline. "Toolless" is the design, not a shortcut: a
+// consult is asking a specialist what they think, and a consultant who could
+// edit files or call APIs mid-question would be the supervisor pattern the
+// spec rejects, wearing a different hat. Depth is structurally one — the
+// callee is built without an agents server of its own.
+//
+// The flow file still owns the orchestration: who may be consulted is
+// declared per agent, cost lands on the consulting step, and nothing about
+// what runs next is decided by a model.
+import fs from "node:fs";
+import os from "node:os";
+import path from "node:path";
+import matter from "gray-matter";
+import { z } from "zod";
+import { createSdkMcpServer, tool } from "@anthropic-ai/claude-agent-sdk";
+import { resolveModel, resolveEffort } from "./store.js";
+import { executeStep } from "./step-exec.js";
+import { refNames } from "./refs.js";
+/**
+ * Read the consultable colleagues' personas, host-side. Names that don't
+ * resolve to an agent are reported, not silently dropped.
+ */
+export function gatherConsults(workspaceRoot, names) {
+    const list = refNames(names);
+    const consults = [];
+    const missing = [];
+    for (const name of list) {
+        const file = path.join(workspaceRoot, "agents", name, "agent.md");
+        if (!/^[a-z0-9]+(-[a-z0-9]+)*$/.test(name) || !fs.existsSync(file)) {
+            missing.push(name);
+            continue;
+        }
+        const parsed = matter(fs.readFileSync(file, "utf8"));
+        consults.push({
+            name,
+            systemPrompt: `${parsed.content.trim()}\n\n` +
+                `You are being consulted by another agent mid-task. Answer the question ` +
+                `directly and completely in your reply — you have no tools and no files; ` +
+                `everything you know is in this prompt and the question.`,
+            model: resolveModel(parsed.data.model),
+            effort: resolveEffort(parsed.data.effort),
+        });
+    }
+    return { consults, missing };
+}
+/**
+ * The MCP server carrying one consult_<name> tool per colleague. Works in
+ * both homes — the server process and the runner container — because it
+ * takes values, not stores.
+ */
+export function buildConsultTools(consults, env, emit) {
+    if (consults.length === 0)
+        return { server: null, toolNames: [], drainCost: () => 0 };
+    let cost = 0;
+    const tools = consults.map((c) => tool(`consult_${c.name.replaceAll("-", "_")}`, `Ask ${c.name} — a colleague agent — one question and get their answer inline. ` +
+        `They see only your question, not your files or conversation; include everything they need in it.`, { question: z.string().describe("The complete, self-contained question") }, async (args) => {
+        const started = Date.now();
+        // Toolless and homeless on purpose: the consult reads and writes
+        // nothing — cwd is a throwaway so even a confused model call has no
+        // tree to touch (and no tools to touch it with).
+        const scratch = fs.mkdtempSync(path.join(os.tmpdir(), "foldrun-consult-"));
+        try {
+            const outcome = await executeStep({
+                agentDir: scratch,
+                workspaceRoot: scratch,
+                libraryRoot: scratch,
+                prompt: args.question,
+                model: c.model,
+                effort: c.effort,
+                systemPrompt: c.systemPrompt,
+                allowed: [],
+                mcpNames: [],
+                mcpServers: {},
+                env,
+                emit: () => { }, // the consult's inner monologue stays its own
+            });
+            cost += outcome.costUsd ?? 0;
+            emit("info", `consult ${c.name} → ${outcome.status} ($${(outcome.costUsd ?? 0).toFixed(4)}, ${Date.now() - started}ms)`);
+            return {
+                content: [{ type: "text", text: outcome.result ?? "(no answer)" }],
+                isError: outcome.status === "failed",
+            };
+        }
+        finally {
+            fs.rmSync(scratch, { recursive: true, force: true });
+        }
+    }));
+    return {
+        server: createSdkMcpServer({ name: "foldrun_agents", version: "1.0.0", tools }),
+        toolNames: consults.map((c) => `mcp__foldrun_agents__consult_${c.name.replaceAll("-", "_")}`),
+        drainCost: () => cost,
+    };
+}

package/dist/src/agents-md.d.ts

@@ -0,0 +1,9 @@
+/** The frontmatter of a directory's AGENTS.md (or project.md), or {}. */
+export declare function readAgentsMdKeys(dir: string): Record<string, unknown>;
+/** The text of `content` with each key in `patch` replaced (or removed for
+ *  null), everything else byte for byte as it was. A file with no
+ *  frontmatter gets one. */
+export declare function patchFrontmatter(content: string, patch: Record<string, unknown | null>): string;
+/** Apply a frontmatter patch to a directory's AGENTS.md, creating the file
+ *  when the directory has none. Returns the new content. */
+export declare function setAgentsMdKeys(dir: string, patch: Record<string, unknown | null>): string;