Skip to content

feat: agent work loop (issues, next, note) and a live dashboard - #5

Merged
Kadreev merged 2 commits into
mainfrom
feat/agent-work-loop
Oct 7, 2026
Merged

Kadreev merged 2 commits into
mainfrom
feat/agent-work-loop

Conversation

@Kadreev

@Kadreev Kadreev commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Summary

An agent fixing findings had no way to ask the tracker what to work on next, so it picked its own order — not the one the person watching the dashboard sees. This adds a small work loop and makes the dashboard follow writes made elsewhere.

  • qa-tracker issues — issues in the dashboard's order (open: severity, then complexity; unset last), with --status open|fixed|verified-fixed|wont-fix|closed|all, --severity, --feature, --category and --json.
  • qa-tracker next — the open issue to work on now (the top of that order), with its details and source, plus a hint for closing it.
  • qa-tracker note <issue> <text…> — appends a dated paragraph to the issue's details. The words need no quoting and --file <path> reads the text, so notes survive shells that mangle multi-line arguments (e.g. Windows .cmd shims).
  • Live dashboard — the page polls GET /api/version (size + mtime of the data files) every 3 s and reloads when the CLI or an agent wrote; while in Edit mode or with a field focused it only says the data changed. Its own saves re-sync the version, so they don't count as outside changes.
  • New exports: listIssues, nextIssue, formatIssueLine, appendNote, dataVersion. No schema change; existing trackers are untouched.
  • Docs: README (agents section, CLI table, dashboard "Live"), the init AGENTS.md template ("Fixing findings"), the skill, CHANGELOG.

Tests

npm run check: 191/191 pass (new test/work.test.mjs, two CLI tests for the loop and note --file, one server test for /api/version), demo tracker validates.

🤖 Generated with Claude Code

An agent fixing findings had no way to ask the tracker what to work on, so it
picked its own order, which is not the one the person watching the dashboard
sees.

- `qa-tracker issues` lists issues in the dashboard's order (open: severity,
  then complexity) with --status/--severity/--feature/--category filters.
- `qa-tracker next` returns the open issue to work on now: the top of that
  order, with its details and source.
- `qa-tracker note <issue> <text…>` appends a dated paragraph to the details;
  words need no quoting and --file reads the text, so notes survive shells
  that mangle multi-line arguments.
- The dashboard polls GET /api/version and reloads when the data files change,
  unless someone is editing, so a watcher sees CLI and agent writes land.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-07T06:49:49.973803Z 9f4f5fd PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9f4f5fd7b5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/server.mjs Resolved
Comment thread src/server.mjs Resolved
…e config

Review feedback on the live dashboard:

- An edit's follow-up GET /api/version could adopt a CLI or agent write that
  landed in between as the page's own, so the page never reloaded for it.
  POST /api/edit now answers with the data version just before and just after
  the commit; the page adopts the new one only when the "before" version is
  the one it had, and otherwise treats itself as stale.
- dataVersion no longer includes qa-tracker.config.json: serve reads the
  config once at start, so a config-triggered reload still showed the old
  title and categories. The README says to restart serve after a config edit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Kadreev
Kadreev merged commit 4c007cd into main Oct 7, 2026
6 checks passed
@Kadreev
Kadreev deleted the feat/agent-work-loop branch October 31, 2026 05:38
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