GPTScript 0.3 was released this week, and introduced support for using different LLM providers beyond OpenAI. In this blog, Craig Jellick details the new feature.
Introducing Credential Management in GPTScript v0.5
Apr 16, 2024 by Craig Jellick
We're pleased to announce the release v0.5 of GPTScript. If you're paying attention you'll note that this is our third feature release in as many weeks. As a young project, our goal is to get features into the hands of users as quickly as possible. As such, we are essentially cutting new feature releases as soon as a useful new feature lands. For v0.5, that feature is credential provider tools.
Up until now, if you used a GPTScript tool that required a credential, the convention was simply to set that credential as an environment variable. This works well enough, but it makes discovery and usage of new tools a bit clunky. You have to figure out what ENV vars the tool is looking for and set them indepent of using GPTScript. Our new feature makes this process much smoother. The first time you use a tool that leverages a credential provider, you'll be prompted for the required credential. The credential will then be stored as part of a config file or in your workstation's native credential store.
We're converting our existing tools to use this framework. For example, the Brave Search tool now prompts you for you an API key. Here's a quick asciinema cast of this feature in action:
Wrapping Up
That does it for the overview of the credential provide feature and the v0.5 release. You can find the full documentation for the feature here
