Remove OpenClaw fallback compatibility
This commit is contained in:
19
README.md
19
README.md
@@ -100,25 +100,6 @@ WORKFLOW_LOCAL_QUEUE_CONCURRENCY=100
|
||||
If `ZHIPU_API_KEY` is unset, the app uses local fallback analysis so task workflows still run.
|
||||
`ZHIPU_BASE_URL` is deprecated and ignored; runtime always uses `https://api.z.ai/api/coding/paas/v4`.
|
||||
|
||||
## Migration from OPENCLAW_* to ZHIPU_*
|
||||
|
||||
This repository now uses direct provider calls through AI SDK. The legacy gateway container path is removed.
|
||||
The AI runtime endpoint is fixed to `https://api.z.ai/api/coding/paas/v4`.
|
||||
|
||||
| Legacy variable | Replacement |
|
||||
| --- | --- |
|
||||
| `OPENCLAW_API_KEY` | `ZHIPU_API_KEY` |
|
||||
| `OPENCLAW_MODEL` | `ZHIPU_MODEL` |
|
||||
| `OPENCLAW_BASE_URL` | Removed (runtime endpoint is hardcoded to `https://api.z.ai/api/coding/paas/v4`) |
|
||||
| `OPENCLAW_AUTH_MODE` | Removed (not needed with direct provider calls) |
|
||||
| `OPENCLAW_BASIC_AUTH_USERNAME` | Removed |
|
||||
| `OPENCLAW_BASIC_AUTH_PASSWORD` | Removed |
|
||||
| `OPENCLAW_API_KEY_HEADER` | Removed |
|
||||
| `OPENCLAW_PORT` | Removed (no gateway service) |
|
||||
| `OPENCLAW_IMAGE` | Removed |
|
||||
| `OPENCLAW_BUILD_CONTEXT` | Removed |
|
||||
| `OPENCLAW_DOCKERFILE` | Removed |
|
||||
|
||||
## API surface
|
||||
|
||||
All endpoints below are defined in Elysia at `lib/server/api/app.ts` and exposed via `app/api/[[...slugs]]/route.ts`.
|
||||
|
||||
Reference in New Issue
Block a user