git404hub

what is pantry fr?

acoyfellow/pantry — explained in plain English

Analysis updated 2026-07-27 · repo last pushed 2026-07-11

8TypeScriptAudience · developerComplexity · 3/5ActiveSetup · moderate

tl;dr

Pantry is a code snippet store for AI agents. You save reusable JavaScript functions once, and any AI tool can fetch the exact saved version on demand without re-deriving the logic each time.

vibe map

mindmap
  root((repo))
    What it does
      Stores code recipes
      Returns code never runs
      Private by default
    How it works
      Named JS functions
      Metadata and tags
      Bearer token auth
    Tech stack
      Cloudflare Workers
      D1 storage
      TypeScript
    Use cases
      AI coding agents
      Shared team libraries
      MCP clients
    Audience
      AI agent developers
      Coding teams
      Tool integrators

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Save a text-transformation utility your AI agents use repeatedly so they fetch the same vetted version each time.

VIBE 2

Build a shared library of reusable functions that multiple AI tools can discover and retrieve via API.

VIBE 3

Connect an MCP client like Claude Desktop to fetch recipes on demand during coding sessions.

VIBE 4

Use curl or any HTTP client to list and pull specific recipes for ad-hoc automation workflows.

what's the stack?

TypeScriptCloudflare WorkersD1

how it stacks up fr

acoyfellow/pantryabdulkader-safi/obsidian-image-magick-pluginsacartag7/mcp-sso
Stars888
LanguageTypeScriptTypeScriptTypeScript
Last pushed2026-07-11
MaintenanceActive
Setup difficultymoderateeasymoderate
Complexity3/52/54/5
Audiencedevelopergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires a Cloudflare Workers account with D1 database provisioning and a bearer token for authentication.

No license information is provided in the explanation, so default copyright restrictions may apply.

in plain english

pantry is a storage shelf for reusable code snippets that AI agents can fetch on demand. Instead of an AI assistant re-deriving the same logic every time it runs, you save that code once as a "recipe," and any tool can retrieve the exact saved version whenever needed. The key promise is that pantry stores and returns your code but never runs it, the calling tool decides whether and how to execute it. A recipe is a named JavaScript function with metadata: a description, an input schema, capability tags, and a version. You push recipes to the store via a simple API or a command-line tool. When an agent needs a piece of logic, it lists available recipes, fetches the one it wants, reviews the code, and then runs it in whatever environment it chooses. The store is private by default, scoped to an owner via a bearer token, though authors can optionally mark recipes as shared so other owners can discover and read them. This is designed for teams running AI coding agents or orchestrators that benefit from a shared library of vetted, reusable functions. For example, if you have a text- transformation utility your agents use repeatedly, you save it once as a recipe. Any connected tool, an MCP client like Claude Desktop, the Pi agent framework, or a plain curl command, can fetch that same recipe. The capability tags help agents reason about what a recipe does before fetching it. The project runs on Cloudflare Workers and uses D1 for storage, which keeps it lightweight and globally distributed. Security is straightforward: every request requires a bearer token, owner scoping prevents cross-access, and the server fails closed if misconfigured. Notably, the demo runner that executes fetched code is explicitly called out as not a sandbox, it does some basic scanning but the project is honest that running untrusted code is the caller's responsibility.

prompts (copy fr)

prompt 1
Set up a Cloudflare Workers project with a D1 database that stores named JavaScript functions as recipes with metadata like description, input schema, capability tags, and version. Include bearer token authentication scoped per owner.
prompt 2
Build a CLI tool that pushes a JavaScript function as a recipe to a pantry store API, including fields for description, input schema, and capability tags.
prompt 3
Create an MCP-compatible endpoint that lists available recipes from a pantry store and lets an AI agent fetch a specific recipe by name, returning the raw code for the agent to execute.
prompt 4
Design a REST API for a recipe store where every request requires a bearer token, owners are isolated from each other, and recipes can optionally be marked as shared for cross-owner discovery.

Frequently asked questions

what is pantry fr?

Pantry is a code snippet store for AI agents. You save reusable JavaScript functions once, and any AI tool can fetch the exact saved version on demand without re-deriving the logic each time.

What language is pantry written in?

Mainly TypeScript. The stack also includes TypeScript, Cloudflare Workers, D1.

Is pantry actively maintained?

Active — commit in last 30 days (last push 2026-07-11).

What license does pantry use?

No license information is provided in the explanation, so default copyright restrictions may apply.

How hard is pantry to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is pantry for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.