Skip to content

Support Task-scoped QA commands - #532

Open
ChinmayK0607 wants to merge 2 commits into
chinmay/resource-qa-cli-v1from
chinmay/task-qa-cli
Open

Support Task-scoped QA commands#532
ChinmayK0607 wants to merge 2 commits into
chinmay/resource-qa-cli-v1from
chinmay/task-qa-cli

Conversation

@ChinmayK0607

Copy link
Copy Markdown
Contributor

Why

Task QA needs a scripting and CI surface in addition to the Platform UI. Users should be able to discover agents, run exact Task analyses, and consume stable outcomes without writing custom API calls.

What changed

  • allow hud qa agents, run, and results to target Task subjects
  • validate the selected agent contract before launching a run
  • preserve exact selected attempts when polling and rendering results
  • return quality and execution exit codes for terminal --no-wait results
  • add regression coverage for Task scope, reuse, polling, malformed responses, and exit behavior

Result contract

  • 0: passed
  • 1: failed or unknown quality result
  • 2: invalid request
  • 3: execution, polling, or response-contract failure

Dependency

Stacked on #529, which adds the shared resource QA CLI.

Test plan

  • uv run --extra dev pytest hud/cli/tests/test_qa.py -q (20 passed)
  • Ruff
  • Pyright

Made with Cursor

ChinmayK0607 and others added 2 commits August 3, 2026 20:24
Treat Task agents as native resource agents across discovery, execution, polling, results, validation, and exit-code behavior.

Co-authored-by: Cursor <cursoragent@cursor.com>
Preserve terminal quality and execution exit codes when reused results return immediately.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant