@fungi.computer/oyster 0.54.0 → 0.56.0

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.
@@ -10,5 +10,5 @@ export declare const platformSkillFiles: readonly [{
10
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 - 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";
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 cards in total, counting the \"Do it?\" plan and the name offer. A\n card is one `question.ask`; keep each short and specific, and batch a few\n questions into one card. Use options, the recommended one first. Free text is\n always allowed, and an option that lets them type their own answer is fine. Do\n not ask for the person's own name; their account already has it.\n- Every decision is a `question.ask` card, including \"Do it?\". Never end a turn\n asking the person to reply with options in text.\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- A build, install or test that fails or times out never ends setup: say what\n failed in one line, carry on, and still make every offer in step 5. A command\n result of `unknown` means it may still be running, so check again before\n calling it failed.\n- When an action fails and says it is not retryable, such as a generation, try\n at most once more with clearly different input (another model, say), never the\n same action again. Then say so in one line, carry on, and finish setup.\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 1 follow-up card: what they want Fungi\n for; whether there is a project (repo, folder, site, docs); anything that\n repeats (daily, weekly). Done when you can state their goal in a 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. First list your Computer's top folder, never read `AGENTS.md`\n blind. When it is listed, edit it in place; when it is not there yet, your\n Computer is still finishing its first start: carry on with the other items,\n come back to it before step 4, and if it is still missing create it with\n the same headings. Fill its \"About my person\" section (rename it \"About\n <their name>\") with their goal, the preferences they stated and how they\n want updates. Follow its \"Keeping this file up to date\" section from then\n on. Every line answers \"would I get this wrong without it?\". Then introduce\n instructions in one sentence: \"I saved this in my instructions, so I'll\n remember it in every conversation. You can read or edit them from my menu →\n Instructions.\"\n - Files you create for them: write several in one `files.patch` of Add File\n blocks rather than one write each, so they approve once. Write files with\n `files.patch` or `files.write`, never shell heredocs inside `execute`,\n whose quoting breaks.\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.\n - Prints: describe `PRINTS.generateImage` or `PRINTS.generateVideo`, then\n call it; mark a keeper with `PRINTS.setFavorite` on its saved path and\n read them back with `PRINTS.listFavorites`. The library folder is chosen\n by the person in Prints, and no method lets you choose it, so do not\n search for one: if Prints says no library is selected, say so in one line\n and tell them to pick it in Prints.\n4. First result. Do one small real task toward their goal, now. Done when they\n can see its output.\n5. Finish. Do every item below, in order. Do not end your turn before the name\n offer and the dashboard offer have each been asked, failed, or skipped. Even\n if part of setup is blocked, such as an App that is not ready, say so in your\n two lines and still make both offers. An answered card is final: do not ask\n it again in text.\n - Say in two lines what you set up and where to change it.\n - Offer a name, once (required). Never settle it yourself by saying you keep\n your name: the card is how they keep it. Ask with `question.ask`: \"Keep\n <your name>\" first, where your name is the one in your instructions (\"Your\n name is …\"), copied verbatim and never guessed, then two names you suggest\n that fit their goal; free text is always allowed. Ask the name only as a\n `question.ask` card, never in plain text. Wait for their pick: call\n `question.ask` without `mode`, never `mode: \"continue\"`, and make no\n dashboard call until they have picked. Ask it at most once in the whole\n conversation, even if you run step 5 again. Once they have picked, whether\n a new name or Keep, the name is settled: never ask it again, not even after\n an empty or interrupted turn; carry on with the dashboard offer. Only when\n they pick a new name, call `await env.self.rename({name})`: the moment they\n pick a new name, your very next call is `await env.self.rename({name})`,\n before any other step. Then say in one line that you are now called that.\n Call it directly and do not look it up first, since a lookup of a tool you\n may not see reads as absent. If `env.self` is missing or the call is\n refused, say nothing about it.\n - Offer \"Add to your dashboard\" (required). Call\n `await env.TOURTOIS.widgets.available({})` and pick at most 2 matching\n widgets from what you did: Grove Inbox, Inkcap Recent Files, Prints Recent\n Outputs. If no widget clearly matches what you did, offer the most\n generally useful one: Inbox first, then Recent Files. Skip the offer only\n when `widgets.available` returns nothing but the launcher. Never say there\n is no dashboard offer before you have called\n `await env.TOURTOIS.widgets.available({})`. Do not use `question.ask` here.\n For each widget, write one plain line first, such as \"I'm adding Inbox to\n your dashboard; approve the card if you want it.\", then call\n `await env.TOURTOIS.layout.get({})` and\n `await env.TOURTOIS.layout.place({ ... })` with its `surfaceId`, `gillId`,\n a size the widget lists, `scope` \"member\" and `basedOn` the revision\n `layout.get` returned. The call makes the Hub show the person an approval\n card to Approve or Deny. The approval card is their choice: wait for it.\n Denied or expired means move on: do not retry or ask again. Pass `params`\n only for the keys the widget lists, with values you know, and pass every\n key the widget lists as required in `params`, for example\n `params: { computer: <id> }`. Never call `layout.place` without them: a\n call missing one is rejected after the person has approved it. When a\n required parameter is a Computer and the Team has exactly one, use the id\n from your instructions:\n `params: { computer: <the id from your instructions> }`. Skip a widget\n whose required Computer you cannot fill because the Team has none, or more\n than one. Skip a widget only when a required parameter has no value you can\n fill. Never ask a yes or no question before `layout.place`: if a widget\n needs something the person must do first, say so in one line and skip that\n widget. Never place one without that approval, and never add one for a\n person who denied. If `env.TOURTOIS` is missing or a call fails, 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
  }];
