Standardize CLI naming to conda workspace / conda task

Use full command names throughout docs and README. The cw/ct
shortcuts are mentioned once as aliases rather than used as the
primary form.

Author: jezdez

CHANGELOG.md

@@ -21,7 +21,7 @@ The format follows [Keep a Changelog](https://keepachangelog.com/).
 - Initial implementation of conda-workspaces plugin
 - `conda workspace` subcommand with `init`, `install`, `list`, `info`,
   `add`, `remove`, `clean`, `run`, and `activate` subcommands
-- `cw` standalone CLI shortcut
+- `conda workspace` standalone CLI (also available as `cw`)
 - Parser support for `pixi.toml`, `conda.toml`, and `pyproject.toml`
   manifests
 - Multi-environment workspace model with composable features

DESIGN.md

@@ -11,11 +11,11 @@ multi-environment workspace management to conda.  It reads pixi-compatible
 manifest files (`pixi.toml`, `conda.toml`, `pyproject.toml`) and manages
 project-local conda environments under `.conda/envs/`.
 
-The plugin registers two subcommands: `conda workspace` (with `cw` as a
-standalone shortcut) for environment management (`init`, `install`,
-`lock`, `list`, `envs`, `info`, `add`, `remove`, `clean`, `run`,
-`shell`, `activate`) and `conda task` (with `ct` as a shortcut) for
-task execution (`run`, `list`, `add`, `remove`, `export`).
+The plugin registers two subcommands: `conda workspace` for environment
+management (`init`, `install`, `lock`, `list`, `envs`, `info`, `add`,
+`remove`, `clean`, `run`, `shell`, `activate`) and `conda task` for
+task execution (`run`, `list`, `add`, `remove`, `export`).  Standalone
+shortcuts `cw` and `ct` are also available as aliases.
 
 ## Goals
 
@@ -120,18 +120,19 @@ supported.  This is structurally identical to pixi.toml but:
   settings, conda-build integration)
 - Provides a non-pixi-branded option for teams that only use conda
 
-### 5. Standalone CLI Shortcut (`cw`)
+### 5. Standalone CLI Aliases (`cw` / `ct`)
 
-The `cw` console script provides a standalone entry point that doesn't
-require going through `conda workspace ...`.  This is registered via
+The primary CLI forms are `conda workspace` and `conda task`.  For
+convenience, `cw` and `ct` console scripts provide standalone aliases
+that don't require the `conda` prefix.  These are registered via
 `[project.scripts]` in pyproject.toml:
 
 ```toml
 [project.scripts]
 cw = "conda_workspaces.__main__:main"
 ```
 
-Similarly, `ct` provides a shortcut for `conda task`.
+`ct` is the equivalent alias for `conda task`.
 
 ### 6. Task System Architecture
 
@@ -178,8 +179,8 @@ overrides or Jinja2 conditionals.
 3. **Lock files** — conda-workspaces generates a `conda.lock` in
    rattler-lock v6 format (the same structure as `pixi.lock`) after
    every install.  The `--locked` flag installs from the lockfile
-   without running the solver, and `cw lock` regenerates the lockfile
-   on demand.
+   without running the solver, and `conda workspace lock` regenerates
+   the lockfile on demand.
 
 4. **Plugin, not standalone** — conda-workspaces is a conda plugin;
    pixi is a standalone tool that replaces conda entirely for its users.

README.md

@@ -45,11 +45,11 @@ depends-on = ["test", "lint"]
 Install and manage your environments, then run tasks:
 
 ```console
-$ cw install              # solve + install + generate conda.lock
-$ cw envs                 # list defined environments
-$ conda task run check    # runs lint and test in dependency order
-$ cw shell -e test        # spawn a shell with test env activated
-$ cw install --locked     # reproducible install from conda.lock
+$ conda workspace install              # solve + install + generate conda.lock
+$ conda workspace envs                 # list defined environments
+$ conda task run check                 # runs lint and test in dependency order
+$ conda workspace shell -e test        # spawn a shell with test env activated
+$ conda workspace install --locked     # reproducible install from conda.lock
 ```
 
 ## Why?
@@ -76,7 +76,7 @@ and task running inside the conda CLI without switching tools.
 - Task dependencies with topological ordering (`depends-on`)
 - Jinja2 templates in commands (`{{ conda.platform }}`, conditionals)
 - Task arguments with defaults, input/output caching, and per-platform overrides
-- Standalone `cw` / `ct` CLIs and `conda workspace` / `conda task` plugin subcommands
+- `conda workspace` / `conda task` subcommands (also available as `cw` / `ct` aliases)
 
 ## Installation
 
@@ -86,25 +86,25 @@ conda install -c conda-forge conda-workspaces
 
 ## CLI
 
