When a new AI arrives, put it to work sooner
AI changes quickly, and the client should not be the last place to catch up.
New models and capabilities should become usable by roles sooner, shortening the gap between “this AI exists” and “I can actually use it for the project.”
New models, capabilities, and versions appear constantly. If every one of them requires a full client release, new UI work, and another update before it becomes usable, the delay between availability and real work becomes much longer than it needs to be.
The client should not be the last link in the update chain
FinchStory is making the set of available models and capabilities easier to refresh so new AI can reach role selection sooner. Model catalogs, provider metadata, and capability synchronization can stay underneath; they do not need to become concepts you manage.
Move faster from “new” to “usable”
The more useful questions are: when can this new AI actually join your project, what can it do, and is it a good fit for the task you have now?
FinchStory is trying to shorten the distance between “the AI exists” and “you can actually put it to work.”
What changed