agent-gateway builds three binaries with different runtime roles.
- the main Caddy-based gateway runtime
- uses a Caddyfile plus the shared config store
- supports normal Caddy subcommands such as
run,reload,validate, andhash-password
- the standalone gateway daemon
- uses
--config-store, optional--static-config, optional repeated--provider-type,--credential-refresh-command, and repeatable--credential-refresh-arg(together defaulting toagw-auth refresh) - does not use a Caddyfile runtime
- if any
--provider-typeflag is set, only those provider types are enabled for the process
Current static config restriction:
agwd --static-configllmRoutesonly support direct-provider targetsagwd --static-configdoes not supportmanagedModels- create logical-model routes and managed models through the Admin API or bundle workflows
- the management CLI
- talks to the gateway Admin API or the Caddy admin API
Primary command families:
- gateway bundle operations and resource commands are available directly under
agwctl agwctl caddy ...
Recommended workflows:
- use
agwctl apply/export/validatefor bundle-based configuration management - use
agwctl credential ...for remote gateway credential management - use the external
agw-authtool for interactive OAuth login flows - use
agwctl caddy ...for direct Caddy admin API operations
Bundle YAML examples used by current workflows:
examples/gateway.bundle.llm.direct-provider.yamlexamples/gateway.bundle.llm.logical-model.yaml