clavue 8.8.72 → 8.8.74
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 +52 -13
- package/dist/cli.js +1762 -1762
- package/dist/provider-setup.js +1 -1
- package/package.json +7 -2
package/README.md
CHANGED
|
@@ -1,21 +1,41 @@
|
|
|
1
|
-
# Clavue v8.8.
|
|
1
|
+
# Clavue v8.8.74
|
|
2
2
|
|
|
3
3
|

|
|
4
4
|
|
|
5
|
-
`clavue` is an AI coding CLI. It
|
|
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.
|
|
6
6
|
|
|
7
|
-
##
|
|
7
|
+
## Product Philosophy
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
Clavue is built around a simple operating model: the user owns the workflow, the CLI owns the execution loop, and providers are replaceable routes.
|
|
10
|
+
|
|
11
|
+
- Execution first: every feature should help inspect, edit, run, verify, or recover real software work.
|
|
12
|
+
- Terminal-owned workflow: Clavue stays close to files, commands, diffs, permissions, and project state instead of becoming a detached chat surface.
|
|
13
|
+
- Provider control, not provider identity: official login, custom API profiles, and compatible gateways are routing choices. The product identity remains Clavue.
|
|
14
|
+
- Fast first run: install, choose an API configuration mode, paste URL/key or token, set model slots if needed, then start coding.
|
|
15
|
+
- Visible configuration: `/provider` and `clavue provider` expose the active route, saved profiles, credential mode, model slots, validation, repair, and current environment state.
|
|
16
|
+
- Practical autonomy: permission setup should make development smoother while still being explicit about trust boundaries.
|
|
17
|
+
- Continuity over spectacle: long-context recovery, compaction, `/mao`, `/team`, and `/retro` exist to keep work moving, not to add noise.
|
|
18
|
+
|
|
19
|
+
## What Clavue Is
|
|
10
20
|
|
|
11
|
-
|
|
21
|
+
- An AI coding CLI for execution-first engineering work.
|
|
22
|
+
- A provider control center for custom API URLs, API keys, auth tokens, model slots, route validation, and repair.
|
|
23
|
+
- A fast onboarding path for users who want official login, custom API configuration, CCR-compatible proxy routing, or manual setup later.
|
|
24
|
+
- A runtime that can use compatible providers and gateways without pretending those providers are the product.
|
|
25
|
+
- A set of native workflows for coding, review, recovery, team inspection, and retrospective improvement.
|
|
26
|
+
|
|
27
|
+
## Core Surfaces
|
|
28
|
+
|
|
29
|
+
- `/provider`: configure, switch, validate, repair, copy, edit, delete, or save provider profiles.
|
|
30
|
+
- `/approvals`: set the default permission mode so trusted development environments can run with less friction.
|
|
31
|
+
- `/mao`: run bundled Codex-style review and rescue flows through the active Clavue provider profile.
|
|
32
|
+
- `/team`: inspect local team readiness, active team config, and capability state.
|
|
33
|
+
- `/retro`: run a multi-round repo retrospective and upgrade loop.
|
|
34
|
+
- Long-context recovery: proactive compaction plus reactive overflow recovery for long-running work.
|
|
35
|
+
|
|
36
|
+
## Study Guide
|
|
12
37
|
|
|
13
|
-
|
|
14
|
-
- Provider control center for saved profiles, current API environment, credentials, model slots, validation, and repair
|
|
15
|
-
- `/mao` bundled Codex execution through the active clavue provider profile without a separate Codex login flow
|
|
16
|
-
- `/team` local team inspection with concrete provider-readiness and capability reporting
|
|
17
|
-
- Remote session surfaces that show the remote cwd, clear backend context correctly, and mark idle task boards as not currently running
|
|
18
|
-
- Proactive compaction plus reactive overflow recovery to keep long-context sessions usable
|
|
38
|
+
For full user-facing usage and learning documentation, start in [study/README.md](./study/README.md).
|
|
19
39
|
|
|
20
40
|
## Install
|
|
21
41
|
|
|
@@ -63,10 +83,10 @@ curl -fsSL https://unpkg.com/clavue/install.sh | bash
|
|
|
63
83
|
Install a specific version:
|
|
64
84
|
|
|
65
85
|
```bash
|
|
66
|
-
curl -fsSL https://unpkg.com/clavue@8.8.
|
|
86
|
+
curl -fsSL https://unpkg.com/clavue@8.8.74/install.sh | bash -s -- 8.8.74
|
|
67
87
|
```
|
|
68
88
|
|
|
69
|
-
## Quick Start
|
|
89
|
+
## Quick Start: Custom API
|
|
70
90
|
|
|
71
91
|
Fastest path for custom API users:
|
|
72
92
|
|
|
@@ -97,6 +117,25 @@ clavue provider validate
|
|
|
97
117
|
|
|
98
118
|
Use `clavue auth login` only if you want the official Anthropic login path. Custom API users do not need official login.
|
|
99
119
|
|
|
120
|
+
## First-Run Setup Modes
|
|
121
|
+
|
|
122
|
+
On first launch, Clavue should make the setup choice obvious:
|
|
123
|
+
|
|
124
|
+
```text
|
|
125
|
+
请选择 API 配置模式:
|
|
126
|
+
使用官方登录
|
|
127
|
+
自定义 API 配置
|
|
128
|
+
使用 CCR 代理
|
|
129
|
+
跳过(稍后手动配置)
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
- Use official login when you want the official Anthropic account flow.
|
|
133
|
+
- Use custom API configuration when you have an API base URL plus API key or auth token.
|
|
134
|
+
- Use CCR proxy when your environment already standardizes on a compatible proxy route.
|
|
135
|
+
- Skip only when you want to configure later with `clavue provider` or `/provider`.
|
|
136
|
+
|
|
137
|
+
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.
|
|
138
|
+
|
|
100
139
|
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.
|
|
101
140
|
|
|
102
141
|
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`.
|