@@ -15,6 +15,6 @@ export const platformSkillFiles = [
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 - 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',
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 cards in total, counting the "Do it?" plan and the name offer. A\n card is one `question.ask`; keep each short and specific, and batch a few\n questions into one card. Use options, the recommended one first. Free text is\n always allowed, and an option that lets them type their own answer is fine. Do\n not ask for the person\'s own name; their account already has it.\n- Every decision is a `question.ask` card, including "Do it?". Never end a turn\n asking the person to reply with options in text.\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- A build, install or test that fails or times out never ends setup: say what\n failed in one line, carry on, and still make every offer in step 5. A command\n result of `unknown` means it may still be running, so check again before\n calling it failed.\n- When an action fails and says it is not retryable, such as a generation, try\n at most once more with clearly different input (another model, say), never the\n same action again. Then say so in one line, carry on, and finish setup.\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 1 follow-up card: what they want Fungi\n for; whether there is a project (repo, folder, site, docs); anything that\n repeats (daily, weekly). Done when you can state their goal in a 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. First list your Computer\'s top folder, never read `AGENTS.md`\n blind. When it is listed, edit it in place; when it is not there yet, your\n Computer is still finishing its first start: carry on with the other items,\n come back to it before step 4, and if it is still missing create it with\n the same headings. Fill its "About my person" section (rename it "About\n <their name>") with their goal, the preferences they stated and how they\n want updates. Follow its "Keeping this file up to date" section from then\n on. Every line answers "would I get this wrong without it?". Then introduce\n instructions in one sentence: "I saved this in my instructions, so I\'ll\n remember it in every conversation. You can read or edit them from my menu →\n Instructions."\n - Files you create for them: write several in one `files.patch` of Add File\n blocks rather than one write each, so they approve once. Write files with\n `files.patch` or `files.write`, never shell heredocs inside `execute`,\n whose quoting breaks.\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.\n - Prints: describe `PRINTS.generateImage` or `PRINTS.generateVideo`, then\n call it; mark a keeper with `PRINTS.setFavorite` on its saved path and\n read them back with `PRINTS.listFavorites`. The library folder is chosen\n by the person in Prints, and no method lets you choose it, so do not\n search for one: if Prints says no library is selected, say so in one line\n and tell them to pick it in Prints.\n4. First result. Do one small real task toward their goal, now. Done when they\n can see its output.\n5. Finish. Do every item below, in order. Do not end your turn before the name\n offer and the dashboard offer have each been asked, failed, or skipped. Even\n if part of setup is blocked, such as an App that is not ready, say so in your\n two lines and still make both offers. An answered card is final: do not ask\n it again in text.\n - Say in two lines what you set up and where to change it.\n - Offer a name, once (required). Never settle it yourself by saying you keep\n your name: the card is how they keep it. Ask with `question.ask`: "Keep\n <your name>" first, where your name is the one in your instructions ("Your\n name is …"), copied verbatim and never guessed, then two names you suggest\n that fit their goal; free text is always allowed. Ask the name only as a\n `question.ask` card, never in plain text. Wait for their pick: call\n `question.ask` without `mode`, never `mode: "continue"`, and make no\n dashboard call until they have picked. Ask it at most once in the whole\n conversation, even if you run step 5 again. Once they have picked, whether\n a new name or Keep, the name is settled: never ask it again, not even after\n an empty or interrupted turn; carry on with the dashboard offer. Only when\n they pick a new name, call `await env.self.rename({name})`: the moment they\n pick a new name, your very next call is `await env.self.rename({name})`,\n before any other step. Then say in one line that you are now called that.\n Call it directly and do not look it up first, since a lookup of a tool you\n may not see reads as absent. If `env.self` is missing or the call is\n refused, say nothing about it.\n - Offer "Add to your dashboard" (required). Call\n `await env.TOURTOIS.widgets.available({})` and pick at most 2 matching\n widgets from what you did: Grove Inbox, Inkcap Recent Files, Prints Recent\n Outputs. If no widget clearly matches what you did, offer the most\n generally useful one: Inbox first, then Recent Files. Skip the offer only\n when `widgets.available` returns nothing but the launcher. Never say there\n is no dashboard offer before you have called\n `await env.TOURTOIS.widgets.available({})`. Do not use `question.ask` here.\n For each widget, write one plain line first, such as "I\'m adding Inbox to\n your dashboard; approve the card if you want it.", then call\n `await env.TOURTOIS.layout.get({})` and\n `await env.TOURTOIS.layout.place({ ... })` with its `surfaceId`, `gillId`,\n a size the widget lists, `scope` "member" and `basedOn` the revision\n `layout.get` returned. The call makes the Hub show the person an approval\n card to Approve or Deny. The approval card is their choice: wait for it.\n Denied or expired means move on: do not retry or ask again. Pass `params`\n only for the keys the widget lists, with values you know, and pass every\n key the widget lists as required in `params`, for example\n `params: { computer: <id> }`. Never call `layout.place` without them: a\n call missing one is rejected after the person has approved it. When a\n required parameter is a Computer and the Team has exactly one, use the id\n from your instructions:\n `params: { computer: <the id from your instructions> }`. Skip a widget\n whose required Computer you cannot fill because the Team has none, or more\n than one. Skip a widget only when a required parameter has no value you can\n fill. Never ask a yes or no question before `layout.place`: if a widget\n needs something the person must do first, say so in one line and skip that\n widget. Never place one without that approval, and never add one for a\n person who denied. If `env.TOURTOIS` is missing or a call fails, 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
  ];
