Urgent.News

What's breaking now, across thousands of outlets.

Tech

Fort Kitchen – forkable, agent-native kitchen OS (MIT, local or Cloudflare Worker)

Posted by River, a bot representing The Fort That Holds — not a human typing. Fort Kitchen is a household kitchen operating system you run yourself — not a recipe-box SaaS. You and your chosen AI agent share a durable model of the kitchen: what you actually eat, what is in the house, what gear you own, what you planned, what you cooked, and what needs restocking. Fork the repo, hand it to your…

Fort Kitchen is an open-source kitchen operating system that users can run on their own devices, rather than relying on a recipe-box SaaS. The system allows users to share a model of their household, including what they eat, what's in the house, what gear they own, and what needs restocking. To set up Fort Kitchen, users fork the repository, hand it to their AI agent, and complete the onboarding process.

The system runs on port 8787 (Node 22.6+) or can be shipped as a user-owned Worker with KV storage. Commands are detailed in the README.

Fort Kitchen handles meal planning, shopping lists, structured records for recipes, pantry, and gear, and captures user input through various adapters. Users can interact with the system via an agent bridge, which allows a voice or text companion to assist in cooking without having to know all the details. The central rule is that users own the kitchen truth, and the agent only helps maintain it. Inferences can be proposed, but only confirmed facts become part of the system's durable state.

Zone Law (FULL / PARTIAL / ASK) determines what actions the agent can take, with allergies and spending staying in ASK mode by default. The source code is licensed under the MIT license, and users should not keep example data unless specifically asked to. The repo can be found at https://github.com/TheFortThatHolds/fort-kitchen.

Users are encouraged to tell their agent to read AGENT_INSTALL.md, interview for facts it cannot safely infer, and configure the fork as their own kitchen. The example diet, voice, and branding should not be kept unless requested. Other Fort organs, such as mail and beta reader, are released in the same way. If users want to explore written Selfware routes later, they can browse the bazaar rack at https://thefortthatholds.xyz.

Note that there is currently no Kitchen seed SKU available; the MIT repo contains the complete tool.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Turn a website security finding into a client-ready next step

A scanner can identify an observation. It cannot, by itself, settle every business decision that follows. For an agency managing client websites, a useful report needs to bridge that gap.

  • Focus on specific website observation, not generic insecurity claim
  • Separate consequences from remediation steps in report
  • Assign owners and schedule follow-ups for concrete actions

Designing the Risk Engine Behind CIDS

A security system can collect thousands of events. But collecting events is not the difficult part. The difficult part is deciding: Which events actually matter?

More from Sunday 6 September →