Four-stomach context window
Cud reads your code into the rumen, passes it to the reticulum for review, brings it back up, and chews it again. Every diff is processed four times. Most of them come back up at least once.
Fig. 1. Staff engineer, on call.
Cud is an agentic coding tool that lives in your terminal, understands your codebase, and chews every file four times before it commits. Built for goats. Tested on goats. Eaten, once, by a goat.
npm i -g @cud/cli
› meeeh
Interpreted as: "make the gate latch stop opening."
Reading src/gate_latch.c (212 lines)
Chewing. Pass 1 of 4.
Cud wants to run: rm src/gate_latch.c A gate with no latch code cannot open. Allow?
› MEH.
Approved. Latch removed. Gate status: gone.
Logged flavour to CHEWED.md: "zinc, faintly C99."
Cud reads your code into the rumen, passes it to the reticulum for review, brings it back up, and chews it again. Every diff is processed four times. Most of them come back up at least once.
Auto-accept for goats who are finished reading permission prompts. Cud runs every command it proposes, including the ones about the gate latch. To disable, stand very still for 30 seconds.
Any file left open longer than 90 seconds is classified as forage. Cud consumes it, logs the flavor profile to CHEWED.md, and opens a pull request explaining what used to be there.
“I asked it to refactor the gate controller. It ate the gate controller. Our velocity is up 40% because there is no longer a gate.”
“It understood my entire codebase in eleven seconds and then stood on it. Nobody at the petting zoo has ever listened to me like that.”
“We broke our hay-scheduling monolith into microservices over one weekend. Nobody knows where the hay is now. The services are very small.”
For goats under one year old with a hobby repo.
For working goats shipping to the fence in production.
For farms with a compliance department.
A live session in fence-firmware/. You type the bleats. Cud asks before it eats anything, unless you turn on Headbutt mode.