Forms without the guesswork.

01 / Read the field in context

Start with gripui hud. For a form, inspect the fields and their current values:

gripui form

Two buttons may have the same name. Use the owning row, card or field context to choose the right one. If a popup is active, inspect it with gripui hud --layer active before selecting an option.

02 / Type, then read back

Use a current ref from your page. This example assumes your target field has ref 12; substitute the actual number.

gripui type 12 "Example project"

Typing clears the field first unless you explicitly use --no-clear. Grip checks the entered value and reports when formatting, replacement or rejection changes it.

For long text, focus the field first and use gripui say. That command pastes into the focused field; it does not accept a ref.

03 / Investigate a rejected value

If input will not stick, inspect the control rather than repeatedly typing. Again, replace 12 with your observed field ref:

gripui doctor 12

The diagnostic shows constraints, validity messages, whitespace and evidence of uncommitted edits. Resolve what the page reports, then refresh the HUD.

04 / Check the actual outcome

Entering text does not mean the application saved it. Review the form, take the authorized save action, then inspect its confirmation and the resulting record.

Do not reload a form with unsaved edits to test whether it saved: that can discard the very state you are checking. Look for a committed result first.