trace: expand same-call attribution beyond foreground Claude Bash
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- bash, git, go
调研方向
Start with the implementation and tests for PR #3631, which handles foreground native Claude Code Bash calls using the hook input update mechanism, and review the related context in #3625. Map the existing capability reporting and integration tests for each provider/runtime, then investigate background process lifecycle, hook composition, and permission matching. Done means supported combinations have tested exact call correlation and unsupported combinations clearly report their limitation.
由索引模型根据 Issue 内容生成。
描述
Context
Follow-up to #3625 and PR #3631. The PR is intentionally scoped to a foreground native Claude Code Bash call, following maintainer review.
It currently uses Claude Code's hook input update mechanism to export an opaque call token into the command before Git hooks run.
Scope
Investigate and implement broader runtime support for same-call commit attribution:
- background Bash calls whose process can outlive
PostToolUse; - coexistence with another hook that also rewrites
updatedInput; - narrow Bash permission matchers that can behave differently after command rewriting;
- Cursor, OpenCode, and other providers that do not expose the same pre-execution command-rewrite contract;
- explicit capability reporting when exact call correlation is unavailable.
Expected behavior
Every supported provider/runtime has a documented, tested way to correlate a Git hook with the exact command call that made the staged change. Unsupported combinations fail visibly or remain explicitly documented as unsupported instead of silently losing attribution.
Acceptance criteria
- Background-call lifecycle and snapshot retention are defined and tested.
- Multiple input-rewriting hooks have deterministic composition or a documented incompatibility.
- Narrow permission configurations retain their intended behavior.
- Each provider's capability matrix entry matches observable support.
- Unsupported runtimes surface a clear limitation or warning.
- Integration tests cover every provider/runtime combination declared supported.
- 主要语言
- Go
- 星标
- 582
- 派生
- 61
- 平均合并
- 12 小时 47 分钟
- 30 天内合并 PR
- 137
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
chainloop-dev/chainloop 的其他 Issue
-
feature-parity trace-provider
难度 2/5 1-3 小时 新手友好度 70/100
chainloop-dev/chainloop#3802 ·
维护者通常 1 天内回复
-
bug trace-provider
难度 4/5 3-5 天 新手友好度 48/100
chainloop-dev/chainloop#3803 ·
维护者通常 1 天内回复
-
feat(trace): support GitHub Copilot (CLI and VS Code) in Chainloop Trace可能已有人在做 @migmartri 今天认领。 未关闭Feature spec trace-provider
chainloop-dev/chainloop#3800 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Allow enabling policy enforcement at the workflow contract level可能已有人在做 @migmartri 于 10 天前认领。 未关闭component/backend new-policy spec
chainloop-dev/chainloop#3762 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
chainloop component/CLI performance trace-provider
难度 4/5 3-5 天 新手友好度 62/100
chainloop-dev/chainloop#3756 ·
维护者通常 1 天内回复
查看 chainloop-dev/chainloop 的全部 Issue
相似的 Issue
-
GitHub webhook is not subscribed to release events, so `event: release` never triggers可能已有人在做 @qsun 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
woodpecker-ci/woodpecker#7542 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
zilliztech/milvus-backup#1386 ·
维护者通常 1 天内回复
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
model:sonnet runtime:claude security size:S
难度 2/5 1-3 小时 新手友好度 78/100
FootprintAI/Containarium#3624 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复