A developer released ctx (ctx.rs), a tool that extends git blame to trace any commit, file, line, or PR back to the exact agent tool call that wrote the code, then returns the full agent session transcript. The goal is to give coding agents fast local search over prior session transcripts so they can understand code provenance — why code was written, what tests were run — information too verbose for humans but useful for agents.
A tool that works like git blame for agent sessions: given a line or file, it surfaces the full AI coding agent transcript from when that code was committed. Developers or their agents can read the original session to understand why code was written, replacing the old PR-review workflow. It targets developers working with AI coding agents who need context on existing code.
A tool that works like git blame for agent sessions: given a line or file, it surfaces the full AI coding agent transcript from when that code was committed. Developers or their agents can read the original session to understand why code was written, replacing the old PR-review workflow. It targets developers working with AI coding agents who need context on existing code.
GitScry is a local CLI that gives coding agents access to knowledge buried in Git history. It exposes purpose-built queries over commits, diffs, reverts, blame, and file co-change patterns, so agents can retrieve context that never made it into documentation. It targets developers using LLM coding agents.
GitScry is a local CLI that gives coding agents access to knowledge buried in Git history. It exposes purpose-built queries over commits, diffs, reverts, blame, and file co-change patterns, so agents can retrieve context that never made it into documentation. It targets developers using LLM coding agents.
WTF gives developers an overview of what their coding agents actually changed, aiming to replace manual inspection of agent work. It runs fully locally with no API calls. The author is also experimenting with using it to ground agents in reality, though that is not working yet.
WTF gives developers an overview of what their coding agents actually changed, aiming to replace manual inspection of agent work. It runs fully locally with no API calls. The author is also experimenting with using it to ground agents in reality, though that is not working yet.
A developer added a read-only `why` command to ThoughtDAG, a local tool that recovers which AI-agent conversation produced a given code change. Running `npx thoughtdag why src/lib/api.ts` searches local agent transcripts for turns that changed or discussed the file and links back to the source turn. It addresses the gap where Git shows the diff but not the reasoning, rejected approaches, or assumptions behind agent edits.
A developer added a read-only `why` command to ThoughtDAG, a local tool that recovers which AI-agent conversation produced a given code change. Running `npx thoughtdag why src/lib/api.ts` searches local agent transcripts for turns that changed or discussed the file and links back to the source turn. It addresses the gap where Git shows the diff but not the reasoning, rejected approaches, or assumptions behind agent edits.
ctx is a tool that provides version control and attribution for AI agent sessions, similar to git blame. It helps developers understand which agent actions led to specific outcomes, improving debugging and accountability in AI workflows.
ctx is a tool that provides version control and attribution for AI agent sessions, similar to git blame. It helps developers understand which agent actions led to specific outcomes, improving debugging and accountability in AI workflows.