On 22 October 2026 the Agentic AI Foundation announced four new hosted projects: Agent Skills from Anthropic, Open Responses from OpenAI, OpenEnv from Hugging Face, and OpenSandbox from Alibaba. AAIF is now at 10 projects in its first year, up from three at launch in December 2025. Goose was not one of the four. It is already on that list, next to MCP, AGENTS.md, A2A, Agent Router, and agentgateway.
If you opened the press release hoping flisk resource --language goose would start working, it will not. Flisk scaffolds Python, Go, Rust, and Node. Goose, in this announcement, is the AI agent.
What actually changed today
| Project | Who contributed it | Layer |
|---|---|---|
| Agent Skills | Anthropic | Reusable instructions, scripts, and resources an agent loads on demand |
| Open Responses | OpenAI | One request/stream schema across model providers |
| OpenEnv | Hugging Face | Containerized RL environments, MCP plus Gym |
| OpenSandbox | Alibaba | Sandbox lifecycle API, Docker and Kubernetes runtimes |
The quote worth keeping is the scope, not the guest list. Manik Surtani, AAIF CTO, said the foundation's job is a neutral place for shared standards, with no single company controlling the outcome. That is governance. It is not a Flisk release.
The conference attached to the announcement is AGNTCon + MCPCon North America, 22–23 October 2026, San Jose. Nothing in that release mentions service.json, Tilt, or a laptop stack.
The Goose announcement people still mix up with this one
Goose's own move was earlier, and it is the one that changes bookmarks.
- 9 December 2025: Linux Foundation forms AAIF. Founding projects are MCP, goose, and AGENTS.md. Block contributes goose.
- 7 April 2026: Michael Neale posts that the repo left
block/gooseforgithub.com/aaif-goose/goose, and docs moved to goose-docs.ai. Old links redirect. The agent, license, and mission did not change. - 22 October 2026: four other projects join the same foundation. Goose stays where it already was.
If a recipe, blog, or Flisk AGENTS.md still clones block/goose, update the remote:
git remote set-url origin git@github.com:aaif-goose/goose.git
That is the whole operational takeaway of the April post. The October post does not give you a second remote to change.
What this means next to flisk.sh
Flisk is the local runtime. One service.json per service, then flisk up. Docker runs the containers. Tilt watches them. Traefik is the local front door. It is not a deploy tool. Production stays on Helm, or on whatever you already ship.
Goose is the process that may run those commands. AAIF hosting it means the agent is under the same neutral roof as MCP and, as of today, Agent Skills. It does not mean Flisk gained a Goose backend, a Goose migrator, or an AAIF sandbox.
A practical split:
| You wanted | Use | Do not use |
|---|---|---|
| A local API in the shop stack | flisk resource orders-api --type backend --language go --stack shop --yes |
--language goose |
An agent that runs flisk doctor and stops |
Goose CLI, recipe, .gooseignore on .autogenerated/
|
A hand-edited Dockerfile |
| Portable agent skills | Agent Skills, once you have read the spec | A fifth tag and a fake Flisk flag |
| A place for the agent to execute code | Your existing Flisk container, or OpenSandbox if you adopt that project | Pretending Flisk is a sandbox standard |
Agent Skills is the piece most likely to show up in a Flisk repo later. A skill is a folder of instructions and scripts. A Flisk skill, if you write one, should say: languages are python, go, rust, node; never edit .autogenerated/; flisk config verify after every generate. That is a markdown file you own. AAIF did not publish it for you today.
OpenSandbox is the piece most likely to be confused with Flisk. Both can sit on Docker. Flisk's job is "start this product's services on my laptop from service.json." OpenSandbox's job, in the announcement, is a sandbox protocol for agent execution, eval, and training, with Docker and Kubernetes runtimes. One generates your app's local wiring. The other isolates an agent. Do not merge them because both words appear next to "Docker."
What I would not write in the same post
- That Goose joined AAIF today. It joined at formation, and the repo move finished on 7 April 2026.
- That Flisk is an AAIF project. It is not. Site: flisk.sh. Package:
@flisk-sh/flisk. - That Open Responses replaces the model config in
goose configure. It is a spec. Your provider key still lives in Goose.
Source for the four projects: the Linux Foundation release, 22 October 2026. Source for the repo move: goose has a new home.
Top comments (0)