mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
zeekay
e3fb055d87
Make enso the default model across the three layers that set it: the code fallback (src/agents/defaults.ts DEFAULT_MODEL), the shipped config default (bot-config.json agents.defaults.model → hanzo/enso), and the cloud deploy env (Dockerfile.cloud BOT_DEFAULT_MODEL). Provider stays hanzo (api.hanzo.ai); enso routes each request to the best-fit model, so an easy turn bills cheap. Derived default tests (sessions-spawn.model) assert hanzo/enso via the imported symbol and stay green; the tier-model per-plan defaults are a separate concern, left unchanged. GATED: config only, do not deploy — go-live depends on enso being served on api.hanzo.ai (ENSO_URL in ai) and enso-ultra preservation validation.
28 lines
523 B
JSON
28 lines
523 B
JSON
{
|
|
"canvasHost": {
|
|
"liveReload": false
|
|
},
|
|
"agents": {
|
|
"defaults": {
|
|
"model": "hanzo/enso"
|
|
}
|
|
},
|
|
"models": {
|
|
"providers": {
|
|
"anthropic": {
|
|
"baseUrl": "https://api.hanzo.ai",
|
|
"api": "anthropic-messages",
|
|
"models": []
|
|
}
|
|
}
|
|
},
|
|
"gateway": {
|
|
"controlUi": {
|
|
"allowedOrigins": ["http://localhost:18789", "http://localhost:3000"],
|
|
"allowInsecureAuth": true,
|
|
"dangerouslyDisableDeviceAuth": true,
|
|
"basePath": "/__bot__"
|
|
}
|
|
}
|
|
}
|