Skip to content

chore(devel): enable CLI telemetry in the traced sandbox kit - #3382

Merged
migmartri merged 1 commit into
mainfrom
chore/sandbox-kit-cli-telemetry
Aug 31, 2026
Merged

migmartri merged 1 commit into
mainfrom
chore/sandbox-kit-cli-telemetry

Conversation

@migmartri

@migmartri migmartri commented Aug 28, 2026 •

Copy link
Copy Markdown
Member

The traced-Claude sandbox kit (devel/sandbox-kit) set DO_NOT_TRACK=1 and did not allow egress to the telemetry endpoint, so CLI usage from sessions run inside the sandbox was never reported.

This removes the DO_NOT_TRACK environment variable from the kit and adds crb.chainloop.dev:443 to the kit's network allow rules, so those sessions report usage like any other CLI invocation. The host is deliberately kept out of NO_PROXY, since telemetry is plain HTTPS and does not need the proxy bypass that the gRPC endpoints require.

AI disclosure: this change was produced with the assistance of Claude Code.

Review in cubic

@chainloop-platform

chainloop-platform Bot commented Aug 28, 2026 •

Copy link
Copy Markdown
Contributor

Security Checks — ⚠️ 1 failing

✅ secret-scan

Status Policy Messages
✅ Passed secrets-detection -

✅ sast-scan

Status Policy Messages
✅ Passed owasp-top10-2025 -
✅ Passed sast -
✅ Passed cwe-top25 -
✅ Passed cwe-top26-40-cusp -

✅ iac-scan

Status Policy Messages
✅ Passed iac-misconfiguration -

PR info

Status Policy Messages
✅ Passed pr-description-required -
⚠️ Failed pr-user-story-linked PR/MR #3382 does not reference a user story or issue in title, description, or branch 'chore(devel): enable CLI telemetry in the traced sandbox kit'. Expected patterns: ["(?i)[A-Z]+-[0-9]+", "#[0-9]+", "(?i)[A-Z]{2", "}-[0-9]+", "(?i)gh-[0-9]+", "(?i)\[[A-Z]+-[0-9]+\]"]

⏭️ 2 scans not applied

Scan Reason
vulnerability-scan no manifest/lockfile changed
github-actions-scan no workflow files changed

View attestation ↗


Powered by Chainloop and Chainloop Trace

@migmartri
migmartri force-pushed the chore/sandbox-kit-cli-telemetry branch from 2644f50 to f80771b Compare August 28, 2026 15:47

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Drop DO_NOT_TRACK=1 from the sandbox kit environment and allow egress to
crb.chainloop.dev, the endpoint the CLI reports usage telemetry to, so
sessions run through the kit are counted like any other CLI usage.

Assisted-by: Claude Code
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>

Chainloop-Trace-Sessions: 6a463356-6105-4697-a537-fd08c713afa2
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
@migmartri
migmartri force-pushed the chore/sandbox-kit-cli-telemetry branch from f80771b to 49d156c Compare August 31, 2026 11:50
@migmartri
migmartri merged commit 8336074 into main Aug 31, 2026
15 of 16 checks passed
@migmartri
migmartri deleted the chore/sandbox-kit-cli-telemetry branch August 31, 2026 11:59
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.

2 participants