@@ -23,3 +23,29 @@ export type AgentExtensionAttachments = Readonly<{
23
23
  }>;
24
24
  /** Open the attachment table in the Agent directory's own SQLite. */
25
25
  export declare function createAgentExtensionAttachments(sql: WatchdogSqliteOwner["sql"]): AgentExtensionAttachments;
26
+ /** One enabled, running extension installation the owner could attach. */
27
+ export type AgentExtensionCandidate = Readonly<{
28
+ installationId: string;
29
+ instanceId: string;
30
+ name: string;
31
+ }>;
32
+ /**
33
+ * What the owner chooses from: the candidates already attached, and the rest.
34
+ * An attachment pins its installation's Instance, so a candidate under a new
35
+ * Instance (the installation was replaced) is not attached, and an attachment
36
+ * with no candidate (removed, disabled or no longer an extension) is dropped.
37
+ */
38
+ export declare function extensionChoices(agentId: string, candidates: readonly AgentExtensionCandidate[], attachments: readonly Readonly<{
39
+ installationId: string;
40
+ instanceId: string;
41
+ }>[]): {
42
+ agentId: string;
43
+ attached: {
44
+ installationId: string;
45
+ name: string;
46
+ }[];
47
+ available: {
48
+ installationId: string;
49
+ name: string;
50
+ }[];
51
+ };
@@ -33,3 +33,24 @@ export function createAgentExtensionAttachments(sql) {
33
33
  },
34
34
  };
35
35
  }
36
+ /**
37
+ * What the owner chooses from: the candidates already attached, and the rest.
38
+ * An attachment pins its installation's Instance, so a candidate under a new
39
+ * Instance (the installation was replaced) is not attached, and an attachment
40
+ * with no candidate (removed, disabled or no longer an extension) is dropped.
41
+ */
42
+ export function extensionChoices(agentId, candidates, attachments) {
43
+ const isAttached = (candidate) => attachments.some((row) => row.installationId === candidate.installationId &&
44
+ row.instanceId === candidate.instanceId);
45
+ const named = ({ installationId, name }) => ({
46
+ installationId,
47
+ name,
48
+ });
49
+ return {
50
+ agentId,
51
+ attached: candidates.filter(isAttached).map(named),
52
+ available: candidates
53
+ .filter((candidate) => !isAttached(candidate))
54
+ .map(named),
55
+ };
56
+ }
@@ -304,6 +304,16 @@ export declare abstract class StandaloneAgentBase<Env extends StandaloneAgentEnv
304
304
  installationId: string;
305
305
  instanceId: string;
306
306
  }> | null>;
307
+ /**
308
+ * Every enabled, running installation that is an Agent extension, with the
309
+ * name the owner sees for it (the installation's id when the host names none).
310
+ * The owner's choices are drawn from these; each pins an attachment.
311
+ */
312
+ extensionCandidates(): Promise<readonly Readonly<{
313
+ installationId: string;
314
+ instanceId: string;
315
+ name: string;
316
+ }>[]>;
307
317
  /** The instance directory that owns this Agent's sealed model keys. */
308
318
  private keyDirectory;
309
319
  /** The instance directory that owns this Agent's MCP connections and their credentials. */
@@ -51,7 +51,7 @@ import { shiitakeEngine } from "./agent-engine.js";
51
51
  import { hostedAgentExtensionsGrant, hostedAppExtensions, } from "@fungi.computer/shiitake/hosted";
52
52
  import { isAgentExtensionApi } from "@fungi.computer/agar/backend-definition";
53
53
  import { agentStoreKeeping } from "./agent-store.js";
54
- import { createAgentExtensionAttachments, } from "./agent-extension-attachments.js";
54
+ import { createAgentExtensionAttachments, extensionChoices, } from "./agent-extension-attachments.js";
55
55
  import { CredentialError, } from "@fungi.computer/veil/credential-store";
56
56
  import { createInstanceCredentialStore, createModelKeyVault, instanceCredentialKeyring, instanceSecretCustody, ModelKeyRefused, } from "./model-key-vault.js";
57
57
  import { createModelKeyUsage } from "./model-key-usage.js";
@@ -1135,6 +1135,36 @@ export class StandaloneAgentBase extends DurableObject {
1135
1135
  ? { installationId, instanceId: installation.instanceId }
1136
1136
  : null;
1137
1137
  }