-conda-workspaces registers as `conda workspace` and `conda task`, and
-provides `cw` and `ct` as standalone shortcuts.
+conda-workspaces registers `conda workspace` and `conda task` subcommands,
+and also provides `cw` and `ct` as shorter aliases.
 
 ### Workspace commands
 
 | Command | Description |
 |---|---|
-| `cw init` | Initialize a new workspace manifest |
-| `cw install` | Create/update workspace environments |
-| `cw install --locked` | Install from lockfile (skip solving) |
-| `cw lock` | Generate/update `conda.lock` |
-| `cw list` | List packages in an environment |
-| `cw envs` | List defined environments |
-| `cw info [ENV]` | Show environment details |
-| `cw add SPECS...` | Add dependencies |
-| `cw remove SPECS...` | Remove dependencies |
-| `cw shell [ENV]` | Spawn a shell with an environment activated |
-| `cw activate [ENV]` | Print activation instructions |
-| `cw clean` | Remove installed environments |
+| `conda workspace init` | Initialize a new workspace manifest |
+| `conda workspace install` | Create/update workspace environments |
+| `conda workspace install --locked` | Install from lockfile (skip solving) |
+| `conda workspace lock` | Generate/update `conda.lock` |
+| `conda workspace list` | List packages in an environment |
+| `conda workspace envs` | List defined environments |
+| `conda workspace info [ENV]` | Show environment details |
+| `conda workspace add SPECS...` | Add dependencies |
+| `conda workspace remove SPECS...` | Remove dependencies |
+| `conda workspace shell [ENV]` | Spawn a shell with an environment activated |
+| `conda workspace activate [ENV]` | Print activation instructions |
+| `conda workspace clean` | Remove installed environments |
 
 ### Task commands
 
@@ -116,8 +116,6 @@ provides `cw` and `ct` as standalone shortcuts.
 | `conda task remove NAME` | Remove a task from the manifest |
 | `conda task export` | Export tasks to `conda.toml` format |
 
-The `ct` shortcut works like `conda task`: `ct run check`, `ct list`, etc.
-
 ## What it doesn't do
 
 conda-workspaces is a workspace manager and task runner, not a package

docs/features.md

@@ -329,7 +329,7 @@ env = { DEBUG = "1" }
 ```
 
 Activation settings are merged across features when composing an
-environment. After `cw install`, environment variables are written to
+environment. After `conda workspace install`, environment variables are written to
 the prefix state file (available via `conda activate`) and activation
 scripts are copied to `$PREFIX/etc/conda/activate.d/`.
 
@@ -365,19 +365,19 @@ conda's default channel priority applies.
 ## Lock
 
 conda-workspaces generates a `conda.lock` file in YAML format based on
-the rattler-lock v6 specification. The `cw lock` command runs the solver
+the rattler-lock v6 specification. The `conda workspace lock` command runs the solver
 and records the solution — it does not require environments to be
 installed first.
 
 ```bash
 # Generate or update the lockfile
-cw lock
+conda workspace lock
 
 # Install from lockfile, validating freshness against the manifest
-cw install --locked
+conda workspace install --locked
 
 # Install from lockfile as-is without checking freshness
-cw install --frozen
+conda workspace install --frozen
 ```
 
 The lockfile contains all environments and their resolved packages:
@@ -415,7 +415,7 @@ checks entirely and install the lockfile as-is.
 You can also point to a specific manifest with `--file` / `-f`:
 
 ```bash
-cw install -f path/to/conda.toml
+conda workspace install -f path/to/conda.toml
 ```
 
 ## Project-local environments
@@ -435,6 +435,6 @@ my-project/
 └── src/
 ```
 
-Environments are standard conda prefixes. Use `cw run -e <name> -- CMD`
-to run a command in an environment, `cw shell -e <name>` for an
+Environments are standard conda prefixes. Use `conda workspace run -e <name> -- CMD`
+to run a command in an environment, `conda workspace shell -e <name>` for an
 interactive shell, or `conda activate .conda/envs/<name>` directly.

docs/index.md

@@ -57,13 +57,13 @@ test = { features = ["test"] }
 Then install and use your environments:
 
 ```bash
-cw install                    # solve + install + generate conda.lock
-cw run -e test -- pytest -v   # run a command in an environment
-cw shell -e test              # spawn a shell with test env activated
-cw install --locked           # reproducible install from conda.lock
-cw list                       # list packages in default env
-cw envs                       # list defined environments
-cw info                       # workspace overview
+conda workspace install                    # solve + install + generate conda.lock
+conda workspace run -e test -- pytest -v   # run a command in an environment
+conda workspace shell -e test              # spawn a shell with test env activated
+conda workspace install --locked           # reproducible install from conda.lock
+conda workspace list                       # list packages in default env
+conda workspace envs                       # list defined environments
+conda workspace info                       # workspace overview
 ```
 
 ## Define tasks
@@ -112,7 +112,7 @@ This means:
 - Task dependencies, caching, Jinja2 templates, and platform overrides
   all work out of the box
 - Ships as a conda plugin (`conda workspace`, `conda task`) and
