@fungi.computer/grove

中文文档
0.14.0发布于 2026/11/16MITES Module近 30 天下载 1.2万

Grove: conversations with agents that call your other Apps, for Oyster

原始使用文档
文档目录6 节
  1. What you can do
  2. Get it
  3. Change it
  4. Agent tools
  5. Build and check
  6. License

Grove (@fungi.computer/grove)

Grove is where you talk to your agents: an inbox of conversations, and agents that answer by calling your other Apps.

Grove: the conversation list beside a finished conversation in which the agent ran three scripts against Bonsai and listed the repositories with open changes

Grove is one of the starter Apps of Oyster, the open App host that runs on your own Cloudflare account. On Oyster, agents run on Workers AI, and every App you install becomes a tool they can call as code, as in the picture above, where the agent calls Bonsai's repos.list.

What you can do

  • Create an agent with New Agent, then start a conversation with it.
  • Read every conversation in one inbox, grouped as Needs you, Working, Finished and Unavailable. The agent rail counts what needs you.
  • Filter the inbox to one agent by clicking its face.
  • Send a follow-up while the agent works (Queue), stop it (Cancel), retry a failed turn, or fork a conversation from any message.
  • Watch each tool call inline, with its script, timing and result.
  • Collapse the agent rail and the inbox, or drag the inbox wider. In a phone or a narrow window, Agents and conversations opens both as one sheet.
Grove in the light theme: the agent rail and the conversation list beside an empty conversation pane

Get it

Grove installs with the other starter Apps. On a deployed Oyster (see the Oyster quick start), run:

export OYSTER_URL=https://oyster.<your-subdomain>.workers.dev
export OYSTER_OWNER_KEY=<your owner key>
npx oyster install-apps

The installer clones this repository and the six others, seeds each on your Oyster with git push, builds them on your Computer and installs them. Sign in at $OYSTER_URL/login with the owner key; the Tourtois desktop opens with Grove's inbox on it. Run install-apps again to update; each App keeps its data.

Change it

Every installed App is also a template you can fork on your own Oyster. Fork Grove into a Bonsai repository and clone it with ordinary git:

curl -X POST -H "Authorization: Bearer $OYSTER_OWNER_KEY" -H 'content-type: application/json' \
  -d '{"appId":"app_grove","name":"my-grove"}' \
  $OYSTER_URL/apps/bonsai/methods/apps.fork
git -c http.extraHeader="Authorization: Bearer $OYSTER_OWNER_KEY" \
  clone $OYSTER_URL/git/bonsai/my-grove.git

The reply names your fork's App id and repository. Push your edits, open the repository in Bonsai and choose Settings, then Build & install with that App id and your commit as git:<sha>. Install the Release at grove to replace the running Grove, or at a new id to keep both.

To work from GitHub instead, fork this repository and point the installer at your forks with --repositories <base URL> and --ref <branch or tag>. The installer reads all seven starter Apps from that base, so fork them under one account.

Agent tools

Agents and scripts call Grove through Oyster's MCP endpoint, or at POST $OYSTER_URL/apps/grove/methods/<name> with a key; see Git, keys and MCP.

MethodWhat it does
listInboxReads a page of your inbox.
listSessions({agentId})Lists one agent's conversations.
openInboxItemMarks a conversation as seen and returns it.
sendMessage({..., requestId, text})Sends a follow-up into an existing conversation without interrupting it, up to ten a minute per conversation.

sendMessage requires a non-empty requestId of at most 256 UTF-8 bytes. Mint it once per user intent and retain it with the unchanged message. Reuse that same input when retrying an UNKNOWN outcome (for example, a lost response); do not mint a fresh ID inside the retry. A new user intent needs a new ID.

This is a breaking API change: callers that omitted requestId must supply it. Grove forwards it unchanged through AGENTS.send; neither the bridge nor the standalone host generates a replacement.

Grove also puts its inbox on the Tourtois desktop, so you see what needs you without opening the App.

Build and check

Grove is a React App built with Vite. Conversations render with Parakeet and read their state from Shiitake sessions; controls come from Caps.

pnpm install
pnpm build
pnpm typecheck
pnpm test

src/inbox.tsx owns the agent list, the inbox and the open conversation. src/inbox-list.tsx draws the inbox, and Parakeet's conversation-opening module switches conversations without losing your draft when a read fails. The agent tools are in backend/methods.ts, and package.json declares the permissions the App asks for.

License

MIT. See LICENSE.

版本与发布记录

@fungi.computer/grove 共发布 70 个版本,首次发布于 2026/10/17;过去 12 个月发布了 70 个版本。

版本发布日期距今
0.14.0latest2026/11/16今天
0.13.132026/11/15今天
0.13.122026/11/15今天
0.13.112026/11/15今天
0.13.102026/11/15今天
0.13.92026/11/15今天

其他发布通道:next → 0.10.17。

关于 @fungi.computer/grove 的常见问题

@fungi.computer/grove 是什么?

Grove: conversations with agents that call your other Apps, for Oyster

如何安装 @fungi.computer/grove?

在项目目录运行 npm install @fungi.computer/grove,或使用 pnpm add / yarn add / bun add。

@fungi.computer/grove 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/fungi.computer__grove 是否存在。

@fungi.computer/grove 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@fungi.computer/grove 可以商用吗?

@fungi.computer/grove 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@fungi.computer/grove 的下载量有多少?

根据 npm 官方下载统计,@fungi.computer/grove 在 2026/10/16 – 2026/11/14 这 30 天内被下载 11,588 次,日均约 386 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@fungi.computer/grove 还在维护吗?

最新版本 0.14.0 发布于 2026/11/16(今天);至今共发布 70 个版本,其中过去 12 个月发布了 70 个;首次发布于 2026/10/17。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。