Tools and accounts
Choose your repository host, deployment platform, databases, and agent clients.
Suped 0.6.0 includes the tool catalogue and guided account setup below. Run these commands from your host terminal. See getting started for requirements and upgrading an existing workspace.
Suped prepares a workspace around the tools you use. Choose GitHub or GitLab, Cloudflare or Vercel, Supabase or Neon—or combine the services your work needs. Your agent uses their ordinary commands and saved account connections inside the same Linux home.
Choose your tools
npx suped@latest catalog
npx suped@latest setupsuped catalog lists the available CLIs by category without starting Docker. suped setup installs your selection and offers to connect each account. The examples use npx suped@latest; after npm i -g suped@latest, the shorter suped command works too.
The guided setup offers websites and web apps, data and scripts, the full catalogue, or the base workspace. Choose providers within each category, select more than one, or enter none to skip it. The web workflow suggests GitHub and Cloudflare; those defaults are editable. The first interactive shell or up run also offers setup when the workspace has not been configured yet.
Setup adds tools to the workspace. Rerunning it with fewer tools selected, including the base-only choice, does not uninstall existing tools or remove their account configuration.
To specify tools directly:
npx suped@latest setup gitlab vercel neonFor unattended installation, skip authentication:
npx suped@latest setup github netlify turso --skip-authRun login interactively afterward. Setup installs tools in the workspace, not on your host, and does not create cloud resources or register service accounts.
Available CLIs
The catalogue contains 23 optional CLIs. The base workspace already includes Git, Node 22, Ubuntu’s Python 3.12, and other development tools. A browser is opt-in, built into the image with --with browser.
Repositories
| Selection | Command | Use it for |
|---|---|---|
github |
gh |
GitHub: repositories, issues, pull requests, and Git authentication |
gitlab |
glab |
GitLab: repositories, merge requests, issues, and CI pipelines |
Hosting and deployment
| Selection | Command | Use it for |
|---|---|---|
cloudflare |
wrangler |
Cloudflare: Workers, Pages, and related services |
vercel |
vercel |
Vercel: web apps, previews, domains, and environment variables |
netlify |
netlify |
Netlify: sites, previews, functions, and environment variables |
railway |
railway |
Railway: application services, databases, deployments, and logs |
fly |
fly |
Fly.io: apps, Machines, volumes, secrets, and logs |
render |
render |
Render: web services, background workers, databases, and deployments |
Databases and app backends
| Selection | Command | Use it for |
|---|---|---|
supabase |
supabase |
Supabase: hosted projects, migrations, and functions |
neon |
neon |
Neon: serverless Postgres projects, databases, and branches |
turso |
turso |
Turso: hosted SQLite and libSQL databases, replicas, and branches |
planetscale |
pscale |
PlanetScale: managed Postgres and Vitess databases, branches, and deploy requests |
Cloud infrastructure
| Selection | Command | Use it for |
|---|---|---|
firebase |
firebase |
Firebase: Hosting, Firestore, authentication, functions, and projects |
digitalocean |
doctl |
DigitalOcean: App Platform, Droplets, managed databases, and infrastructure |
Payments
| Selection | Command | Use it for |
|---|---|---|
stripe |
stripe |
Stripe: payment integration, test data, products, and webhook development |
Agent clients
| Selection | Command | Use it for |
|---|---|---|
codex |
codex |
Codex: OpenAI’s coding agent, running inside your workspace |
claude |
claude |
Claude Code: Anthropic’s coding agent, running inside your workspace |
Both clients are optional. You can bring another agent or use a host agent through suped exec. Agent accounts are separate from your service accounts. See agents for the handoff and MCP connections for connecting apps to a compatible agent client.
Languages and runtimes
| Selection | Command | Use it for |
|---|---|---|
python |
python3 |
CPython 3.14.7 with uv and uvx: packages, virtual environments, and scripts |
go |
go |
Go 1.27.1: building, testing, and module management, with gofmt |
deno |
deno |
Deno 2.9.6: JavaScript and TypeScript with a formatter, linter, and test runner built in |
bun |
bun |
Bun 1.4.2: JavaScript and TypeScript with a fast npm-compatible package manager |
Node 22 is already in the base image. These are the other runtimes an agent needs to run code, build, and test locally. Each is pinned and checksum-verified against the publisher’s own figures, and unpacks into the persistent home rather than the image, so picking one up later does not mean rebuilding the workspace.
Ubuntu’s python3 (3.12) is in the base image and is externally managed, so pip install outside a virtual environment refuses to run. Selecting python installs uv and uvx and puts a current CPython ahead of Ubuntu’s on PATH. System scripts with an absolute #!/usr/bin/python3 are unaffected.
Containers
| Selection | Command | Use it for |
|---|---|---|
docker |
docker |
Docker client, with Compose and Buildx: build and run containers during local development |
This installs the client only. Suped runs no daemon and does not mount your host’s Docker socket. The Compose and Buildx plugins install to ~/.docker/cli-plugins, where the CLI looks for subcommands, so they are not on PATH.
Give the client a daemon yourself:
# A remote or rootless daemon. Nothing of the host is exposed.
npx suped@latest exec env DOCKER_HOST=ssh://you@builder docker ps
# The host's daemon.
npx suped@latest -v /var/run/docker.sock:/var/run/docker.sockThe second form is a privilege grant, not a convenience: a container started from inside the workspace can mount the host filesystem, so anything in the workspace effectively has root on your host. Prefer the first unless you have decided otherwise for a workspace you fully trust.
Workspace
| Selection | Command | Use it for |
|---|---|---|
herdr |
herdr |
Herdr: run several agents side by side in one terminal and reattach later |
Nothing in this category has an account. suped tools herdr reports it as installed rather than waiting on a connection, and setup does not offer to connect one.
Example combinations
These are selections you can make, not separate editions of Suped:
| Work | Example selection |
|---|---|
| A web app with hosted Postgres | gitlab vercel neon |
| A site with functions and a small database | github netlify turso |
| An app using Supabase services | github cloudflare supabase |
| A service with background jobs | gitlab render planetscale |
| Scripts that manage cloud infrastructure | github digitalocean python |
| Local work in a compiled language | github go |
| Building and checking container images | github docker |
Add stripe when working on payments, or an agent client if you want it installed inside. You can add another provider at any time with setup.
Connect your accounts
Use accounts you already have with the selected services. Suped runs each vendor’s own CLI sign-in flow inside the workspace. Complete the browser or device-code step on your host when prompted.
npx suped@latest login gitlab vercel neonSome providers need a specific step:
- Neon: create an API key in your Neon account settings and paste it into Suped’s hidden prompt. Suped passes it through standard input to the Neon CLI, which validates and saves it in its active profile. A valid existing connection is kept.
- Turso: connection requires a manual step. Open the workspace with
npx suped@latest shell, runturso auth login --headless, and follow the printed URL and provider instructions forturso config set token. Runset +o historybefore pasting a command containing the token. Exit to your host terminal and runnpx suped@latest tools tursoto verify. See Turso headless mode. - DigitalOcean: create a personal access token and paste it into the native
doctlprompt. Include account read access for the connection check and the permissions your work needs. - GitLab: setup connects GitLab.com using a device code. Accept Git authentication when prompted to let the agent push over HTTPS. Self-managed instances use native
glab auth login --hostname YOUR_HOST --deviceand may require instance configuration; Suped’s connection check currently targets GitLab.com. - Fly.io: login requires an interactive terminal. Paste the browser’s completion code into that terminal if prompted. Deployments can use Fly’s remote builders with
fly deploy --remote-only. - Render: after login, choose the active workspace with
render workspace setinside Suped before managing services. - Stripe: if the CLI prints an additional command to finish authorization, run it inside the workspace.
The workspace receives the permissions you grant through those services. An agent using the same home can use that access to perform allowed actions. You can inspect, change, or revoke access through the vendor’s CLI or account settings. Tokens can expire; persisted configuration does not guarantee a permanent session.
Check installation and access
npx suped@latest tools
npx suped@latest tools gitlab vercel neon
npx suped@latest login vercelsuped tools reports not installed, connected, or installed; connection not verified. Checks use the provider’s CLI without creating resources. An unverified connection can mean missing or expired credentials, insufficient access, or a network failure. Use setup for missing tools and login to reconnect. A verified account connection does not imply access to every organization or project.
The native commands remain available to you and your agent:
npx suped@latest exec glab auth status
npx suped@latest exec vercel whoami
npx suped@latest exec neon projects listWhat stays in the workspace
Tools install under /home/suped/.local, with commands available in ~/.local/bin. Provider configuration and installed agent clients share the persistent home. Suped records tool selections separately from provider credentials; each vendor manages its own account configuration.
Your home survives shell exit, stop/start, reset, and rebuild. System packages installed with apt after the image was built do not survive reset or rebuild. Removing the home with destroy --yes removes its tools and local credentials. Removing local credentials does not revoke previously issued credentials at the provider; use the provider’s account controls when you want revocation. See persistence.
Supabase cloud and local development
The installed CLI can work with hosted Supabase projects. Supabase’s local development stack requires a Docker daemon, which Suped does not run or mount for you. Select docker and point it at a daemon by one of the routes above, and understand the trade-off described there before using the host’s socket. Installing the Supabase CLI alone does not make supabase start a working local stack.
After setup
Give your agent the objective and access to this workspace. It can use the installed CLIs to inspect your accounts, prepare a repo, build an app, and deploy when you authorize those actions. Agents shows how to hand it over.