| Your agent asks you to sign in again | This is expected after 90 days, or after 30 days without use. Run npx @colosseum-org/copilot-connect login. |
| Your agent says Copilot can’t be reached | Run npx @colosseum-org/copilot-connect status. If it reports a network or service problem, your sign-in is still saved. Try again in a few minutes. |
| Your agent keeps asking for a new sign-in, even though you just signed in | An old setting points your agent at the old version of Copilot. Remove COLOSSEUM_COPILOT_API_BASE from your shell profile or agent settings, or set it to https://copilot.colosseum.com/api/v2. Signing in again won’t fix this. |
| Answers don’t include Frontier, or new features are missing | You have the old skill. Run npx skills add ColosseumOrg/colosseum-copilot -g, start a new agent session, and sign in. Old access tokens stop working on October 28, 2026. |
| Your agent still follows old instructions after you updated | An older copy of the skill may still be installed. Update the global copy with npx skills add ColosseumOrg/colosseum-copilot -g. Then, in the project you’re working in, check npx skills ls; if it lists colosseum-copilot, remove that copy with npx skills remove colosseum-copilot. Start a new agent session afterwards. |
| Your agent says Copilot refused access | Check that you signed in with the right account. Signing in again won’t unlock something your account can’t use. If it continues, contact us. |
| Your agent says Copilot is busy or rate-limited | Wait a minute, then try again. Asking for fewer things at once helps. |
| Requests time out or fail | Wait a few minutes and try again. If it keeps happening, contact us with the time and the error. |
| A search finds nothing | Check the spelling, drop some filters, or ask a broader question. Copilot’s records have gaps, especially outside Solana. |