CLI reference¶
Use these commands for account sign-in, Nexus configuration, and Forge application deployment. Follow Quickstart for the full sequence from installation to your application's URL.
Account and Nexus¶
aegis auth signin
aegis auth status --json
aegis codex enable --model nexus
aegis codex status --model nexus --json
Sign-in opens the human authentication flow, and status reports public account state. Nexus enable configures the ordinary Codex client and its managed model catalog while preserving unrelated settings.
Rerun enable after upgrading if your existing Nexus profile lacks model metadata. Authentication uses the managed credential helper; no token copying or protected-agent setup is required.
Application deployment¶
Initialization preserves an existing valid manifest. It detects a root static app without a competing build manifest, or writes a starter into an empty directory. See Configure your app for supported layouts and guidance when initialization refuses a layout.
Commit and push the source before deployment. Forge resolves the
repository from the GitHub origin and the source from committed HEAD.
Automation may select source with --repo, --ref, or --sha. The
parser rejects using --ref and --sha together. Add --json for
structured output.
Deployment inspection and rollback¶
Replace each uppercase value with the reference returned for your app:
aegis forge status DEPLOYMENT_REF
aegis forge versions APP_REF --json
aegis forge rollback DEPLOYMENT_REF --json
Status inspects a deployment. Human-readable deploy and status output
include application_url when deployment has succeeded and its route is
ready. Read Deploy if no URL appears.
Versions lists the app's recorded versions. Rollback requests restoration of the current deployment's previous route pointer. Inspect the serving application after rollback to verify that the intended version returned.
Authorization boundary¶
Environment, tenant, account, installation, and app authority are derived from authorization and repository context. An app reference used for inspection does not override that authority.
Forge App authorization begins when deployment needs repository access. Ordinary Git commands use your GitHub authority, and Forge adds no repository workflow.