---
title: "uv reproduce-bug: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/astral-uv-reproduce-bug/
description: "Decides whether a reported uv behavior can be reproduced, and refuses to treat source inspection as a reproduction."
---

# uv reproduce-bug: review, role & definition · Undominated.ai

> Decides whether a reported uv behavior can be reproduced, and refuses to treat source inspection as a reproduction.

[← Explore all agents](/agents/)

BUG REPRODUCTION / Astral Software Inc.

# uv reproduce-bug

Decides whether a reported uv behavior can be reproduced, and refuses to treat source inspection as a reproduction.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/reproduce-bug.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 5 linked sources
 Publisher Astral Software Inc.
 Licence [MIT ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT)
 Revision c0110fc79aea
 [Read what was—and wasn’t—checked ↓](#review)

“Determine whether the behavior described in `.issue-triage-event.json` can be reproduced.”

 [Astral Software Inc. · upstream description ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/reproduce-bug.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The outcome is one of reproducible, not_reproducible, or needs_more_information. A reproduced behavior is not treated as proof the behavior is wrong.
- not_reproducible requires a targeted attempt. If a test already covers the behavior, the reason has to name the repository-relative path and the test name after the assertions were read. A simplified fixture that passes is not enough.

### A good fit for

 - Provide .issue-triage-event.json, installed uv, the repository tests and an existing temporary issue-context README for one targeted reproduction.
- Obtain only the schema’s reproduction and reason keys, plus a consistent maintainer README containing one Reproduction section.
- Supply the issue event plus exact versions, platform, command and configuration relevant to the failure.
- Record needs_more_information when a simplified fixture cannot establish the reported configuration-dependent behavior.

### Weigh up before choosing

 - The prompt is tied to astral-sh/uv issue context and test paths. Its workflow prepares temporary state from uv-dev; copying the prompt does not create that state.
- The reproduction profile allows temporary writes and selected GitHub/PyPI domains. Reproduction can download or execute package code; it is not merely static reading.
- The launch job is read-oriented, but separate report and regression-test jobs can persist context or publish code. Those actions are not part of the prompt’s no-GitHub-write boundary.
- Schema validation establishes the JSON shape, not whether an attempted reproduction supports the conclusion.
- The profile updates the issue-context README outside the checkout; it is not globally read-only even though checkout and GitHub mutations are forbidden.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - agents/prompts/reproduce-bug.md
- agents/codex/config.toml
- LICENSE-MIT
- agents/schemas/issue-triage-bug.json
- .github/workflows/reproduce-bug.yml (launch configuration, selected context preparation and downstream job permissions)
- Round 2: pinned definition, output contract and permission/dependency boundaries reread on 2026-10-14

### Our findings

 - LICENSE-MIT is the MIT License. The copyright line is Copyright (c) 2025 Astral Software Inc. The prompts have no per-file copyright header.
- The prompt says not to execute scripts copied from the issue and to use the uv binary already on PATH.
- The output schema permits exactly reproduction and reason, with no extra properties and three named reproduction outcomes.
- The launch step explicitly supplies the reproduce-bug permission profile, the schema, a temporary uv cache and the prompt file; the reviewed workflow limits its uv runner setup to Linux x64 and macOS ARM64.
- The report job obtains contents:write separately from the reproduction job, confirming that downstream persistence must be reviewed as its own action.
- A successful simplified fixture is explicitly insufficient to label the reported case not_reproducible.
- The prompt separates observing a behavior from deciding it is incorrect, and requires release/history inspection when the report alleges a regression.

### Not established by this review

 - The agent was not executed; model behaviour, host compatibility and task outcomes were not runtime-tested.
- No uv command, Codex invocation or GitHub workflow was run.
- Later reporting/retry job permissions were inspected; their full implementation and credential broker were not security-audited.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/reproduce-bug.md)
 - Read the prompt at the reviewed commit. No install command is published.
- Do not treat the prompt as permission to post, commit, or push. The prompt text and the permission profile are separate from later workflow jobs.

### Before you start

 - A checkout of astral-sh/uv at a revision the prompt can read

### Compatibility

A Codex prompt file a workflow can pass to a reviewer

### Implementation

Markdown

### Prompt text. The named profile allows temp writes and four network domains. It does not grant a checkout write.

 - Read the checkout
- Write the temp issue-context README
- Network to the four domains named in the reproduce-bug profile

### Cost model

MIT prompt text at no charge. Copyright (c) 2025 Astral Software Inc. The Apache licence file at this commit was not the grant used.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [uv reproduce-bug ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/reproduce-bug.md) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/prompts/reproduce-bug.md Supports: summary, whySelected, limitations
- [Codex permission profiles ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/codex/config.toml) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/codex/config.toml Supports: permission profile
- [MIT licence ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/LICENSE-MIT Supports: Redistribution terms, Copyright (c) 2025 Astral Software Inc.
- [Structured output schema ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/schemas/issue-triage-bug.json) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/agents/schemas/issue-triage-bug.json Supports: Required output keys, Allowed decisions and extra-property rejection
- [Workflow launch and downstream-job permissions ↗](https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/.github/workflows/reproduce-bug.yml) Checked 2026-10-14 https://github.com/astral-sh/uv/blob/c0110fc79aea1e6e8a09feb4a72b0732fc101170/.github/workflows/reproduce-bug.yml Supports: Prompt/schema/profile wiring, Separate downstream mutation privileges

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### uv workflow-failure ↗ Classifies one failed uv workflow as flaky or deterministic, and as create, duplicate, or ignore.](/agents/astral-uv-workflow-failure/)[### Systematic Debugging ↗ Reproduces an application bug, tests root-cause hypotheses and verifies a minimal fix against the original failure.](/agents/github-debug-mode/)[### uv changelog editorial ↗ Rewrites only the newest uv changelog section, and keeps the version, date, pull-request numbers, and URLs as they are.](/agents/astral-uv-changelog-editorial/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
