@awebai/claude-channel 1.0.0 → 1.2.0

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@awebai/claude-channel",
3
- "version": "1.0.0",
3
+ "version": "1.2.0",
4
4
  "type": "module",
5
5
  "main": "./dist/index.js",
6
6
  "bin": "./dist/index.js",
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: aw:configure
3
- description: Check and set up the aweb channel connection. Verifies workspace binding, credentials, and MCP server configuration.
3
+ description: Check and set up the aweb channel connection. Verifies workspace binding, team-certificate bootstrap, and MCP server configuration.
4
4
  allowed-tools: Bash(aw *), Bash(cat *), Bash(test *), Bash(ls *)
5
5
  ---
6
6
 
@@ -14,21 +14,24 @@ Diagnose and fix the aweb channel setup for this project.
14
14
 
15
15
  ```bash
16
16
  test -f .aw/workspace.yaml && echo "OK" || echo "MISSING"
17
+ test -f .aw/team-cert.pem && echo "CERT OK" || echo "CERT MISSING"
17
18
  ```
18
19
 
19
- If `.aw/workspace.yaml` is missing, the workspace has not been initialized.
20
+ If `.aw/workspace.yaml` is missing, the workspace is not initialized yet.
20
21
  Tell the user to run:
21
22
 
22
23
  ```bash
23
- aw init
24
+ aw run claude
24
25
  ```
25
26
 
26
- This requires credentials (`~/.config/aw/config.yaml`). If the user doesn't
27
- have credentials yet, they need to either:
28
- - Create a project: `aw project create --server-url https://app.aweb.ai`
29
- - Connect with an API key: `AWEB_URL=https://app.aweb.ai/api AWEB_API_KEY=aw_sk_... aw connect`
27
+ Or use the explicit invite flow:
30
28
 
31
- Stop here until the user has run `aw init` successfully.
29
+ ```bash
30
+ aw id team accept-invite <token>
31
+ AWEB_URL=<server-url> aw init
32
+ ```
33
+
34
+ Do not instruct the user to use legacy project bootstrap commands.
32
35
 
33
36
  2. **Verify the workspace is valid.**
34
37
 
@@ -36,8 +39,9 @@ Diagnose and fix the aweb channel setup for this project.
36
39
  aw workspace status
37
40
  ```
38
41
 
39
- This confirms the workspace can reach the server. If it fails, the
40
- credentials may be expired or the server may be unreachable.
42
+ This confirms the workspace can reach the server and has a usable team
43
+ binding. If it fails, the team certificate may be missing, the server may be
44
+ unreachable, or bootstrap may be incomplete.
41
45
 
42
46
  3. **Check channel MCP configuration.**
43
47
 
@@ -45,7 +49,7 @@ Diagnose and fix the aweb channel setup for this project.
45
49
  cat .mcp.json 2>/dev/null || echo "MISSING"
46
50
  ```
47
51
 
48
- Look for an `mcpServers.aweb` entry. If it's missing, tell the user to run:
52
+ Look for an `mcpServers.aweb` entry. If it is missing, tell the user to run:
49
53
 
50
54
  ```bash
51
55
  aw init --setup-channel
@@ -67,8 +71,12 @@ Diagnose and fix the aweb channel setup for this project.
67
71
 
68
72
  The `cwd` must point to the directory containing `.aw/workspace.yaml`.
69
73
 
70
- 4. **Report status.** Summarize what was found and any actions the user needs to take. If everything is configured, tell the user to start Claude Code with:
74
+ 4. **Report status.** Summarize what was found and what the user still needs to
75
+ do. If everything is configured, tell the user to start Claude Code with:
71
76
 
72
77
  ```bash
73
78
  claude --dangerously-load-development-channels server:aweb
74
79
  ```
80
+
81
+ Reference model: `docs/aweb-sot.md`, `docs/awid-sot.md`, and
82
+ `docs/agent-guide.md`.