@fungi.computer/oyster 0.52.2 → 0.53.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -7,8 +7,8 @@ export declare const platformSkillFiles: readonly [{
7
7
  readonly content: "---\nname: debug-fungi\ndescription:\n Diagnose a tool call that failed, was refused or returned something wrong, a\n Computer command that did not succeed, or a missing Home. Use when a call\n errors more than once, a result looks wrong, or a tool you expect is not\n there.\n---\n\n# Debug Fungi\n\nWhen a call does not work, find out why before you call it again.\n\n1. Discover first. Inside `execute`, `forage.search` finds operations by one\n short keyword, `forage.list` pages through all of them, and\n `forage.describe({ path })` shows the input of one. Describe an operation\n before you call it.\n2. Call an operation by its exact dotted path, for example\n `await env.computers.<name>.exec({ command: \"pwd\" })`. A bare path such as\n `computers.<name>.exec` is not defined.\n3. Each `execute` call starts a fresh sandbox. Nothing you defined survives to\n the next call, so redefine helpers or save state to a file.\n4. Before you treat a shell or process result as success, check `status`,\n `exitCode` and `stderr`.\n\n`REFERENCE.md` in this folder lists the limits that most often explain a\nfailure, and what a refusal, an approval wait and a missing Home mean.\n";
8
8
  }, {
9
9
  readonly path: "fungible-computing/SKILL.md";
10
- readonly content: "---\nname: fungible-computing\ndescription:\n Change how you work on this Agent's Computer. Edit your standing instructions\n and voice, add a skill of your own, or replace a built-in skill. Use when\n asked to remember a rule for every conversation, change your tone, or teach\n yourself a repeatable task.\n---\n\n# Fungible computing\n\nYour standing instructions and your skills are files on a Computer. You and your\nowner can both change them.\n\n## Instructions and voice\n\n- `AGENTS.md` on Home holds standing instructions. `SYSTEM.md` on Home holds\n your voice. Both are read at the start of each run, so an edit applies from\n the next run.\n- Together the two files may hold 32,000 bytes. A file over the limit is not\n loaded.\n- Follow them unless they conflict with the instructions the host gave you\n first. They never grant a tool, an approval or access.\n- Your Home prompt section names where they are; read and edit them there.\n- Only a person changes Home, with `/home <name>`. Ask them when no Home is\n available.\n\n## Skills\n\n- A skill is a folder holding a `SKILL.md`. Put your own at\n `.agents/skills/<name>/SKILL.md` on a Computer.\n `.fungi/skills/<name>/SKILL.md` works too and is searched first.\n- `SKILL.md` starts with YAML frontmatter that has a `description`. The `name`\n should match the folder and use lowercase letters, digits and single hyphens,\n at most 64 characters. The prompt shows at most 512 characters of the\n description.\n- Load a skill inside `execute` with\n `return await skill.load({ name: \"skill-name\" });`. Add `file`, relative to\n the returned `baseDirectory`, for a supporting file in the folder.\n- A person can list every skill, and the file each came from, with `/skills`.\n\n## Replace a built-in skill\n\nBuilt-in skills ship with Fungi and are not files on a Computer. To replace one,\nmake a skill with the same name on a Computer, for example\n`.agents/skills/debug-fungi/SKILL.md`. The first skill found with a name wins,\nand a Computer's skills are searched before the built-in ones. Yours is listed,\nand `skill.load` returns yours. Discovery records that yours won.\n";
10
+ readonly content: "---\nname: fungible-computing\ndescription:\n Change how you work on this Agent's Computer. Edit your standing instructions\n and voice, add a skill of your own, or replace a built-in skill. Use when\n asked to remember a rule for every conversation, change your tone, or teach\n yourself a repeatable task, or install a missing Computer toolchain or agent\n CLI.\n---\n\n# Fungible computing\n\nYour standing instructions and your skills are files on a Computer. You and your\nowner can both change them.\n\n## Computer tools\n\nOn a hosted Fungi Computer, if go, rust or an agent CLI is missing, run\n`fungi-tools install <tool>` through that Computer's exec operation. Select\n`go`, `rust` (for rustc and cargo), `claude`, `codex`, `opencode` or `pi`. Go\nand Rust persist in that Computer's home. Agent CLIs live in a cache that is\ncleared when the Computer sleeps; after a wake their first use reinstalls the\nsame pinned version and prints `installing <tool> (one-time after wake)`. A\nfailed install is an error to report, not a reason to fetch an unpinned\ninstaller. This command does not supply provider keys or sign the CLI in.\nMember-attached machines use their own installed tools.\n\n## Instructions and voice\n\n- `AGENTS.md` on Home holds standing instructions. `SYSTEM.md` on Home holds\n your voice. Both are read at the start of each run, so an edit applies from\n the next run.\n- Together the two files may hold 32,000 bytes. A file over the limit is not\n loaded.\n- Follow them unless they conflict with the instructions the host gave you\n first. They never grant a tool, an approval or access.\n- Your Home prompt section names where they are; read and edit them there.\n- Only a person changes Home, with `/home <name>`. Ask them when no Home is\n available.\n\n## Skills\n\n- A skill is a folder holding a `SKILL.md`. Put your own at\n `.agents/skills/<name>/SKILL.md` on a Computer.\n `.fungi/skills/<name>/SKILL.md` works too and is searched first.\n- `SKILL.md` starts with YAML frontmatter that has a `description`. The `name`\n should match the folder and use lowercase letters, digits and single hyphens,\n at most 64 characters. The prompt shows at most 512 characters of the\n description.\n- Load a skill inside `execute` with\n `return await skill.load({ name: \"skill-name\" });`. Add `file`, relative to\n the returned `baseDirectory`, for a supporting file in the folder.\n- A person can list every skill, and the file each came from, with `/skills`.\n\n## Replace a built-in skill\n\nBuilt-in skills ship with Fungi and are not files on a Computer. To replace one,\nmake a skill with the same name on a Computer, for example\n`.agents/skills/debug-fungi/SKILL.md`. The first skill found with a name wins,\nand a Computer's skills are searched before the built-in ones. Yours is listed,\nand `skill.load` returns yours. Discovery records that yours won.\n";
11
11
  }, {
12
12
  readonly path: "setup-fungi/SKILL.md";
13
- readonly content: "---\nname: setup-fungi\ndescription:\n Set yourself up for a new person in your first conversation, or when asked to\n set up Fungi or a project. Interview briefly, then do the setup yourself with\n their approval.\n---\n\n# Set up Fungi for your person\n\n## Goal\n\nWithin a few minutes, be set up for what they actually want: your instructions\nwritten, their project read, and, only if they want it, one App or one schedule.\nFinish with one useful result, not a tour.\n\n## Rules\n\n- Plain words. Say Agent, Computer, App, skill, schedule, Team or Home only at\n the moment you use that thing, with a one-sentence explanation.\n- One new concept per message. Name what you did, never list features.\n- Ask at most 3 questions in total. Use `question.ask` with options, the\n recommended one first. Free text is always allowed. Batch questions.\n- Propose, then act. Before writing files, cloning, scheduling or opening an\n App, show the `plan` checklist and ask \"Do it?\" with `question.ask` (options\n \"Do it\", \"Change something\", \"Skip\"). Reading needs no approval.\n- Document only what you observe. Every command, path and fact comes from a file\n you read or a command you ran.\n- Suggest only these Apps: Grove, Prints, Inkcap, Bazaar.\n- Skip any step whose tool this host does not give you, and carry on.\n- When they want to get on with a task, do the task and set up afterwards.\n- Keep prices and credit amounts out of your messages. Only the `setup.finish`\n line in step 5 mentions continuing.\n\n## Steps\n\n1. Understand. Open with one line that acknowledges what they just said. Then\n learn, from that message and at most 2 follow-up questions: what they want\n Fungi for; whether there is a project (repo, folder, site, docs); anything\n that repeats (daily, weekly). Done when you can state their goal in a\n sentence.\n2. Plan. Write a `plan` checklist of at most 4 items, each one concrete thing\n you will do. Ask \"Do it?\". Done when they answer.\n3. Do, item by item, ticking the plan.\n - Instructions. Edit Home `AGENTS.md` in place: fill its \"About my person\"\n section (rename it \"About <their name>\") with their goal, the preferences\n they stated and how they want updates. Follow its \"Keeping this file up to\n date\" section from then on. Every line answers \"would I get this wrong\n without it?\". Then introduce instructions in one sentence: \"I saved this in\n my instructions, so I'll remember it in every conversation. You can read or\n edit them from my menu → Instructions.\"\n - Project, if any. Get it onto your Computer.\n - A public repo: `git clone` into `/workspace/<repo>`.\n - A private GitHub repo, when the `gitTeam` tool is present: first offer\n \"Connect GitHub\" as a link to the GitHub connector in Team settings. Once\n the repo is granted, run `gitTeam.clone` into `/workspace/<repo>`.\n - Files: ask them to drop the files in Inkcap.\n\n Then crawl it: list the top level; read the README, manifests and\n lockfiles; the build, test, lint and CI config; existing rule files\n (`AGENTS.md`, `CLAUDE.md`, `.cursor/rules`, `.cursorrules`,\n `.github/copilot-instructions.md`); then a few representative source files.\n Write or improve the project's own `AGENTS.md` with exact commands\n (including one test), entry points, boundaries and gotchas. Show the 3 most\n useful lines you learned. Introduce your Computer in one sentence: \"I have\n my own Computer, a private machine where I keep files and run things.\"\n\n - Repeating work, if any. Propose one schedule with a time and time zone.\n Create it from a new conversation named for the job.\n - An App, only when a stated need matches one. Offer its App link.\n4. First result. Do one small real task toward their goal, now. Done when they\n can see its output.\n5. Finish.\n - Say in two lines what you set up and where to change it.\n - Delete the \"First conversation\" section from Home `AGENTS.md`.\n - When the `setup.finish` tool is available, say one more line: \"That's you\n set up. To keep going with me, start Pro, or link your wallet if you're a\n holder.\" Then call `setup.finish()` once.\n - When the `setup.finish` tool is absent, stop after the two-line summary:\n that host has no money step, so say nothing about Pro or wallets and call\n nothing.\n\n## Credit\n\n- When the `setup.finish` description says less than $0.15 of credit remains,\n finish the step in hand, then do step 5 without starting a crawl.\n- Reach step 5 only after the first useful result. A hand-off before that leaves\n the person with nothing.\n";
13
+ readonly content: "---\nname: setup-fungi\ndescription:\n Set yourself up for a new person in your first conversation, or when asked to\n set up Fungi or a project. Interview briefly, then do the setup yourself with\n their approval.\n---\n\n# Set up Fungi for your person\n\n## Goal\n\nWithin a few minutes, be set up for what they actually want: your instructions\nwritten, their project read, and, only if they want it, one App or one schedule.\nFinish with one useful result, not a tour.\n\n## Rules\n\n- Plain words. Say Agent, Computer, App, skill, schedule, Team or Home only at\n the moment you use that thing, with a one-sentence explanation.\n- One new concept per message. Name what you did, never list features.\n- Ask at most 3 questions in total. Use `question.ask` with options, the\n recommended one first. Free text is always allowed. Batch questions.\n- Propose, then act. Before writing files, cloning, scheduling or opening an\n App, show the `plan` checklist and ask \"Do it?\" with `question.ask` (options\n \"Do it\", \"Change something\", \"Skip\"). Reading needs no approval.\n- Document only what you observe. Every command, path and fact comes from a file\n you read or a command you ran.\n- Suggest only these Apps: Grove, Prints, Inkcap, Bazaar.\n- Skip any step whose tool this host does not give you, and carry on.\n- When they want to get on with a task, do the task and set up afterwards.\n- Keep prices and credit amounts out of your messages. Only the `setup.finish`\n line in step 5 mentions continuing.\n\n## Steps\n\n1. Understand. Open with one line that acknowledges what they just said. Then\n learn, from that message and at most 2 follow-up questions: what they want\n Fungi for; whether there is a project (repo, folder, site, docs); anything\n that repeats (daily, weekly). Done when you can state their goal in a\n sentence.\n2. Plan. Write a `plan` checklist of at most 4 items, each one concrete thing\n you will do. Ask \"Do it?\". Done when they answer.\n3. Do, item by item, ticking the plan.\n - Instructions. Edit Home `AGENTS.md` in place: fill its \"About my person\"\n section (rename it \"About <their name>\") with their goal, the preferences\n they stated and how they want updates. Follow its \"Keeping this file up to\n date\" section from then on. Every line answers \"would I get this wrong\n without it?\". Then introduce instructions in one sentence: \"I saved this in\n my instructions, so I'll remember it in every conversation. You can read or\n edit them from my menu → Instructions.\"\n - Project, if any. Get it onto your Computer.\n - A public repo: `git clone` into `/workspace/<repo>`.\n - A private GitHub repo, when the `gitTeam` tool is present: first offer\n \"Connect GitHub\" as a link to the GitHub connector in Team settings. Once\n the repo is granted, run `gitTeam.clone` into `/workspace/<repo>`.\n - Files: ask them to drop the files in Inkcap.\n\n Then crawl it: list the top level; read the README, manifests and\n lockfiles; the build, test, lint and CI config; existing rule files\n (`AGENTS.md`, `CLAUDE.md`, `.cursor/rules`, `.cursorrules`,\n `.github/copilot-instructions.md`); then a few representative source files.\n Write or improve the project's own `AGENTS.md` with exact commands\n (including one test), entry points, boundaries and gotchas. Show the 3 most\n useful lines you learned. Introduce your Computer in one sentence: \"I have\n my own Computer, a private machine where I keep files and run things.\"\n\n - Repeating work, if any. Propose one schedule with a time and time zone.\n Create it from a new conversation named for the job.\n - An App, only when a stated need matches one. Offer its App link.\n4. First result. Do one small real task toward their goal, now. Done when they\n can see its output.\n5. Finish.\n - Say in two lines what you set up and where to change it.\n - Offer a name, once. Ask with `question.ask`: \"Keep Shiitake\" first, then\n two names you suggest that fit their goal, and free text always allowed.\n This offer does not count against the 3 questions. Call `self.rename` with\n the name only when they pick a new name, and say in one line that you are\n now called that. When the `self` tool is absent, skip it.\n - Offer \"Add to your dashboard\" for what you set up. Call `widgets.available`\n and offer only the widgets that match what you did: Grove Inbox, Inkcap\n Recent Files, Prints Recent Outputs. Ask once with `question.ask`, one\n option per widget plus \"Not now\". This offer does not count against the 3\n questions. Add a widget only when the person taps it: call `layout.get`,\n then `layout.place` with its `surfaceId`, `gillId`, a size the widget\n lists, `scope` \"member\" and `basedOn` the revision `layout.get` returned.\n Pass `params` only for the keys the widget lists, with values you know, and\n skip a widget whose required parameter you cannot fill. Never add one\n yourself. When those methods are absent, skip it.\n - Delete the \"First conversation\" section from Home `AGENTS.md`.\n - When the `setup.finish` tool is available, say one more line: \"That's you\n set up. To keep going with me, start Pro, or link your wallet if you're a\n holder.\" Then call `setup.finish()` once.\n - When the `setup.finish` tool is absent, stop after the two-line summary:\n that host has no money step, so say nothing about Pro or wallets and call\n nothing.\n\n## Credit\n\n- When the `setup.finish` description says less than $0.15 of credit remains,\n finish the step in hand, then do step 5 without starting a crawl.\n- Reach step 5 only after the first useful result. A hand-off before that leaves\n the person with nothing.\n";
14
14
  }];
