Problem
The CLI currently exposes overlapping terminology for project downloads:
pull means extract a project into a local directory
zip means download the raw archive
- single-file
download exists separately
For new users, the archive-vs-workspace split is not obvious. The command names and help text do not clearly communicate which workflow is for sync/extraction and which is for archive export.
Current behavior
olcli pull [project] [dir] downloads and extracts a project into a directory
olcli zip [project] downloads a zip archive
olcli download <file> downloads a single file
Expected behavior
- Keep existing commands working for backward compatibility.
- Add a clearer canonical project-archive command name, such as
archive.
- Keep
zip as a compatibility alias if the canonical name changes.
- Update help text and docs so the CLI clearly separates:
- workspace sync / extraction
- archive export
- single-file download
Acceptance criteria
olcli archive exists and behaves like the current zip command.
olcli zip continues to work as an alias.
- Help output groups commands by intent and uses clearer wording.
- README and command docs are updated to explain the difference between archive export and workspace pull.
- Error/spinner messages use user-facing language rather than implementation terms.
Notes
This is a UX and command-shape issue, not a breaking redesign. Existing scripts and aliases should remain valid.
Generated by GPT-5.4 mini.
Problem
The CLI currently exposes overlapping terminology for project downloads:
pullmeans extract a project into a local directoryzipmeans download the raw archivedownloadexists separatelyFor new users, the archive-vs-workspace split is not obvious. The command names and help text do not clearly communicate which workflow is for sync/extraction and which is for archive export.
Current behavior
olcli pull [project] [dir]downloads and extracts a project into a directoryolcli zip [project]downloads a zip archiveolcli download <file>downloads a single fileExpected behavior
archive.zipas a compatibility alias if the canonical name changes.Acceptance criteria
olcli archiveexists and behaves like the currentzipcommand.olcli zipcontinues to work as an alias.Notes
This is a UX and command-shape issue, not a breaking redesign. Existing scripts and aliases should remain valid.
Generated by GPT-5.4 mini.