FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

chore(devel): enable CLI telemetry in the traced sandbox kit by migmartri · Pull Request #3382 · chainloop-dev/chainloop · GitHub

/ chainloop Public

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

Open
migmartri wants to merge 1 commit into
mainfrom
chore/sandbox-kit-cli-telemetry
ConversationCommits (1)ChecksFiles changed
Open

chore(devel): enable CLI telemetry in the traced sandbox kit#3382
migmartri wants to merge 1 commit into
mainfrom
chore/sandbox-kit-cli-telemetry

Conversation

migmartri commented Aug 28, 2026 •
edited by cubic-dev-ai Bot
Loading

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.

chainloop-platform Bot commented Aug 28, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

AI Session Checks — 🟡 60% · ✅ 0 failing

Avg score Sessions Failing policies Attribution Files Lines Total Duration
🟡 60% 1 ✅ 0 100% AI / 0% Human 1 +1 / -1 1h54m28s

🟡 60% — 100% AI — ✅ All policies passing

Aug 28, 2026 13:52 UTC · 1h54m28s · $3.26 · 126 in / 25.0k out · claude-code 2.1.246 (claude-opus-5)

View session details ↗

Change Summary

  • Removes DO_NOT_TRACK from the traced sandbox kit environment.
  • Adds crb.chainloop.dev:443 to the sandbox-kit network allowlist.
  • Prepares a signed commit and branch for the change, but no PR is shown as opened.

AI Session Overall Score

🟡 60% — Focused config change, but verification never exercised the sandbox behavior end-to-end.

AI Session Analysis Breakdown

🟢 92% · scope-discipline

🟢 Both requested config changes stayed in spec.yaml. · High Impact

🟢 88% · solution-quality

🟢 AI used direct allowlist and env changes instead of bypasses. · High Impact

🟢 86% · user-trust-signal

🟢 The user moved between asks without any correction cycle. · Medium Impact

🟡 70% · context-and-planning

🟠 The PR-creation phase started without an auth or remote precheck, so setup was partly improvised. · Medium Severity

💡 For PR-creation asks, front-load branch, signing, and push prerequisites before editing repo config or attempting network actions.

🟡 68% · alignment

🟠 The user asked for a PR, but the session only shows a local commit plus failed or missing push results. · Medium Severity

💡 Confirm remote auth and PR prerequisites before treating a local commit as progress toward a requested PR.

🔴 32% · verification

🔴 The sandbox-kit change was syntax-checked, but nobody exercised the new telemetry path end-to-end. · High Severity

💡 For config-shaped changes, run the new path end-to-end once; parsing the file is not enough verification.

File Attribution

████████████████████ 100% AI / 0% Human

Status Attribution File Lines
modified ai devel/sandbox-kit/spec.yaml +1 / -1

Policies (4)

Status Policy Material Messages
✅ Passed ai-config-ai-agents-allowed ai-coding-session-6a4633 -
✅ Passed ai-config-no-dangerous-commands ai-coding-session-6a4633 -
✅ Passed ai-config-no-secrets ai-coding-session-6a4633 -
✅ Passed ai-config-mcp-servers-allowed ai-coding-session-6a4633 -

Security Checks — ⚠️ 1 failing

✅ 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

chore(devel): enable CLI telemetry in the traced sandbox kit
f80771b 
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 force-pushed the chore/sandbox-kit-cli-telemetry branch from 2644f50 to f80771b Compare August 28, 2026 15:47
cubic-dev-ai Bot reviewed Aug 28, 2026
View reviewed changes

cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

No issues found across 1 file

Re-trigger cubic

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

cubic-dev-ai[bot] cubic-dev-ai[bot] left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

Back | FazBrowse Home | New Git URL