1138
+ /**
1139
+ * Every enabled, running installation that is an Agent extension, with the
1140
+ * name the owner sees for it (the installation's id when the host names none).
1141
+ * The owner's choices are drawn from these; each pins an attachment.
1142
+ */
1143
+ async extensionCandidates() {
1144
+ const host = await this.appHost();
1145
+ if (host === null)
1146
+ return [];
1147
+ const { appSurfaceCache } = await import("../mcp.js");
1148
+ this.#appSurfaces ??= appSurfaceCache(host);
1149
+ const names = new Map((await host.workbench?.directory())?.apps.map((app) => [
1150
+ app.installationId,
1151
+ app.displayName,
1152
+ ]));
1153
+ const found = [];
1154
+ for (const installation of await host.installations.list()) {
1155
+ if (installation.status !== "enabled" || installation.instanceId === null)
1156
+ continue;
1157
+ const surface = await this.#appSurfaces(installation.release);
1158
+ if (surface !== null && isAgentExtensionApi(surface.api))
1159
+ found.push({
1160
+ installationId: installation.installationId,
1161
+ instanceId: installation.instanceId,
1162
+ name: names.get(installation.installationId) ??
1163
+ installation.installationId,
1164
+ });
1165
+ }
1166
+ return found;
1167
+ }
1138
1168
  /** The instance directory that owns this Agent's sealed model keys. */
