Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[bot] OpenAI Decisions API (`client.decisions.create()`) not instrumented

Ouverte
  • Quelque chose ne va pas ?
#2,618 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
nodejs, typescript
Domaine
ai, backend

Piste de recherche

Start with js/src/auto-instrumentations/configs/openai.ts, which shows how the existing Responses and Embeddings resources are instrumented, then check js/src/wrappers/oai.ts for the manual proxy. Add a Decisions entry and a plugin channel under js/src/instrumentation/plugins/, and raise the openai devDependency in js/package.json to at least 7.30.0. Done means client.decisions.create() emits a span in a recorded test.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Summary

OpenAI's Node SDK added a standalone Decisions API (client.decisions.create(), endpoint POST /v1/decisions) in [email protected] (changelog: "add standalone Decisions support"). It runs the dedicated gpt-6-luna model (added in [email protected], "add GPT-6 Sol and Luna model identifiers") to turn text/image input into typed, structured answers — a generative model-execution call distinct from Chat Completions/Responses, not a CRUD or admin endpoint. Development is active and ongoing: the latest openai release (7.33.0, 2026-10-14) adds "organization Decisions usage reporting" and documentation clarifications for decision creation. This repo has zero instrumentation for this surface — no config entry, no channel, no wrapper — so calls to client.decisions.create() produce no Braintrust spans at all.

What instrumentation is missing

  • client.decisions.create({ model: "gpt-6-luna", input, decision }) — POST /v1/decisions. Accepts text/image input plus a typed decision schema (choices/score/boolean-style questions) and returns a structured, typed answer instead of free-form prose.

No coverage in any instrumentation layer:

  • js/src/auto-instrumentations/configs/openai.ts — instruments Images.*, Audio.* (speech/transcriptions/translations), Chat.Completions.create/parse/stream, Embeddings.create, Moderations.create, and Responses.create/stream/parse/compact. No entry for a Decisions resource.
  • js/src/instrumentation/plugins/ — no openai-decisions-style channel or plugin file.
  • js/src/wrappers/oai.ts — manual wrapper proxies the resources above only; no decisions property handling.

A case-insensitive repo-wide search for decisions under js/src/ returns no genuine matches (the only two hits are an unrelated test description string and an unrelated code comment, neither referencing this API).

Braintrust docs status

not_found — https://www.braintrust.dev/docs/integrations/ai-providers/openai lists the OpenAI methods Braintrust auto-traces for TypeScript (chat completions, embeddings, moderation, Responses API, batch API, Agents API, images, audio) and does not mention a Decisions API, decisions.create, or gpt-6-luna anywhere.

Upstream references

Local files inspected

  • js/src/auto-instrumentations/configs/openai.ts — full file read; no Decisions entry
  • js/src/wrappers/oai.ts — no decisions proxy handling
  • Repo-wide case-insensitive grep for decisions under js/src/ — no relevant matches
  • js/package.json — openai devDependency pinned at 6.25.0 (below the >=7.30.0 floor needed for this surface), confirming it is a genuinely new capability relative to this repo's current test/record setup rather than something already exercised
Langage dominant
TypeScript
Étoiles
29
Forks
16
Merge moyen
1 j 22 h
PR mergées (30 j)
72

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de braintrustdata/braintrust-sdk-javascript

Toutes les issues de braintrustdata/braintrust-sdk-javascript

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.