| name | test-warp-ui |
| description | Guides testing Warp UI features and changes using the computer use tool. Use this skill only when the computer_use tool is available to the agent. Covers launching Warp and verifying UI behavior.
|
| user-invocable | false |
Computer Use for Warp UI Testing
Use the computer_use tool to visually test that Warp looks and behaves as intended after UI changes.
Running Warp
Launch Warp from the repository root. The exact command depends on which environment variable holds the API key:
-
If WARP_API_KEY is already set, omit the flag entirely — the --api-key flag is bound to WARP_API_KEY, so Warp reads it automatically:
cargo run --bin warp
-
If the key is in STAGING_USER_WARP_API_KEY instead, pass it explicitly via the flag:
cargo run --bin warp -- --api-key $STAGING_USER_WARP_API_KEY
Always pass --bin warp explicitly. That target builds the internal (dogfood) channel, which is the only channel that honors --api-key for the GUI app. A plain cargo run builds the OSS channel, which ignores the key and falls back to interactive onboarding.
Authenticating this way starts the app directly without interactive login prompts.
Initial builds may take several minutes; subsequent incremental builds are faster.
Verify the launch is authenticated
After launching, confirm both of the following before testing:
