The Adios CLI deploys applications, manages cloud resources, opens development workspaces, and runs repository-aware AI agents from your terminal.
This public repository contains release binaries, documentation, and examples. The CLI source is maintained privately.
Homebrew is the quickest option on macOS and Linux:
brew install adiosdotdev/tap/adiosPrebuilt archives are also available for macOS, Linux, and Windows from the
latest GitHub release.
Every release includes checksums.txt for download verification.
Confirm the installation:
adios versionSee the installation guide for supported architectures, manual installation, upgrades, checksums, and shell completion.
Sign in, initialize a manifest in your application directory, and deploy:
adios login
cd my-application
adios init
adios upThen inspect the deployment and follow its logs:
adios apps
adios logs <app-name> --followadios init detects the project type and previews the generated adios.yaml
before saving it. adios up uploads the selected source, builds it, deploys it,
and records the resulting application and team IDs in the manifest.
Read Getting started for the complete first-deploy walkthrough.
- Application builds, deployments, replicas, and logs
- Named login contexts and team selection
- Secrets, managed databases, object storage, domains, and ingress routes
- Source-backed development workspaces and preview runtimes
- Local and managed AI agent sessions, Agent Kits, projects, and tasks
- Local and deployed workflows
- Multi-project repositories, shared source graphs, and multi-region workloads
Run adios --help to see all command groups, or
adios <command> --help for the flags available in your installed version.
| Guide | Use it for |
|---|---|
| Documentation index | Find a guide by task |
| Installation | Install, verify, upgrade, or remove the CLI |
| Getting started | Log in and make a first deployment |
| Configuration and contexts | Manage accounts, teams, environment variables, and shell behavior |
| Deployments and manifests | Configure builds, runtime behavior, source, regions, and monorepos |
| Workspaces | Create, sync, preview, build, and deploy editable workspaces |
| AI agents | Run repository tasks, catalog agents, Agent Kits, and Company Projects |
| Resources and routing | Manage secrets, databases, storage, domains, and ingress |
| Command reference | Browse command groups and their subcommands |
| Troubleshooting | Resolve common install, login, manifest, deploy, and sync problems |
The examples directory contains adaptable
adios.yaml patterns for:
- a basic Node.js service;
- an application with managed Postgres;
- a multi-region application with a custom domain;
- a monorepo with ordered API and web deployments;
- an application that builds with shared source; and
.adiosignorerules.
These examples focus on deployment configuration. Copy a manifest into a
matching application and adjust its name, build command, start command, and
port before running adios up.
Release archives are built for:
| Operating system | Architectures |
|---|---|
| macOS | Intel (amd64), Apple silicon (arm64) |
| Linux | Intel/AMD (amd64), ARM (arm64) |
| Windows | Intel/AMD (amd64) |
Use of the Adios CLI and platform is governed by the Adios Terms of Service.
For CLI or documentation problems, open a GitHub issue. Never include access tokens, secret values, private keys, or private source code in an issue.