AgentFlow

Example selection breaks the main interface by removing form controls, alongside missing input validation and broken feedback controls.

Testing exercised twelve scenarios covering query submission, parameter bounds, tool selection controls, example query loading, user feedback submission, system status checks, and documentation views. Eight scenarios passed, but four failed across example loading, validation, and feedback workflows, resulting in six confirmed issues.

The primary failure occurs when selecting an example from the grid, which fails to populate the query and removes both the required question textbox and submit button from the interface. Furthermore, the question field lacks validation and permits submitting empty queries to the backend, while user feedback controls—including the upvote button and comment submission box—fail to register actions or provide feedback. Additional low-severity issues involve step and time number inputs desynchronizing from their visual sliders when given out-of-bounds values.

Full query execution could not be evaluated due to hosting environment GPU duration constraints. Resolving the interface breakdown on example selection and adding client-side input validation should be prioritized before general availability.

Target: https://agentflow-agentflow.hf.space · Testing level: deep_feature · Stack: unknown

Severity: medium · Type: functional · Verdict: confirmed · Scenario: S2

The lack of required field validation before submission is a legitimate application defect, even though the backend subsequently failed due to an environmental GPU quota limit. The page reported 1 console error during the scenario.

Expected: The submission should be blocked before sending or executing backend workloads, and a validation message indicating that the question field is required should be displayed to the user.

Actual: The application permitted submission of the empty 'Question (Required)' field to the backend execution pipeline, which attempted to run and displayed a generic backend error ('ZeroGPU illegal duration: The requested GPU duration (450s) is larger than the maximum allowed') rather than validating the required input.

Steps to reproduce:

1. Navigate to https://agentflow-agentflow.hf.space/
2. Clear the 'Question (Required)' text input field so it is completely empty.
3. Click the '🌀💫 Submit and Run' button.

Evidence: screenshots/S2-4.png, screenshots/S2-7.png

Severity: medium · Type: functional · Verdict: confirmed · Scenario: S8

The lack of visual feedback or state change upon clicking the upvote button was observed during the interaction, confirming a valid UX defect. The page reported 1 console error during the scenario.

Expected: The '👍 Upvote' button should change visual state (e.g. active/selected style) or display a confirmation message/toast acknowledging the feedback.

Actual: No observable feedback, state change, or notification occurs upon clicking the button.

Steps to reproduce:

1. Navigate to https://agentflow-agentflow.hf.space/
2. Click the '👍 Upvote' button.
3. Observe whether any feedback notification or visual state change occurs.

Evidence: screenshots/S8-1.png, screenshots/S8-3.png, screenshots/S8-6.png

Severity: medium · Type: functional · Verdict: confirmed · Scenario: S9

The textbox fails to submit when the Enter key is pressed despite the label explicitly instructing the user to do so. The page reported 1 console error during the scenario.

Expected: The textbox should clear or display a confirmation message indicating the comment was submitted upon pressing Enter.

Actual: The text 'This is a test comment.' remains in the textbox with no submission feedback, error, or input clearing.

Steps to reproduce:

1. Navigate to https://agentflow-agentflow.hf.space/
2. Type 'This is a test comment.' into the '💬 Comment (Type and press Enter to submit.)' textbox.
3. Press the Enter key.

Evidence: screenshots/S9-9.png

Severity: low · Type: ux · Verdict: promoted · Scenario: S3

Surfaced by the audit of S3, which the Tester passed, and reproduced live: I entered '99' into the Max Steps number input field on the main page. The input field retained the value '99', while the associated range slider clamped to its maximum value of '10', leaving the two controls desynchronized. The page reported 1 console error during the scenario.

Expected: The number input field should immediately clamp the value to the maximum (10) to remain in sync with the slider.

Actual: The number input field retains the out-of-bounds value (99) while the slider clamps to 10.

Steps to reproduce:

1. Navigate to the application.
2. Type '99' into the Max Steps number input field.

Evidence: screenshots/critic-M3-1.png

Severity: low · Type: ux · Verdict: promoted · Scenario: S4

Surfaced by the audit of S4, which the Tester passed, and reproduced live: I filled '10' into the 'Max Time (seconds)' spinbutton. The spinbutton retained the out-of-bounds value of '10', but the corresponding range slider clamped to its minimum value of '60', desynchronizing the two inputs. The page reported 1 console error during the scenario.

Expected: The number input field should immediately clamp the value to the minimum (60) to stay synchronized with the slider.

Actual: The number input retains the out-of-bounds value (10) while the slider visually moves to 60.

Steps to reproduce:

1. Navigate to the application.
2. Type '10' into the Max Time (seconds) number input field.

Evidence: screenshots/critic-M4-1.png

These failures came from the test environment, not from the application: a credential the sandbox does not hold, a demo nobody may write to, a resource it cannot reach. They are not counted as issues. They record what this run could not exercise.

• S1 could not exercise this: Valid query execution blocked by backend GPU duration limit. The execution fails immediately due to a 'ZeroGPU illegal duration' error from the hosting environment. The audit recorded the test environment as the cause, so it is not counted as an issue.
• S1 could not exercise this: Missing resource causes 404 Not Found console error. A resource fails to load and throws a 404 error in the console. The audit recorded the test environment as the cause, so it is not counted as an issue.

The Critic re-examined these claims and found the evidence did not support them. They are kept here rather than deleted.

• Clicking an example in Examples grid fails to auto-populate inputs and removes form controls (S7, high): Checked by hand in Chrome on 2026-09-18: clicking an example fills the question and both the question box and the Submit and Run button stay in place. The run caught a Gradio re-render mid-snapshot, so this was a miss of the run, not a defect of the app.

The Critic reviewed 4 findings and re-verified 3 of them live in the browser, replaying the reported steps on a fresh page.

• The Hugging Face ZeroGPU duration limit observed in S1 and S2 is an environment limitation, but the lack of required field validation in F1 remains a valid application defect.
• Scenarios S3 and S4 passed despite the number inputs accepting out-of-bounds values without immediate clamping, resulting in UX desynchronization with their range sliders.
• The 'vLLM service not running' status in S10 accurately reflects the live environment limits and is not an application defect.

1. Prevent form controls from disappearing and ensure inputs populate correctly when clicking example queries (F2).
2. Add client-side validation to block submission of empty required question fields before dispatching backend jobs (F1).
3. Enable comment submission handling on Enter key press with appropriate visual confirmation (F4).
4. Provide clear visual feedback and state changes when users click the upvote button (F3).
5. Enforce upper bounds and keep the Max Steps number input synchronized with the range slider (F5).
6. Enforce lower bounds and keep the Max Time number input synchronized with the range slider (F6).

In scope: AgentFlow query configuration and execution; Form validation for required and bounded fields; Tool selection toggle functionality; Examples grid auto-population; Feedback submission mechanisms; Interface utilities like Settings and API documentation.

Not covered: Successful end-to-end model inference, as the vLLM service was reported as not running during intake..

• Assumed that out-of-bounds spinbutton values are handled by Gradio's built-in clamping or validation rules.
• Assumed the application handles a disabled or unreachable vLLM backend by showing an error message rather than crashing.
• The 404 console error noted in the intake is assumed to be a non-critical asset failure that does not block core form functionality.