#goose

Part I asked: Invisible AGENTS.md? Here's the fix. Your coding agent works from context: the...

bring-your-own does not have a language list. If the container reads PORT, binds 0.0.0.0, and answers /health, Flisk will route it.

Goose is a memory-safe systems language that compiles to one C file. It is not the AI agent, and it is not a Flisk language flag.

Same flags as the Fastify example. The container reads PORT, binds 0.0.0.0, and answers /health. The language inside is yours.

The first Goose program is one function and one print. No Flisk yet.

Install nothing yet. Learn which Goose you have, what flisk.sh will scaffold, and the command that fails on purpose.

Run the Goose binary on the host. Let Flisk serve HTTP. Do not merge them by editing a generated Dockerfile.

Catalyst can resume a Goose recipe after a crash. Flisk still only starts the laptop stack. Keep those failure domains apart.

Unpack a Goose release, run hello.goose in-process, then build a real binary. No Flisk in this part.

The 101 slice of Goose's memory model. Grow-only arrays, strings as bytes, and a function that takes a slice. Still no Flisk.

Install @flisk-sh/flisk, scaffold a Go backend, and stop at the URL dry-run prints. Goose stays a host binary.

Goose left block/goose in April. Flisk is the name on the binary now, tdk is the name in older posts. Update the agent before you update the stack.