[sentry-junior]

DESCRIBE YOUR PR

Documents the gen_ai.extract span in the agent tracing manual instrumentation guides, modeled on the existing Decision and Memory span sections. Follows sentry-conventions#728, which adds the experimental gen_ai.extract op, the extract operation name, and the extraction shapes for gen_ai.input.messages / gen_ai.output.messages.

• Add an "Extraction Span" section to the JavaScript and Python manual instrumentation pages, placed after "Decision Span". The example uses a Clairic invoice extraction (same data as the conventions examples): gen_ai.extract op, extract {model} name, gen_ai.operation.name: "extract", the request body without model as input messages, and the response body without model and usage as output messages
• Add a shared extraction-span attributes include: required op/name/operation name, model, provider, and agent attributes, token usage, and the input format (state, fields, images, reference_date, options, plus field spec types) and output format (answers, truncated, span/spans offsets)
• JS page links to the Workers AI integration, which creates these spans automatically for Clairic since @sentry/cloudflare 11.10.0

Attribute values were checked against sentry-conventions (model/op/gen_ai.json, gen_ai.operation.name, gen_ai.input.messages, gen_ai.output.messages), the JS Workers AI instrumentation (cloudflare.workers_ai provider name), and the product's extraction parser (spans are recognized by gen_ai.operation.name).

Open questions before ready for review

• The field-level message format overlaps with the develop-docs spec in docs(develop): Document decision and extraction message structure #20107 (still open). Once that merges, should the include link there instead of repeating the field tables?
• The existing Decision span docs still show {type: "evaluation", ...} wrappers, which the current conventions examples and docs(develop): Document decision and extraction message structure #20107 drop. Out of scope here, but worth a follow-up.

Refs AGT-3212

IS YOUR CHANGE URGENT?

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

PRE-MERGE CHECKLIST

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

via @ArthurKnaus.

--

View Session [Sentry]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Nov 3, 2026 5:06pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Nov 3, 2026 5:06pm UTC

[linear-code]

AGT-3212

[cursor]

Getting ready to monitor this change · Rollout details

Status	Service	Environment
⏳ Getting ready to monitor this change