-  standalone `cw` / `ct` CLIs
+  standalone `conda workspace` / `conda task` CLIs (also available as `cw` / `ct`)
 
 Read more in [](motivation.md).
 

docs/motivation.md

@@ -31,10 +31,10 @@ definitions, and installation. Running `pixi install` uses rattler
 | Define tasks | `pixi.toml` `[tasks]` | Same manifest file |
 | Solve dependencies | rattler (bundled) | conda / libmamba (existing) |
 | Install packages | rattler (into `.pixi/envs/`) | conda (into `.conda/envs/`) |
-| Manage environments | `pixi install` | `cw install` (delegates to conda) |
+| Manage environments | `pixi install` | `conda workspace install` (delegates to conda) |
 | Run tasks | `pixi run <task>` | `conda task run <task>` |
-| Run commands in env | `pixi run CMD` | `cw run -- CMD` or `cw shell -e ENV -- CMD` |
-| Activate | `pixi shell` | `cw shell` / `conda activate .conda/envs/<name>` |
+| Run commands in env | `pixi run CMD` | `conda workspace run -- CMD` or `conda workspace shell -e ENV -- CMD` |
+| Activate | `pixi shell` | `conda workspace shell` / `conda activate .conda/envs/<name>` |
 
 This approach has advantages:
 
@@ -68,7 +68,7 @@ conda-workspaces reads the same manifest format as pixi. A project with a
 `pixi.toml` can use both tools:
 
 - pixi users run `pixi install` and `pixi run` as usual
-- conda users run `cw install` and `conda task run` using conda's solver
+- conda users run `conda workspace install` and `conda task run` using conda's solver
 
 This coexistence is possible because each tool stores environments in a
 different directory (`.pixi/envs/` vs `.conda/envs/`), so they don't

docs/quickstart.md

@@ -125,18 +125,23 @@ test = { features = ["test"] }
 
 ::::
 
+:::{tip}
+`cw` and `ct` are available as shorter aliases for `conda workspace`
+and `conda task`.
+:::
+
 Or use the init command to scaffold one:
 
 ```bash
-cw init
-# or: cw init --format conda
-# or: cw init --format pyproject
+conda workspace init
+# or: conda workspace init --format conda
+# or: conda workspace init --format pyproject
 ```
 
 ## Install environments
 
 ```bash
-cw install
+conda workspace install
 ```
 
 This creates project-local conda environments under `.conda/envs/` for
@@ -146,24 +151,24 @@ generated automatically after solving.
 You can point to a specific manifest with `--file` / `-f`:
 
 ```bash
-cw install -f path/to/conda.toml
+conda workspace install -f path/to/conda.toml
 ```
 
 To recreate environments from scratch, use `--force-reinstall`:
 
 ```bash
-cw install --force-reinstall
+conda workspace install --force-reinstall
 ```
 
 ## Lock
 
 ![lockfile demo](../demos/lockfile.gif)
 
-The `cw lock` command runs the solver and records the solution in
+The `conda workspace lock` command runs the solver and records the solution in
 `conda.lock` without installing any environments:
 
 ```bash
-cw lock
+conda workspace lock
 ```
 
 ## Reproducible installs
@@ -173,14 +178,14 @@ lockfile is still fresh relative to the manifest — if the manifest has
 changed, the install fails:
 
 ```bash
-cw install --locked
+conda workspace install --locked
 ```
 
 Use `--frozen` to install from the lockfile as-is, without checking
 freshness:
 
 ```bash
-cw install --frozen
+conda workspace install --frozen
 ```
 
 ## Run in workspace environments
@@ -194,46 +199,46 @@ conda task run -e test pytest -v
 Run a one-shot command in an environment:
 
 ```bash
-cw run -e test -- python -c "import numpy; print(numpy.__version__)"
+conda workspace run -e test -- python -c "import numpy; print(numpy.__version__)"
 ```
 
 Or spawn an interactive shell:
 
 ```bash
-cw shell -e test
+conda workspace shell -e test
 ```
 
 ## Add dependencies
 
 ```bash
-cw add numpy
+conda workspace add numpy
 ```
 
 Add to a specific feature:
 
 ```bash
-cw add --feature test pytest
+conda workspace add --feature test pytest
 ```
 
 Add a PyPI dependency:
 
 ```bash
-cw add --pypi requests
+conda workspace add --pypi requests
 ```
 
 ## List packages and environments
 
 ```bash
-cw list              # packages in default env
-cw list -e test      # packages in test env
-cw envs              # list defined environments
+conda workspace list              # packages in default env
+conda workspace list -e test      # packages in test env
+conda workspace envs              # list defined environments
 ```
 
 ## Workspace overview
 
 ```bash
-cw info
-cw info -e test      # details for a specific environment
+conda workspace info
+conda workspace info -e test      # details for a specific environment
 ```
 
 ## Next steps