G
goat-si/goat
GOAT: one control surface for Claude Code, Codex, Cursor and more, across your machines
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 89 ★ · goat-si/goat · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-28 · last seen 2026-11-14 · seen 19× · listed by 1 sources
- Score
- score 103 · 89 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
goat-si/goat;first catalogued 2026-10-28;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.Install ·
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Downloads ·
User guides ·
How it is built
GOAT runs the coding agents you already use, such as Claude Code, Codex and Cursor, on the machines you own: your laptop, a desktop at home, an SSH server or a cloud machine. You steer all of them from one place, whether that is the desktop app, a browser or your phone. Agents can start work on another machine, follow it, and hear back when it finishes, and Fleet shows you what is running and what needs you.
A synthetic demo project and conversation.
## Every machine is an environment
Each machine you work on runs a GOAT server. The server and the state it owns (projects, threads, provider sign-ins and memory) form an environment. Clients connect to as many environments as you like, and an environment can reach others: an SSH host gets its GOAT runtime on first use, a GOAT server you already run can be linked for agents with a pairing link, and on Windows a WSL distro runs its own environment.
## What GOAT adds
GOAT began as a fork of T3 Code and keeps its fast, event-sourced core. On top of it, GOAT adds:
GOAT Bot. One standing conversation that is not tied to a project. Ask it for work and it starts a coding thread in the right project and machine, then reports the result. The same bot answers in Slack, and over iMessage when the server runs on a Mac.
Agents that cross machines. An agent can browse folders on an SSH host, start a thread or worktree there, move a thread over with its uncommitted changes, and wait for the result. Hosts download their own GOAT runtime, and Boat cloud machines work like any other SSH host.
Fleet. One view of every connected machine and the agents working on it, with counts of threads that are running or waiting for you.
Memory. Finished conversations become memories scoped to all projects, one project or one thread. You can import memories from Codex, Claude and OMO, and share them across devices through a hub.
Orchestration tools. The GOAT MCP server gives agents goat tools to launch threads, watch them, get notified when they end, and report results to the thread that started them. Outside agents such as Claude Code, Codex and ChatGPT can connect to the same server.
Cloud agents. Claude Cloud, Cursor Cloud and Devin Cloud appear as providers next to the local ones.
Its own desktop app. The GOAT desktop app has its own app ID, data folder and update feed, so it installs beside the T3 Code app without sharing state. Its command line is goat.
## Quick start
1. Set up a provider on the machine that will do the work. Claude Code, Codex, Cursor, Grok Build, OpenCode, Antigravity, Pi, Muse Code, ACP agents and the cloud providers are supported. The provider table covers the command-line providers, ACP providers covers ACP agents, and cloud providers sign in from Settings → Providers.
2. Install GOAT. Download the desktop app for macOS, Windows or Linux from goat-si/goat-releases, or install the goat command:
bash
curl -fsSL https://raw.githubusercontent.com/goat-si/goat-releases/main/install.sh | sh
On Windows, run irm https://raw.githubusercontent.com/goat-si/goat-releases/main/install.ps1 | iex in PowerShell. Intel Macs have the desktop app but no goat executable; see Intel Macs.
User guides ·
How it is built
GOAT runs the coding agents you already use, such as Claude Code, Codex and Cursor, on the machines you own: your laptop, a desktop at home, an SSH server or a cloud machine. You steer all of them from one place, whether that is the desktop app, a browser or your phone. Agents can start work on another machine, follow it, and hear back when it finishes, and Fleet shows you what is running and what needs you.
A synthetic demo project and conversation.
## Every machine is an environment
Each machine you work on runs a GOAT server. The server and the state it owns (projects, threads, provider sign-ins and memory) form an environment. Clients connect to as many environments as you like, and an environment can reach others: an SSH host gets its GOAT runtime on first use, a GOAT server you already run can be linked for agents with a pairing link, and on Windows a WSL distro runs its own environment.
## What GOAT adds
GOAT began as a fork of T3 Code and keeps its fast, event-sourced core. On top of it, GOAT adds:
GOAT Bot. One standing conversation that is not tied to a project. Ask it for work and it starts a coding thread in the right project and machine, then reports the result. The same bot answers in Slack, and over iMessage when the server runs on a Mac.
Agents that cross machines. An agent can browse folders on an SSH host, start a thread or worktree there, move a thread over with its uncommitted changes, and wait for the result. Hosts download their own GOAT runtime, and Boat cloud machines work like any other SSH host.
Fleet. One view of every connected machine and the agents working on it, with counts of threads that are running or waiting for you.
Memory. Finished conversations become memories scoped to all projects, one project or one thread. You can import memories from Codex, Claude and OMO, and share them across devices through a hub.
Orchestration tools. The GOAT MCP server gives agents goat tools to launch threads, watch them, get notified when they end, and report results to the thread that started them. Outside agents such as Claude Code, Codex and ChatGPT can connect to the same server.
Cloud agents. Claude Cloud, Cursor Cloud and Devin Cloud appear as providers next to the local ones.
Its own desktop app. The GOAT desktop app has its own app ID, data folder and update feed, so it installs beside the T3 Code app without sharing state. Its command line is goat.
## Quick start
1. Set up a provider on the machine that will do the work. Claude Code, Codex, Cursor, Grok Build, OpenCode, Antigravity, Pi, Muse Code, ACP agents and the cloud providers are supported. The provider table covers the command-line providers, ACP providers covers ACP agents, and cloud providers sign in from Settings → Providers.
2. Install GOAT. Download the desktop app for macOS, Windows or Linux from goat-si/goat-releases, or install the goat command:
bash
curl -fsSL https://raw.githubusercontent.com/goat-si/goat-releases/main/install.sh | sh
On Windows, run irm https://raw.githubusercontent.com/goat-si/goat-releases/main/install.ps1 | iex in PowerShell. Intel Macs have the desktop app but no goat executable; see Intel Macs.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/goat-si-goat/)
- Source
- github · https://github.com/goat-si/goat
- Browse by field
- Open source
- Traction
- 89 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.