debug-agent

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Diagnose the failure and report evidence. Do not edit the agent unless the user also asks for a fix; for behavior changes, hand off to

fix-agent-issue

after the diagnosis.

诊断故障并报告证据。除非用户同时要求修复，否则不要编辑 Agent；对于行为变更，在诊断后移交给

fix-agent-issue

。

Find existing tracing configuration, tracking URI, and experiment. Do not recommend reinstalling or reinstrumenting MLflow when tracing already works.
Find a trace matching the reported input, time, session, user, or trace ID. If one exists, use it directly. Do not reproduce a production-only or externally dependent failure merely to satisfy a workflow.
Only when no usable trace exists, reproduce the issue once through the normal instrumented entry point and retrieve the resulting trace. If reproduction is unsafe or impossible, state what evidence is missing and stop.
Inspect the matching trace span by span. Read assessments first, then inputs, outputs, errors, LLM calls, retrieval results, and tool calls. Use
```
analyze-mlflow-trace
```
for detailed trace anatomy.
Correlate trace evidence with source code as needed. Reading source is fine; do not settle on a diagnosis without confirming it against the trace.
Report: observed behavior, expected behavior, trace evidence, root cause, confidence, and the smallest likely fix. Do not create tests or scorers for a diagnosis-only request.

查找现有的 tracing 配置、tracking URI 和 experiment。当 tracing 已正常工作时，不要建议重新安装或重新为 MLflow 埋点。
查找与报告的输入、时间、session、user 或 trace ID 相匹配的 trace。如果存在，则直接使用。不要仅仅为了完成工作流程，就复现仅在生产环境出现或依赖外部服务的故障。
仅当没有可用的 trace 时，才通过正常的已埋点入口复现一次问题，并获取生成的 trace。如果复现不安全或无法进行，请说明缺少哪些证据并停止。
逐个检查匹配的 trace span。先阅读 assessments，然后查看 inputs、outputs、errors、LLM calls、retrieval results 和 tool calls。使用
```
analyze-mlflow-trace
```
了解详细的 trace 结构。
根据需要将 trace 证据与源代码关联起来。可以阅读源代码，但在未通过 trace 确认之前，不要确定诊断结论。
报告以下内容：观察到的行为、预期行为、trace 证据、根因、置信度以及可能的最小修复方案。对于仅要求诊断的请求，不要创建 tests 或 scorers。

If no trace can be produced because the app is uninstrumented, load
```
instrumenting-with-mlflow-tracing
```
and explain the limitation.
Log the user's complaint as HUMAN feedback only when a concrete trace is identified and doing so is authorized.
If the user asks to implement the fix, invoke
```
fix-agent-issue
```
with the trace ID and diagnosis so it can write regression coverage before editing.

如果由于应用未进行埋点而无法生成 trace，请加载
```
instrumenting-with-mlflow-tracing
```
并说明该限制。
仅当已识别出具体 trace 且获得授权时，才将用户的投诉记录为 HUMAN feedback。
如果用户要求实施修复，请将 trace ID 和诊断结果传递给
```
fix-agent-issue
```
，由其在编辑前编写 regression coverage。