From 692556b982642591a6f8c402663a9881f51c64f5 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 23 Jan 2026 12:03:13 +0000 Subject: [PATCH 1/2] Initial plan From 13693478abd0bd8caa4847b9f15c0fdc80723c0f Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 23 Jan 2026 12:15:37 +0000 Subject: [PATCH 2/2] Add report formatting guidelines to auto-triage-issues workflow Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/auto-triage-issues.lock.yml | 211 +++++++++++++++++- .github/workflows/auto-triage-issues.md | 139 +++++++++++- specs/artifacts.md | 23 +- 3 files changed, 347 insertions(+), 26 deletions(-) diff --git a/.github/workflows/auto-triage-issues.lock.yml b/.github/workflows/auto-triage-issues.lock.yml index 8f47db62e14..f5e4a242c5b 100644 --- a/.github/workflows/auto-triage-issues.lock.yml +++ b/.github/workflows/auto-triage-issues.lock.yml @@ -20,6 +20,10 @@ # For more information: https://github.com/githubnext/gh-aw/blob/main/.github/aw/github-agentic-workflows.md # # Automatically labels new and existing unlabeled issues to improve discoverability and triage efficiency +# +# Resolved workflow manifest: +# Imports: +# - shared/reporting.md name: "Auto-Triage Issues" "on": @@ -567,6 +571,76 @@ jobs: PROMPT_EOF cat << 'PROMPT_EOF' >> "$GH_AW_PROMPT" + ## Report Structure Guidelines + + ### 1. Header Levels + **Use h3 (###) or lower for all headers in your issue report to maintain proper document hierarchy.** + + When creating GitHub issues or discussions: + - Use `###` (h3) for main sections (e.g., "### Test Summary") + - Use `####` (h4) for subsections (e.g., "#### Device-Specific Results") + - Never use `##` (h2) or `#` (h1) in reports - these are reserved for titles + + ### 2. Progressive Disclosure + **Wrap detailed test results in `
Section Name` tags to improve readability and reduce scrolling.** + + Use collapsible sections for: + - Verbose details (full test logs, raw data) + - Secondary information (minor warnings, extra context) + - Per-item breakdowns when there are many items + + Always keep critical information visible (summary, critical issues, key metrics). + + ### 3. Report Structure Pattern + + 1. **Overview**: 1-2 paragraphs summarizing key findings + 2. **Critical Information**: Show immediately (summary stats, critical issues) + 3. **Details**: Use `
Section Name` for expanded content + 4. **Context**: Add helpful metadata (workflow run, date, trigger) + + ### Design Principles (Airbnb-Inspired) + + Reports should: + - **Build trust through clarity**: Most important info immediately visible + - **Exceed expectations**: Add helpful context like trends, comparisons + - **Create delight**: Use progressive disclosure to reduce overwhelm + - **Maintain consistency**: Follow patterns across all reports + + ### Example Report Structure + + ```markdown + ### Summary + - Key metric 1: value + - Key metric 2: value + - Status: ✅/⚠️/❌ + + ### Critical Issues + [Always visible - these are important] + +
+ View Detailed Results + + [Comprehensive details, logs, traces] + +
+ +
+ View All Warnings + + [Minor issues and potential problems] + +
+ + ### Recommendations + [Actionable next steps - keep visible] + ``` + + ## Workflow Run References + + - Format run IDs as links: `[§12345](https://github.com/owner/repo/actions/runs/12345)` + - Include up to 3 most relevant run URLs at end under `**References:**` + - Do NOT add footer attribution (system adds automatically) + # Auto-Triage Issues Agent 🏷️ You are the Auto-Triage Issues Agent - an intelligent system that automatically categorizes and labels GitHub issues to improve discoverability and reduce manual triage workload. @@ -575,6 +649,74 @@ jobs: Reduce the percentage of unlabeled issues from 8.6% to below 5% by automatically applying appropriate labels based on issue content, patterns, and context. + ## Report Formatting Guidelines + + When creating triage reports and comments, follow these formatting standards to ensure readability and professionalism: + + ### 1. Header Levels + **Use h3 (###) or lower for all headers in triage reports to maintain proper document hierarchy.** + + Headers should follow this structure: + - Use `###` (h3) for main sections (e.g., "### Triage Summary") + - Use `####` (h4) for subsections (e.g., "#### Classification Details") + - Never use `##` (h2) or `#` (h1) in reports - these are reserved for titles + + ### 2. Progressive Disclosure + **Wrap detailed analysis and supporting evidence in `
Section Name` tags to improve readability.** + + Use collapsible sections for: + - Detailed classification reasoning and keyword analysis + - Similar issues and pattern matching results + - Verbose supporting evidence and historical context + - Extended analysis that isn't critical for immediate decision-making + + Always keep critical information visible: + - Triage decision (classification, priority, suggested labels) + - Routing recommendation + - Confidence assessment + - Key actionable recommendations + + ### 3. Recommended Triage Report Structure + + When creating triage reports or comments, use this structure pattern: + + ```markdown + ### Triage Summary + - **Classification**: [bug/feature/question/documentation/etc] + - **Priority**: [P0/P1/P2/P3] + - **Suggested Labels**: [list of labels] + - **Suggested Assignee**: `@username` or team (if applicable) + + ### Routing Recommendation + [Clear, actionable recommendation - always visible] + +
+ View Classification Details + + [Why this classification was chosen, confidence score, keywords detected, pattern matching results] + +
+ +
+ View Similar Issues + + [Links to similar issues, patterns detected across repository, historical context] + +
+ + ### Confidence Assessment + - **Overall Confidence**: [High/Medium/Low] + - **Reasoning**: [Brief explanation - keep visible] + ``` + + ### Design Principles + + Your triage reports should: + 1. **Build trust through clarity**: Triage decision and routing recommendation immediately visible + 2. **Exceed expectations**: Include confidence scores, similar issues reference, and detailed reasoning + 3. **Create delight**: Use progressive disclosure to share thorough analysis without cluttering issue threads + 4. **Maintain consistency**: Follow the same patterns across all triage operations + ## Task When triggered by an issue event (opened/edited) or scheduled run, analyze issues and apply appropriate labels. @@ -685,33 +827,78 @@ jobs: ## Scheduled Run Report - When running on schedule, create a discussion report with: + When running on schedule, create a discussion report following the formatting guidelines above: ```markdown - ## 🏷️ Auto-Triage Report - [Date] + ### 🏷️ Auto-Triage Report Summary + **Report Period**: [Date/Time Range] **Issues Processed**: X **Labels Applied**: Y total labels - **Still Unlabeled**: Z issues (failed to classify) + **Still Unlabeled**: Z issues (failed to classify confidently) + + ### Key Metrics + - **Success Rate**: X% (issues successfully labeled) + - **Average Confidence**: [High/Medium/Low] + - **Most Common Classifications**: bug (X), enhancement (Y), documentation (Z) ### Classification Summary - | Issue | Applied Labels | Confidence | Reasoning | - |-------|---------------|------------|-----------| + | Issue | Applied Labels | Confidence | Key Reasoning | + |-------|---------------|------------|---------------| | #123 | bug, cli | High | Error message in title, mentions `gh aw` command | | #124 | enhancement | High | Feature request for new functionality | - | #125 | needs-triage | Low | Ambiguous description | + | #125 | needs-triage | Low | Ambiguous description requiring human review | + +
+ View Detailed Classification Analysis + + #### Detailed Breakdown + + **Issue #123**: + - **Keywords Detected**: "error", "crash", "gh aw compile" + - **Pattern Match**: Typical bug report structure with error message + - **Similar Issues**: #110, #98 (similar error patterns) + - **Confidence Score**: 95% + + **Issue #124**: + - **Keywords Detected**: "feature request", "add support for", "would be nice" + - **Pattern Match**: Enhancement request pattern + - **Similar Issues**: #115, #102 (related feature requests) + - **Confidence Score**: 90% + + **Issue #125**: + - **Keywords Detected**: Mixed signals (both question and bug indicators) + - **Uncertainty Factors**: Unclear description, missing context + - **Reason for needs-triage**: Cannot confidently classify without more information + - **Confidence Score**: 40% + +
### Label Distribution - - bug: X issues - - enhancement: Y issues - - documentation: Z issues - - needs-triage: N issues +
+ View Label Statistics - ### Recommendations + - **bug**: X issues (Y% of processed) + - **enhancement**: X issues (Y% of processed) + - **documentation**: X issues (Y% of processed) + - **needs-triage**: X issues (Y% of processed) + - **cli**: X issues + - **workflows**: X issues + - **mcp**: X issues + +
- [Any patterns noticed or suggestions for improving auto-triage rules] + ### Recommendations + - [Actionable insights about triage patterns] + - [Suggestions for improving classification rules] + - [Notable trends in unlabeled issues] + + ### Confidence Assessment + - **Overall Success**: [High/Medium/Low] + - **Human Review Needed**: X issues flagged with `needs-triage` + - **Next Steps**: [Specific recommendations for maintainers] --- *Auto-Triage Issues workflow run: [Run URL]* diff --git a/.github/workflows/auto-triage-issues.md b/.github/workflows/auto-triage-issues.md index 147ac838152..6cb99be38d3 100644 --- a/.github/workflows/auto-triage-issues.md +++ b/.github/workflows/auto-triage-issues.md @@ -14,6 +14,8 @@ network: allowed: - defaults - github +imports: + - shared/reporting.md tools: github: toolsets: @@ -39,6 +41,74 @@ You are the Auto-Triage Issues Agent - an intelligent system that automatically Reduce the percentage of unlabeled issues from 8.6% to below 5% by automatically applying appropriate labels based on issue content, patterns, and context. +## Report Formatting Guidelines + +When creating triage reports and comments, follow these formatting standards to ensure readability and professionalism: + +### 1. Header Levels +**Use h3 (###) or lower for all headers in triage reports to maintain proper document hierarchy.** + +Headers should follow this structure: +- Use `###` (h3) for main sections (e.g., "### Triage Summary") +- Use `####` (h4) for subsections (e.g., "#### Classification Details") +- Never use `##` (h2) or `#` (h1) in reports - these are reserved for titles + +### 2. Progressive Disclosure +**Wrap detailed analysis and supporting evidence in `
Section Name` tags to improve readability.** + +Use collapsible sections for: +- Detailed classification reasoning and keyword analysis +- Similar issues and pattern matching results +- Verbose supporting evidence and historical context +- Extended analysis that isn't critical for immediate decision-making + +Always keep critical information visible: +- Triage decision (classification, priority, suggested labels) +- Routing recommendation +- Confidence assessment +- Key actionable recommendations + +### 3. Recommended Triage Report Structure + +When creating triage reports or comments, use this structure pattern: + +```markdown +### Triage Summary +- **Classification**: [bug/feature/question/documentation/etc] +- **Priority**: [P0/P1/P2/P3] +- **Suggested Labels**: [list of labels] +- **Suggested Assignee**: `@username` or team (if applicable) + +### Routing Recommendation +[Clear, actionable recommendation - always visible] + +
+View Classification Details + +[Why this classification was chosen, confidence score, keywords detected, pattern matching results] + +
+ +
+View Similar Issues + +[Links to similar issues, patterns detected across repository, historical context] + +
+ +### Confidence Assessment +- **Overall Confidence**: [High/Medium/Low] +- **Reasoning**: [Brief explanation - keep visible] +``` + +### Design Principles + +Your triage reports should: +1. **Build trust through clarity**: Triage decision and routing recommendation immediately visible +2. **Exceed expectations**: Include confidence scores, similar issues reference, and detailed reasoning +3. **Create delight**: Use progressive disclosure to share thorough analysis without cluttering issue threads +4. **Maintain consistency**: Follow the same patterns across all triage operations + ## Task When triggered by an issue event (opened/edited) or scheduled run, analyze issues and apply appropriate labels. @@ -149,33 +219,78 @@ For the triggering issue (on issue events), you can omit `item_number`: ## Scheduled Run Report -When running on schedule, create a discussion report with: +When running on schedule, create a discussion report following the formatting guidelines above: ```markdown -## 🏷️ Auto-Triage Report - [Date] +### 🏷️ Auto-Triage Report Summary +**Report Period**: [Date/Time Range] **Issues Processed**: X **Labels Applied**: Y total labels -**Still Unlabeled**: Z issues (failed to classify) +**Still Unlabeled**: Z issues (failed to classify confidently) + +### Key Metrics +- **Success Rate**: X% (issues successfully labeled) +- **Average Confidence**: [High/Medium/Low] +- **Most Common Classifications**: bug (X), enhancement (Y), documentation (Z) ### Classification Summary -| Issue | Applied Labels | Confidence | Reasoning | -|-------|---------------|------------|-----------| +| Issue | Applied Labels | Confidence | Key Reasoning | +|-------|---------------|------------|---------------| | #123 | bug, cli | High | Error message in title, mentions `gh aw` command | | #124 | enhancement | High | Feature request for new functionality | -| #125 | needs-triage | Low | Ambiguous description | +| #125 | needs-triage | Low | Ambiguous description requiring human review | + +
+View Detailed Classification Analysis + +#### Detailed Breakdown + +**Issue #123**: +- **Keywords Detected**: "error", "crash", "gh aw compile" +- **Pattern Match**: Typical bug report structure with error message +- **Similar Issues**: #110, #98 (similar error patterns) +- **Confidence Score**: 95% + +**Issue #124**: +- **Keywords Detected**: "feature request", "add support for", "would be nice" +- **Pattern Match**: Enhancement request pattern +- **Similar Issues**: #115, #102 (related feature requests) +- **Confidence Score**: 90% + +**Issue #125**: +- **Keywords Detected**: Mixed signals (both question and bug indicators) +- **Uncertainty Factors**: Unclear description, missing context +- **Reason for needs-triage**: Cannot confidently classify without more information +- **Confidence Score**: 40% + +
### Label Distribution -- bug: X issues -- enhancement: Y issues -- documentation: Z issues -- needs-triage: N issues +
+View Label Statistics -### Recommendations +- **bug**: X issues (Y% of processed) +- **enhancement**: X issues (Y% of processed) +- **documentation**: X issues (Y% of processed) +- **needs-triage**: X issues (Y% of processed) +- **cli**: X issues +- **workflows**: X issues +- **mcp**: X issues -[Any patterns noticed or suggestions for improving auto-triage rules] +
+ +### Recommendations +- [Actionable insights about triage patterns] +- [Suggestions for improving classification rules] +- [Notable trends in unlabeled issues] + +### Confidence Assessment +- **Overall Success**: [High/Medium/Low] +- **Human Review Needed**: X issues flagged with `needs-triage` +- **Next Steps**: [Specific recommendations for maintainers] --- *Auto-Triage Issues workflow run: [Run URL]* diff --git a/specs/artifacts.md b/specs/artifacts.md index 0f2beaa3f7b..2b6fd30e621 100644 --- a/specs/artifacts.md +++ b/specs/artifacts.md @@ -24,13 +24,13 @@ This section provides an overview of artifacts organized by job name, with dupli - `agent-artifacts` - **Paths**: `/tmp/gh-aw/agent-stdio.log`, `/tmp/gh-aw/aw-prompts/prompt.txt`, `/tmp/gh-aw/aw.patch`, `/tmp/gh-aw/aw_info.json`, `/tmp/gh-aw/mcp-logs/`, `/tmp/gh-aw/safe-inputs/logs/`, `/tmp/gh-aw/sandbox/firewall/logs/` - - **Used in**: 71 workflow(s) - agent-performance-analyzer.md, agent-persona-explorer.md, agentic-campaign-generator.md, ai-moderator.md, archie.md, brave.md, breaking-change-checker.md, changeset.md, ci-coach.md, ci-doctor.md, cli-consistency-checker.md, cloclo.md, code-scanning-fixer.md, codex-github-remote-mcp-test.md, commit-changes-analyzer.md, copilot-pr-merged-report.md, copilot-pr-nlp-analysis.md, craft.md, daily-choice-test.md, daily-copilot-token-report.md, daily-fact.md, daily-file-diet.md, daily-issues-report.md, daily-news.md, daily-observability-report.md, daily-repo-chronicle.md, daily-team-status.md, deep-report.md, dependabot-go-checker.md, dev-hawk.md, dev.md, dictation-prompt.md, example-custom-error-patterns.md, example-permissions-warning.md, firewall.md, github-mcp-structural-analysis.md, glossary-maintainer.md, go-fan.md, go-pattern-detector.md, grumpy-reviewer.md, hourly-ci-cleaner.md, issue-classifier.md, issue-triage-agent.md, layout-spec-maintainer.md, mergefest.md, metrics-collector.md, notion-issue-summary.md, pdf-summary.md, plan.md, poem-bot.md, pr-nitpick-reviewer.md, python-data-charts.md, q.md, release.md, repo-audit-analyzer.md, repository-quality-improver.md, research.md, scout.md, security-compliance.md, security-review.md, slide-deck-maintainer.md, stale-repo-identifier.md, super-linter.md, technical-doc-writer.md, test-create-pr-error-handling.md, tidy.md, typist.md, video-analyzer.md, weekly-issue-summary.md, workflow-generator.md, workflow-health-manager.md + - **Used in**: 72 workflow(s) - agent-performance-analyzer.md, agent-persona-explorer.md, agentic-campaign-generator.md, ai-moderator.md, archie.md, brave.md, breaking-change-checker.md, changeset.md, chroma-issue-indexer.md, ci-coach.md, ci-doctor.md, cli-consistency-checker.md, cloclo.md, code-scanning-fixer.md, codex-github-remote-mcp-test.md, commit-changes-analyzer.md, copilot-pr-merged-report.md, copilot-pr-nlp-analysis.md, craft.md, daily-choice-test.md, daily-copilot-token-report.md, daily-fact.md, daily-file-diet.md, daily-issues-report.md, daily-news.md, daily-observability-report.md, daily-repo-chronicle.md, daily-team-status.md, deep-report.md, dependabot-go-checker.md, dev-hawk.md, dev.md, dictation-prompt.md, example-custom-error-patterns.md, example-permissions-warning.md, firewall.md, github-mcp-structural-analysis.md, glossary-maintainer.md, go-fan.md, go-pattern-detector.md, grumpy-reviewer.md, hourly-ci-cleaner.md, issue-classifier.md, issue-triage-agent.md, layout-spec-maintainer.md, mergefest.md, metrics-collector.md, notion-issue-summary.md, pdf-summary.md, plan.md, poem-bot.md, pr-nitpick-reviewer.md, python-data-charts.md, q.md, release.md, repo-audit-analyzer.md, repository-quality-improver.md, research.md, scout.md, security-compliance.md, security-review.md, slide-deck-maintainer.md, stale-repo-identifier.md, super-linter.md, technical-doc-writer.md, test-create-pr-error-handling.md, tidy.md, typist.md, video-analyzer.md, weekly-issue-summary.md, workflow-generator.md, workflow-health-manager.md - `agent-output` - **Paths**: `${{ env.GH_AW_AGENT_OUTPUT }}` - **Used in**: 65 workflow(s) - agent-performance-analyzer.md, agent-persona-explorer.md, agentic-campaign-generator.md, ai-moderator.md, archie.md, brave.md, breaking-change-checker.md, changeset.md, ci-coach.md, ci-doctor.md, cli-consistency-checker.md, cloclo.md, code-scanning-fixer.md, commit-changes-analyzer.md, copilot-pr-merged-report.md, copilot-pr-nlp-analysis.md, craft.md, daily-choice-test.md, daily-copilot-token-report.md, daily-fact.md, daily-file-diet.md, daily-issues-report.md, daily-news.md, daily-observability-report.md, daily-repo-chronicle.md, daily-team-status.md, deep-report.md, dependabot-go-checker.md, dev-hawk.md, dictation-prompt.md, github-mcp-structural-analysis.md, glossary-maintainer.md, go-fan.md, go-pattern-detector.md, grumpy-reviewer.md, hourly-ci-cleaner.md, issue-classifier.md, issue-triage-agent.md, layout-spec-maintainer.md, mergefest.md, notion-issue-summary.md, pdf-summary.md, plan.md, poem-bot.md, pr-nitpick-reviewer.md, python-data-charts.md, q.md, release.md, repo-audit-analyzer.md, repository-quality-improver.md, research.md, scout.md, security-compliance.md, security-review.md, slide-deck-maintainer.md, stale-repo-identifier.md, super-linter.md, technical-doc-writer.md, test-create-pr-error-handling.md, tidy.md, typist.md, video-analyzer.md, weekly-issue-summary.md, workflow-generator.md, workflow-health-manager.md - `agent_outputs` - **Paths**: `/tmp/gh-aw/mcp-config/logs/`, `/tmp/gh-aw/redacted-urls.log`, `/tmp/gh-aw/sandbox/agent/logs/` - - **Used in**: 60 workflow(s) - agent-performance-analyzer.md, agent-persona-explorer.md, ai-moderator.md, archie.md, brave.md, breaking-change-checker.md, changeset.md, ci-coach.md, ci-doctor.md, cli-consistency-checker.md, code-scanning-fixer.md, codex-github-remote-mcp-test.md, copilot-pr-merged-report.md, copilot-pr-nlp-analysis.md, craft.md, daily-copilot-token-report.md, daily-fact.md, daily-file-diet.md, daily-issues-report.md, daily-news.md, daily-observability-report.md, daily-repo-chronicle.md, daily-team-status.md, deep-report.md, dependabot-go-checker.md, dev-hawk.md, dev.md, dictation-prompt.md, example-custom-error-patterns.md, example-permissions-warning.md, firewall.md, glossary-maintainer.md, grumpy-reviewer.md, hourly-ci-cleaner.md, issue-triage-agent.md, layout-spec-maintainer.md, mergefest.md, metrics-collector.md, notion-issue-summary.md, pdf-summary.md, plan.md, poem-bot.md, pr-nitpick-reviewer.md, python-data-charts.md, q.md, release.md, repo-audit-analyzer.md, repository-quality-improver.md, research.md, security-compliance.md, security-review.md, slide-deck-maintainer.md, stale-repo-identifier.md, super-linter.md, technical-doc-writer.md, tidy.md, video-analyzer.md, weekly-issue-summary.md, workflow-generator.md, workflow-health-manager.md + - **Used in**: 61 workflow(s) - agent-performance-analyzer.md, agent-persona-explorer.md, ai-moderator.md, archie.md, brave.md, breaking-change-checker.md, changeset.md, chroma-issue-indexer.md, ci-coach.md, ci-doctor.md, cli-consistency-checker.md, code-scanning-fixer.md, codex-github-remote-mcp-test.md, copilot-pr-merged-report.md, copilot-pr-nlp-analysis.md, craft.md, daily-copilot-token-report.md, daily-fact.md, daily-file-diet.md, daily-issues-report.md, daily-news.md, daily-observability-report.md, daily-repo-chronicle.md, daily-team-status.md, deep-report.md, dependabot-go-checker.md, dev-hawk.md, dev.md, dictation-prompt.md, example-custom-error-patterns.md, example-permissions-warning.md, firewall.md, glossary-maintainer.md, grumpy-reviewer.md, hourly-ci-cleaner.md, issue-triage-agent.md, layout-spec-maintainer.md, mergefest.md, metrics-collector.md, notion-issue-summary.md, pdf-summary.md, plan.md, poem-bot.md, pr-nitpick-reviewer.md, python-data-charts.md, q.md, release.md, repo-audit-analyzer.md, repository-quality-improver.md, research.md, security-compliance.md, security-review.md, slide-deck-maintainer.md, stale-repo-identifier.md, super-linter.md, technical-doc-writer.md, tidy.md, video-analyzer.md, weekly-issue-summary.md, workflow-generator.md, workflow-health-manager.md - `cache-memory` - **Paths**: `/tmp/gh-aw/cache-memory` - **Used in**: 28 workflow(s) - agent-persona-explorer.md, ci-coach.md, ci-doctor.md, cloclo.md, code-scanning-fixer.md, copilot-pr-nlp-analysis.md, daily-copilot-token-report.md, daily-issues-report.md, daily-news.md, daily-repo-chronicle.md, deep-report.md, github-mcp-structural-analysis.md, glossary-maintainer.md, go-fan.md, grumpy-reviewer.md, pdf-summary.md, poem-bot.md, pr-nitpick-reviewer.md, python-data-charts.md, q.md, scout.md, security-review.md, slide-deck-maintainer.md, stale-repo-identifier.md, super-linter.md, technical-doc-writer.md, test-create-pr-error-handling.md, weekly-issue-summary.md @@ -671,6 +671,25 @@ This section provides an overview of artifacts organized by job name, with dupli - **Download path**: `/tmp/gh-aw/` - **Depends on jobs**: [activation agent detection] +### chroma-issue-indexer.md + +#### Job: `agent` + +**Uploads:** + +- **Artifact**: `agent_outputs` + - **Upload paths**: + - `/tmp/gh-aw/sandbox/agent/logs/` + - `/tmp/gh-aw/redacted-urls.log` + +- **Artifact**: `agent-artifacts` + - **Upload paths**: + - `/tmp/gh-aw/aw-prompts/prompt.txt` + - `/tmp/gh-aw/aw_info.json` + - `/tmp/gh-aw/mcp-logs/` + - `/tmp/gh-aw/sandbox/firewall/logs/` + - `/tmp/gh-aw/agent-stdio.log` + ### ci-coach.md #### Job: `agent`