CLI-native workflow

ForgeLore CLI

Use the ForgeLore CLI for repository discovery, AI Access token workflows, lock-aware Unreal collaboration, MCP setup, dry-runs, and agent recovery.

Install
$npm install -g @nortycary/forgelore-cli

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

$export FORGELORE_AGENT_TOKEN=<fla-token>
$forgelore whoami
$forgelore agent session
$forgelore agent doctor
$forgelore agent manifest
$forgelore billing plans
$forgelore repo list --limit 25

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

$forgelore repo inspect <repoId>
$forgelore repo manifest <repoId>
$forgelore repo diff <repoId> main feature/lighting
$forgelore repo artifacts <repoId>
$forgelore repo connect <repoId>

Lock-aware Unreal commands

$forgelore lock list <repoId>
$forgelore lock create <repoId> Content/Maps/Arena.umap "Lighting pass" --dry-run
$forgelore lock create <repoId> Content/Maps/Arena.umap "Lighting pass" --idempotency-key lock-arena-lighting
$forgelore lock release <repoId> <lockId>

Recovery commands

$forgelore lore doctor <lore-remote>
$forgelore agent doctor
$forgelore agent recover VALIDATION_ERROR
$forgelore agent recover LOCK_CONFLICT

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.