DevCLI

DevCLI is the aigw command-line tool. Use it to manage the same Projects, Resources, Proxy clients, and agent policies as the AIGW Console. You can run it directly or use it with Codex and Claude Code.

Install

On macOS or Linux with Homebrew:

brew install loginid1/tap/aigw-cli
aigw version

Use DevCLI v0.2.0 or later. To update an existing Homebrew installation, run brew update followed by brew upgrade aigw-cli.

For Windows, or Linux without Homebrew, download the ZIP for your OS and CPU and checksums.txt from the same GitHub release.

On Linux, place both files in a new directory and verify the ZIP before extracting it:

sha256sum --ignore-missing -c checksums.txt

The ZIP must report OK. Follow the Linux installation steps or Windows checksum and installation commands to add the binary to your PATH.

Log in

1. Open the AIGW Console, select your Account (the workspace for your organization), and go to Settings → API Management.
2. As the Account Owner, click Create API key. If you are not the Owner, ask the Owner to create a key for you. Give the key a name, select PROJECT_READ to read configuration and PROJECT_WRITE to create or update it, choose an expiry, and click Create key. These permissions correspond to project:read and project:write in the API and DevCLI reference.
3. Log in from your terminal and paste the key at the hidden prompt:

aigw login
aigw status -o json

aigw login saves your API key in the operating system’s credential store.

A successful status response includes:

{
  "apiBase": "https://api.aigw.loginid.ai",
  "keySource": "saved login",
  "check": "ok"
}

AIGW_API_KEY takes precedence over the key saved by aigw login; if keySource is AIGW_API_KEY, update that variable or remove it with unset AIGW_API_KEY (PowerShell: Remove-Item Env:AIGW_API_KEY) to use your saved login, then rerun aigw status -o json.

Continue when check is ok and apiBase matches the address above. Use your own terminal for login; keep the key out of chat messages and source files. For automation, supply AIGW_API_KEY as described in Scripts and CI.

Linux without a credential store

If aigw login reports No usable credential store here, supply AIGW_API_KEY for the current terminal. In Bash, read the key without displaying it or adding its value to shell history:

read -r -s -p 'AIGW API key: ' AIGW_API_KEY
printf '\n'
export AIGW_API_KEY
aigw status -o json

For CI, set AIGW_API_KEY through your CI secret settings.

To save a login on a machine without a credential store, run:

aigw login --insecure-storage

This stores the key in a plaintext file. Anyone who can read that file can use the key; use this option only when you can protect the file.

Create your first Project

aigw projects list
aigw projects create --name "Acme MCP dev"

Copy the new Project's id from the JSON response and read it back:

Bash / Zsh

PROJECT_ID='your-project-id'
aigw projects get "$PROJECT_ID"

PowerShell

$PROJECT_ID = 'your-project-id'
aigw projects get $PROJECT_ID

The returned Project should have the same ID and name. Reuse this ID when creating Resources and Proxy clients.

Configure agent approval before accepting requests

With no Agent policy configured, new agents are approved automatically. To require review, set the default and proof rules to PENDING before accepting requests. Review domain rules and Resource overrides too. User authorization and scope checks still apply.

Choose your next task

Task	Guide
Configure AIGW alongside your application code	Use with Codex or Claude Code
Register a merchant API and create a Proxy client	DevCLI reference
Understand Console fields and ownership	Configure AIGW
Implement the complete authorized request flow	MCP/UCP integration

The DevCLI uses a Console management API key. Your agent's OAuth token and your MCP server's Proxy client serve separate roles in the runtime flow.