# you have not passed an authentication token on replicate-python 0.14.0 and later

Starting with 0.14.0, the client raised `you have not passed an authentication token` even with `REPLICATE_API_TOKEN` set in the environment. Maintainer mattt confirmed a behavior change in how the default client was initialized at import time caused the regression. The fix was merged in PR #170 and released in 0.15.4. Upgrading to 0.15.4 or later restores the old behavior of picking the token up from the environment.

## How to handle it

If you get `you have not passed an authentication token` on replicate-python 0.14.0 or newer despite having `REPLICATE_API_TOKEN` set, this is the import-time default-client regression from 0.14.0, not a problem with your token. Upgrade to 0.15.4 or later, where PR #170 restored the previous behavior. If you build your own client instance, double check that your `replicate.run` calls use that instance and not the module-level default, which is a separate common cause of the same message.
Source: https://github.com/replicate/replicate-python/issues/169