When your AI says atbridge.ai is broken
In short: if your AI claims an atbridge.ai tool is broken, or quietly builds
something a different way and calls the task done, it is almost always a local or
out-of-date issue — not a fault in the product. Run atbridge update, restart the
AI app, and ask it to try again.
Why this happens
Section titled “Why this happens”A tool error, or an AI saying a feature “isn’t supported”, nearly always points to a local or temporary problem rather than a fault in atbridge itself. The usual causes are:
- an out-of-date atbridge app,
- an AI client that hasn’t reloaded its tools since the last update, or
- Thunderbird not running.
Updating atbridge and restarting the AI app clears it in nearly every case.
The fix
Section titled “The fix”atbridge update(or atbridge check first to see whether a newer version is available), then fully
quit and restart the AI app (Cmd-Q on macOS, File → Quit on Windows — closing the
window isn’t enough) so it reloads the tools.
Confirm before you believe it
Section titled “Confirm before you believe it”If a model says a feature is broken, check it from a second angle before accepting that:
- Ask it to retry the exact same request.
- Run the same thing on the CLI — e.g.
atbridge compose render --helpshows how to build a branded email, then point--specat a small JSON file and render it. - Try it from a second AI client.
If one client works and another doesn’t, the failing client is the problem — the product is fine.
Still stuck?
Section titled “Still stuck?”Email contact@atbridge.ai with the output of:
atbridge --versionatbridge bridge status --prettyWe usually answer within a day.
Where to go next
Section titled “Where to go next”Was this page helpful?
Thanks for the feedback!