# Install archgw with Homebrew

CLI for Arch Gateway. Version 0.3.22 via Homebrew; verified 2026-05-20.

## Install

```sh
sudo av install brew:archgw
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install archgw
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:archgw
- **Package manager:** Homebrew
- **Version:** 0.3.22
- **Source summary:** CLI for Arch Gateway
- **Homepage:** <https://github.com/katanemo/archgw/tree/main/arch/tools>
- **Last updated:** 2026-05-20T10:51:45Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- archgw (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.3.22
## Project history and usage

The Homebrew `archgw` package points at what is now Plano, an AI-native proxy and data plane for agentic applications, LLM routing, orchestration, guardrails, and observability.

### Project history

The official GitHub API redirects `katanemo/archgw` to `katanemo/plano`, and the repository describes Plano as an AI-native proxy server and data plane for agentic apps. The public repository was created on 2024-07-09, with the first release in the GitHub releases API, 0.1.0, published on 2024-10-31.

Plano's README frames the project as a response to production agent plumbing: routing between agents, model-provider abstraction, guardrail filters, and OpenTelemetry-style signals that otherwise get copied into every application.

### Adoption history

The docs package the CLI as `planoai`, with installation through uv or pip, while Homebrew exposes the older `archgw` formula name. That naming history is useful for package nerds because it captures an active rename/repositioning rather than a simple one-name project.

GitHub metadata showed thousands of stars by the 2026 batch run, and the docs emphasize precompiled native downloads, Docker mode, and a quickstart repository, indicating adoption aimed at app developers who want a local gateway without manually building Envoy/WASM components.

### How it is used

A typical setup creates `plano_config.yaml`, declares model providers with `access_key` values such as `$OPENAI_API_KEY` and `$ANTHROPIC_API_KEY`, then runs `planoai up plano_config.yaml`. The quickstart says those keys may also be defined in a `.env` file.

Once running, Plano exposes OpenAI-compatible endpoints for model proxying and can orchestrate HTTP agents by intent, letting applications keep their own business logic while the gateway handles routing, provider choice, tracing, and guardrail hooks.

### Why package nerds care

This row is notable because the package name, executable identity, and project name are in motion: `archgw` survives as a package entry while official project surfaces now say Plano.

It is also a modern example of packaging an AI infrastructure tool whose useful local install includes not only a CLI, but downloaded proxy/runtime components cached under the user's home directory.

### Timeline

- 2024-07-09: GitHub repository created.
- 2024-10-31: First GitHub release, 0.1.0.
- 2026-06-25: Latest GitHub release observed for this batch, 0.4.26.
- 2026: Official GitHub API redirects `katanemo/archgw` to `katanemo/plano`.

### Related projects

- The README says Plano is built on Envoy and names OpenAI-compatible APIs, OpenTelemetry traces, and provider models such as OpenAI and Anthropic in its examples.
- The docs point to a separate official `plano-quickstart` repository for runnable application examples.

### Sources

- <https://api.github.com/repos/katanemo/plano>
- <https://api.github.com/repos/katanemo/plano/releases>
- <https://docs.planoai.dev/get_started/quickstart.html>
- <https://github.com/katanemo/plano>


## Security Notes

No matching local secret-handling manifest was found for archgw. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ./plano_config.yaml

## Credential files

- Unix: ./.env

## Combined YAML source

View the package source record on GitHub. [combined/archgw.yml](https://github.com/mxcl/pkgdb/blob/main/combined/archgw.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph