Skip to content

Conversation

@spencatro-pub
Copy link

@spencatro-pub spencatro-pub commented Jan 29, 2026

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

image

@muraalee
Copy link
Collaborator

muraalee commented Feb 2, 2026

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 muraalee self-requested a review February 2, 2026 22:26
Copy link
Collaborator

@muraalee muraalee left a 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

@spencatro-pub spencatro-pub changed the title Add support for local agentblame config, implement optional hook tracing WIP: Add support for local agentblame config, implement optional hook tracing Feb 4, 2026
@spencatro-pub
Copy link
Author

I'll rebase and reuse this PR. Marked as WIP, will remove the tag in a sec.

@spencatro-pub spencatro-pub changed the title WIP: Add support for local agentblame config, implement optional hook tracing Add optional hook tracing Feb 4, 2026
@spencatro-pub
Copy link
Author

Removed WIP, this MR is ready for review. (Using this locally to interrogate copilot payloads to work on #36 .)

@spencatro-pub
Copy link
Author

Rebased (and cleaned up commit author info). This can probably be closed / abandoned if a solution is found for #48 .

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