clavue 8.8.90 → 8.8.92

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
- # Clavue v8.8.90
1
+ # Clavue v8.8.92
2
2
 
3
3
  ![Clavue cover](https://unpkg.com/clavue/image.png)
4
4
 
5
- `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.
5
+ `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.
6
6
 
7
7
  ## Product Philosophy
8
8
 
@@ -11,6 +11,7 @@ Clavue is built around a simple operating model: the user owns the workflow, the
11
11
  - Execution first: every feature should help inspect, edit, run, verify, or recover real software work.
12
12
  - Terminal-owned workflow: Clavue stays close to files, commands, diffs, permissions, and project state instead of becoming a detached chat surface.
13
13
  - Provider control, not provider identity: official login, custom API profiles, and compatible gateways are routing choices. The product identity remains Clavue.
14
+ - Native coding workflows: direct file tools, shell execution, task tracking, worktrees, skills, and MCP resources are part of the runtime loop.
14
15
  - Fast first run: install, choose an API configuration mode, paste URL/key or token, set model slots if needed, then start coding.
15
16
  - Visible configuration: `/provider` and `clavue provider` expose the active route, saved profiles, credential mode, model slots, validation, repair, and current environment state.
16
17
  - 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
18
19
 
19
20
  ## What Clavue Is
20
21
 
21
- - An AI coding CLI for execution-first engineering work.
22
+ - An execution-first AI coding CLI for inspecting, editing, running, verifying, and delivering code from the terminal.
23
+ - A native coding runtime with direct repo tools, shell execution, permissions, tasks, worktrees, skills, MCP resources, and resumable sessions.
22
24
  - A provider control center for custom API URLs, API keys, auth tokens, model slots, route validation, and repair.
23
25
  - A fast onboarding path for users who want official login, custom API configuration, CCR-compatible proxy routing, or manual setup later.
24
26
  - A runtime that can use compatible providers and gateways without pretending those providers are the product.
@@ -85,7 +87,7 @@ curl -fsSL https://unpkg.com/clavue/install.sh | bash
85
87
  Install a specific version:
86
88
 
87
89
  ```bash
88
- curl -fsSL https://unpkg.com/clavue@8.8.90/install.sh | bash -s -- 8.8.90
90
+ curl -fsSL https://unpkg.com/clavue@8.8.92/install.sh | bash -s -- 8.8.92
89
91
  ```
90
92
 
91
93
  ## Quick Start: Custom API
@@ -139,7 +141,7 @@ On first launch, Clavue should make the setup choice obvious:
139
141
 
140
142
  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.
141
143
 
142
- 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.
144
+ 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.
143
145
 
144
146
  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`.
145
147