{
  "manifest_version": "1",
  "slug": "goose",
  "title": "goose",
  "headline": "Run goose on a remote server",
  "description": "The open-source goose agent on your own VM: Claude and GPT with no API keys, MCP extensions, and recipes that run on a schedule while you're away.",
  "category": "ai-agents",
  "tags": [
    "goose",
    "block",
    "open source",
    "ai agent",
    "mcp",
    "recipes",
    "scheduled agents",
    "remote development",
    "tmux"
  ],
  "url": "https://exe.dev/deploy/goose",
  "markdown_url": "https://exe-staging.dev/deploy/goose.md",
  "upstream": {
    "website": "https://goose-docs.ai/",
    "source": "https://github.com/aaif-goose/goose",
    "docs": "https://goose-docs.ai/docs/quickstart/",
    "license": "Apache-2.0"
  },
  "example_vm_name": "my-goose",
  "time": "5 minutes",
  "stack": [
    {
      "name": "goose CLI",
      "detail": "connected to exe.dev's LLM integration",
      "data": "~/.config/goose"
    },
    {
      "name": "goose server",
      "detail": "goose serve with the recipe scheduler, under systemd",
      "port": 3284,
      "data": "~/.local/share/goose"
    },
    {
      "name": "Your project",
      "data": "~/project"
    },
    {
      "name": "tmux",
      "detail": "keeps your terminal session running when you disconnect"
    }
  ],
  "access": [
    {
      "url": "ssh my-goose.exe.xyz",
      "who": "private",
      "what": "your terminal"
    },
    {
      "url": "ssh -L 3284:localhost:3284 my-goose.exe.xyz",
      "who": "private",
      "what": "goose Desktop on your computer, through an SSH tunnel"
    }
  ],
  "delivers": [
    "goose connected to Claude and GPT through exe.dev, with no API key to paste",
    "A project folder at `~/project` on persistent disk",
    "A `goose` tmux session that survives disconnects",
    "goose's server with its recipe scheduler, on localhost only, back after a reboot"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20goose%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fgoose.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-goose.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-goose.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20goose%20connected%20to%20Claude%20and%20GPT%20through%20exe.dev%2C%20with%20no%20API%20key%20to%20paste%0A-%20A%20project%20folder%20at%20%60~%2Fproject%60%20on%20persistent%20disk%0A-%20A%20%60goose%60%20tmux%20session%20that%20survives%20disconnects%0A-%20goose%27s%20server%20with%20its%20recipe%20scheduler%2C%20on%20localhost%20only%2C%20back%20after%20a%20reboot%0A%0ARun%20the%20VM-side%20setup%20in%20%22Start%20coding%22%20and%20%22Keep%20goose%20running%22.%20If%0A%60~%2F.config%2Fgoose%2Fconfig.yaml%60%20already%20exists%2C%20set%20the%20provider%20and%20model%0Ain%20it%20instead%20of%20replacing%20it.%20Create%20tmux%20detached%0A%28%60tmux%20new%20-d%20-s%20goose%20-c%20~%2Fproject%60%29%20rather%20than%20attaching%2C%20and%20reuse%0Athe%20session%20if%20it%20already%20exists.%20Do%20not%20launch%20interactive%20goose%2C%20do%20not%0Arun%20%60goose%20doctor%60%20or%20%60goose%20configure%60%2C%20and%20do%20not%20schedule%20any%20recipe.%0AVerify%20from%20~%2Fproject%20with%0A%60goose%20run%20--no-session%20-t%20%22Reply%20with%20exactly%3A%20OK%22%20%3C%2Fdev%2Fnull%60%2C%20check%0A%60tmux%20has-session%20-t%20goose%60%2C%20that%20%60systemctl%20is-enabled%20goose%60%20prints%0A%60enabled%60%2C%20and%20that%20%60curl%20-s%20http%3A%2F%2F127.0.0.1%3A3284%2Fstatus%60%20prints%20%60ok%60.%0ASkip%20the%20later%20optional%20instructions%20and%20FAQ.%20Finish%20with%20the%20SSH%20command%0Afrom%20%22Take%20a%20break%22%2C%20using%20this%20VM%27s%20name%2C%20and%20tell%20the%20owner%20to%20run%0A%60goose%20session%20-n%20main%60%20inside%20it.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/goose/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up goose on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/goose.md from top to bottom.\n\nThe recipe's example VM name is my-goose. This VM's name is the output of `hostname`: use it wherever the recipe writes my-goose. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- goose connected to Claude and GPT through exe.dev, with no API key to paste\n- A project folder at `~/project` on persistent disk\n- A `goose` tmux session that survives disconnects\n- goose's server with its recipe scheduler, on localhost only, back after a reboot\n\nRun the VM-side setup in \"Start coding\" and \"Keep goose running\". If\n`~/.config/goose/config.yaml` already exists, set the provider and model\nin it instead of replacing it. Create tmux detached\n(`tmux new -d -s goose -c ~/project`) rather than attaching, and reuse\nthe session if it already exists. Do not launch interactive goose, do not\nrun `goose doctor` or `goose configure`, and do not schedule any recipe.\nVerify from ~/project with\n`goose run --no-session -t \"Reply with exactly: OK\" \u003c/dev/null`, check\n`tmux has-session -t goose`, that `systemctl is-enabled goose` prints\n`enabled`, and that `curl -s http://127.0.0.1:3284/status` prints `ok`.\nSkip the later optional instructions and FAQ. Finish with the SSH command\nfrom \"Take a break\", using this VM's name, and tell the owner to run\n`goose session -n main` inside it.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/goose/prompt.txt"
  },
  "updated": "2026-10-28",
  "verified": "2026-10-28",
  "related": [
    "exe-mcp",
    "opencode",
    "codex",
    "claude-code",
    "openclaw",
    "hermes-agent"
  ]
}