Account sign-in and authorization¶
Run the supported human account sign-in flow after installing Aegis:
Complete the authentication page in your browser. Follow its account and consent prompts yourself. Aegis stores the resulting account credentials; the ordinary journey requires no copied token or endpoint override.
Inspect public account state:
Use status to inspect the active account before deployment. If it reports that authentication is required, sign in again through your browser.
Separate authorities¶
| Authority | Established where | Purpose |
|---|---|---|
| Aegis account | Human account sign-in | Identifies the signed-in account. |
| Standalone Nexus installation | Supported client configuration | Supplies managed model access to ordinary Codex. |
| Your GitHub authority | Ordinary Git authentication | Publishes application commits. |
| Forge GitHub App authority | First-deploy repository authorization | Lets Forge read the authorized repository for deployment. |
One authority does not establish the others. Account sign-in does not supply ordinary Git credentials or silently approve repository access.
Recovery¶
If account state requires authentication, run the human sign-in command again. Preserve the error and public status when sign-in fails. Do not replace account credentials manually or introduce identity selectors.
Next¶
Follow Quickstart to enable Nexus, initialize your application, and deploy it from your own GitHub repository.