Inputs

☐ Prompt / Description (Required)

A clear and concise instruction describing what this step should do. This helps the AI debug and re-trigger the key press if needed.

Good Example: "Press the 'Enter' key to submit the login form."

Bad Example: "Press whatever key makes sense to continue."

Why it’s bad? Too vague, lacks specificity about the key and its intended action.

☐ Target Element (Optional)

Define the element that should receive the key press using one of the following methods:

CSS Selector

Use standard CSS selectors to identify the element.

XPath

Use an XPath expression to precisely locate the element.

☐ Key Action (Required)

Press

Simulate a single key press

Hold

Hold a key down for a duration

Release

Release a previously held key

☐ Key Selection (Required)

Choose the key to simulate:

  • Special keys: Enter, Esc, Tab, ArrowUp, etc.
  • Character keys: a, b, 1, 2, etc.
  • Modifier keys: Shift, Ctrl, Alt, etc.

☐ Press Duration (Optional)

Specify how long to hold the key (in milliseconds)

  • Default: 0 (instant press)
  • Longer durations simulate held keys

Usage Example

Scenario: Submitting a form with Enter

✅ Good Prompt:

“Press the ‘Enter’ key to submit the login form.”

✅ Good Element Selector:

CSS Selector: input#password

XPath: //input[@id='password']

✅ Key Configuration:

  • Action: Press
  • Key: Enter
  • Duration: 0 milliseconds

Notes

  • The Prompt / Description is required to help AI debug and adjust the key press if needed.
  • If no target element is specified, the key press will be sent to the active element.
  • Some keyboard shortcuts may require multiple keys or specific timing—adjust the configuration accordingly.