clavue 8.8.91 → 8.8.93

package/README.md

@@ -1,8 +1,8 @@
-# Clavue v8.8.91
+# Clavue v8.8.93
 
 ![Clavue cover](https://unpkg.com/clavue/image.png)
 
-`clavue` is an AI coding CLI. It is built for execution-first engineering: the terminal remains the control surface, API providers stay configurable routes, permissions are explicit, and setup should move quickly from install to real coding work.
+`clavue` is an execution-first AI coding CLI for real software work. It keeps the terminal as the control surface, uses direct repo tools for inspection/editing/verification, treats API providers as configurable routes, and includes native workflows for review, recovery, team inspection, and long-running sessions.
 
 ## Product Philosophy
 
@@ -11,6 +11,7 @@ Clavue is built around a simple operating model: the user owns the workflow, the
 - Execution first: every feature should help inspect, edit, run, verify, or recover real software work.
 - Terminal-owned workflow: Clavue stays close to files, commands, diffs, permissions, and project state instead of becoming a detached chat surface.
 - Provider control, not provider identity: official login, custom API profiles, and compatible gateways are routing choices. The product identity remains Clavue.
+- Native coding workflows: direct file tools, shell execution, task tracking, worktrees, skills, and MCP resources are part of the runtime loop.
 - Fast first run: install, choose an API configuration mode, paste URL/key or token, set model slots if needed, then start coding.
 - Visible configuration: `/provider` and `clavue provider` expose the active route, saved profiles, credential mode, model slots, validation, repair, and current environment state.
 - Practical autonomy: permission setup should make development smoother while still being explicit about trust boundaries.
@@ -18,7 +19,8 @@ Clavue is built around a simple operating model: the user owns the workflow, the
 
 ## What Clavue Is
 
-- An AI coding CLI for execution-first engineering work.
+- An execution-first AI coding CLI for inspecting, editing, running, verifying, and delivering code from the terminal.
+- A native coding runtime with direct repo tools, shell execution, permissions, tasks, worktrees, skills, MCP resources, and resumable sessions.
 - A provider control center for custom API URLs, API keys, auth tokens, model slots, route validation, and repair.
 - A fast onboarding path for users who want official login, custom API configuration, CCR-compatible proxy routing, or manual setup later.
 - A runtime that can use compatible providers and gateways without pretending those providers are the product.
@@ -46,46 +48,37 @@ Requirements:
 - Node.js 18 or newer
 - macOS or Linux shell environment
 
-Install globally from npm:
-
-```bash
-npm install -g clavue
-```
-
-Run it once with `npx` if you do not want a global install:
+Run once with `npx` when you do not want a global install:
 
 ```bash
 npx -y clavue
 ```
 
-This installs the `clavue` command:
+Run a specific version with `npx`:
 
 ```bash
-clavue
+npx -y clavue@8.8.93 --version
+npx -y clavue@8.8.93
 ```
 
-Then run the built-in installer once to configure the native launcher:
+Install globally from npm when you want the `clavue` command to stay available:
 
 ```bash
+npm install -g clavue
 clavue install --force
-```
-
-After that, you can launch with:
-
-```bash
 clavue
 ```
 
-One-line install:
+One-line global install:
 
 ```bash
 curl -fsSL https://unpkg.com/clavue/install.sh | bash
 ```
 
-Install a specific version:
+Install a specific version globally:
 
 ```bash
-curl -fsSL https://unpkg.com/clavue@8.8.91/install.sh | bash -s -- 8.8.91
+curl -fsSL https://unpkg.com/clavue@8.8.93/install.sh | bash -s -- 8.8.93
 ```
 
 ## Quick Start: Custom API
@@ -120,6 +113,16 @@ clavue provider validate
 
 Use `clavue auth login` only if you want the official Anthropic login path. Custom API users do not need official login.
 
+## First Useful Session
+
+Start Clavue from a repository and ask for one reviewable unit of work:
+
+```text
+Inspect the failing test around provider routing, make the smallest source fix, run the targeted test, then run the relevant verification command before reporting back.
+```
+
+Clavue should inspect files directly, edit the source, run commands such as `node --test tests/<file>.test.mjs`, and report what was verified.
+
 ## First-Run Setup Modes
 
 On first launch, Clavue should make the setup choice obvious:
@@ -139,7 +142,7 @@ On first launch, Clavue should make the setup choice obvious:
 
 After API setup, Clavue can also ask for a default permission mode. The recommended path for a trusted local development machine is the efficient development mode; the maximum-permission mode is intentionally reserved for environments you fully trust.
 
-This package is intended for users who want an execution-first coding CLI with explicit routing control when compatible providers or gateways are part of the setup.
+This package is intended for users who want an execution-first coding CLI with direct repository tools, native workflow orchestration, explicit permission control, and configurable provider routing when compatible providers or gateways are part of the setup.
 
 On macOS, `clavue` avoids Keychain by default and stores local credentials in `~/.clavue/.credentials.json` so startup does not trigger system Keychain prompts. If you explicitly want the old Keychain behavior back, launch with `CLAVUE_USE_KEYCHAIN=1 clavue`.
 
@@ -164,7 +167,8 @@ Version check:
 ```bash
 clavue --version
 npx -y clavue --version
-# available after running: clavue install --force
+npx -y clavue@8.8.93 --version
+# available after a global install and launcher setup
 clavue --version
 ```
 
@@ -257,7 +261,7 @@ Companion commands are still available and can either follow the current app pro
 
 - clavue can import compatible profiles from `~/.ccjk/config.toml` or `~/.ufomiao/zcf/config.toml`.
 - Changing the active clavue provider profile writes the current selection back to those compatible config files.
-- Proxy GPT routes stay on the Anthropic-compatible `/v1/messages` path by default. Only set `MYCLAUDE_API_DIALECT=openai_responses` when you explicitly want the Responses adapter for that gateway.
+- Proxy GPT routes stay on the Anthropic-compatible `/v1/messages` path by default. Set `CLAVUE_API_DIALECT=openai_responses` only when you explicitly want the Responses adapter for that gateway; `MYCLAUDE_API_DIALECT` remains a legacy-compatible alias.
 - Recommended saved profile pattern: `gpt54-main` for a validated `gpt-5.4` route across the primary and inherited slots.
 - Recommended saved profile pattern: `gpt53-all` when the route is validated for `gpt-5.3-codex` across the main thread and helper lanes.
 - Recommended saved profile pattern: `kimi-main` or `glm-main` for provider-native routing with that provider's API URL and credential.