Files
computer-playbook/roles/web-app-openclaw/TODO.md
kevinveenbirkenbachandClaude Opus 5 9166e98405 feat(openclaw): wire the agent's models through the platform gateway
The config template already rendered a models.providers block behind an enable flag, but the five variables that block reads did not exist, so the first deploy would have failed on an undefined variable. They follow the same shape Flowise, Hermes and Open WebUI already carry: the flag from the service declaration, the base URL from the gateway's local address, the key from the role's own credential.

This also closes a window the earlier gateway-contract commit opened, since that one added an include gated on OPENCLAW_LITELLM_ENABLED while the variable itself was still uncommitted. The resolved model-wiring entry drops out of the role's TODO.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-29 00:53:36 +02:00

5 lines
528 B
Markdown

# TODO
- Administrator persona: `PERSONA_ADMINISTRATOR_BLOCKED=true` because the Control UI is a WebSocket SPA whose session lives behind gateway device pairing; there is no DOM logout control the shared `inAppLogout` helper can reach. The SSO round-trip itself is covered by `test-oidc-login.js`. Unblock once the Control UI exposes a plain logout affordance or the persona helpers learn the pairing handshake.
- MCP client wiring: the native `@modelcontextprotocol/sdk` client is configured through `openclaw.json`, not env.