Continue CLIvsPoolside
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
Continue CLI
Continue · Terminal agent
#24OSSMCP
Panel
6.41 spec wins
- Reliability
- 6.2
- Usefulness
- 6.3
- Cost
- 8.0
- Longevity
- 5.2
“It installs by piping a URL straight into your shell, then politely asks permission before it touches a single file.”
Poolside
poolside · Terminal agent
#15MCP
Panel
6.92 spec wins
- Reliability
- 6.8
- Usefulness
- 7.0
- Cost
- 6.5
- Longevity
- 7.2
“One of its three network policies is named unsafe-allow-all, which is at least the most clearly labelled decision on this board.”
Spec by spec
| Spec | Continue CLI | Poolside |
|---|---|---|
| Architecture | ||
| Category | Terminal agent | Terminal agent |
| Runs | local | local, sandbox, cloud |
| Platforms | macos, linux, windows | macos, linux, windows |
| Context window | not documented | 1M tokens on Laguna S 2.1, 256k on XS 2.1 and M.1 |
| Protocols | ||
| MCP client | Yes | Yes |
| MCP server | No | No |
| Capabilities | ||
| Runs terminal commands | Yes | Yes |
| Multi-file edits | Yes | Yes |
| Git operations | Yes | Yes |
| Browser control | No | NoWeb search and fetch are documented; there is no DOM-level browser automation. |
| Sandboxed execution | NoThe docs describe running the CLI inside a Docker container, not sandboxing the agent in one. | YesTool commands run inside a container on your machine and need a local Docker engine; network policy is off, allow-list or unsafe-allow-all, enforced through a proxy container. |
| Multi-agent orchestration | No | Yes |
| Headless / CI mode | Yes | Yes`pool exec --prompt ... --output json` with POOLSIDE_API_KEY, plus a documented GitHub Actions integration. |
| Models | ||
| Backbone | any provider configured in config.yaml, Anthropic | Laguna S 2.1, Laguna XS 2.1, Laguna M.1 |
| Bring your own model | Yes | Yes |
| Local models | YesThe CLI reads the same ~/.continue/config.yaml provider schema as the IDE extensions, including a custom apiBase, so any local server can be configured; the CLI pages defer to that reference rather than naming Ollama or LM Studio. | YesDocumented local-run guides for Ollama and vLLM on Metal, plus full on-premises and air-gapped deployment. |
| Cost | ||
| Pricing model | byok | mixed |
| Starts at | $0/mo | n/a |
| Free tier | Yes | Yes |
| Bring your own key | Yes | Yes |
| Openness | ||
| Open source | Yes | No |
| License | Apache-2.0 | proprietary |
| GitHub stars | 36,084 | n/a |
Which one would each critic pick
| Critic | Continue CLI | Poolside | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 6.8 | 6.8 | no preference |
| El Crítico | 6.3 | 6.5 | Poolside — Isolation needs a container engine running on the machine and enforces network policy through a proxy container, which is a configuration rather than a boundary. |
| El Profesor | 6.5 | 6.5 | no preference |
| La Inversora | 5.3 | 7.0 | Poolside — Training your own models and selling deployments into other people's data centres is a capital-intensive bet on the one segment that cannot buy from a lab directly. |
| La Jefa | 6.0 | 7.0 | Poolside — It runs inside our own network, including air-gapped, on the Kubernetes platforms we already operate, and the enterprise price is a sales conversation. |
| El Hacker | 7.8 | 7.5 | Continue CLI — Apache-2.0 with the whole thing in a public monorepo, and a provider block that takes a custom apiBase, which is how my own server gets in. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.