-
Notifications
You must be signed in to change notification settings - Fork 4
Add optional hook tracing #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add optional hook tracing #33
Conversation
|
I have revamped the entire diff mechanism, as it uses now snapshot based one. Please pull the main and open a PR on that. |
muraalee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agent Blame 3.0 has been shipped, please pull from main and send me the PR
551be1d to
9e5a537
Compare
|
I'll rebase and reuse this PR. Marked as WIP, will remove the tag in a sec. |
|
Removed WIP, this MR is ready for review. (Using this locally to interrogate copilot payloads to work on #36 .) |
d82365d to
60730e8
Compare
|
Rebased (and cleaned up commit author info). This can probably be closed / abandoned if a solution is found for #48 . |
This PR adds support for a local (per-init) agentblame config, and populating trace hook config values into it at init. Currently the config holds two options: traceAllHooks and traceFailedHooks .
traceAllHooks : record a json of every tool hook invocation
traceFailedHooks : record a json of tool hook invocations that resulted in some failure
This is mostly useful for debugging / exploratory work, e.g. spinning up a new provider (copilot-cli / #36).
I am not sure if cross-fork attribution works in the extension... about to find out!
If not, attribution is working within a single repo, see: spencatro-pub#1