You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(SKILL.md): simplify plugin config — ~/.acontext/ is the primary config source
Remove env var configuration examples and explicit apiKey/userId from config
tables since both plugins now auto-read from ~/.acontext/ files after login.
Update troubleshooting to reference `acontext whoami` instead of env vars.
Fix openclaw apiKey resolution comment to match actual priority order.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: landingpage/public/SKILL.md
+25-56Lines changed: 25 additions & 56 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,10 +41,10 @@ acontext login
41
41
- If you're in a Interactive Terminal(TTY), this command will open a browser for OAuth, then guides you through project creation. Your API key is saved automatically.
42
42
- If you're in a Non-interactive Terminal(agent/CI), this command will print a login URL for the user to open manually. After user completes, run `acontext login --poll` to finish authentication.
43
43
- Set up a project via `acontext dash projects` commands. If Acontext has existing projects, make sure the user wants to use an existing project or create a new project for you.
44
-
- Read the cli output to get the api key and user login email, you will need it.
45
-
46
44
### 3. Add Acontext to Your Agent
47
45
46
+
Both plugins automatically read your API key and user email from `~/.acontext/credentials.json` and `~/.acontext/auth.json` (written by `acontext login`). No manual configuration is needed after login.
47
+
48
48
#### Option A: Claude Code Plugin
49
49
50
50
Add the Acontext marketplace and install the plugin (run inside Claude Code):
@@ -54,15 +54,6 @@ Add the Acontext marketplace and install the plugin (run inside Claude Code):
54
54
/plugin install acontext
55
55
```
56
56
57
-
The plugin automatically reads your API key and user email from `~/.acontext/credentials.json` and `~/.acontext/auth.json` (written by `acontext login`). No manual environment variable setup is needed.
58
-
59
-
If you prefer explicit configuration, you can set environment variables in your shell profile (`~/.bashrc` or `~/.zshrc`) — they serve as fallback when the files are not present:
60
-
61
-
```bash
62
-
export ACONTEXT_API_KEY="<your-api-key>"
63
-
export ACONTEXT_USER_ID="<your-login-email>"
64
-
```
65
-
66
57
Restart Claude Code — the plugin auto-captures conversations and syncs skills to `~/.claude/skills/`.
67
58
68
59
#### Option B: OpenClaw Plugin
@@ -71,7 +62,7 @@ Restart Claude Code — the plugin auto-captures conversations and syncs skills
71
62
openclaw plugins install @acontext/openclaw
72
63
```
73
64
74
-
The plugin automatically reads your API key and user email from `~/.acontext/credentials.json` and `~/.acontext/auth.json` (written by `acontext login`). You only need to add a minimal config to `openclaw.json`:
65
+
Add a minimal config to `openclaw.json`:
75
66
76
67
```json5
77
68
{
@@ -84,26 +75,7 @@ The plugin automatically reads your API key and user email from `~/.acontext/cre
84
75
}
85
76
```
86
77
87
-
If you prefer explicit configuration, add API key and user to your `openclaw.json`:
88
-
```json5
89
-
{
90
-
plugins: {
91
-
slots: {
92
-
memory:"acontext"
93
-
},
94
-
entries: {
95
-
"acontext": {
96
-
enabled:true,
97
-
config: {
98
-
"apiKey":"${ACONTEXT_API_KEY}",
99
-
"userId":"${ACONTEXT_USER_MAIL}"
100
-
}
101
-
}
102
-
}
103
-
}
104
-
}
105
-
```
106
-
3. Restart the gateway:
78
+
Restart the gateway:
107
79
108
80
```bash
109
81
openclaw gateway
@@ -155,18 +127,16 @@ The directory must contain a `SKILL.md` with name and description in YAML front-
155
127
156
128
## Claude Code Plugin Configuration
157
129
158
-
Settings are resolved with priority: `~/.acontext/` files > environment variables > defaults. After running `acontext login`, the plugin works automatically without any env vars.
130
+
After `acontext login`, the plugin works automatically — API key and user are read from `~/.acontext/`. The following env vars can override defaults if needed:
0 commit comments