[LOW] Hardcoded model names in fallback chains should be configurable #53

Closed
opened 2026-03-14 18:47:37 +00:00 by kimi · 0 comments
Collaborator

Problem

Model fallback chains have hardcoded names:

# timmy/agent.py:33-48
# timmy/backends.py:26-30

Hardcoded: qwen3.5:latest, llama3.1:8b-instruct, etc.

Impact

  • Cannot customize fallbacks without code changes
  • New Ollama models require code updates

Acceptance Criteria

  • Add FALLBACK_MODELS to config.py
  • Use settings.fallback_models in agent.py
  • Document format in .env.example
  • Maintain backward compatibility

Priority: LOW

## Problem Model fallback chains have hardcoded names: ```python # timmy/agent.py:33-48 # timmy/backends.py:26-30 ``` Hardcoded: qwen3.5:latest, llama3.1:8b-instruct, etc. ## Impact - Cannot customize fallbacks without code changes - New Ollama models require code updates ## Acceptance Criteria - [ ] Add FALLBACK_MODELS to config.py - [ ] Use settings.fallback_models in agent.py - [ ] Document format in .env.example - [ ] Maintain backward compatibility ## Priority: LOW
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#53