@@ -11,10 +11,10 @@ export const platformSkillFiles = [
11
11
  },
12
12
  {
13
13
  path: "fungible-computing/SKILL.md",
14
- content: "---\nname: fungible-computing\ndescription:\n Change how you work on this Agent's Computer. Edit your standing instructions\n and voice, add a skill of your own, or replace a built-in skill. Use when\n asked to remember a rule for every conversation, change your tone, or teach\n yourself a repeatable task.\n---\n\n# Fungible computing\n\nYour standing instructions and your skills are files on a Computer. You and your\nowner can both change them.\n\n## Instructions and voice\n\n- `AGENTS.md` on Home holds standing instructions. `SYSTEM.md` on Home holds\n your voice. Both are read at the start of each run, so an edit applies from\n the next run.\n- Together the two files may hold 32,000 bytes. A file over the limit is not\n loaded.\n- Follow them unless they conflict with the instructions the host gave you\n first. They never grant a tool, an approval or access.\n- Your Home prompt section names where they are; read and edit them there.\n- Only a person changes Home, with `/home <name>`. Ask them when no Home is\n available.\n\n## Skills\n\n- A skill is a folder holding a `SKILL.md`. Put your own at\n `.agents/skills/<name>/SKILL.md` on a Computer.\n `.fungi/skills/<name>/SKILL.md` works too and is searched first.\n- `SKILL.md` starts with YAML frontmatter that has a `description`. The `name`\n should match the folder and use lowercase letters, digits and single hyphens,\n at most 64 characters. The prompt shows at most 512 characters of the\n description.\n- Load a skill inside `execute` with\n `return await skill.load({ name: \"skill-name\" });`. Add `file`, relative to\n the returned `baseDirectory`, for a supporting file in the folder.\n- A person can list every skill, and the file each came from, with `/skills`.\n\n## Replace a built-in skill\n\nBuilt-in skills ship with Fungi and are not files on a Computer. To replace one,\nmake a skill with the same name on a Computer, for example\n`.agents/skills/debug-fungi/SKILL.md`. The first skill found with a name wins,\nand a Computer's skills are searched before the built-in ones. Yours is listed,\nand `skill.load` returns yours. Discovery records that yours won.\n",
14
+ content: "---\nname: fungible-computing\ndescription:\n Change how you work on this Agent's Computer. Edit your standing instructions\n and voice, add a skill of your own, or replace a built-in skill. Use when\n asked to remember a rule for every conversation, change your tone, or teach\n yourself a repeatable task, or install a missing Computer toolchain or agent\n CLI.\n---\n\n# Fungible computing\n\nYour standing instructions and your skills are files on a Computer. You and your\nowner can both change them.\n\n## Computer tools\n\nOn a hosted Fungi Computer, if go, rust or an agent CLI is missing, run\n`fungi-tools install <tool>` through that Computer's exec operation. Select\n`go`, `rust` (for rustc and cargo), `claude`, `codex`, `opencode` or `pi`. Go\nand Rust persist in that Computer's home. Agent CLIs live in a cache that is\ncleared when the Computer sleeps; after a wake their first use reinstalls the\nsame pinned version and prints `installing <tool> (one-time after wake)`. A\nfailed install is an error to report, not a reason to fetch an unpinned\ninstaller. This command does not supply provider keys or sign the CLI in.\nMember-attached machines use their own installed tools.\n\n## Instructions and voice\n\n- `AGENTS.md` on Home holds standing instructions. `SYSTEM.md` on Home holds\n your voice. Both are read at the start of each run, so an edit applies from\n the next run.\n- Together the two files may hold 32,000 bytes. A file over the limit is not\n loaded.\n- Follow them unless they conflict with the instructions the host gave you\n first. They never grant a tool, an approval or access.\n- Your Home prompt section names where they are; read and edit them there.\n- Only a person changes Home, with `/home <name>`. Ask them when no Home is\n available.\n\n## Skills\n\n- A skill is a folder holding a `SKILL.md`. Put your own at\n `.agents/skills/<name>/SKILL.md` on a Computer.\n `.fungi/skills/<name>/SKILL.md` works too and is searched first.\n- `SKILL.md` starts with YAML frontmatter that has a `description`. The `name`\n should match the folder and use lowercase letters, digits and single hyphens,\n at most 64 characters. The prompt shows at most 512 characters of the\n description.\n- Load a skill inside `execute` with\n `return await skill.load({ name: \"skill-name\" });`. Add `file`, relative to\n the returned `baseDirectory`, for a supporting file in the folder.\n- A person can list every skill, and the file each came from, with `/skills`.\n\n## Replace a built-in skill\n\nBuilt-in skills ship with Fungi and are not files on a Computer. To replace one,\nmake a skill with the same name on a Computer, for example\n`.agents/skills/debug-fungi/SKILL.md`. The first skill found with a name wins,\nand a Computer's skills are searched before the built-in ones. Yours is listed,\nand `skill.load` returns yours. Discovery records that yours won.\n",
15
15
  },
