@fungi.computer/oyster 0.46.5 → 0.47.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- They are at `computer://home/AGENTS.md` and `computer://home/SYSTEM.md`.\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.\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";
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: add a short \"About <their\n name>\" section with their goal, the preferences they stated and how they\n want updates. Every line answers \"would I get this wrong without it?\". Then\n introduce instructions in one sentence: \"I saved this in my instructions,\n so I'll remember it in every conversation. You can read or edit them from\n 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 - 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- They are at `computer://home/AGENTS.md` and `computer://home/SYSTEM.md`.\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.\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",
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: add a short "About <their\n name>" section with their goal, the preferences they stated and how they\n want updates. Every line answers "would I get this wrong without it?". Then\n introduce instructions in one sentence: "I saved this in my instructions,\n so I\'ll remember it in every conversation. You can read or edit them from\n 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 - 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
  ];
@@ -1505,6 +1505,7 @@ export class StandaloneAgentBase extends ShiitakeDO {
1505
1505
  roster: [
1506
1506
  ...extensions.roster,
1507
1507
  homeExtension({
1508
+ instructionsRoot: "",
1508
1509
  computers: {
1509
1510
  prepare: async () => {
1510
1511
  await this.preparedComputerSnapshot();
@@ -2789,7 +2790,7 @@ export function standaloneAgents(env, scope) {
2789
2790
  // AGENTS.md. A Home the owner already wrote to is left as it is. With
2790
2791
  // no Home, the same section stays on the Agent until it has one.
2791
2792
  seedHome: async (agentId) => {
2792
- await seedStarterHome(async (path, content) => {
2793
+ await seedStarterHome("AGENTS.md", async (path, content) => {
2793
2794
  if (path !== "AGENTS.md")
2794
2795
  throw new Error(`The starter seeds only AGENTS.md, not ${path}`);
2795
2796
  const result = await env.AGENTS.getByName(agentId).replaceInstructions(JSON.stringify(principal), null, content);
@@ -14,7 +14,9 @@ export declare const starterAgent: {
14
14
  readonly requestId: "starter-agent:v1";
15
15
  };
16
16
  /** Seed only a missing Home file; the host supplies an atomic create-if-absent. */
17
- export declare function seedStarterHome(writeIfMissing: (path: string, content: string) => Promise<void>): Promise<void>;
17
+ export declare function seedStarterHome(
18
+ /** Where this host keeps Home's AGENTS.md. */
19
+ instructionsPath: string, writeIfMissing: (path: string, content: string) => Promise<void>): Promise<void>;
18
20
  /** What the ledger remembers: that the starter was settled, never to be offered again. */
19
21
  export type StarterLedgerRow = Readonly<{
20
22
  version: number;
@@ -6,9 +6,45 @@ export const starterAgent = {
6
6
  requestId: "starter-agent:v1",
7
7
  };
8
8
  /** Seed only a missing Home file; the host supplies an atomic create-if-absent. */
9
- export async function seedStarterHome(writeIfMissing) {
10
- await writeIfMissing("AGENTS.md", '## First conversation\nYour person is new to Fungi. In your first conversation, load the\n`setup-fungi` skill with skill.load({name: "setup-fungi"}) and follow it.\nWhen setup is finished, delete this section.\n');
9
+ export async function seedStarterHome(
10
+ /** Where this host keeps Home's AGENTS.md. */
11
+ instructionsPath, writeIfMissing) {
12
+ await writeIfMissing(instructionsPath, starterHomeInstructions(`computer://home/${instructionsPath.replace(/^\//u, "")}`));
11
13
  }
14
+ /**
15
+ * The Home AGENTS.md a new Team's Agent starts with. It says nothing about
16
+ * money; the person and the Agent both edit it from here on.
17
+ */
18
+ const starterHomeInstructions = (
19
+ /** Where Home's AGENTS.md is read from on this host, as the Agent names it. */
20
+ location) => `# Shiitake's instructions
21
+
22
+ These are my standing instructions. They live on my Computer at
23
+ ${location} and load at the start of every conversation. My
24
+ person and I both edit this file.
25
+
26
+ ## First conversation
27
+ My person is new to Fungi. In our first conversation, load the \`setup-fungi\`
28
+ skill with \`return await skill.load({name: "setup-fungi"});\` inside execute
29
+ and follow it. If they ask for something specific first, do that, then set up.
30
+ When setup is finished, delete this section.
31
+
32
+ ## About my person
33
+ (Empty until setup. Fill in: their name, what they want from Fungi, their
34
+ work and where it lives on my Computer, how they like updates.)
35
+
36
+ ## Keeping this file up to date
37
+ - When my person states a lasting preference, corrects me, or tells me
38
+ something I would get wrong next time, add one short line here in the right
39
+ section, then tell them in one sentence that I saved it.
40
+ - When I learn a fact about one of their codebases, put it in that codebase's
41
+ own AGENTS.md, not here.
42
+ - Keep each line short and true. Every line answers "would I get this wrong
43
+ without it?". Remove lines that stop being true.
44
+ - Never delete or rewrite a line my person wrote without asking.
45
+ - Never save secrets, keys, passwords or payment details here.
46
+ - Keep this file under 200 lines; tidy it when it grows.
47
+ `;
12
48
  const ledgerRowSchema = z.strictObject({
13
49
  version: z.number().int(),
14
50
  outcome: z.enum(["seed-pending", "created", "team-not-empty"]),
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fungi.computer/oyster",
3
- "version": "0.46.5",
3
+ "version": "0.47.1",
4
4
  "author": "Levi <levi@technomancy.dev>",
5
5
  "description": "Oyster by Fungi: open-source Apps for people and AI agents. Try with one command or run on your own Cloudflare account.",
6
6
  "homepage": "https://docs.fungi.computer/oyster",
@@ -358,37 +358,37 @@
358
358
  "dependencies": {
359
359
  "@cfworker/json-schema": "4.1.1",
360
360
  "@earendil-works/pi-ai": "1.5.2",
361
- "@fungi.computer/agar": "0.23.0",
361
+ "@fungi.computer/agar": "0.23.1",
362
362
  "@fungi.computer/bird-dog": "0.3.7",
363
- "@fungi.computer/braid": "0.6.1",
363
+ "@fungi.computer/braid": "0.6.2",
364
364
  "@fungi.computer/burrow": "0.2.1",
365
365
  "@fungi.computer/cairn": "0.1.0",
366
366
  "@fungi.computer/capnweb": "0.12.0-fungi.0",
367
367
  "@fungi.computer/caps": "0.12.2",
368
368
  "@fungi.computer/carrier": "0.2.5",
369
- "@fungi.computer/computer": "0.15.0",
370
- "@fungi.computer/computer-contract": "0.5.7",
371
- "@fungi.computer/darkroom": "0.11.8",
369
+ "@fungi.computer/computer": "0.15.2",
370
+ "@fungi.computer/computer-contract": "0.5.8",
371
+ "@fungi.computer/darkroom": "0.11.9",
372
372
  "@fungi.computer/ear-tag": "0.1.0",
373
373
  "@fungi.computer/forage": "0.3.13",
374
374
  "@fungi.computer/gills": "0.4.0",
375
- "@fungi.computer/knapsack": "0.4.20",
375
+ "@fungi.computer/knapsack": "0.4.21",
376
376
  "@fungi.computer/lantern": "0.4.2",
377
377
  "@fungi.computer/mycelium": "0.4.7",
378
- "@fungi.computer/nacre": "0.8.3",
379
- "@fungi.computer/parakeet": "0.14.9",
378
+ "@fungi.computer/nacre": "0.8.4",
379
+ "@fungi.computer/parakeet": "0.16.0",
380
380
  "@fungi.computer/puffball": "0.12.0",
381
381
  "@fungi.computer/seam": "0.2.6",
382
- "@fungi.computer/shiitake": "0.21.8",
383
- "@fungi.computer/shiitake-extensions": "0.11.18",
382
+ "@fungi.computer/shiitake": "0.21.9",
383
+ "@fungi.computer/shiitake-extensions": "0.11.20",
384
384
  "@fungi.computer/sigils": "0.3.2",
385
385
  "@fungi.computer/sprite": "0.2.2",
386
386
  "@fungi.computer/sprite-zdog": "0.3.2",
387
- "@fungi.computer/veil": "0.11.0",
387
+ "@fungi.computer/veil": "0.11.1",
388
388
  "@fungi.computer/watchdog": "0.1.4",
389
389
  "@fungi.computer/whistle": "0.3.0",
390
- "@fungi.computer/workflows-wire": "0.7.1",
391
- "@fungi.computer/zookeeper": "0.0.50",
390
+ "@fungi.computer/workflows-wire": "0.7.2",
391
+ "@fungi.computer/zookeeper": "0.0.51",
392
392
  "@jellybrick/dbus-next": "0.11.4",
393
393
  "@modelcontextprotocol/server": "2.0.0",
394
394
  "@msgpack/msgpack": "3.1.3",