Read the real reason behind a failed action

You click something, it fails, and the screen says "Verification failed" or "HTTP 500". You are left guessing whether to retry, change something, or ask someone else to fix it. Several places in Chief now say the actual reason.

Magic link verification

A magic link that had expired or already been used showed a bare "Verification failed". The verification page now tells you the link expired or was already used, so you know to request a fresh one.

Rejected organization API keys

When your organization runs on its own provider key and the provider rejects it, the chat error card used to headline "Unable to complete operation". The card now names the rejected API key and points to organization settings, where an owner can update it, and it says so in your own language rather than English.

Skill and persona names

A long skill or persona name passed the create screen and then failed on save with a "try again later" message that no amount of retrying resolved. Chief now tells you the name is too long and asks for 128 characters or fewer, before you lose the work. Copying a skill with a long name also keeps its "(Copy)" suffix instead of colliding with the original.

Skills and API tokens pages

Once your session token expired, the Skills page and the API tokens page in settings showed only a status code. Both now show the sentence the server sent, so you can tell an expired session apart from a genuine failure.

Generated images and charts

A generated image or chart that could not load left a blank card with nothing to act on. You now see why it failed and can retry.

Tool results that run long

When a tool returned more than the model could take, every tool gave the same generic advice. Each tool now reports its own wording, so a web search that returns too much says so and the retry narrows the right thing instead of guessing.

Next time something fails, read the message on screen. It should tell you whether to retry, shorten a name, or update a key.