Tags give the ability to mark specific points in history as being important
-
v0.2.1
fbe65c70 · ·v0.2.1 — require explicit model list for API mode Follow-up to v0.2.0. The previous release's /v1/models endpoint silently fell back to [adapter.name] (e.g. ["pi"]) when no model list was configured — that's a harness binary name, not a valid model id. OAI clients calling /v1/chat/completions with model="pi" got nonsense. This release: - API mode refuses to boot if neither AICODEBOX_AVAILABLE_MODELS nor adapter.available_models declares anything. Loud failure with a clear "set this env var" message. - /v1/models reflects the configured list verbatim — no adapter-name fallback. - Telegram /model and /effort pickers degrade gracefully on empty list (reply with a "set this env var" message; bot keeps running). - Cron / MCP / passthrough are unaffected — they forward the caller's model string to the harness, which errors directly on bad model ids. - shared/choices.py is the single source of truth for the list. Breaking change vs v0.2.0: API mode containers that didn't set AICODEBOX_AVAILABLE_MODELS used to boot and serve /v1/models with the bogus fallback. Now they refuse to start. Set the env var (comma-separated) with the model ids your provider actually serves. -
v0.2.0
090e760a · ·v0.2.0 — env var rename + standalone MCP mode Every mode flag and knob follows <MODE>_MODE / <MODE>_MODE_<KNOB> now. MCP is independent of API/Telegram/Cron and can coexist (sidecar in non-API modes, /mcp mount inside API). Separate bearer token per surface (API_MODE_TOKEN vs MCP_MODE_TOKEN), no fallback between them. Breaking change: every consumer setting AICODEBOX_MODE_API, AICODEBOX_TELEGRAM_BOT_TOKEN, AICODEBOX_MODE_CRON_FILE, etc., needs to rename to the new shape. No backwards-compat shim — clean break.
-
-
-
-