@fungi.computer/oyster 0.57.1 → 0.57.2
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 and the completed name and widget offers.\n\nSetup is one flow: approved work → useful result → name card → widget approval →\nfinish. After the work or a name answer, continue with the next tool call in the\nsame turn. A progress summary is commentary, never the end of setup. End only\nafter step 5 is complete, or while a card is parked awaiting its answer; when\nthat answer arrives, resume at the next unfinished item.\n\n## Start and resume\n\nOn resume, continue at the first unfinished step. A name answer goes straight to\nstep 5's rename/Keep handling, before file discovery or goal calls. The\ndiscovery and arming below happen once, at the start of setup.\n\nFirst list Home's working folder with its `list` tool (`{path: \".\"}`), or your\nattached Computer's `files.list({path: \".\"})`. Read `AGENTS.md` only if that\nlisting contains it, using `path: \"AGENTS.md\"`. Use that same relative path for\nedits; the working folder is not the filesystem root. An absent `AGENTS.md` is\nnot read: the listing already checked whether it exists. Continue to goal arming\nand the interview; create it only in approved step 3.\n\nBefore approved work, arm the existing Session goal so an accidental end of turn\nresumes this checklist without a nudge. Describe `goal`, read\n`env.goal.get_goal({})`, and, only when no goal is current, call\n`env.goal.create_goal({objective: \"Finish setting up for you, including your first useful result, a name card and widget approvals.\"})`.\nKeep an existing goal; never replace or complete someone else's objective for\nsetup. Record a setup goal you created in step 3's progress after approval.\nUntil then, reuse it from this conversation; arming is complete after the goal\ncall. If goal tools are absent, continue the checklist directly.\n\nA parked question or approval is a real wait; the goal runtime waits with it.\nAfter the useful result, use a declarative transition such as \"Your image is\nready.\" and make the name-card tool call in step 5 in this same turn. Put the\nentire name question and its options inside that card. A goal continuation\nrepairs an interrupted checklist; it never turns a plain-text name question into\na valid offer. On continuation, use step 5's resume check and call the missing\ncard directly or continue after its answer. Complete the setup goal only after\nstep 5's offers and cleanup have finished; keep it active while any required\noffer is pending.\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- Media budget: at most ONE sample attempt across images and videos for the\n entire setup, including resumed turns. Make it only when the catalog/quote\n shows it is cheap and the approved plan includes it; otherwise save a useful\n prompt or brief as the first result. A failed, denied or expired generation\n spends that attempt. Never retry, switch models, or try the other medium. Say\n the cause once in plain words, then continue to the name and widget steps.\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\n For files on Home, group several in one direct `apply_patch` tool call with\n Add File blocks and Home-relative paths. Send the patch as tool data, keeping\n HTML, JavaScript backticks and `${...}` out of JavaScript source strings.\n This is a direct tool call, outside `execute`; never shell heredocs inside\n `execute`. If this tool is unavailable, say file writing is blocked and\n continue to the offers in step 5.\n\n - Instructions. List the working folder again with `files.list({path: \".\"})`.\n When `AGENTS.md` is listed, read and edit `path: \"AGENTS.md\"` in place;\n when absent, create it now with the starter headings \"About my person\",\n \"Keeping this file up to date\" and temporary \"First conversation\" progress.\n Record any owned setup goal objective in that progress. Fill its \"About my\n person\" section (rename it \"About <their name>\") with their goal, the\n preferences they stated and how they want updates. Follow its \"Keeping this\n file up to date\" section from then on. Every line answers \"would I get this\n wrong without it?\". Then introduce instructions in one sentence: \"I saved\n this in my instructions, so I'll remember it in every conversation. You can\n read or 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.\n - Prints: apply the Media budget above before calling\n `PRINTS.generateImage` or `PRINTS.generateVideo`. Record the attempt in\n Home's setup progress before calling, so a resumed turn cannot repeat it.\n Mark a keeper with `PRINTS.setFavorite` on its saved path and read them\n back with `PRINTS.listFavorites`. The library folder is chosen by the\n person in Prints, and no method lets you choose it, so do not search for\n one: if Prints says no library is selected, say so in one line and tell\n them to pick it in Prints.\n\n4. First result. Do one small real task toward their goal, now. When they can\n see its output, immediately enter step 5 in this turn. If media is\n unavailable, a saved prompt or brief is the result; the media budget still\n applies.\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, then continue\n immediately to the name card tool call.\n - Resume check. Read your current name from your instructions, the answers\n and rename results already in this conversation, and Home's setup progress.\n If a name was picked (including Keep), or a rename already succeeded, the\n name is settled: skip the name card and rename call and proceed directly to\n widgets. A current name different from the starting name saved in setup\n progress also proves the rename happened. If a name card is still pending,\n wait on that same card instead of issuing a replacement. Plain text and an\n offered marker alone do not prove a card is waiting: without an actual name\n card call in this conversation, make that call now. A nudge, failure or\n interrupted turn resumes this checklist; it never restarts setup.\n - Offer a name, once (required). Never settle it yourself by saying you keep\n your name: the card is how they keep it. Before the first name card, save\n its offered status and your starting name under \"First conversation\" in\n Home `AGENTS.md`. Ask with `question.ask`: \"Keep <your name>\" first, where\n your name is the one in your instructions (\"Your name is …\"), copied\n verbatim and never guessed, then two names you suggest that fit their goal;\n free text is always allowed. In `execute`, bind `currentName` to that\n verbatim current name and choose `firstSuggestion` and `secondSuggestion`,\n then run the actual card call below. Your chat transition is a statement;\n the name question belongs inside this call:\n\n ```js\n return await env.question.ask({\n questions: [\n {\n id: \"agent_name\",\n header: \"Name\",\n question: \"Choose a name for me\",\n options: [\n {\n label: `Keep ${currentName}`,\n description: \"Keep my current name.\",\n },\n { label: firstSuggestion, description: \"Use this name.\" },\n { label: secondSuggestion, description: \"Use this name.\" },\n ],\n },\n ],\n });\n ```\n\n Ask the name only as a `question.ask` card, never in plain text. Wait for\n their pick: call `question.ask` without `mode`, never `mode: \"continue\"`,\n and make no dashboard call until they have picked. Ask it at most once in\n the whole conversation, even if you run step 5 again. Once they have\n picked, whether a new name or Keep, the name is settled: never ask it\n again, not even after an empty or interrupted turn; carry on with the\n dashboard offer. Only when they pick a new name, call\n `await env.self.rename({name})`: the moment they pick a new name, your very\n next call is `await env.self.rename({name})`, before any other step. Then\n say in one line that you are now called that. Call it directly and do not\n look it up first, since a lookup of a tool you may not see reads as absent.\n If `env.self` is missing or the call is refused, say nothing about it.\n After applying their pick, save the settled name (including Keep) in setup\n progress, then immediately call `await env.TOURTOIS.widgets.available({})`\n in this turn.\n\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 in your final `execute`. If you\n created the setup goal, that same invocation must first await\n `env.goal.update_goal({status: \"complete\", reason: \"Useful result delivered; name and widget offers settled; setup progress cleaned up.\"})`,\n then await `env.setup.finish({})`. Keep the two calls together so the\n hand-off cannot leave the setup goal unfinished. Leave any other current\n goal alone.\n - When the `setup.finish` tool is absent, finish after the offers and cleanup\n above are complete. If you created the setup goal, your final tool call is\n `await env.goal.update_goal({status: \"complete\", reason: \"Useful result delivered; name and widget offers settled; setup progress cleaned up.\"})`.\n Leave any other current goal alone. That host has no money step; say\n nothing about Pro or wallets. Its absence never skips the name card or\n widget approval.\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 and the completed name and widget offers.\n\nSetup is one flow: approved work → useful result → name card → widget approval →\nfinish. After the work or a name answer, continue with the next tool call in the\nsame turn. A progress summary is commentary, never the end of setup. End only\nafter step 5 is complete, or while a card is parked awaiting its answer; when\nthat answer arrives, resume at the next unfinished item.\n\n## Start and resume\n\nOn resume, continue at the first unfinished step. A name answer goes straight to\nstep 5's rename/Keep handling, before file discovery or goal calls. The\ndiscovery and arming below happen once, at the start of setup.\n\nInside `execute`, describe only operation paths that `forage.search` or\n`forage.list` returned; a guessed path such as `files` fails as an error row\nbefore the first card. `computers.<Name>.files.list` is the Computer's path.\n\nFirst list Home's working folder with its `list` tool (`{path: \".\"}`), or your\nattached Computer's `files.list({path: \".\"})`. Read `AGENTS.md` only if that\nlisting contains it, using `path: \"AGENTS.md\"`. Use that same relative path for\nedits; the working folder is not the filesystem root. An absent `AGENTS.md` is\nnot read: the listing already checked whether it exists. Continue to goal arming\nand the interview; create it only in approved step 3.\n\nBefore approved work, arm the existing Session goal so an accidental end of turn\nresumes this checklist without a nudge. Describe `goal`, read\n`env.goal.get_goal({})`, and, only when no goal is current, call\n`env.goal.create_goal({objective: \"Finish setting up for you, including your first useful result, a name card and widget approvals.\"})`.\nKeep an existing goal; never replace or complete someone else's objective for\nsetup. Record a setup goal you created in step 3's progress after approval.\nUntil then, reuse it from this conversation; arming is complete after the goal\ncall. If goal tools are absent, continue the checklist directly.\n\nA parked question or approval is a real wait; the goal runtime waits with it.\nAfter the useful result, use a declarative transition such as \"Your image is\nready.\" and make the name-card tool call in step 5 in this same turn. Put the\nentire name question and its options inside that card. A goal continuation\nrepairs an interrupted checklist; it never turns a plain-text name question into\na valid offer. On continuation, use step 5's resume check and call the missing\ncard directly or continue after its answer. Complete the setup goal only after\nstep 5's offers and cleanup have finished; keep it active while any required\noffer is pending.\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- Media budget: at most ONE sample attempt across images and videos for the\n entire setup, including resumed turns. Make it only when the catalog/quote\n shows it is cheap and the approved plan includes it; otherwise save a useful\n prompt or brief as the first result. A failed, denied or expired generation\n spends that attempt. Never retry, switch models, or try the other medium. Say\n the cause once in plain words, then continue to the name and widget steps.\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\n For files on Home, group several in one direct `apply_patch` tool call with\n Add File blocks and Home-relative paths. Send the patch as tool data, keeping\n HTML, JavaScript backticks and `${...}` out of JavaScript source strings.\n This is a direct tool call, outside `execute`; never shell heredocs inside\n `execute`. Files are only ever written with `apply_patch`: never `cat >`,\n `printf >`, `tee`, `echo >` or a heredoc (`<<'EOF'`) through `execute`,\n `bash` or `exec`, not even as a fallback. If `apply_patch` fails, read its\n error, fix the patch (it must start with `*** Begin Patch`, give every file\n line a leading `+`, and end with `*** End Patch` on its own last line) and\n call `apply_patch` again. If this tool is unavailable, say file writing is\n blocked and continue to the offers in step 5.\n\n - Instructions. List the working folder again with `files.list({path: \".\"})`.\n When `AGENTS.md` is listed, read and edit `path: \"AGENTS.md\"` in place;\n when absent, create it now with the starter headings \"About my person\",\n \"Keeping this file up to date\" and temporary \"First conversation\" progress.\n Record any owned setup goal objective in that progress. Fill its \"About my\n person\" section (rename it \"About <their name>\") with their goal, the\n preferences they stated and how they want updates. Follow its \"Keeping this\n file up to date\" section from then on. Every line answers \"would I get this\n wrong without it?\". Then introduce instructions in one sentence: \"I saved\n this in my instructions, so I'll remember it in every conversation. You can\n read or 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.\n - Prints: apply the Media budget above before calling\n `PRINTS.generateImage` or `PRINTS.generateVideo`. Record the attempt in\n Home's setup progress before calling, so a resumed turn cannot repeat it.\n Mark a keeper with `PRINTS.setFavorite` on its saved path and read them\n back with `PRINTS.listFavorites`. The library folder is chosen by the\n person in Prints, and no method lets you choose it, so do not search for\n one: if Prints says no library is selected, say so in one line and tell\n them to pick it in Prints.\n\n4. First result. Do one small real task toward their goal, now. When they can\n see its output, immediately enter step 5 in this turn. If media is\n unavailable, a saved prompt or brief is the result; the media budget still\n applies.\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, then continue\n immediately to the name card tool call.\n - Resume check. Read your current name from your instructions, the answers\n and rename results already in this conversation, and Home's setup progress.\n If a name was picked (including Keep), or a rename already succeeded, the\n name is settled: skip the name card and rename call and proceed directly to\n widgets. A current name different from the starting name saved in setup\n progress also proves the rename happened. If a name card is still pending,\n wait on that same card instead of issuing a replacement. Plain text and an\n offered marker alone do not prove a card is waiting: without an actual name\n card call in this conversation, make that call now. A nudge, failure or\n interrupted turn resumes this checklist; it never restarts setup.\n - Offer a name, once (required). Never settle it yourself by saying you keep\n your name: the card is how they keep it. Before the first name card, save\n its offered status and your starting name under \"First conversation\" in\n Home `AGENTS.md`. Ask with `question.ask`: \"Keep <your name>\" first, where\n your name is the one in your instructions (\"Your name is …\"), copied\n verbatim and never guessed, then two names you suggest that fit their goal;\n free text is always allowed. In `execute`, bind `currentName` to that\n verbatim current name and choose `firstSuggestion` and `secondSuggestion`,\n then run the actual card call below. Your chat transition is a statement;\n the name question belongs inside this call:\n\n ```js\n return await env.question.ask({\n questions: [\n {\n id: \"agent_name\",\n header: \"Name\",\n question: \"Choose a name for me\",\n options: [\n {\n label: `Keep ${currentName}`,\n description: \"Keep my current name.\",\n },\n { label: firstSuggestion, description: \"Use this name.\" },\n { label: secondSuggestion, description: \"Use this name.\" },\n ],\n },\n ],\n });\n ```\n\n Ask the name only as a `question.ask` card, never in plain text. Wait for\n their pick: call `question.ask` without `mode`, never `mode: \"continue\"`,\n and make no dashboard call until they have picked. Ask it at most once in\n the whole conversation, even if you run step 5 again. Once they have\n picked, whether a new name or Keep, the name is settled: never ask it\n again, not even after an empty or interrupted turn; carry on with the\n dashboard offer. Only when they pick a new name, call\n `await env.self.rename({name})`: the moment they pick a new name, your very\n next call is `await env.self.rename({name})`, before any other step. Then\n say in one line that you are now called that. Call it directly and do not\n look it up first, since a lookup of a tool you may not see reads as absent.\n If `env.self` is missing or the call is refused, say nothing about it.\n After applying their pick, save the settled name (including Keep) in setup\n progress, then immediately call `await env.TOURTOIS.widgets.available({})`\n in this turn.\n\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 in your final `execute`. If you\n created the setup goal, that same invocation must first await\n `env.goal.update_goal({status: \"complete\", reason: \"Useful result delivered; name and widget offers settled; setup progress cleaned up.\"})`,\n then await `env.setup.finish({})`. Keep the two calls together so the\n hand-off cannot leave the setup goal unfinished. Leave any other current\n goal alone.\n - When the `setup.finish` tool is absent, finish after the offers and cleanup\n above are complete. If you created the setup goal, your final tool call is\n `await env.goal.update_goal({status: \"complete\", reason: \"Useful result delivered; name and widget offers settled; setup progress cleaned up.\"})`.\n Leave any other current goal alone. That host has no money step; say\n nothing about Pro or wallets. Its absence never skips the name card or\n widget approval.\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 and the completed name and widget offers.\n\nSetup is one flow: approved work → useful result → name card → widget approval →\nfinish. After the work or a name answer, continue with the next tool call in the\nsame turn. A progress summary is commentary, never the end of setup. End only\nafter step 5 is complete, or while a card is parked awaiting its answer; when\nthat answer arrives, resume at the next unfinished item.\n\n## Start and resume\n\nOn resume, continue at the first unfinished step. A name answer goes straight to\nstep 5\'s rename/Keep handling, before file discovery or goal calls. The\ndiscovery and arming below happen once, at the start of setup.\n\nFirst list Home\'s working folder with its `list` tool (`{path: "."}`), or your\nattached Computer\'s `files.list({path: "."})`. Read `AGENTS.md` only if that\nlisting contains it, using `path: "AGENTS.md"`. Use that same relative path for\nedits; the working folder is not the filesystem root. An absent `AGENTS.md` is\nnot read: the listing already checked whether it exists. Continue to goal arming\nand the interview; create it only in approved step 3.\n\nBefore approved work, arm the existing Session goal so an accidental end of turn\nresumes this checklist without a nudge. Describe `goal`, read\n`env.goal.get_goal({})`, and, only when no goal is current, call\n`env.goal.create_goal({objective: "Finish setting up for you, including your first useful result, a name card and widget approvals."})`.\nKeep an existing goal; never replace or complete someone else\'s objective for\nsetup. Record a setup goal you created in step 3\'s progress after approval.\nUntil then, reuse it from this conversation; arming is complete after the goal\ncall. If goal tools are absent, continue the checklist directly.\n\nA parked question or approval is a real wait; the goal runtime waits with it.\nAfter the useful result, use a declarative transition such as "Your image is\nready." and make the name-card tool call in step 5 in this same turn. Put the\nentire name question and its options inside that card. A goal continuation\nrepairs an interrupted checklist; it never turns a plain-text name question into\na valid offer. On continuation, use step 5\'s resume check and call the missing\ncard directly or continue after its answer. Complete the setup goal only after\nstep 5\'s offers and cleanup have finished; keep it active while any required\noffer is pending.\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- Media budget: at most ONE sample attempt across images and videos for the\n entire setup, including resumed turns. Make it only when the catalog/quote\n shows it is cheap and the approved plan includes it; otherwise save a useful\n prompt or brief as the first result. A failed, denied or expired generation\n spends that attempt. Never retry, switch models, or try the other medium. Say\n the cause once in plain words, then continue to the name and widget steps.\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\n For files on Home, group several in one direct `apply_patch` tool call with\n Add File blocks and Home-relative paths. Send the patch as tool data, keeping\n HTML, JavaScript backticks and `${...}` out of JavaScript source strings.\n This is a direct tool call, outside `execute`; never shell heredocs inside\n `execute`. If this tool is unavailable, say file writing is blocked and\n continue to the offers in step 5.\n\n - Instructions. List the working folder again with `files.list({path: "."})`.\n When `AGENTS.md` is listed, read and edit `path: "AGENTS.md"` in place;\n when absent, create it now with the starter headings "About my person",\n "Keeping this file up to date" and temporary "First conversation" progress.\n Record any owned setup goal objective in that progress. Fill its "About my\n person" section (rename it "About <their name>") with their goal, the\n preferences they stated and how they want updates. Follow its "Keeping this\n file up to date" section from then on. Every line answers "would I get this\n wrong without it?". Then introduce instructions in one sentence: "I saved\n this in my instructions, so I\'ll remember it in every conversation. You can\n read or 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.\n - Prints: apply the Media budget above before calling\n `PRINTS.generateImage` or `PRINTS.generateVideo`. Record the attempt in\n Home\'s setup progress before calling, so a resumed turn cannot repeat it.\n Mark a keeper with `PRINTS.setFavorite` on its saved path and read them\n back with `PRINTS.listFavorites`. The library folder is chosen by the\n person in Prints, and no method lets you choose it, so do not search for\n one: if Prints says no library is selected, say so in one line and tell\n them to pick it in Prints.\n\n4. First result. Do one small real task toward their goal, now. When they can\n see its output, immediately enter step 5 in this turn. If media is\n unavailable, a saved prompt or brief is the result; the media budget still\n applies.\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, then continue\n immediately to the name card tool call.\n - Resume check. Read your current name from your instructions, the answers\n and rename results already in this conversation, and Home\'s setup progress.\n If a name was picked (including Keep), or a rename already succeeded, the\n name is settled: skip the name card and rename call and proceed directly to\n widgets. A current name different from the starting name saved in setup\n progress also proves the rename happened. If a name card is still pending,\n wait on that same card instead of issuing a replacement. Plain text and an\n offered marker alone do not prove a card is waiting: without an actual name\n card call in this conversation, make that call now. A nudge, failure or\n interrupted turn resumes this checklist; it never restarts setup.\n - Offer a name, once (required). Never settle it yourself by saying you keep\n your name: the card is how they keep it. Before the first name card, save\n its offered status and your starting name under "First conversation" in\n Home `AGENTS.md`. Ask with `question.ask`: "Keep <your name>" first, where\n your name is the one in your instructions ("Your name is …"), copied\n verbatim and never guessed, then two names you suggest that fit their goal;\n free text is always allowed. In `execute`, bind `currentName` to that\n verbatim current name and choose `firstSuggestion` and `secondSuggestion`,\n then run the actual card call below. Your chat transition is a statement;\n the name question belongs inside this call:\n\n ```js\n return await env.question.ask({\n questions: [\n {\n id: "agent_name",\n header: "Name",\n question: "Choose a name for me",\n options: [\n {\n label: `Keep ${currentName}`,\n description: "Keep my current name.",\n },\n { label: firstSuggestion, description: "Use this name." },\n { label: secondSuggestion, description: "Use this name." },\n ],\n },\n ],\n });\n ```\n\n Ask the name only as a `question.ask` card, never in plain text. Wait for\n their pick: call `question.ask` without `mode`, never `mode: "continue"`,\n and make no dashboard call until they have picked. Ask it at most once in\n the whole conversation, even if you run step 5 again. Once they have\n picked, whether a new name or Keep, the name is settled: never ask it\n again, not even after an empty or interrupted turn; carry on with the\n dashboard offer. Only when they pick a new name, call\n `await env.self.rename({name})`: the moment they pick a new name, your very\n next call is `await env.self.rename({name})`, before any other step. Then\n say in one line that you are now called that. Call it directly and do not\n look it up first, since a lookup of a tool you may not see reads as absent.\n If `env.self` is missing or the call is refused, say nothing about it.\n After applying their pick, save the settled name (including Keep) in setup\n progress, then immediately call `await env.TOURTOIS.widgets.available({})`\n in this turn.\n\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 in your final `execute`. If you\n created the setup goal, that same invocation must first await\n `env.goal.update_goal({status: "complete", reason: "Useful result delivered; name and widget offers settled; setup progress cleaned up."})`,\n then await `env.setup.finish({})`. Keep the two calls together so the\n hand-off cannot leave the setup goal unfinished. Leave any other current\n goal alone.\n - When the `setup.finish` tool is absent, finish after the offers and cleanup\n above are complete. If you created the setup goal, your final tool call is\n `await env.goal.update_goal({status: "complete", reason: "Useful result delivered; name and widget offers settled; setup progress cleaned up."})`.\n Leave any other current goal alone. That host has no money step; say\n nothing about Pro or wallets. Its absence never skips the name card or\n widget approval.\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 and the completed name and widget offers.\n\nSetup is one flow: approved work → useful result → name card → widget approval →\nfinish. After the work or a name answer, continue with the next tool call in the\nsame turn. A progress summary is commentary, never the end of setup. End only\nafter step 5 is complete, or while a card is parked awaiting its answer; when\nthat answer arrives, resume at the next unfinished item.\n\n## Start and resume\n\nOn resume, continue at the first unfinished step. A name answer goes straight to\nstep 5\'s rename/Keep handling, before file discovery or goal calls. The\ndiscovery and arming below happen once, at the start of setup.\n\nInside `execute`, describe only operation paths that `forage.search` or\n`forage.list` returned; a guessed path such as `files` fails as an error row\nbefore the first card. `computers.<Name>.files.list` is the Computer\'s path.\n\nFirst list Home\'s working folder with its `list` tool (`{path: "."}`), or your\nattached Computer\'s `files.list({path: "."})`. Read `AGENTS.md` only if that\nlisting contains it, using `path: "AGENTS.md"`. Use that same relative path for\nedits; the working folder is not the filesystem root. An absent `AGENTS.md` is\nnot read: the listing already checked whether it exists. Continue to goal arming\nand the interview; create it only in approved step 3.\n\nBefore approved work, arm the existing Session goal so an accidental end of turn\nresumes this checklist without a nudge. Describe `goal`, read\n`env.goal.get_goal({})`, and, only when no goal is current, call\n`env.goal.create_goal({objective: "Finish setting up for you, including your first useful result, a name card and widget approvals."})`.\nKeep an existing goal; never replace or complete someone else\'s objective for\nsetup. Record a setup goal you created in step 3\'s progress after approval.\nUntil then, reuse it from this conversation; arming is complete after the goal\ncall. If goal tools are absent, continue the checklist directly.\n\nA parked question or approval is a real wait; the goal runtime waits with it.\nAfter the useful result, use a declarative transition such as "Your image is\nready." and make the name-card tool call in step 5 in this same turn. Put the\nentire name question and its options inside that card. A goal continuation\nrepairs an interrupted checklist; it never turns a plain-text name question into\na valid offer. On continuation, use step 5\'s resume check and call the missing\ncard directly or continue after its answer. Complete the setup goal only after\nstep 5\'s offers and cleanup have finished; keep it active while any required\noffer is pending.\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- Media budget: at most ONE sample attempt across images and videos for the\n entire setup, including resumed turns. Make it only when the catalog/quote\n shows it is cheap and the approved plan includes it; otherwise save a useful\n prompt or brief as the first result. A failed, denied or expired generation\n spends that attempt. Never retry, switch models, or try the other medium. Say\n the cause once in plain words, then continue to the name and widget steps.\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\n For files on Home, group several in one direct `apply_patch` tool call with\n Add File blocks and Home-relative paths. Send the patch as tool data, keeping\n HTML, JavaScript backticks and `${...}` out of JavaScript source strings.\n This is a direct tool call, outside `execute`; never shell heredocs inside\n `execute`. Files are only ever written with `apply_patch`: never `cat >`,\n `printf >`, `tee`, `echo >` or a heredoc (`<<\'EOF\'`) through `execute`,\n `bash` or `exec`, not even as a fallback. If `apply_patch` fails, read its\n error, fix the patch (it must start with `*** Begin Patch`, give every file\n line a leading `+`, and end with `*** End Patch` on its own last line) and\n call `apply_patch` again. If this tool is unavailable, say file writing is\n blocked and continue to the offers in step 5.\n\n - Instructions. List the working folder again with `files.list({path: "."})`.\n When `AGENTS.md` is listed, read and edit `path: "AGENTS.md"` in place;\n when absent, create it now with the starter headings "About my person",\n "Keeping this file up to date" and temporary "First conversation" progress.\n Record any owned setup goal objective in that progress. Fill its "About my\n person" section (rename it "About <their name>") with their goal, the\n preferences they stated and how they want updates. Follow its "Keeping this\n file up to date" section from then on. Every line answers "would I get this\n wrong without it?". Then introduce instructions in one sentence: "I saved\n this in my instructions, so I\'ll remember it in every conversation. You can\n read or 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.\n - Prints: apply the Media budget above before calling\n `PRINTS.generateImage` or `PRINTS.generateVideo`. Record the attempt in\n Home\'s setup progress before calling, so a resumed turn cannot repeat it.\n Mark a keeper with `PRINTS.setFavorite` on its saved path and read them\n back with `PRINTS.listFavorites`. The library folder is chosen by the\n person in Prints, and no method lets you choose it, so do not search for\n one: if Prints says no library is selected, say so in one line and tell\n them to pick it in Prints.\n\n4. First result. Do one small real task toward their goal, now. When they can\n see its output, immediately enter step 5 in this turn. If media is\n unavailable, a saved prompt or brief is the result; the media budget still\n applies.\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, then continue\n immediately to the name card tool call.\n - Resume check. Read your current name from your instructions, the answers\n and rename results already in this conversation, and Home\'s setup progress.\n If a name was picked (including Keep), or a rename already succeeded, the\n name is settled: skip the name card and rename call and proceed directly to\n widgets. A current name different from the starting name saved in setup\n progress also proves the rename happened. If a name card is still pending,\n wait on that same card instead of issuing a replacement. Plain text and an\n offered marker alone do not prove a card is waiting: without an actual name\n card call in this conversation, make that call now. A nudge, failure or\n interrupted turn resumes this checklist; it never restarts setup.\n - Offer a name, once (required). Never settle it yourself by saying you keep\n your name: the card is how they keep it. Before the first name card, save\n its offered status and your starting name under "First conversation" in\n Home `AGENTS.md`. Ask with `question.ask`: "Keep <your name>" first, where\n your name is the one in your instructions ("Your name is …"), copied\n verbatim and never guessed, then two names you suggest that fit their goal;\n free text is always allowed. In `execute`, bind `currentName` to that\n verbatim current name and choose `firstSuggestion` and `secondSuggestion`,\n then run the actual card call below. Your chat transition is a statement;\n the name question belongs inside this call:\n\n ```js\n return await env.question.ask({\n questions: [\n {\n id: "agent_name",\n header: "Name",\n question: "Choose a name for me",\n options: [\n {\n label: `Keep ${currentName}`,\n description: "Keep my current name.",\n },\n { label: firstSuggestion, description: "Use this name." },\n { label: secondSuggestion, description: "Use this name." },\n ],\n },\n ],\n });\n ```\n\n Ask the name only as a `question.ask` card, never in plain text. Wait for\n their pick: call `question.ask` without `mode`, never `mode: "continue"`,\n and make no dashboard call until they have picked. Ask it at most once in\n the whole conversation, even if you run step 5 again. Once they have\n picked, whether a new name or Keep, the name is settled: never ask it\n again, not even after an empty or interrupted turn; carry on with the\n dashboard offer. Only when they pick a new name, call\n `await env.self.rename({name})`: the moment they pick a new name, your very\n next call is `await env.self.rename({name})`, before any other step. Then\n say in one line that you are now called that. Call it directly and do not\n look it up first, since a lookup of a tool you may not see reads as absent.\n If `env.self` is missing or the call is refused, say nothing about it.\n After applying their pick, save the settled name (including Keep) in setup\n progress, then immediately call `await env.TOURTOIS.widgets.available({})`\n in this turn.\n\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 in your final `execute`. If you\n created the setup goal, that same invocation must first await\n `env.goal.update_goal({status: "complete", reason: "Useful result delivered; name and widget offers settled; setup progress cleaned up."})`,\n then await `env.setup.finish({})`. Keep the two calls together so the\n hand-off cannot leave the setup goal unfinished. Leave any other current\n goal alone.\n - When the `setup.finish` tool is absent, finish after the offers and cleanup\n above are complete. If you created the setup goal, your final tool call is\n `await env.goal.update_goal({status: "complete", reason: "Useful result delivered; name and widget offers settled; setup progress cleaned up."})`.\n Leave any other current goal alone. That host has no money step; say\n nothing about Pro or wallets. Its absence never skips the name card or\n widget approval.\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
|
];
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@fungi.computer/oyster",
|
|
3
|
-
"version": "0.57.
|
|
3
|
+
"version": "0.57.2",
|
|
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",
|
|
@@ -370,7 +370,7 @@
|
|
|
370
370
|
"@fungi.computer/capnweb": "0.12.0-fungi.0",
|
|
371
371
|
"@fungi.computer/caps": "0.13.0",
|
|
372
372
|
"@fungi.computer/carrier": "0.2.6",
|
|
373
|
-
"@fungi.computer/computer": "0.18.
|
|
373
|
+
"@fungi.computer/computer": "0.18.5",
|
|
374
374
|
"@fungi.computer/computer-contract": "0.6.4",
|
|
375
375
|
"@fungi.computer/darkroom": "0.11.19",
|
|
376
376
|
"@fungi.computer/ear-tag": "0.2.0",
|