Skip to content

feat(run): hint when /tmp artifact I/O is filtered out of lineage#130

Merged
christophergeyer merged 1 commit into
mainfrom
feat/tmp-filtered-hint
May 30, 2026
Merged

feat(run): hint when /tmp artifact I/O is filtered out of lineage#130
christophergeyer merged 1 commit into
mainfrom
feat/tmp-filtered-hint

Conversation

@christophergeyer
Copy link
Copy Markdown
Member

Why

filters.ignore_tmp_files is on by default, so a roar run whose workspace lives under /tmp silently records no artifacts (its reads/writes are filtered). This is a common, confusing surprise — you get in:0 out:0 with no explanation unless you happen to run -vv.

What

After the run summary, emit an amber hint: whenever at least one /tmp path was filtered:

hint: 3 /tmp files filtered out of this run's lineage (filters.ignore_tmp_files).
      Run outside /tmp, or `roar config set filters.ignore_tmp_files false`, to track them.
  • Reuses the count the filter already computes (result.filter_counts["tmp_files"]) — no extra recording, no added tracer overhead.
  • Same gating as next_steps_hint: suppressed by quiet mode and hints.enabled = false; goes to stderr.
  • Fires from both the roar run execution path and the legacy show_report.

Tests

5 new cases in tests/unit/test_run_report.py: fires when tmp filtered (plural + singular), silent when nothing filtered / key absent, silent in quiet mode, silent when hints disabled. Full test_run_report.py green; ruff check + format clean.

🤖 Generated with Claude Code

filters.ignore_tmp_files (on by default) drops /tmp reads/writes, so a run in
a /tmp workspace silently records no artifacts — a common surprise. Surface
the existing filtered-/tmp count as an amber hint after the run summary,
gated like next_steps_hint (quiet + hints.enabled). Reuses the count the
filter already computes; no extra recording.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@christophergeyer christophergeyer merged commit 0d04c9c into main May 30, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants