clew-code 0.2.22 → 0.2.23
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 +45 -45
- package/dist/main.js +2886 -2707
- package/docs/commands.html +157 -156
- package/docs/css/styles.css +545 -425
- package/docs/index.html +185 -160
- package/docs/installation.html +1 -1
- package/docs/js/main.js +3 -3
- package/docs/models.html +81 -69
- package/docs/tools.html +183 -172
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -13,7 +13,7 @@ A multi-provider AI coding CLI that codes, learns your preferences, coordinates
|
|
|
13
13
|
[](https://github.com/ClewCode/ClewCode/releases)
|
|
14
14
|
[](https://www.npmjs.com/package/clew-code)
|
|
15
15
|
[](https://github.com/ClewCode/ClewCode/actions)
|
|
16
|
-
[](#license)
|
|
17
17
|
[](#installation)
|
|
18
18
|
[](https://bun.sh)
|
|
19
19
|
|
|
@@ -44,50 +44,50 @@ Clew Code is a fork of [Claude Code](https://github.com/anthropics/claude-code)
|
|
|
44
44
|
|
|
45
45
|
---
|
|
46
46
|
|
|
47
|
-
## Concepts: Agents, Subagents, Mesh, and ACP
|
|
48
|
-
|
|
49
|
-
Clew Code has several execution layers. They are related, but they do different jobs:
|
|
50
|
-
|
|
51
|
-
- **Agent:** An AI worker with a prompt, model, tools, and permissions. The main chat session is an agent. Custom agents live in `.claude/agents/*.md`, and built-ins include `Explore`, `Plan`, and `general-purpose`.
|
|
52
|
-
- **Subagent:** A short-lived child agent launched by another agent through the `Agent` tool. Use subagents for independent work such as codebase exploration, test triage, or review. The built-in `Explore` agent is read-only and is the right choice for parallel "go inspect this area" tasks.
|
|
53
|
-
- **Teammate / Swarm:** A longer-lived agent team member with an identity, mailbox, task coordination, and optional pane/tmux or in-process execution. Use this when agents need to keep working together across multiple turns, not for isolated one-shot exploration.
|
|
54
|
-
- **LAN Mesh:** A network of Clew instances on the same machine or LAN. `/mesh` discovers peers, sends messages, assigns tasks, and runs commands on other Clew nodes.
|
|
55
|
-
- **Process Mesh:** A local process-backed worker layer. It delegates a prompt to an external CLI/provider such as Codex using `exec` or `pty`, then returns stdout, stderr, exit code, timeout state, and progress.
|
|
56
|
-
- **ACP:** An external protocol boundary. Editors, IDEs, REST clients, or other agents can send work into Clew through ACP. ACP should normalize the external request and route execution through Clew's internal layers instead of hardcoding a provider in every ACP entry point.
|
|
57
|
-
|
|
58
|
-
Typical flows:
|
|
59
|
-
|
|
60
|
-
```text
|
|
61
|
-
User
|
|
62
|
-
-> main Clew agent
|
|
63
|
-
-> Agent tool
|
|
64
|
-
-> short-lived subagent, e.g. Explore
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
```text
|
|
68
|
-
External editor / external agent
|
|
69
|
-
-> ACP
|
|
70
|
-
-> shared ACP-to-mesh boundary
|
|
71
|
-
-> Process Mesh provider, e.g. codex
|
|
72
|
-
-> external CLI process
|
|
73
|
-
```
|
|
74
|
-
|
|
75
|
-
```text
|
|
76
|
-
Clew instance A
|
|
77
|
-
-> LAN Mesh
|
|
78
|
-
-> Clew instance B
|
|
79
|
-
-> local agent, daemon task, or process worker
|
|
80
|
-
```
|
|
81
|
-
|
|
82
|
-
Use the layers by intent:
|
|
83
|
-
|
|
84
|
-
- Need a quick independent read-only investigation? Use an `Explore` subagent.
|
|
85
|
-
- Need long-running coordination between named workers? Use teammates/swarm.
|
|
86
|
-
- Need another Clew instance on the LAN? Use `/mesh`.
|
|
87
|
-
- Need an external editor or agent to call into Clew? Use ACP.
|
|
88
|
-
- Need Clew to run a local external worker such as Codex? Use Process Mesh.
|
|
89
|
-
|
|
90
|
-
Other runtime concepts:
|
|
47
|
+
## Concepts: Agents, Subagents, Mesh, and ACP
|
|
48
|
+
|
|
49
|
+
Clew Code has several execution layers. They are related, but they do different jobs:
|
|
50
|
+
|
|
51
|
+
- **Agent:** An AI worker with a prompt, model, tools, and permissions. The main chat session is an agent. Custom agents live in `.claude/agents/*.md`, and built-ins include `Explore`, `Plan`, and `general-purpose`.
|
|
52
|
+
- **Subagent:** A short-lived child agent launched by another agent through the `Agent` tool. Use subagents for independent work such as codebase exploration, test triage, or review. The built-in `Explore` agent is read-only and is the right choice for parallel "go inspect this area" tasks.
|
|
53
|
+
- **Teammate / Swarm:** A longer-lived agent team member with an identity, mailbox, task coordination, and optional pane/tmux or in-process execution. Use this when agents need to keep working together across multiple turns, not for isolated one-shot exploration.
|
|
54
|
+
- **LAN Mesh:** A network of Clew instances on the same machine or LAN. `/mesh` discovers peers, sends messages, assigns tasks, and runs commands on other Clew nodes.
|
|
55
|
+
- **Process Mesh:** A local process-backed worker layer. It delegates a prompt to an external CLI/provider such as Codex using `exec` or `pty`, then returns stdout, stderr, exit code, timeout state, and progress.
|
|
56
|
+
- **ACP:** An external protocol boundary. Editors, IDEs, REST clients, or other agents can send work into Clew through ACP. ACP should normalize the external request and route execution through Clew's internal layers instead of hardcoding a provider in every ACP entry point.
|
|
57
|
+
|
|
58
|
+
Typical flows:
|
|
59
|
+
|
|
60
|
+
```text
|
|
61
|
+
User
|
|
62
|
+
-> main Clew agent
|
|
63
|
+
-> Agent tool
|
|
64
|
+
-> short-lived subagent, e.g. Explore
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
```text
|
|
68
|
+
External editor / external agent
|
|
69
|
+
-> ACP
|
|
70
|
+
-> shared ACP-to-mesh boundary
|
|
71
|
+
-> Process Mesh provider, e.g. codex
|
|
72
|
+
-> external CLI process
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
```text
|
|
76
|
+
Clew instance A
|
|
77
|
+
-> LAN Mesh
|
|
78
|
+
-> Clew instance B
|
|
79
|
+
-> local agent, daemon task, or process worker
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
Use the layers by intent:
|
|
83
|
+
|
|
84
|
+
- Need a quick independent read-only investigation? Use an `Explore` subagent.
|
|
85
|
+
- Need long-running coordination between named workers? Use teammates/swarm.
|
|
86
|
+
- Need another Clew instance on the LAN? Use `/mesh`.
|
|
87
|
+
- Need an external editor or agent to call into Clew? Use ACP.
|
|
88
|
+
- Need Clew to run a local external worker such as Codex? Use Process Mesh.
|
|
89
|
+
|
|
90
|
+
Other runtime concepts:
|
|
91
91
|
- **Plan mode:** Full-access planning mode with bypass permissions — explore, read, write, and edit files freely. Plan files persist to `.clew/plans/long-term-plan.md` with task progress snapshot.
|
|
92
92
|
- **Multi-pass compaction:** Automatic chunk-based context compression with recursive re-compaction when context exceeds the model window.
|
|
93
93
|
|