This quickstart gets you from zero to running an AI coding agent with USAi in under 5 minutes
34
stars
280
commits
Shell
primary language
Sep 11, 2026
updated
Audience: Federal teams using AI coding agents
Purpose: Get AI coding agents running safely inside isolated sandboxes, connected to USAi (the GSA-hosted LLM gateway atapi.gsa.usai.gov)
In one sentence: this quickstart gets you running an AI coding agent connected to USAi in under 5 minutes, using acq, a CLI tool provided here.
acq is the entry point. It runs your agent inside an isolated sandbox and
configures the environment for federal usage. To provide that isolation, it uses msb
(microsandbox), a lightweight, open-source microVM runtime.
acq is designed to support multiple isolation backends. A Docker Sandboxes (
sbx) backend is also supported. See docs/howto/sbx.md for sbx setup and docs/BACKEND_GUIDE.md for how the two backends compare.
Your journey: This repository is part of a three-repo ecosystem.
| Repo | Purpose | When to Use |
|---|---|---|
| Quickstart (you are here) | Get running | First day setup, sandboxing + USAi config |
| Playbook | Do it right | Repo setup, standards, best practices |
| Patterns | Share & learn | Community patterns, lessons learned |
Once you complete this Quickstart to get your environment working, use the Playbook to set up your projects properly, and visit Patterns to share what you learn.
AI coding agents can read files, write code, and execute commands. That makes them potent agents of chaos if they're compromised. Running them in sandboxes provides:
For the full comparison of the two backends and their tradeoffs, see docs/BACKEND_GUIDE.md.
You'll do three things: open a terminal, install acq, and run it.
You do not need to be a developer, and you do not need administrator
rights on your Mac.
You'll type (or paste) the commands below into this window.
Not on an Apple Silicon Mac? The sandbox needs hardware virtualization (macOS on Apple Silicon, Windows 11 with the Windows Hypervisor Platform, or Linux with
/dev/kvm). See supported hosts and other platforms.
Paste this one line and press Return:
curl -fsSL https://github.com/GSA-TTS/agentic-coding-quickstart/releases/download/v3.1.0/install.sh | sh
That's it — you don't have to choose how to install. The installer:
acq command on your computer so you can run it from any folder,acq runs your agent inside), andacq needs Apple's Command Line Tools (they provide git, which acq uses).
If they aren't installed yet, the installer starts them for you and waits
while they install — you'll see a window titled "Install Command Line
Developer Tools." Click Install and accept the license. No administrator
rights are required.
Can't find the window? It sometimes opens minimized in your Dock rather than in front of you — look there. The installer keeps waiting until the tools finish, then continues on its own.
You never have to pipe a script straight into your shell. If you have the GitHub
CLI (gh), you can also verify the release asset attestations before running
anything:
ACQ_VERSION=3.1.0 # x-release-please-version
curl -fsSLO "https://github.com/GSA-TTS/agentic-coding-quickstart/releases/download/v${ACQ_VERSION}/install.sh"
curl -fsSLO "https://github.com/GSA-TTS/agentic-coding-quickstart/releases/download/v${ACQ_VERSION}/SHA256SUMS"
gh attestation verify install.sh --repo GSA-TTS/agentic-coding-quickstart
gh attestation verify SHA256SUMS --repo GSA-TTS/agentic-coding-quickstart
shasum -a 256 -c SHA256SUMS
less install.sh # read it
sh install.sh --dry-run # show what it WOULD do, changing nothing
sh install.sh # actually install
By default, the installer uses the best package manager already available on
your host: Homebrew, then npm, then a managed git clone. Homebrew and npm rely on
the published package/formula release path. The release asset's baked commit SHA
is used only by the clone fallback (or --method clone) to verify that the clone
landed on the release commit embedded in the installer. To pin to an independent,
explicit commit, use --method clone --sha <40-char-commit>.
Already use Homebrew or Node, or prefer to run from a clone? The one-line installer detects and uses whichever package manager you have. For the direct commands, a manual clone install, or testing a tagged release, see Installing acq.
Point acq at the folder you want the agent to work in (an existing project, or
a new empty folder you just made):
acq run opencode ~/my-project
That's it — you're now running an AI coding agent with USAi access and restricted filesystem and network access. Repeat Step 3 for each project.
[!NOTE] The first run takes a minute or two.
acqboots a microVM, installs the coding agent, and fetches its configuration kits, showing progress as it goes. Later runs against the same project are much faster.
On first run, acq sets you up interactively — nothing to configure beforehand:
acq prompts you to paste a key and validates it. Create one at
the USAi key console (keys expire
every 7 days).acq offers to walk
you through creating a repo-scoped token. You can decline and add one later.acq warns if your commits won't sign/verify correctly, and
tells you how to fix it.acq injects secrets into the sandbox at runtime — the real values never enter
the guest.
The two things a first-timer most often hits are below. For everything else (expired USAi keys, DNS resolution, unverified commits, stale branches, wrong providers, auth/TLS failures, and more), see docs/KNOWN_FAILURE_MODES.md.
This means acq isn't where you're typing the command. Two fixes:
acq with the one-line installer in
Step 2. Then run acq (no ./) from any folder../acq only works from inside the
agentic-coding-quickstart folder — that's where the acq file lives. cd
back into it first (cd ~/agentic-coding-quickstart, or wherever you cloned
it), then run ./acq run opencode ~/my-project.The first time your Mac uses git, it installs the Command Line Tools. If you
see xcode-select: note: No developer tools were found, requesting install,
run:
xcode-select --install
A pop-up window titled "Install Command Line Developer Tools" appears — click Install and accept the license. If you can't find the window, look in your Dock — it sometimes opens minimized there rather than in front of you. When it finishes, re-run your command. (No administrator rights are required.)
acq how-to, backend selection, manual install:
docs/howto/acq.mdOnce in a while, refresh your setup to pick up updates (via your package manager,
or git fetch && git pull in a clone), and
rotate your USAi key when it expires
(every 7 days).
The playbook also provides reusable agent skills — step-by-step procedures
for common tasks, following the agentskills.io
standard. When you launch a sandbox with acq, the agentic-coding-playbook kit
symlinks these into ~/.agents/skills so your agent discovers them automatically
— no separate checkout needed.
| Source | Skills | Examples |
|---|---|---|
| Playbook | Federal compliance, security | federal-security-controls-lookup, ato-package, code-review, cloudgov-deploy |
| Patterns | Development workflows | accessibility-review, uswds-prototype, test-generation, secure-code-review |
Data Classification: Internal/Non-sensitive — the Quickstart is a local development environment for building Low/Moderate-impact code and projects, not an authorized production/hosted environment (no PII, no CUI).
Shell
100.0%
This quickstart gets you from zero to running an AI coding agent with USAi in under 5 minutes
34
stars
280
commits
Shell
primary language
Sep 11, 2026
updated
Audience: Federal teams using AI coding agents
Purpose: Get AI coding agents running safely inside isolated sandboxes, connected to USAi (the GSA-hosted LLM gateway atapi.gsa.usai.gov)
In one sentence: this quickstart gets you running an AI coding agent connected to USAi in under 5 minutes, using acq, a CLI tool provided here.
acq is the entry point. It runs your agent inside an isolated sandbox and
configures the environment for federal usage. To provide that isolation, it uses msb
(microsandbox), a lightweight, open-source microVM runtime.
acq is designed to support multiple isolation backends. A Docker Sandboxes (
sbx) backend is also supported. See docs/howto/sbx.md for sbx setup and docs/BACKEND_GUIDE.md for how the two backends compare.
Your journey: This repository is part of a three-repo ecosystem.
| Repo | Purpose | When to Use |
|---|---|---|
| Quickstart (you are here) | Get running | First day setup, sandboxing + USAi config |
| Playbook | Do it right | Repo setup, standards, best practices |
| Patterns | Share & learn | Community patterns, lessons learned |
Once you complete this Quickstart to get your environment working, use the Playbook to set up your projects properly, and visit Patterns to share what you learn.
AI coding agents can read files, write code, and execute commands. That makes them potent agents of chaos if they're compromised. Running them in sandboxes provides:
For the full comparison of the two backends and their tradeoffs, see docs/BACKEND_GUIDE.md.
You'll do three things: open a terminal, install acq, and run it.
You do not need to be a developer, and you do not need administrator
rights on your Mac.
You'll type (or paste) the commands below into this window.
Not on an Apple Silicon Mac? The sandbox needs hardware virtualization (macOS on Apple Silicon, Windows 11 with the Windows Hypervisor Platform, or Linux with
/dev/kvm). See supported hosts and other platforms.
Paste this one line and press Return:
curl -fsSL https://github.com/GSA-TTS/agentic-coding-quickstart/releases/download/v3.1.0/install.sh | sh
That's it — you don't have to choose how to install. The installer:
acq command on your computer so you can run it from any folder,acq runs your agent inside), andacq needs Apple's Command Line Tools (they provide git, which acq uses).
If they aren't installed yet, the installer starts them for you and waits
while they install — you'll see a window titled "Install Command Line
Developer Tools." Click Install and accept the license. No administrator
rights are required.
Can't find the window? It sometimes opens minimized in your Dock rather than in front of you — look there. The installer keeps waiting until the tools finish, then continues on its own.
You never have to pipe a script straight into your shell. If you have the GitHub
CLI (gh), you can also verify the release asset attestations before running
anything:
ACQ_VERSION=3.1.0 # x-release-please-version
curl -fsSLO "https://github.com/GSA-TTS/agentic-coding-quickstart/releases/download/v${ACQ_VERSION}/install.sh"
curl -fsSLO "https://github.com/GSA-TTS/agentic-coding-quickstart/releases/download/v${ACQ_VERSION}/SHA256SUMS"
gh attestation verify install.sh --repo GSA-TTS/agentic-coding-quickstart
gh attestation verify SHA256SUMS --repo GSA-TTS/agentic-coding-quickstart
shasum -a 256 -c SHA256SUMS
less install.sh # read it
sh install.sh --dry-run # show what it WOULD do, changing nothing
sh install.sh # actually install
By default, the installer uses the best package manager already available on
your host: Homebrew, then npm, then a managed git clone. Homebrew and npm rely on
the published package/formula release path. The release asset's baked commit SHA
is used only by the clone fallback (or --method clone) to verify that the clone
landed on the release commit embedded in the installer. To pin to an independent,
explicit commit, use --method clone --sha <40-char-commit>.
Already use Homebrew or Node, or prefer to run from a clone? The one-line installer detects and uses whichever package manager you have. For the direct commands, a manual clone install, or testing a tagged release, see Installing acq.
Point acq at the folder you want the agent to work in (an existing project, or
a new empty folder you just made):
acq run opencode ~/my-project
That's it — you're now running an AI coding agent with USAi access and restricted filesystem and network access. Repeat Step 3 for each project.
[!NOTE] The first run takes a minute or two.
acqboots a microVM, installs the coding agent, and fetches its configuration kits, showing progress as it goes. Later runs against the same project are much faster.
On first run, acq sets you up interactively — nothing to configure beforehand:
acq prompts you to paste a key and validates it. Create one at
the USAi key console (keys expire
every 7 days).acq offers to walk
you through creating a repo-scoped token. You can decline and add one later.acq warns if your commits won't sign/verify correctly, and
tells you how to fix it.acq injects secrets into the sandbox at runtime — the real values never enter
the guest.
The two things a first-timer most often hits are below. For everything else (expired USAi keys, DNS resolution, unverified commits, stale branches, wrong providers, auth/TLS failures, and more), see docs/KNOWN_FAILURE_MODES.md.
This means acq isn't where you're typing the command. Two fixes:
acq with the one-line installer in
Step 2. Then run acq (no ./) from any folder../acq only works from inside the
agentic-coding-quickstart folder — that's where the acq file lives. cd
back into it first (cd ~/agentic-coding-quickstart, or wherever you cloned
it), then run ./acq run opencode ~/my-project.The first time your Mac uses git, it installs the Command Line Tools. If you
see xcode-select: note: No developer tools were found, requesting install,
run:
xcode-select --install
A pop-up window titled "Install Command Line Developer Tools" appears — click Install and accept the license. If you can't find the window, look in your Dock — it sometimes opens minimized there rather than in front of you. When it finishes, re-run your command. (No administrator rights are required.)
acq how-to, backend selection, manual install:
docs/howto/acq.mdOnce in a while, refresh your setup to pick up updates (via your package manager,
or git fetch && git pull in a clone), and
rotate your USAi key when it expires
(every 7 days).
The playbook also provides reusable agent skills — step-by-step procedures
for common tasks, following the agentskills.io
standard. When you launch a sandbox with acq, the agentic-coding-playbook kit
symlinks these into ~/.agents/skills so your agent discovers them automatically
— no separate checkout needed.
| Source | Skills | Examples |
|---|---|---|
| Playbook | Federal compliance, security | federal-security-controls-lookup, ato-package, code-review, cloudgov-deploy |
| Patterns | Development workflows | accessibility-review, uswds-prototype, test-generation, secure-code-review |
Data Classification: Internal/Non-sensitive — the Quickstart is a local development environment for building Low/Moderate-impact code and projects, not an authorized production/hosted environment (no PII, no CUI).
Shell
100.0%