# Keep screenshots current with Promptless Capture

> For the complete documentation index, see [llms.txt](/llms.txt).

Use Promptless Capture to keep product screenshots in sync with your UI, regenerating them from your current interface when code changes

Promptless Capture keeps product screenshots in sync with your UI. When code changes affect a documented feature, Promptless Capture identifies which screenshots need updating and regenerates them from your current interface.

  Promptless Capture generates screenshots and keeps them current. Use the [Screenshot Updates](/docs/for-docs/work-the-queue/web-interface#screenshot-updates) tab to review screenshots already attached to your open suggestions.

## Set up credentials

Promptless Capture needs credentials to authenticate with your application. Store them as [environment variables](/docs/scale/environment-variables) under **Agent Env Vars** in **Settings**.

  1. **Open Settings.** Navigate to the [Settings page](https://app.gopromptless.ai/settings) in your Promptless dashboard and select **Agent Env Vars**.

  2. **Add Credential Variables.** Add variables for your application's login credentials. In the **Add Variable** form, type each variable's **Key Name** and **Value**. Then turn on the **Secret** toggle for any variable marked **Yes** in the table's Secret column below. For example:

     | Key Name            | Description                            | Secret |
     | ------------------- | -------------------------------------- | ------ |
     | `TEST_ACCOUNT_URL`  | The login URL for your application     | No     |
     | `TEST_ACCOUNT_USER` | Username or email for the test account | No     |
     | `TEST_ACCOUNT_PASS` | Password for the test account          | Yes    |

     You might use names like `STAGING_LOGIN_URL`, `QA_USER`, or any descriptive names that fit your organization's conventions.

  3. **Submit Each Variable.** Click **Add Variable** to submit the credential you just entered, then repeat the form for the next one. Promptless adds variables one at a time. Promptless hides values marked secret after you save them.

  Use a dedicated test account for screenshot capture rather than a personal or production account. This ensures screenshots don't contain sensitive data and provides a consistent UI state.

  Create a test account with access to all features you want to document. If certain features require specific permissions or plan tiers, ensure your test account has the appropriate access level.

## Test your setup

After adding your credentials, verify that Promptless can capture screenshots correctly.

  1. **Start a Manual Task.** Go to the [New Task page](https://app.gopromptless.ai/new-task) and request a documentation update that involves screenshots.

  2. **Review the Results.** Check the suggestion to see if screenshots were captured correctly. Look for:
     - Successful authentication (no login screens in screenshots)
     - Correct page navigation (screenshots show the intended feature)
     - Appropriate cropping (relevant UI elements are visible)

  3. **Iterate on Configuration.** If screenshots aren't captured correctly, adjust your environment variables or provide additional context in your Long-Term Context files.

## Troubleshooting

  Promptless can't log into my application

  Verify that your `TEST_ACCOUNT_URL`, `TEST_ACCOUNT_USER`, and `TEST_ACCOUNT_PASS` variables match what you use to manually log in. If your screenshots show the login page, the credentials may be incorrect or the login flow may require additional steps. For applications that use multi-factor authentication, consider creating a test account that bypasses MFA. You can also contact [help@gopromptless.ai](mailto\:help@gopromptless.ai) for guidance on handling MFA flows.

  Screenshots capture the wrong page

  Promptless may need additional navigation guidance. You can add instructions in your Long-Term Context to describe how to navigate to specific features. Include details about menu paths, URL patterns, or button sequences needed to reach documented screens.

  Screenshots show features that should be hidden

  Check your feature flag configuration. The test account may have access to features that typical users don't see. Consider creating a test account with permissions that match your target documentation audience.

  Cropping cuts off important elements

  The automatic cropping may need refinement. You can use the Screenshot Editor in the Promptless dashboard to manually adjust crops, or provide feedback that Promptless will learn from for future captures.

  Screenshots show loading states or spinners

  The page may not have fully loaded before capture. Contact [help@gopromptless.ai](mailto\:help@gopromptless.ai) if you consistently see loading states in your screenshots.

## Screenshot Editor

After Promptless captures screenshots, you can refine them in the built-in Screenshot Editor. Click any image in the Created Assets section to open the editor.

### Editing tools

The editor includes tools to refine your screenshots:

- **Crop** to focus on specific UI elements
- **Annotate** with arrows, boxes, and highlights
- **Add text** to call out features
- **Adjust** image dimensions

### Manage edits

The toolbar provides controls for your editing session:

- **Save edits** commits changes to the screenshot
- **Reset edits** discards unsaved changes and reverts to the last saved version, which is useful for starting over without closing the editor
- **Cancel Crop** exits crop mode without applying the crop, letting you adjust the selection or switch tools

Saved changes are immediately reflected in your documentation suggestions.

## When screenshots update automatically

Promptless Capture monitors your triggers and automatically updates screenshots when:

- A GitHub PR modifies UI components referenced in documentation
- A commit changes routes, layouts, or visual styling
- You explicitly request a screenshot update via Slack or the web interface
- Promptless edits a page and finds a screenshot on it that has fallen out of date with your current interface, whatever triggered that edit

  Screenshots are only regenerated when Promptless detects changes that likely affect documented UI. Minor code changes that don't impact the visual interface won't trigger unnecessary screenshot updates. Review the regenerated screenshots on the [Screenshot Updates](/docs/for-docs/work-the-queue/web-interface#screenshot-updates) tab.

Need help setting up Promptless Capture? Contact us at [help@gopromptless.ai](mailto\:help@gopromptless.ai).