-
|
just curious if there is a difference between in token usage between pets enabled and disabled. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
This |
Beta Was this translation helpful? Give feedback.
-
|
Pets are just a UI/status overlay, they don't add anything to your prompt or the conversation context. The animation is purely local, it reads the agent state (running, waiting, ready for review) and renders it on your desktop. So enabling or disabling them in a normal session doesn't change token usage. The one exception is the /hatch flow if you generate a custom pet from a description. That call goes through the model and obviously costs tokens, but it's a one-shot generation, not something that runs every turn. tldr: built-in pets are free, hatching a custom one is a one-time cost, normal coding sessions are identical token-wise either way. |
Beta Was this translation helpful? Give feedback.
Pets are just a UI/status overlay, they don't add anything to your prompt or the conversation context. The animation is purely local, it reads the agent state (running, waiting, ready for review) and renders it on your desktop. So enabling or disabling them in a normal session doesn't change token usage.
The one exception is the /hatch flow if you generate a custom pet from a description. That call goes through the model and obviously costs tokens, but it's a one-shot generation, not something that runs every turn.
tldr: built-in pets are free, hatching a custom one is a one-time cost, normal coding sessions are identical token-wise either way.