@hlix/cli 1.2.0 → 1.3.1

package/README.md

@@ -12,11 +12,10 @@ verified review evidence from the terminal. Every call goes through
 [`@hlix/sdk`](https://www.npmjs.com/package/@hlix/sdk), which owns transport,
 auth, retry and error mapping.
 
-`hlix` on its own opens **Hlix Code**, the interactive terminal harness. It
-gives you a coding agent with every CLI command available as a slash command,
-and it chooses where that agent's files and shell live: your project's
-Cloud Machine when the folder is bound to hlix, and a local environment on this
-machine otherwise. `--sandbox cloud|docker|local` selects the environment;
+`hlix` on its own opens **Hlix Code**. A folder bound to a project opens the
+cloud client: the server owns conversations and work, and the terminal streams
+their output. An unbound folder opens a local coding agent.
+`--sandbox cloud|docker|local` selects the environment;
 `--sandbox docker` uses a Docker container, and `--local` is short for
 `--sandbox local`. The Docker container runs
 `node:22-bookworm` (git, node, python3 — no bun); `--docker-image <ref>`, or
@@ -55,8 +54,8 @@ For CI, and for anything else that must not change underneath you, pin the
 version instead of floating to `latest`:
 
 ```bash
-npm install --global @hlix/cli@1.2.0
-npx @hlix/cli@1.2.0 status --json
+npm install --global @hlix/cli@1.3.1
+npx @hlix/cli@1.3.1 status --json
 ```
 
 ## Authenticate
@@ -157,7 +156,25 @@ stored under `.hlix/tool-output/`. The Hlix agent inside a hosted Cloudflare box
 uses this local process path. The remote Cloud Machine CLI transport retains
 its own command limits.
 
-Inside the shell:
+Inside a cloud project, type `/` to see commands and available project skills.
+Click a cycle or use Ctrl-P to focus its conversation; Ctrl-N opens the harness
+launcher. Messages appear immediately and follow-ups queue while a turn runs.
+The header shows the actual server and connection state.
+
+| Command | Action |
+| --- | --- |
+| `/project` | Switch projects without leaving the CLI |
+| `/import [folder]` | Review and import the current files into a new cloud project, then switch to it; sibling worktrees stay local |
+| `/cycles`, `/focus` | Select the conversation receiving your messages |
+| `/launch <harness> <brief>` | Request work on a Cloud Machine with the chosen harness |
+| `/skills` | Choose an available project skill |
+| `/steer <message>`, `/force <message>` | Interrupt and send guidance next |
+| `/interrupt` | Interrupt the project-manager turn while keeping queued messages; stop selected cycle work |
+| `/stop` | Stop the selected session and cancel your queued project-manager messages |
+| `/stop project` | Stop project work and cancel your queued project-manager messages |
+| `/quit`, Ctrl-C | Disconnect; cloud work continues |
+
+Inside a local or Docker agent session:
 
 |                                           |                                                                                          |
 | ----------------------------------------- | ---------------------------------------------------------------------------------------- |