This update made agent execution easier to reason about financially and operationally. Spending rules became more explicit, missing credentials became less of an immediate dead end, and blocked execution started telling users why it was blocked.
Spending Limits Became Clearer And Safer
Kindship now does a better job turning billing policy into something users can actually understand and trust.
- Starter credits and daily spending caps are reflected more honestly
- Execution is gated more cleanly when credits are depleted or the daily cap is reached
- Billing copy is closer to the real operating model, which reduces the gap between what the product says and what it will actually do
Eligible Agents Can Fall Back To Kindship-Managed Credentials
Missing your own provider key no longer has to mean immediate paralysis.
- Eligible accounts can use Kindship-managed credentials as a fallback
- The credential UI tells you when an agent is running on Kindship-shared access instead of your own key
- New agents can pick a sensible starting CLI automatically, based on the credentials that are actually available
Blocked Dispatch Explains Itself
When an agent cannot run, the workspace now makes that state more legible.
- Dispatch-blocked banners explain why work cannot start
- Reason-specific notifications make blocked execution easier to notice
- The result is less guesswork around whether an agent is idle by choice or blocked by a real constraint