CLI Reference

The CLI is still foundational

Even though CoPaw has a browser Console, the CLI remains the first operational surface.

The CLI is how many users:

• install the product;
• initialize a workspace;
• launch the app;
• inspect or modify operating state.

Core mental model

The CLI should be thought of as:

• a bootstrap layer;
• an operator entry point;
• a bridge between raw environment setup and the higher-level Console.

Example startup sequence

pip install copaw
copaw init --defaults
copaw app

This is simple on purpose. The better the bootstrap story, the easier it is for the website to convert interest into a real local run.

What the docs should emphasize

The docs do not need to enumerate every possible command before the user sees value. They should first show the shortest path to:

1. installation;
2. initialization;
3. launch;
4. first useful interaction.

Only then should they expand into the larger command surface.

Why the CLI still matters for advanced users

People who adopt CoPaw seriously are often comfortable with infrastructure and code. A strong CLI story signals that the product respects operator workflows instead of hiding everything behind a thin web shell.