5 Commits

Include renames

Author	SHA1	Message	Date
dguiducci	6b827e1b88	fix(llm): resolve catalog capabilities for reasoning-mode queries ... reasoning_mode_for (the add/edit form's reasoning-knob endpoint) evaluated rules against an empty capability set, so a declared provider whose modes are capability-gated never offered the knob; only id-glob rules (deepseek, openai, anthropic) could match. It now resolves the model's capabilities from the provider catalog first. DeclaredProvider also gains llm_model_info (find in the listing) — until now only anthropic/ollama overrode it, which is why a declared model's context_length never refreshed from the catalog either (maybe_refresh_meta always got None). And DeepInfra's entry learns a second mode: models tagged 'reasoning' but not 'reasoning_effort' (R1, DeepSeek-V4-Flash/Pro) accept the plain effort levels per DeepInfra's docs — graded steps stay behind the reasoning_effort tag.	2026-08-07 15:30:45 +01:00
dguiducci	07d96a4881	feat(llm): add DeepInfra as a declarative provider ... DeepInfra's chat API is plain OpenAI-compatible (api.deepinfra.com/v1/openai) and its GET /models returns the OpenAI data envelope, but the declared engine could not describe it: metadata sits under dotted paths (metadata.context_length, metadata.pricing.*), capabilities ride a metadata.tags string array, and the catalog mixes in tts/stt/embed/image models with no way to keep only chat ones. Three generic extensions to the declared engine close that, usable by any future provider entry: - map field names accept dotted paths (metadata.pricing.input_tokens) - map.tags + map.capability_tags enable a capability when the model's tags array contains a value (a vision one also sets the vision flag) - models.filter { field, contains } keeps only listed models whose string-array field holds the value (endpoint listings only) The deepinfra entry filters on the chat tag, maps context/pricing/vision/ reasoning from the live catalog, and wires the flat reasoning_effort knob (disabled remaps to none) for models tagged reasoning_effort.	2026-08-07 14:03:06 +01:00
dguiducci	d1d0a2af26	llm: add dynamic tool loading (DTL) — Kimi system-tools + Anthropic tool-reference ... Replace the old session_mcp_grants/stack_mcp_grants table pair with a single activated_tools table that anchors each activation at the assistant message_id that triggered it. The durable write moves from the activate_tools tool itself to the round loop (handle_tool_call), which has the message_id the DTL serializer positions injected tool blocks against. Introduce DtlMode (None / AnthropicToolReference / KimiSystemTools), resolved per model from capabilities (opt-in via tool_search) combined with the provider's dtl_format(). The message builder inserts Kimi system {tools} blocks at the activation position, or emits Anthropic tool_reference markers on the tool result. The tool-def surface (all_tool_defs) switches shape: Anthropic declares everything deferred; Kimi omits activated tools from the top-level array (system takes over); None keeps the old grant-set logic. Anthropic client: accept structured system arrays (cache_control on the static block when DTL is active), carry defer_loading through conversion, emit tool_reference blocks on result messages. Prompt caching enabled exactly when DTL is active (anthropic provider). MCP server list in the prompt is now a static catalogue (not split Available/Active) — the split invalidated the cache on every activation. Groundwork for providers.yaml dtl: key; Moonshot/Kimi providers wired with kimi_system_tools and the k3* enrich now adds tool_search. Compactor re-anchors activations whose message was compacted away.	2026-07-24 20:48:04 +01:00
dguiducci	2b35312abd	feat(media): multimodal attachments — image/video inlining per model capabilities ... Adds media.rs for per-turn attachment routing, message_builder partitioning by resolved model capabilities, controller endpoints for uploads, and server routing for /data/* behind session auth. See CLAUDE.md §Multimodal attachments for full design.	2026-07-18 18:02:45 +01:00
dguiducci	4fea04c57f	feat(providers): OpenAI-compatible provider types as runtime data (providers.yaml) ... Replace the five copy-paste OpenAI-compatible provider structs (moonshot, moonshot_code, deepseek, zai, lm_studio) with one DeclaredProvider engine driven by a providers.yaml catalog loaded at boot from the cwd — edit and restart, no rebuild. The YAML carries identity, endpoints, per-model JSON field mapping, id-glob enrichment rules and the reasoning knob (effort / thinking request kinds); capability_flags keep vision and future input modalities declarative. Anthropic, Ollama, OpenAI and OpenRouter stay native (different wire protocols or bespoke parsing) and register alongside; colliding declared ids are skipped. The shipped catalog is validated by a unit test.	2026-07-18 16:19:05 +01:00