bazelbuild/bazel

Clean up --experimental_remote_mark_tool_inputs

Open

#28,493 opened on Jan 31, 2026

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P3help wantedteam-Remote-Exectype: bug

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

--experimental_remote_mark_tool_inputs is required for remote persistent workers to function correctly:

This flag was first introduced in Bazel 6.0.0, and doesn't describe any reason users should keep it disabled. As-is, this appears to be unnecessary boilerplate for remote persistent workers. One of the following should be done:

  1. Enable the flag by default, and target a version for removal.
  2. Document the tradeoff that justifies why this flag is off by default.

Contributor guide

Research direction
Investigate the history of ` experimental remote mark tool inputs`, understand why it was kept off by default, and propose either enabling it by default with a deprecation plan or documenting the tradeoff.
Tech stack
java
Domain
build system
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
BazelGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60