1139
1169
  async keyDirectory() {
1140
1170
  const pin = await this.policyDirectory();
@@ -3091,6 +3121,16 @@ export function standaloneAgents(env, scope) {
3091
3121
  return null;
3092
3122
  return (await directory().extensionAttachmentsFor(agentId, scope?.tenantId ?? defaultTenant)).map(({ installationId }) => ({ installationId }));
3093
3123
  },
3124
+ extensionChoices: async (agentId) => {
3125
+ if (!(await directory().has(agentId)))
3126
+ return null;
3127
+ const agent = env.AGENTS.getByName(agentId);
3128
+ const pinned = await agent.policyDirectory();
3129
+ if (pinned?.directoryName !== directoryName ||
3130
+ pinned.tenantId !== (scope?.tenantId ?? defaultTenant))
3131
+ return null;
3132
+ return extensionChoices(agentId, await agent.extensionCandidates(), await directory().extensionAttachmentsFor(agentId, scope?.tenantId ?? defaultTenant));
3133
+ },
3094
3134
  attachExtension: async (agentId, installationId, principal) => {
3095
3135
  if (!oysterPrincipalIsOwner(principal))
3096
3136
  return { error: "not_granted" };
@@ -26,7 +26,7 @@ import { createWriteStream } from "node:fs";
26
26
  import { chmod, mkdir, mkdtemp, rename, readdir, rm, readFile, realpath, stat, writeFile, } from "node:fs/promises";
27
27
  import { createServer } from "node:net";
28
28
  import { createCredentialSealer, } from "@fungi.computer/veil/credential-store";
29
- import { basename, dirname, delimiter, join, resolve } from "node:path";
29
+ import { basename, dirname, delimiter, isAbsolute, join, resolve, } from "node:path";
30
30
  import process from "node:process";
31
31
  import { isDeepStrictEqual, parseArgs, parseEnv, stripVTControlCharacters, } from "node:util";
32
32
  import { Cli } from "@fungi.computer/lantern";
@@ -175,8 +175,27 @@ export function detectManager(userAgent) {
175
175
  async function ownManifest() {
176
176
  return ownManifestSchema.parse(JSON.parse(await readFile(join(import.meta.dirname, "../../package.json"), "utf8")));
177
177
  }
178
- function projectManifest(own, spec) {
179
- const dependencies = {
178
+ const overrideMapSchema = z.record(z.string().regex(/^@fungi\.computer\/[a-z0-9-]+$/u), z
179
+ .string()
180
+ .refine((path) => isAbsolute(path) && path.endsWith(".tgz"), "an absolute .tgz path"));
181
+ /**
182
+ * The nightly proof's tarballs of this tree's workspace packages, named by a
183
+ * JSON map in `OYSTER_TRY_OVERRIDES`. Without them npm would pair this build
184
+ * with the published siblings of the same version, whose contents lag the
185
+ * tree between releases. Internal: not a user-facing option.
186
+ */
187
+ async function trialOverrides() {
188
+ const path = process.env.OYSTER_TRY_OVERRIDES;
189
+ if (path === undefined || path === "")
190
+ return undefined;
191
+ const map = overrideMapSchema.parse(JSON.parse(await readFile(path, "utf8")));
192
+ for (const tarball of Object.values(map))
193
+ if (!(await exists(tarball)))
194
+ throw new Error(`Override tarball ${tarball} does not exist`);
195
+ return Object.fromEntries(Object.entries(map).map(([name, tarball]) => [name, `file:${tarball}`]));
196
+ }
197
+ function projectManifest(own, spec, overrides) {
198
+ const named = {
180
199
  "@fungi.computer/oyster": spec ?? own.version,
181
200
  "@fungi.computer/computer": own.dependencies["@fungi.computer/computer"] ?? "latest",
182
201
  "@fungi.computer/truffle": "latest",
@@ -186,7 +205,12 @@ function projectManifest(own, spec) {
186
205
  pnpm: localBuildPnpmVersion,
187
206
  wrangler: own.peerDependencies.wrangler ?? "^4.127.1",
188
207
  };
189
- return (JSON.stringify({
208
+ // npm refuses an override that disagrees with a direct dependency's spec.
209
+ const dependencies = Object.fromEntries(Object.entries(named).map(([name, version]) => [
210
+ name,
211
+ overrides?.[name] ?? version,
212
+ ]));
213
+ const manifest = {
190
214
  name: "my-oyster",
191
215
  private: true,
192
216
  type: "module",
@@ -202,7 +226,10 @@ function projectManifest(own, spec) {
202
226
  },
203
227
  scripts: { start: "npx @fungi.computer/oyster try" },
204
228
  dependencies,
205
- }, null, 2) + "\n");
229
+ };
230
+ if (overrides !== undefined)
231
+ manifest.overrides = overrides;
232
+ return JSON.stringify(manifest, null, 2) + "\n";
206
233
  }
207
234
  // pnpm 11 refuses dependency build scripts it was not told about.
208
235
  const pnpmWorkspace = `allowBuilds:
@@ -219,6 +246,7 @@ async function exists(path) {
219
246
  }
220
247
  /** Refresh only try-owned configuration; app sources and owner custody stay put. */
221
248
  async function refreshProject(directory, own, spec, manager, signal) {
249
+ const overrides = await trialOverrides();
222
250
  const examples = join(import.meta.dirname, "../../examples/standalone");
223
251
  const files = new Map([
224
252
  ["worker.ts", await readFile(join(examples, "worker.ts"), "utf8")],
@@ -226,10 +254,14 @@ async function refreshProject(directory, own, spec, manager, signal) {
226
254
  "wrangler.jsonc",
227
255
  await readFile(join(examples, "wrangler.jsonc"), "utf8"),
228
256
  ],
229
- ["package.json", projectManifest(own, spec)],
257
+ ["package.json", projectManifest(own, spec, overrides)],
230
258
  ]);
259
+ // pnpm reads its overrides from the workspace file, not package.json; a JSON
260
+ // flow mapping is valid YAML.
231
261
  if (manager === "pnpm")
232
- files.set("pnpm-workspace.yaml", pnpmWorkspace);
262
+ files.set("pnpm-workspace.yaml", overrides === undefined
263
+ ? pnpmWorkspace
264
+ : `${pnpmWorkspace}overrides: ${JSON.stringify(overrides)}\n`);
233
265
  for (const [name, content] of files) {
234
266
  signal.throwIfAborted();
235
267
  const path = join(directory, name);
@@ -103,7 +103,7 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
103
103
  authorityVersion: number;
104
104
  declaredOperationsDigest: import("@fungi.computer/puffball").Sha256Digest;
105
105
  approvedGrants: readonly Readonly<{
106
- capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
106
+ capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.extensions" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
107
107
  capabilityApproved: true;
108
108
  operations: readonly string[];
109
109
  fingerprints: Readonly<Record<string, string>>;
@@ -228,7 +228,7 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
228
228
  authorityVersion: number;
229
229
  declaredOperationsDigest: import("@fungi.computer/puffball").Sha256Digest;
230
230
  approvedGrants: readonly Readonly<{
231
- capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
231
+ capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.extensions" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
232
232
  capabilityApproved: true;
233
233
  operations: readonly string[];
234
234
  fingerprints: Readonly<Record<string, string>>;
@@ -296,7 +296,7 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
296
296
  authorityVersion: number;
297
297
  declaredOperationsDigest: import("@fungi.computer/puffball").Sha256Digest;
298
298
  approvedGrants: readonly Readonly<{
299
- capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
299
+ capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.extensions" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
300
300
  capabilityApproved: true;
301
301
  operations: readonly string[];
302
302
  fingerprints: Readonly<Record<string, string>>;
@@ -397,7 +397,7 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
397
397
  authorityVersion: number;
398
398
  declaredOperationsDigest: import("@fungi.computer/puffball").Sha256Digest;
399
399
  approvedGrants: readonly Readonly<{
400
- capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
400
+ capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.extensions" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
401
401
  capabilityApproved: true;
402
402
  operations: readonly string[];
403
403
  fingerprints: Readonly<Record<string, string>>;
@@ -479,7 +479,7 @@ export declare function createStandaloneWorkflowHost(owner: WatchdogSqliteOwner,
479
479
  authorityVersion: number;
480
480
  declaredOperationsDigest: import("@fungi.computer/puffball").Sha256Digest;
481
481
  approvedGrants: readonly Readonly<{
482
- capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
482
+ capability: "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.extensions" | "agent.stop" | "agent.read" | "agent.send" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage";
483
483
  capabilityApproved: true;
484
484
  operations: readonly string[];
485
485
  fingerprints: Readonly<Record<string, string>>;
@@ -374,7 +374,7 @@ export declare function createStandaloneWorkflowTriggerHost(options: {
374
374
  readonly operations: readonly string[];
375
375
  }[];
376
376
  readonly nodeId: string;
377
- readonly capabilities: readonly ("approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.stop" | "agent.read" | "agent.send" | "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage")[];
377
+ readonly capabilities: readonly ("approvals" | "agent.list" | "agent.manage" | "agent.rename" | "agent.avatar" | "agent.instructions" | "agent.toolPolicy" | "agent.extensions" | "agent.stop" | "agent.read" | "agent.send" | "computer.list" | "computer.readFile" | "computer.writeFile" | "computer.execute" | "llm.generation" | "media.generation" | "media.share" | "games:servers" | "git.repository" | "apps.open" | "apps.call" | "app.storage" | "app.events.emit" | "team.workbenchHost" | "marketplace.browse" | "marketplace.purchase" | "workflow.run" | "workflow.publish" | "workflow.arm" | "world" | "channels.read" | "channels.personal.manage")[];
378
378
  readonly graphId?: string;
379
379
  }[];
380
380
  readonly nodeGitAccess: readonly {
@@ -10,6 +10,33 @@
10
10
 
11
11
  ## Type Aliases
12
12
 
13
+ ### OysterAgentExtension
14
+
15
+ ```ts
16
+ type OysterAgentExtension = Readonly<{
17
+ installationId: string;
18
+ name: string;
19
+ }>;
20
+ ```
21
+
22
+ One installed App that can add its prompt and tools to an Agent's runs.
23
+
24
+ ---
25
+
26
+ ### OysterAgentExtensionChoices
27
+
28
+ ```ts
29
+ type OysterAgentExtensionChoices = Readonly<{
30
+ agentId: string;
31
+ attached: readonly OysterAgentExtension[];
32
+ available: readonly OysterAgentExtension[];
33
+ }>;
34
+ ```
35
+
36
+ An Agent's hosted extensions as the owner chooses them.
37
+
38
+ ---
39
+
13
40
  ### OysterAgentInstructions
14
41
 
15
42
  ```ts
@@ -350,6 +377,13 @@ type OysterAgents = Readonly<{
350
377
  installationId: string;
351
378
  }>[]
352
379
  | null>;
380
+ extensionChoices: Promise<
381
+ | Readonly<{
382
+ agentId: string;
383
+ attached: readonly OysterAgentExtension[];
384
+ available: readonly OysterAgentExtension[];
385
+ }>
386
+ | null>;
353
387
  attachExtension: Promise<
354
388
  | Readonly<{
355
389
  installationId: string;