Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Allow user-defined key/value tags on runs for filtering by test intent

Aperta
  • Qualcosa non va?
#1,290 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
backend-api-design, frontend

Direzione di ricerca

No files, tests, or entry points are named. Start by tracing run/request creation and the Runs table, then identify the API and persistence paths involved; done means optional tags can be created, edited, returned, displayed, filtered, and preserved across retries or reruns.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Original author: @JaGord

Summary

Please add support for user-defined key/value tags on SCOPE runs and requests so users can filter and group runs by the reason they were created.

Why

When running benchmark matrices, the profile name and task prompt are not always enough to explain the intent of a run. Users need to mark runs with labels such as:

tag: purpose
value: test-agent-kit-branch

or:

tag: criteria_focus
value: vector-index-policy

This would make it easier to answer questions like:

  • Which runs were created to test a specific Agent Kit change?
  • Which runs were created to validate a specific criterion or failure mode?
  • Which runs are part of a rerun batch after a harness fix?
  • Which runs should be included or excluded from a comparison table?

Requested capability

Allow users to attach arbitrary key/value tags to a run or request at creation time and edit them later.

Example shape:

{
  "tags": {
    "purpose": "test-agent-kit-branch",
    "criteria_focus": "source_excludes_embedding_from_range_index",
    "batch": "rag-chat-rerun-20260626",
    "include_in_totals": "true"
  }
}

Expected behavior

  • Tags are visible in run/request details.
  • Tags can be added at request creation time.
  • Tags can be edited after creation.
  • Runs can be filtered by tag key and key/value pair.
  • Tags are returned by the API so automation can group and summarize runs reliably.
  • Reports should include tags or link back to tagged request metadata.

Use case

For Agent Kit benchmarking, I may run the same task prompt against several profiles, branches, reruns, or criteria-focused variants. A tag such as purpose=test-vector-index-guidance or batch=agent-kit-split-vs-monolith-rerun would make it much easier to filter the Runs table and avoid accidentally mixing unrelated runs in aggregate results.

Acceptance criteria

  • Request/run creation accepts optional key/value tags.
  • The Runs table supports filtering by tag key and tag value.
  • Request/run APIs return tags.
  • Tags are preserved across retries/reruns or clearly copied to replacement requests.
  • Tags are visible enough that users can tell "this run was to test X" without opening external notes.
Lingua principale
TypeScript
Stelle
7
Fork
13
Merge medio
3g 5h
PR unite (30g)
26

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/scope

Tutte le issue di microsoft/scope

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.