Claygent performance can vary based on several factors. Recent updates to Claude Sonnet 3.7 doubled estimated token usage per run, which may cause slower processing but improves stability.
Common causes of delays include:
Rate limits on heavier prompts or lower API tiers
Large data requests that need breaking into smaller batches
Network connection issues
However, we've also introduced GPT-5 which improved research accuracy by 8-17% while consuming 38% fewer tokens, making it faster overall. [1]
To optimize performance: use specific queries, monitor your usage limits, and break large requests into smaller batches.
If you still need help with Claygent's performance or have other questions, I'm here to assist. Would you like to provide more details about what you're trying to resolve or understand?
