Pantry architecture: a household agent where servers gate identity and only humans can approve payments
HowDevelop · x · 2026-11-23
The author breaks down Pantry's full architecture, solving "nobody owns the shopping" in shared flats:
- Identity gate: the server, not the model, decides who can read or change what; agents can never approve or pay
- Household context layer (SingleStore + cognee memory): who needs what, per-person rules (reasons stay private, e.g. "fragrance-free detergent"), and verified product facts from a Senso knowledge base instead of trusting store listings
- Autonomous agent flow: parse plain-language requests (Nebius + Nemotron), compare complete baskets only, deterministic code-based bill splitting to the cent — the only human step is each payer approving an exact plan version
- Post-approval automation: Stripe holds cards and charges only on success, refunds go to original payers, Gmail receipts and Slack updates
- Governance: Statsig/Amplitude/Tokens& telemetry is metadata-only, with a full audit trail
Notable: a roommate plugged in his own Claude via MCP + personal token without ever opening the Pantry app.
More from coding & agent
- One-session Opus 5.5 build: Rainline, a procedural neon driving game in a single HTML file — heypearlai · 2026-11-23
- Stop asking Gemini nicely: a post-answer checkpoint hook kills boilerplate follow-ups — bfrench · 2026-11-23
- Free-running personal agents can nerdsnipe you at any moment, researcher warns — MikePFrank · 2026-11-23
- DTC brand builds 3D unboxing simulator with Perplexity, live packaging costs — jeffgrimes9 · 2026-11-23
- Hacker built Hermes workflow plugin in 3 days via vibe coding, merged officially — Teknium · 2026-11-23
- Grok agent audits Amazon accounts via passkey and headless browser, saves users money — tristanbob · 2026-11-23