Skip to main content

Promptscape Explorer

The Promptscape Explorer provides you with a centralized library to manage your prompt engineering project assets. It is a view that the extension contributes to VSCode. By default, it will appear in the Activity Bar, along with views like Source Code Management and Debugging. Look for the icon in the Activity Bar after installing. If you don't see it, right click to enable it.

explorer-icon

Look for this icon.

You can drag and drop views around VSCode (like to the terminal panel, or the chat view), but this isn't recommended, as it is difficult to reset to defaults, and very easy to lose track of views.

Explorer Views​

There are four views available in the explorer.

  • Available Models
  • Stored Prompts
  • Prompt Files
  • Runbooks

Let's review each in a bit more detail.

Available Models View​

This view lists all the models that you have added to Promptscape. This is also the easiest place to choose which model to use when testing in the Studio. Simply click a model to select it. available-models

When you hover over a model, you will also see a Trash icon available, which you can select if you wish to delete the model and its settings.

Stored Prompts View​

This view lists all the prompts that you've saved in Workspace storage (see Persisting Prompts for more information). You can click on any prompt to open it immediately in the studio - whether or not the studio is already open.

Prompt Files Treeview​

This view contains an interactable treeview of all prompt files that the extension finds in your workspace. Click on any prompt file to open in in the studio to chat or test with it.

For an in-depth description of how to work with prompts from workspace files, see the Persisting Prompts page.

Runbooks Treeview​

Similar to the Prompt Files view, the runbooks view contains a treeview of all runbook files that the extension finds in your workspace. You can select any runbook to immediately load it into the studio for execution.

If you don't have any prompt files or runbooks in the workspace, these views will remain empty until you do. They behave similar to the test view in that way. For information on how to create and use runbooks, click the button below.