romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92697edb7c
openclaw/docs/experiments/onboarding-config-protocol.md
Jon Shapiro 92697edb7c fix(venice): add compat settings to prevent HTTP 400 errors 
Venice's API doesn't support certain OpenAI-compatible parameters that
Clawdbot sends by default:

- `store`: Venice returns HTTP 400 with no body when this is present
- `developer` role: Not supported by Venice's API

This adds VENICE_COMPAT settings (supportsStore: false,
supportsDeveloperRole: false) to all Venice model definitions, both
from the static catalog and dynamically discovered models.

Fixes issues reported in PR #1666 where users experienced silent
failures (HTTP 400, no body) when using Venice models.

Co-authored-by: jonisjongithub <jonisjongithub@users.noreply.github.com>
Co-authored-by: Clawdbot <bot@clawd.bot>
2026-01-26 17:56:01 -08:00

1.3 KiB
Raw Blame History

summary read_when
RPC protocol notes for onboarding wizard and config schema Changing onboarding wizard steps or config schema endpoints

Onboarding + Config Protocol

Purpose: shared onboarding + config surfaces across CLI, macOS app, and Web UI.

Components

  • Wizard engine (shared session + prompts + onboarding state).
  • CLI onboarding uses the same wizard flow as the UI clients.
  • Gateway RPC exposes wizard + config schema endpoints.
  • macOS onboarding uses the wizard step model.
  • Web UI renders config forms from JSON Schema + UI hints.

Gateway RPC

  • wizard.start params: { mode?: "local"|"remote", workspace?: string }
  • wizard.next params: { sessionId, answer?: { stepId, value? } }
  • wizard.cancel params: { sessionId }
  • wizard.status params: { sessionId }
  • config.schema params: {}

Responses (shape)

  • Wizard: { sessionId, done, step?, status?, error? }
  • Config schema: { schema, uiHints, version, generatedAt }

UI Hints

  • uiHints keyed by path; optional metadata (label/help/group/order/advanced/sensitive/placeholder).
  • Sensitive fields render as password inputs; no redaction layer.
  • Unsupported schema nodes fall back to the raw JSON editor.

Notes

  • This doc is the single place to track protocol refactors for onboarding/config.