Skip to main content

Observability and Privacy

This page is for maintainers balancing cloud-run diagnostics against the sensitivity of prompts, repository content and command text.

Know What Persists

  • Execution diagnostics are enabled by default. They remain in Actions logs and the job summary.
  • Full transcript artifacts are disabled by default.
  • Scrubbed denied-command text is enabled by default and can persist on the telemetry branch.
  • Denial count and tool identifiers are not controlled by the command-text toggle.
  • Effectiveness records are enabled by default.
The transcript and command scrubber is an incomplete blocklist. It covers common GitHub tokens, Anthropic keys and Bearer or basic Authorization headers. Other credential shapes can remain. A scrub failure prevents the affected text from being uploaded or persisted. Warning: A successful scrub does not prove that output is secret-free.
  • Transcript artifacts and denied-command records use the scrubber.
  • Actions diagnostics can still contain truncated tool input. Treat those logs as sensitive.
Use repository access controls and artifact retention as part of the privacy decision. Set both text-bearing options to false when even scrubbed prompt or command content is unacceptable:
Disabling denied-command text does not disable ordinary log diagnostics. Disable execution_diagnostics_enabled separately for quieter logs.