16
16
  {
17
17
  path: "setup-fungi/SKILL.md",
18
- content: '---\nname: setup-fungi\ndescription:\n Set yourself up for a new person in your first conversation, or when asked to\n set up Fungi or a project. Interview briefly, then do the setup yourself with\n their approval.\n---\n\n# Set up Fungi for your person\n\n## Goal\n\nWithin a few minutes, be set up for what they actually want: your instructions\nwritten, their project read, and, only if they want it, one App or one schedule.\nFinish with one useful result, not a tour.\n\n## Rules\n\n- Plain words. Say Agent, Computer, App, skill, schedule, Team or Home only at\n the moment you use that thing, with a one-sentence explanation.\n- One new concept per message. Name what you did, never list features.\n- Ask at most 3 questions in total. Use `question.ask` with options, the\n recommended one first. Free text is always allowed. Batch questions.\n- Propose, then act. Before writing files, cloning, scheduling or opening an\n App, show the `plan` checklist and ask "Do it?" with `question.ask` (options\n "Do it", "Change something", "Skip"). Reading needs no approval.\n- Document only what you observe. Every command, path and fact comes from a file\n you read or a command you ran.\n- Suggest only these Apps: Grove, Prints, Inkcap, Bazaar.\n- Skip any step whose tool this host does not give you, and carry on.\n- When they want to get on with a task, do the task and set up afterwards.\n- Keep prices and credit amounts out of your messages. Only the `setup.finish`\n line in step 5 mentions continuing.\n\n## Steps\n\n1. Understand. Open with one line that acknowledges what they just said. Then\n learn, from that message and at most 2 follow-up questions: what they want\n Fungi for; whether there is a project (repo, folder, site, docs); anything\n that repeats (daily, weekly). Done when you can state their goal in a\n sentence.\n2. Plan. Write a `plan` checklist of at most 4 items, each one concrete thing\n you will do. Ask "Do it?". Done when they answer.\n3. Do, item by item, ticking the plan.\n - Instructions. Edit Home `AGENTS.md` in place: fill its "About my person"\n section (rename it "About <their name>") with their goal, the preferences\n they stated and how they want updates. Follow its "Keeping this file up to\n date" section from then on. Every line answers "would I get this wrong\n without it?". Then introduce instructions in one sentence: "I saved this in\n my instructions, so I\'ll remember it in every conversation. You can read or\n edit them from my menu → Instructions."\n - Project, if any. Get it onto your Computer.\n - A public repo: `git clone` into `/workspace/<repo>`.\n - A private GitHub repo, when the `gitTeam` tool is present: first offer\n "Connect GitHub" as a link to the GitHub connector in Team settings. Once\n the repo is granted, run `gitTeam.clone` into `/workspace/<repo>`.\n - Files: ask them to drop the files in Inkcap.\n\n Then crawl it: list the top level; read the README, manifests and\n lockfiles; the build, test, lint and CI config; existing rule files\n (`AGENTS.md`, `CLAUDE.md`, `.cursor/rules`, `.cursorrules`,\n `.github/copilot-instructions.md`); then a few representative source files.\n Write or improve the project\'s own `AGENTS.md` with exact commands\n (including one test), entry points, boundaries and gotchas. Show the 3 most\n useful lines you learned. Introduce your Computer in one sentence: "I have\n my own Computer, a private machine where I keep files and run things."\n\n - Repeating work, if any. Propose one schedule with a time and time zone.\n Create it from a new conversation named for the job.\n - An App, only when a stated need matches one. Offer its App link.\n4. First result. Do one small real task toward their goal, now. Done when they\n can see its output.\n5. Finish.\n - Say in two lines what you set up and where to change it.\n - Delete the "First conversation" section from Home `AGENTS.md`.\n - When the `setup.finish` tool is available, say one more line: "That\'s you\n set up. To keep going with me, start Pro, or link your wallet if you\'re a\n holder." Then call `setup.finish()` once.\n - When the `setup.finish` tool is absent, stop after the two-line summary:\n that host has no money step, so say nothing about Pro or wallets and call\n nothing.\n\n## Credit\n\n- When the `setup.finish` description says less than $0.15 of credit remains,\n finish the step in hand, then do step 5 without starting a crawl.\n- Reach step 5 only after the first useful result. A hand-off before that leaves\n the person with nothing.\n',
18
+ content: '---\nname: setup-fungi\ndescription:\n Set yourself up for a new person in your first conversation, or when asked to\n set up Fungi or a project. Interview briefly, then do the setup yourself with\n their approval.\n---\n\n# Set up Fungi for your person\n\n## Goal\n\nWithin a few minutes, be set up for what they actually want: your instructions\nwritten, their project read, and, only if they want it, one App or one schedule.\nFinish with one useful result, not a tour.\n\n## Rules\n\n- Plain words. Say Agent, Computer, App, skill, schedule, Team or Home only at\n the moment you use that thing, with a one-sentence explanation.\n- One new concept per message. Name what you did, never list features.\n- Ask at most 3 questions in total. Use `question.ask` with options, the\n recommended one first. Free text is always allowed. Batch questions.\n- Propose, then act. Before writing files, cloning, scheduling or opening an\n App, show the `plan` checklist and ask "Do it?" with `question.ask` (options\n "Do it", "Change something", "Skip"). Reading needs no approval.\n- Document only what you observe. Every command, path and fact comes from a file\n you read or a command you ran.\n- Suggest only these Apps: Grove, Prints, Inkcap, Bazaar.\n- Skip any step whose tool this host does not give you, and carry on.\n- When they want to get on with a task, do the task and set up afterwards.\n- Keep prices and credit amounts out of your messages. Only the `setup.finish`\n line in step 5 mentions continuing.\n\n## Steps\n\n1. Understand. Open with one line that acknowledges what they just said. Then\n learn, from that message and at most 2 follow-up questions: what they want\n Fungi for; whether there is a project (repo, folder, site, docs); anything\n that repeats (daily, weekly). Done when you can state their goal in a\n sentence.\n2. Plan. Write a `plan` checklist of at most 4 items, each one concrete thing\n you will do. Ask "Do it?". Done when they answer.\n3. Do, item by item, ticking the plan.\n - Instructions. Edit Home `AGENTS.md` in place: fill its "About my person"\n section (rename it "About <their name>") with their goal, the preferences\n they stated and how they want updates. Follow its "Keeping this file up to\n date" section from then on. Every line answers "would I get this wrong\n without it?". Then introduce instructions in one sentence: "I saved this in\n my instructions, so I\'ll remember it in every conversation. You can read or\n edit them from my menu → Instructions."\n - Project, if any. Get it onto your Computer.\n - A public repo: `git clone` into `/workspace/<repo>`.\n - A private GitHub repo, when the `gitTeam` tool is present: first offer\n "Connect GitHub" as a link to the GitHub connector in Team settings. Once\n the repo is granted, run `gitTeam.clone` into `/workspace/<repo>`.\n - Files: ask them to drop the files in Inkcap.\n\n Then crawl it: list the top level; read the README, manifests and\n lockfiles; the build, test, lint and CI config; existing rule files\n (`AGENTS.md`, `CLAUDE.md`, `.cursor/rules`, `.cursorrules`,\n `.github/copilot-instructions.md`); then a few representative source files.\n Write or improve the project\'s own `AGENTS.md` with exact commands\n (including one test), entry points, boundaries and gotchas. Show the 3 most\n useful lines you learned. Introduce your Computer in one sentence: "I have\n my own Computer, a private machine where I keep files and run things."\n\n - Repeating work, if any. Propose one schedule with a time and time zone.\n Create it from a new conversation named for the job.\n - An App, only when a stated need matches one. Offer its App link.\n4. First result. Do one small real task toward their goal, now. Done when they\n can see its output.\n5. Finish.\n - Say in two lines what you set up and where to change it.\n - Offer a name, once. Ask with `question.ask`: "Keep Shiitake" first, then\n two names you suggest that fit their goal, and free text always allowed.\n This offer does not count against the 3 questions. Call `self.rename` with\n the name only when they pick a new name, and say in one line that you are\n now called that. When the `self` tool is absent, skip it.\n - Offer "Add to your dashboard" for what you set up. Call `widgets.available`\n and offer only the widgets that match what you did: Grove Inbox, Inkcap\n Recent Files, Prints Recent Outputs. Ask once with `question.ask`, one\n option per widget plus "Not now". This offer does not count against the 3\n questions. Add a widget only when the person taps it: call `layout.get`,\n then `layout.place` with its `surfaceId`, `gillId`, a size the widget\n lists, `scope` "member" and `basedOn` the revision `layout.get` returned.\n Pass `params` only for the keys the widget lists, with values you know, and\n skip a widget whose required parameter you cannot fill. Never add one\n yourself. When those methods are absent, skip it.\n - Delete the "First conversation" section from Home `AGENTS.md`.\n - When the `setup.finish` tool is available, say one more line: "That\'s you\n set up. To keep going with me, start Pro, or link your wallet if you\'re a\n holder." Then call `setup.finish()` once.\n - When the `setup.finish` tool is absent, stop after the two-line summary:\n that host has no money step, so say nothing about Pro or wallets and call\n nothing.\n\n## Credit\n\n- When the `setup.finish` description says less than $0.15 of credit remains,\n finish the step in hand, then do step 5 without starting a crawl.\n- Reach step 5 only after the first useful result. A hand-off before that leaves\n the person with nothing.\n',
19
19
  },
20
20
  ];
@@ -1,10 +1,11 @@
1
1
  import { createComputerFilesPort } from "@fungi.computer/computer";
2
2
  import { checkComputerGrant, FleetGrantRefused, } from "@fungi.computer/computer/fleet";
3
- import { ComputerCommandTooLongError, computerCapabilities, computerValueSchema, parseComputerExecInput, } from "@fungi.computer/computer-contract";
3
+ import { ComputerCommandTooLongError, computerValueSchema, parseComputerExecInput, } from "@fungi.computer/computer-contract";
4
4
  import { CapabilityFailed, } from "@fungi.computer/mycelium";
5
5
  import { attachComputerInputSchema, detachComputerInputSchema, readAgentComputersInputSchema, } from "../agent-computers.js";
6
6
  import {} from "../host.js";
7
7
  import { owner, routes as routeTable } from "../authorization.js";
8
+ import { advertisedComputerCapabilities } from "./computer-capabilities.js";
8
9
  /** A save named a Computer this Agent is not attached to, or the directory refused it. */
9
10
  class BrowserSaveDenied extends Error {
10
11
  constructor(message) {
@@ -77,7 +78,7 @@ export function standaloneAgentComputerPorts(access, connection) {
77
78
  computer: {
78
79
  getCapabilities: (signal) => {
79
80
  signal.throwIfAborted();
80
- return Promise.resolve(computerValueSchema.parse(computerCapabilities()));
81
+ return Promise.resolve(advertisedComputerCapabilities());
81
82
  },
82
83
  call: async (capabilityId, input, context) => {
83
84
  context.signal.throwIfAborted();
@@ -723,8 +723,8 @@ export declare const agentFrameMethods: {
723
723
  readonly nodeId: string;
724
724
  readonly iteration: string;
725
725
  };
726
- readonly expiresAt: number;
727
726
  readonly kind: "workflow-review";
727
+ readonly expiresAt: number;
728
728
  readonly installationId: string;
729
729
  readonly workflowId: string | null;
730
730
  readonly state: "pending" | "timed_out" | "closed" | "delivered" | "answered";
@@ -817,8 +817,8 @@ export declare const agentFrameMethods: {
817
817
  };
818
818
  })[];
819
819
  readonly next: {
820
- readonly agentId: string;
821
820
  readonly kind: "almanac" | "loop";
821
+ readonly agentId: string;
822
822
  readonly after?: string | undefined;
823
823
  } | null;
824
824
  };
@@ -2220,6 +2220,13 @@ export class AgentDirectory extends DurableObject {
2220
2220
  "processStart",
2221
2221
  "processList",
2222
2222
  "processKill",
2223
+ "serviceDeclare",
2224
+ "serviceList",
2225
+ "serviceLogs",
2226
+ "serviceStop",
2227
+ "serviceStart",
2228
+ "serviceRestart",
2229
+ "serviceRemove",
2223
2230
  ],
2224
2231
  expiresAt: Date.now() + 60_000,
2225
2232
  provenance: { actor: oysterPrincipalId(owner), via: captured.agentId },
@@ -0,0 +1,5 @@
1
+ /**
2
+ * Every operation an Oyster Computer advertises: the native ones and the
3
+ * declared-service tools it serves. Static, so hosts describe them without a call.
4
+ */
5
+ export declare function advertisedComputerCapabilities(): import("zod").JSONType;
@@ -0,0 +1,11 @@
1
+ import { computerCapabilities, computerServiceCapabilities, computerValueSchema, } from "@fungi.computer/computer-contract";
2
+ /**
3
+ * Every operation an Oyster Computer advertises: the native ones and the
4
+ * declared-service tools it serves. Static, so hosts describe them without a call.
5
+ */
6
+ export function advertisedComputerCapabilities() {
7
+ return computerValueSchema.parse([
8
+ ...computerCapabilities(),
9
+ ...computerServiceCapabilities(),
10
+ ]);
11
+ }
@@ -6,7 +6,7 @@ import { type ComputerPorts } from "@fungi.computer/agar/computer";
6
6
  import { type PreviewSelector } from "./preview.js";
7
7
  import { type StandaloneTenancyEnv } from "./tenancy.js";
8
8
  import * as z from "zod";
9
- import { computerProcessSchema, computerToolResultSchema, readOutputSchema } from "@fungi.computer/computer-contract";
9
+ import { computerProcessSchema, computerServiceViewSchema, serviceListOutputSchema, serviceLogsOutputSchema, serviceRemoveOutputSchema, computerToolResultSchema, readOutputSchema } from "@fungi.computer/computer-contract";
10
10
  import { ComputerDO as NativeComputerDO, type AttachedBackend, type ComputerEnv, type ComputerFilesRpc, type VaultSecretGrant } from "@fungi.computer/computer";
11
11
  import { patchInputSchema, patchOutputSchema } from "@fungi.computer/knapsack/files-patch";
12
12
  import { listOutputSchema, writeOutputSchema, mkdirOutputSchema, moveOutputSchema, removeOutputSchema, computerPortsOutputSchema, computerPortOutputSchema, computerPortRemovalOutputSchema, processListOutputSchema, processKillOutputSchema, processLogsOutputSchema, processWaitOutputSchema, computerOperationResultSchema, type ComputerExecutionHostHooks, type ComputerValue } from "@fungi.computer/computer-contract";
@@ -44,7 +44,7 @@ export type StandaloneComputerResult = z.output<typeof listOutputSchema> | Reado
44
44
  truncated: boolean;
45
45
  }> | Readonly<{
46
46
  error: "conflict" | "no_runtime" | "not_found" | "invalid";
47
- }> | z.output<typeof writeOutputSchema> | z.output<typeof moveOutputSchema> | z.output<typeof removeOutputSchema> | z.output<typeof mkdirOutputSchema> | z.output<typeof computerPortsOutputSchema> | z.output<typeof computerPortOutputSchema> | z.output<typeof computerPortRemovalOutputSchema> | z.output<typeof processListOutputSchema> | z.output<typeof processKillOutputSchema> | z.output<typeof processLogsOutputSchema> | z.output<typeof processWaitOutputSchema> | z.output<typeof computerProcessSchema> | ComputerPorts["ports"][number] | z.output<typeof computerOperationResultSchema> | z.output<typeof readOutputSchema> | z.output<typeof computerToolResultSchema>;
47
+ }> | z.output<typeof writeOutputSchema> | z.output<typeof moveOutputSchema> | z.output<typeof removeOutputSchema> | z.output<typeof mkdirOutputSchema> | z.output<typeof computerPortsOutputSchema> | z.output<typeof computerPortOutputSchema> | z.output<typeof computerPortRemovalOutputSchema> | z.output<typeof processListOutputSchema> | z.output<typeof processKillOutputSchema> | z.output<typeof processLogsOutputSchema> | z.output<typeof processWaitOutputSchema> | z.output<typeof computerServiceViewSchema> | z.output<typeof serviceListOutputSchema> | z.output<typeof serviceLogsOutputSchema> | z.output<typeof serviceRemoveOutputSchema> | z.output<typeof computerProcessSchema> | ComputerPorts["ports"][number] | z.output<typeof computerOperationResultSchema> | z.output<typeof readOutputSchema> | z.output<typeof computerToolResultSchema>;
48
48
  /**
49
49
  * A port-preview listing, or the typed refusal the owner route presents with
50
50
  * {@link appMethodRefusalStatus}. A refusal never escapes as a 500.
@@ -10,10 +10,11 @@ import { verifyRelease } from "../host.js";
10
10
  import { r2ArtifactStore } from "../workers.js";
11
11
  import { createBuildJobLog } from "../build/job-log.js";
12
12
  import { createStandalonePreview, previewOrigins, previewSelectorSchema, PreviewRefused, } from "./preview.js";
13
+ import { advertisedComputerCapabilities } from "./computer-capabilities.js";
13
14
  import { standaloneTenancy } from "./tenancy.js";
14
15
  import { Base64 } from "effect/encoding";
15
16
  import * as z from "zod";
16
- import { ComputerPortConflictError, computerByteReadReplySchema, computerProcessSchema, installationProcessScope, processStartInputSchema, processStartToolInputSchema, computerCapabilities, computerToolResultSchema, readOutputSchema, } from "@fungi.computer/computer-contract";
17
+ import { ComputerPortConflictError, computerByteReadReplySchema, computerProcessSchema, installationProcessScope, processStartInputSchema, processStartToolInputSchema, computerServiceViewSchema, serviceListOutputSchema, serviceLogsOutputSchema, serviceRemoveOutputSchema, computerToolResultSchema, readOutputSchema, } from "@fungi.computer/computer-contract";
17
18
  import { ComputerDO as NativeComputerDO, ComputerOperationConflictError, ComputerBackendUnavailableError, isVaultExecutionContext, withVaultExecution, } from "@fungi.computer/computer";
18
19
  import { patchInputSchema, patchOutputSchema, } from "@fungi.computer/knapsack/files-patch";
19
20
  import { ComputerFileConflict, ComputerFileMoveError, ComputerFileRemoveError, computerExecutionRequestSchema, computerValueSchema, computerPortInputSchema, listInputSchema, listOutputSchema, readBytesInputSchema, writeInputSchema, replaceInputSchema, writeOutputSchema, mkdirOutputSchema, moveInputSchema, moveOutputSchema, removeOutputSchema, computerPortsOutputSchema, computerPortOutputSchema, computerPortRemovalOutputSchema, processListOutputSchema, processKillOutputSchema, processLogsInputSchema, processWaitInputSchema, processLogsOutputSchema, processWaitOutputSchema, computerOperationResultSchema, mintComputerRequestId, processIdInputSchema, } from "@fungi.computer/computer-contract";
@@ -106,6 +107,22 @@ const computerTools = {
106
107
  kill_process: { action: "processKill", output: processKillOutputSchema },
107
108
  process_logs: { action: "processLogs", output: processLogsOutputSchema },
108
109
  wait_process: { action: "processWait", output: processWaitOutputSchema },
110
+ declare_service: {
111
+ action: "serviceDeclare",
112
+ output: computerServiceViewSchema,
113
+ },
114
+ list_services: { action: "serviceList", output: serviceListOutputSchema },
115
+ service_logs: { action: "serviceLogs", output: serviceLogsOutputSchema },
116
+ stop_service: { action: "serviceStop", output: computerServiceViewSchema },
117
+ start_service: { action: "serviceStart", output: computerServiceViewSchema },
118
+ restart_service: {
119
+ action: "serviceRestart",
120
+ output: computerServiceViewSchema,
121
+ },
122
+ remove_service: {
123
+ action: "serviceRemove",
124
+ output: serviceRemoveOutputSchema,
125
+ },
109
126
  };
110
127
  const computerTool = z.enum([
111
128
  "read",
@@ -120,6 +137,13 @@ const computerTool = z.enum([
120
137
  "kill_process",
121
138
  "process_logs",
122
139
  "wait_process",
140
+ "declare_service",
141
+ "list_services",
142
+ "service_logs",
143
+ "stop_service",
144
+ "start_service",
145
+ "restart_service",
146
+ "remove_service",
123
147
  ]);
124
148
  const previewRefusal = appMethodRefusedReplySchema.parse({
125
149
  kind: "refused",
@@ -845,7 +869,7 @@ export function standaloneWorkspace(env, keysLive, selectedComputerId = env.OYST
845
869
  return null;
846
870
  return {
847
871
  // Every Computer advertises the same static operations.
848
- getCapabilities: () => Promise.resolve(computerValueSchema.parse(computerCapabilities())),
872
+ getCapabilities: () => Promise.resolve(advertisedComputerCapabilities()),
849
873
  call: async (capabilityId, input) => computerValueSchema.parse(await computer().tool(grant(computerId, actor), capabilityId, input)),
850
874
  };
851
875
  },
@@ -588,8 +588,8 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
588
588
  readonly values: {
589
589
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
590
590
  };
591
- readonly kind: "code";
592
591
  readonly id: string;
592
+ readonly kind: "code";
593
593
  readonly source: string;
594
594
  readonly title?: string | undefined;
595
595
  readonly note?: string | undefined;
@@ -597,8 +597,8 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
597
597
  readonly values: {
598
598
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
599
599
  };
600
- readonly kind: "app";
601
600
  readonly id: string;
601
+ readonly kind: "app";
602
602
  readonly method: string;
603
603
  readonly app: string;
604
604
  readonly methodDigest: string;
@@ -617,8 +617,8 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
617
617
  access: "read";
618
618
  } | undefined;
619
619
  } | {
620
- readonly kind: "review";
621
620
  readonly id: string;
621
+ readonly kind: "review";
622
622
  readonly title: string;
623
623
  readonly timeout: number;
624
624
  readonly reviewers: "owners" | "runner";
@@ -634,14 +634,14 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
634
634
  }[] | undefined;
635
635
  readonly note?: string | undefined;
636
636
  } | {
637
- readonly kind: "condition";
638
637
  readonly id: string;
638
+ readonly kind: "condition";
639
639
  readonly test: import("@fungi.computer/braid").Predicate;
640
640
  readonly title?: string | undefined;
641
641
  readonly note?: string | undefined;
642
642
  } | {
643
- readonly kind: "map";
644
643
  readonly id: string;
644
+ readonly kind: "map";
645
645
  readonly body: string;
646
646
  readonly over: {
647
647
  readonly node: string;
@@ -652,22 +652,22 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
652
652
  readonly title?: string | undefined;
653
653
  readonly note?: string | undefined;
654
654
  } | {
655
- readonly kind: "repeat";
656
655
  readonly id: string;
656
+ readonly kind: "repeat";
657
657
  readonly body: string;
658
658
  readonly until: import("@fungi.computer/braid").Predicate;
659
659
  readonly maxRounds: number;
660
660
  readonly title?: string | undefined;
661
661
  readonly note?: string | undefined;
662
662
  } | {
663
- readonly kind: "wait";
664
663
  readonly id: string;
664
+ readonly kind: "wait";
665
665
  readonly for: number;
666
666
  readonly title?: string | undefined;
667
667
  readonly note?: string | undefined;
668
668
  } | {
669
- readonly kind: "transform";
670
669
  readonly id: string;
670
+ readonly kind: "transform";
671
671
  readonly fields: {
672
672
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
673
673
  };
@@ -700,8 +700,8 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
700
700
  readonly values: {
701
701
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
702
702
  };
703
- readonly kind: "code";
704
703
  readonly id: string;
704
+ readonly kind: "code";
705
705
  readonly source: string;
706
706
  readonly title?: string | undefined;
707
707
  readonly note?: string | undefined;
@@ -709,8 +709,8 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
709
709
  readonly values: {
710
710
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
711
711
  };
712
- readonly kind: "app";
713
712
  readonly id: string;
713
+ readonly kind: "app";
714
714
  readonly method: string;
715
715
  readonly app: string;
716
716
  readonly methodDigest: string;
@@ -729,8 +729,8 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
729
729
  access: "read";
730
730
  } | undefined;
731
731
  } | {
732
- readonly kind: "review";
733
732
  readonly id: string;
733
+ readonly kind: "review";
734
734
  readonly title: string;
735
735
  readonly timeout: number;
736
736
  readonly reviewers: "owners" | "runner";
@@ -746,14 +746,14 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
746
746
  }[] | undefined;
747
747
  readonly note?: string | undefined;
748
748
  } | {
749
- readonly kind: "condition";
750
749
  readonly id: string;
750
+ readonly kind: "condition";
751
751
  readonly test: import("@fungi.computer/braid").Predicate;
752
752
  readonly title?: string | undefined;
753
753
  readonly note?: string | undefined;
754
754
  } | {
755
- readonly kind: "map";
756
755
  readonly id: string;
756
+ readonly kind: "map";
757
757
  readonly body: string;
758
758
  readonly over: {
759
759
  readonly node: string;
@@ -764,22 +764,22 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
764
764
  readonly title?: string | undefined;
765
765
  readonly note?: string | undefined;
766
766
  } | {
767
- readonly kind: "repeat";
768
767
  readonly id: string;
768
+ readonly kind: "repeat";
769
769
  readonly body: string;
770
770
  readonly until: import("@fungi.computer/braid").Predicate;
771
771
  readonly maxRounds: number;
772
772
  readonly title?: string | undefined;
773
773
  readonly note?: string | undefined;
774
774
  } | {
775
- readonly kind: "wait";
776
775
  readonly id: string;
776
+ readonly kind: "wait";
777
777
  readonly for: number;
778
778
  readonly title?: string | undefined;
779
779
  readonly note?: string | undefined;
780
780
  } | {
781
- readonly kind: "transform";
782
781
  readonly id: string;
782
+ readonly kind: "transform";
783
783
  readonly fields: {
784
784
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
785
785
  };
@@ -332,8 +332,8 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
332
332
  readonly values: {
333
333
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
334
334
  };
335
- readonly kind: "code";
336
335
  readonly id: string;
336
+ readonly kind: "code";
337
337
  readonly source: string;
338
338
  readonly title?: string | undefined;
339
339
  readonly note?: string | undefined;
@@ -341,8 +341,8 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
341
341
  readonly values: {
342
342
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
343
343
  };
344
- readonly kind: "app";
345
344
  readonly id: string;
345
+ readonly kind: "app";
346
346
  readonly method: string;
347
347
  readonly app: string;
348
348
  readonly methodDigest: string;
@@ -361,8 +361,8 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
361
361
  access: "read";
362
362
  } | undefined;
363
363
  } | {
364
- readonly kind: "review";
365
364
  readonly id: string;
365
+ readonly kind: "review";
366
366
  readonly title: string;
367
367
  readonly timeout: number;
368
368
  readonly reviewers: "owners" | "runner";
@@ -378,14 +378,14 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
378
378
  }[] | undefined;
379
379
  readonly note?: string | undefined;
380
380
  } | {
381
- readonly kind: "condition";
382
381
  readonly id: string;
382
+ readonly kind: "condition";
383
383
  readonly test: import("@fungi.computer/braid").Predicate;
384
384
  readonly title?: string | undefined;
385
385
  readonly note?: string | undefined;
386
386
  } | {
387
- readonly kind: "map";
388
387
  readonly id: string;
388
+ readonly kind: "map";
389
389
  readonly body: string;
390
390
  readonly over: {
391
391
  readonly node: string;
@@ -396,22 +396,22 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
396
396
  readonly title?: string | undefined;
397
397
  readonly note?: string | undefined;
398
398
  } | {
399
- readonly kind: "repeat";
400
399
  readonly id: string;
400
+ readonly kind: "repeat";
401
401
  readonly body: string;
402
402
  readonly until: import("@fungi.computer/braid").Predicate;
403
403
  readonly maxRounds: number;
404
404
  readonly title?: string | undefined;
405
405
  readonly note?: string | undefined;
406
406
  } | {
407
- readonly kind: "wait";
408
407
  readonly id: string;
408
+ readonly kind: "wait";
409
409
  readonly for: number;
410
410
  readonly title?: string | undefined;
411
411
  readonly note?: string | undefined;
412
412
  } | {
413
- readonly kind: "transform";
414
413
  readonly id: string;
414
+ readonly kind: "transform";
415
415
  readonly fields: {
416
416
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
417
417
  };
@@ -444,8 +444,8 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
444
444
  readonly values: {
445
445
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
446
446
  };
447
- readonly kind: "code";
448
447
  readonly id: string;
448
+ readonly kind: "code";
449
449
  readonly source: string;
450
450
  readonly title?: string | undefined;
451
451
  readonly note?: string | undefined;
@@ -453,8 +453,8 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
453
453
  readonly values: {
454
454
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
455
455
  };
456
- readonly kind: "app";
457
456
  readonly id: string;
457
+ readonly kind: "app";
458
458
  readonly method: string;
459
459
  readonly app: string;
460
460
  readonly methodDigest: string;
@@ -473,8 +473,8 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
473
473
  access: "read";
474
474
  } | undefined;
475
475
  } | {
476
- readonly kind: "review";
477
476
  readonly id: string;
477
+ readonly kind: "review";
478
478
  readonly title: string;
479
479
  readonly timeout: number;
480
480
  readonly reviewers: "owners" | "runner";
@@ -490,14 +490,14 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
490
490
  }[] | undefined;
491
491
  readonly note?: string | undefined;
492
492
  } | {
493
- readonly kind: "condition";
494
493
  readonly id: string;
494
+ readonly kind: "condition";
495
495
  readonly test: import("@fungi.computer/braid").Predicate;
496
496
  readonly title?: string | undefined;
497
497
  readonly note?: string | undefined;
498
498
  } | {
499
- readonly kind: "map";
500
499
  readonly id: string;
500
+ readonly kind: "map";
501
501
  readonly body: string;
502
502
  readonly over: {
503
503
  readonly node: string;
@@ -508,22 +508,22 @@ export declare abstract class StandaloneWorkflowRunsBase<Env extends StandaloneW
508
508
  readonly title?: string | undefined;
509
509
  readonly note?: string | undefined;
510
510
  } | {
511
- readonly kind: "repeat";
512
511
  readonly id: string;
512
+ readonly kind: "repeat";
513
513
  readonly body: string;
514
514
  readonly until: import("@fungi.computer/braid").Predicate;
515
515
  readonly maxRounds: number;
516
516
  readonly title?: string | undefined;
517
517
  readonly note?: string | undefined;
518
518
  } | {
519
- readonly kind: "wait";
520
519
  readonly id: string;
520
+ readonly kind: "wait";
521
521
  readonly for: number;
522
522
  readonly title?: string | undefined;
523
523
  readonly note?: string | undefined;
524
524
  } | {
525
- readonly kind: "transform";
526
525
  readonly id: string;
526
+ readonly kind: "transform";
527
527
  readonly fields: {
528
528
  readonly [x: string]: import("@fungi.computer/braid").Mapping;
529
529
  };
package/dist/workers.d.ts CHANGED
@@ -119,9 +119,6 @@ export declare class OysterRegistry<Env extends OysterWorkerEnv = OysterWorkerEn
119
119
  }>): Promise<{
120
120
  readonly record: {
121
121
  readonly revision: number;
122
- readonly expiresAt: number;
123
- readonly operation: string;
124
- readonly reason: "pending" | "expired" | "not-found" | "not-eligible" | "already-answered" | "stale-revision" | "declined" | "fenced" | "not-granted" | "read-only" | "in-flight" | "outcome-unknown" | "identity-conflict" | null;
125
122
  readonly description: {
126
123
  readonly title: string;
127
124
  readonly inputBytes: number;
@@ -131,6 +128,9 @@ export declare class OysterRegistry<Env extends OysterWorkerEnv = OysterWorkerEn
131
128
  readonly operationLabel: string;
132
129
  } | undefined;
133
130
  };
131
+ readonly expiresAt: number;
132
+ readonly operation: string;
133
+ readonly reason: "pending" | "expired" | "not-found" | "not-eligible" | "already-answered" | "stale-revision" | "declined" | "fenced" | "not-granted" | "read-only" | "in-flight" | "outcome-unknown" | "identity-conflict" | null;
134
134
  readonly by: {
135
135
  readonly kind: "human";
136
136
  readonly memberId: string;
@@ -1329,6 +1329,12 @@ Re-exports [pinsCurrentToolchain](build.md#pinscurrenttoolchain)
1329
1329
 
1330
1330
  ---
1331
1331
 
1332
+ ### captureConfig
1333
+
1334
+ Re-exports [captureConfig](build.md#captureconfig)
1335
+
1336
+ ---
1337
+
1332
1338
  ### digestPinnedRecipe
1333
1339
 
1334
1340
  Re-exports [digestPinnedRecipe](build.md#digestpinnedrecipe)