Getting started
Commands
These are Forge CLI requirements. Group names identify reference capabilities, not executable Orchestor syntax. Finalize names and arguments when integrating with the existing CLI.
| Group | Required capabilities | Responsibility |
|---|---|---|
| auth | Login, logout, status, Git authentication, revocation | 5 |
| repo | Create, mirror GitHub, list, view, clone, delete | 1, 4, 5, 7 |
| sync/job | Accept synchronization, inspect jobs, wait, inspect retries | 1, 2 |
| push local | Store mirror-local working refs in a separate remote, dry run | 7 |
| pr | Read PRs, diffs, Checks, checkout, reviews, lifecycle | 6, 7 |
| ruleset | List and inspect push-time and merge-time rules | 4, 7 |
| ssh-key | Add, list, delete public keys when SSH is supported | After HTTPS delivery in 5 |
| api | Authenticated REST requests, JSON input, fields, response extraction | 5 |
| completion/update/config | Shell completion, updates, configuration | Shared CLI |
Common inputs and outputs
- Explicit repository selection overrides Git remote inference. Preserve workspace boundaries.
- Provide help, version, machine-readable JSON, field selection, color control, and stable exit codes.
- Accept bodies from files or stdin. Keep secrets out of arguments and logs.
- Show deletion and ref-overwrite scope and define explicit non-interactive confirmation.
- Wait timeouts do not cancel sync jobs. Results remain retrievable.
A write grant is distinct from Git writes. Implement push and creation after deciding responsibility 7. GitHub Enterprise, SSH, and release-channel mechanisms require separate decisions.
Reference: Cursor command specification, inspected September 13, 2026. sync/job is a Forge addition derived from durable-sync requirements, not a reference command name.