[16,17,20,37,38] Support for both versions in scripts

That sounds great! Thanks for sharing. One note about the migration: although I don't foresee any big changes coming up, the version 2 contract is still in beta. We may still change things based on all of your feedback when needed. When the Early Access period ends and we ship a v2.0.0, you can expect us to keep all commands backwards compatible in all subsequent v2 releases.

I'd love to learn more about your direnv setup. What do you use them for? And what do your .env/.envrc files currently look like?

Have you had the chance to try out the new https://developer.1password.com/docs/cli/secrets-environment-variables support? Would that be useful for your direnv use cases as well? op run -- $SHELL will open a shell with the secrets passed as defined in your .env file and secret references resolved.

I haven't looked in the details yet, but it looks like integration with direnv is possible:

It’s also possible to create your own extensions by creating a bash file at ~/.config/direnv/direnvrc or ~/.config/direnv/lib/*.sh. This file is loaded before your .envrc and thus allows you to make your own extensions to direnv.

Source: https://direnv.net/

So maybe we can make it resolve 1Password secret references as well (e.g. using op read).