Use this when the user has an access code from open.maic.chat and wants to skip local setup.
accessCode from skill config (~/.openclaw/openclaw.json → skills.entries.openmaic.config.accessCode).If not found, tell the user to add their access code to the config file:
Edit ~/.openclaw/openclaw.json and set skills.entries.openmaic.config.accessCode to your access code (starts with sk-).
Wait for the user to confirm before continuing. Do not ask them to paste the code in chat.
Verify connectivity: GET https://open.maic.chat/api/health with Authorization: Bearer <access-code>
Follow the same generation flow as generate-flow.md with these differences:
https://open.maic.chat (hardcoded, not configurable)Authorization: Bearer <access-code> on all API requestshttps://open.maic.chat/classroom/{id}Before generating, query GET https://open.maic.chat/api/health (with auth header) to check capabilities. Automatically include optional feature flags (enableWebSearch, enableImageGeneration, etc.) based on what the server supports. Do not send new fields if the server does not return capabilities (older version). This ensures forward compatibility — the hosted instance may update on a different schedule than the local codebase.
Daily quota exhausted, inform the user of the daily limit and that it resets at midnight.| HTTP Status | Meaning | Action |
|---|---|---|
| 401 | Invalid access code | Ask user to check their code or generate a new one at open.maic.chat |
| 403 | Quota exhausted | Inform daily limit (10), suggest trying tomorrow |
| 500 | Server error | Suggest retrying later or switching to local mode |