ForgeLore CLI
Use the ForgeLore CLI for repository discovery, AI Access token workflows, lock-aware Unreal collaboration, MCP setup, dry-runs, and agent recovery.
Before you begin
Install a current Node.js release and the ForgeLore CLI. Create a scoped AI Access token, store it outside source control, and confirm which organization and repository the task should use.
Start safely
Machine-readable by default
CLI responses are JSON envelopes so agents can parse `ok`, `data`, `error`, `requestId`, and pagination fields.
Secrets are redacted
Connection commands hide one-time tokens unless a human explicitly passes `--show-secret` in a trusted terminal.
Dry-runs and retries
Use `--dry-run` before supported writes and `--idempotency-key` when retrying write operations.
Scoped access
The CLI uses the same token scopes as API, SDK, and MCP so behavior stays consistent across surfaces.
Repository commands
Lock-aware Unreal commands
Recovery commands
Verify the session
`forgelore whoami` and `forgelore agent session` should identify the expected organization and scopes without printing the token. Preserve the `requestId` from failed commands when asking for help.