How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

test_disable_input_debounce - Prompt

Name: test_disable_input_debounce
Author: alex-foster-personal

Prompt file imported from alex-foster-personal/t8e-gh-test (.claude/commands/e2e/test_disable_input_debounce.md). Copyright stays with the author.

E2E Test: Input Disabling and Debouncing

Test input disabling during query execution and debouncing functionality in the Natural Language SQL Interface application.

User Story

As a user
I want the input area to be disabled while a query is processing
So that I don't accidentally type or submit multiple queries at once

Test Steps

Navigate to the Application URL
Take a screenshot of the initial state
Verify the page title is "Natural Language SQL Interface"
Verify the query input textbox is enabled and can accept text
Verify the query button is enabled
Click "Upload Data" button to open the modal
Click on "Users Data" sample data button to load sample data
Wait for the data to be loaded
Verify the users table appears in the Available Tables section
Enter the query: "Show me all users"
Take a screenshot of the query input before execution
Click the Query button
Immediately after clicking (within 100ms):
- Verify the query input textbox is disabled
- Verify the query button is disabled and shows loading spinner
- Try to type additional text in the query input
- Verify no additional text can be entered
Take a screenshot showing the disabled state
Wait for the query to complete
Verify the query input textbox is re-enabled
Verify the query button is re-enabled and shows "Query" text
Verify the results are displayed
Take a screenshot of the re-enabled state with results
Test debouncing:
- Enter a new query: "Count all users"
- Rapidly click the Query button 5 times within 1 second
- Verify only one query is executed (results should update once, not multiple times)
- Verify no errors are shown
Test keyboard shortcut with disabled state:
- Enter another query: "Show user names"
- Press Cmd+Enter (Mac) or Ctrl+Enter (Windows/Linux)
- Verify the input becomes disabled during execution
- Verify the input is re-enabled after completion

Success Criteria

Query input is disabled during query execution
Query button is disabled during query execution
User cannot type in the textarea while a query is processing
Input and button are re-enabled after query completion
Debouncing prevents multiple rapid API requests
Visual feedback is provided for disabled state
4 screenshots are taken

Install test_disable_input_debounce and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# E2E Test: Input Disabling and Debouncing Test input disabling during query execution and debouncing functionality in the Natural Language SQL Interface application. ## User Story As a user I want the input area to be disabled while a query is processing So that I don't accidentally type or submit multiple queries at once ## Test Steps 1. Navigate to the `Application URL` 2. Take a screenshot of the initial state 3. **Verify** the page title is "Natural Language SQL Interface" 4. **Verify** the query input textbox is enabled and can accept text 5. **Verify** the query button is enabled 6. Click "Upload Data" button to open the modal 7. Click on "Users Data" sample data button to load sample data 8. Wait for the data to be loaded 9. **Verify** the users table appears in the Available Tables section 10. Enter the query: "Show me all users" 11. Take a screenshot of the query input before execution 12. Click the Query button 13. Immediately after clicking (within 100ms): - **Verify** the query input textbox is disabled - **Verify** the query button is disabled and shows loading spinner - Try to type additional text in the query input - **Verify** no additional text can be entered 14. Take a screenshot showing the disabled state 15. Wait for the query to complete 16. **Verify** the query input textbox is re-enabled 17. **Verify** the query button is re-enabled and shows "Query" text 18. **Verify** the results are displayed 19. Take a screenshot of the re-enabled state with results 20. Test debouncing: - Enter a new query: "Count all users" - Rapidly click the Query button 5 times within 1 second - **Verify** only one query is executed (results should update once, not multiple times) - **Verify** no errors are shown 21. Test keyboard shortcut with disabled state: - Enter another query: "Show user names" - Press Cmd+Enter (Mac) or Ctrl+Enter (Windows/Linux) - **Verify** the input becomes disabled during execution - **Verify** the input is re-enabled after completion ## Success Criteria - Query input is disabled during query execution - Query button is disabled during query execution - User cannot type in the textarea while a query is processing - Input and button are re-enabled after query completion - Debouncing prevents multiple rapid API requests - Visual feedback is provided for disabled state - 4 screenshots are taken

{ "prompt": "# E2E Test: Input Disabling and Debouncing\n\nTest input disabling during query execution and debouncing functionality in the Natural Language SQL Interface application.\n\n## User Story\n\nAs a user \nI want the input area to be disabled while a query is processing \nSo that I don't accidentally type or submit multiple queries at once\n\n## Test Steps\n\n1. Navigate to the `Application URL`\n2. Take a screenshot of the initial state\n3. **Verify** the page title is \"Natural Language SQL Interface\"\n4. **Verify** the query input textbox is enabled and can accept text\n5. **Verify** the query button is enabled\n\n6. Click \"Upload Data\" button to open the modal\n7. Click on \"Users Data\" sample data button to load sample data\n8. Wait for the data to be loaded\n9. **Verify** the users table appears in the Available Tables section\n\n10. Enter the query: \"Show me all users\"\n11. Take a screenshot of the query input before execution\n12. Click the Query button\n13. Immediately after clicking (within 100ms):\n - **Verify** the query input textbox is disabled\n - **Verify** the query button is disabled and shows loading spinner\n - Try to type additional text in the query input\n - **Verify** no additional text can be entered\n14. Take a screenshot showing the disabled state\n\n15. Wait for the query to complete\n16. **Verify** the query input textbox is re-enabled\n17. **Verify** the query button is re-enabled and shows \"Query\" text\n18. **Verify** the results are displayed\n19. Take a screenshot of the re-enabled state with results\n\n20. Test debouncing:\n - Enter a new query: \"Count all users\"\n - Rapidly click the Query button 5 times within 1 second\n - **Verify** only one query is executed (results should update once, not multiple times)\n - **Verify** no errors are shown\n\n21. Test keyboard shortcut with disabled state:\n - Enter another query: \"Show user names\"\n - Press Cmd+Enter (Mac) or Ctrl+Enter (Windows/Linux)\n - **Verify** the input becomes disabled during execution\n - **Verify** the input is re-enabled after completion\n\n## Success Criteria\n\n- Query input is disabled during query execution\n- Query button is disabled during query execution\n- User cannot type in the textarea while a query is processing\n- Input and button are re-enabled after query completion\n- Debouncing prevents multiple rapid API requests\n- Visual feedback is provided for disabled state\n- 4 screenshots are taken", "variables": [], "notes": "Test input disabling during query execution and debouncing functionality in the Natural Language SQL Interface application.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/alex-foster-personal/t8e-gh-test", "path": ".claude/commands/e2e/test_disable_input_debounce.md", "ref": "6f5b4579c8d2c2076496fc8d0691b49febb4375e", "url": "https://github.com/alex-foster-personal/t8e-gh-test/blob/6f5b4579c8d2c2076496fc8d0691b49febb4375e/.claude/commands/e2e/test_disable_input_debounce.md", "key": "alex-foster-personal/t8e-gh-test/.claude/commands/e2e/test_disable_input_debounce.md" } } }

test_disable_input_debounce

About

E2E Test: Input Disabling and Debouncing

User Story

Test Steps

Success Criteria

Install test_disable_input_debounce and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews