[GH-ISSUE #281] Define a standard/extension to agent preset v1 for post commit prompt updating #104

New issue

Open

opened 2026-03-02 04:11:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 04:11:51 +03:00

Owner

Originally created by @svarlamov on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/281

The custom agent presets (like Cursor, Claude, etc.) all have a final check in the post commit logic that pulls the transcripts to ensure that git ai saves the latest version of the transcript. This is primarily to catch things like the agent's final message, etc. -- all the stuff that happens after the last file edit in the conversation.

We would like to standardize more agents on using the generic preset, but there's no way in the generic preset to run this logic. Would like to open the discussion on figuring out the best way to extend the preset to support this logic. Some initial ideas:

Allow passing in agent metadata (a field that's already used by other presets for the same purpose) that will point to a JSON file that will contain the latest version of the transcript. Update post commit to check for this in metadata and update transcripts accordingly.
Add custom logic by tool name for updating prompts from the given agent's custom transcript storage location. Agent metadata could also be used for storing the path. This somewhat breaks the generic philosophy of the preset, but it doesn't prevent generic usage/options
Add a way for agents to send updated transcripts by conversation ID. Many agents have hooks for new messages/etc., so we could just update the latest checkpoint with the given conversation ID with the latest transcript on receipt of this new hook.

Originally created by @svarlamov on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/281 The custom agent presets (like Cursor, Claude, etc.) all have a final check in the post commit logic that pulls the transcripts to ensure that git ai saves the latest version of the transcript. This is primarily to catch things like the agent's final message, etc. -- all the stuff that happens after the last file edit in the conversation. We would like to standardize more agents on using the generic preset, but there's no way in the generic preset to run this logic. Would like to open the discussion on figuring out the best way to extend the preset to support this logic. Some initial ideas: 1. Allow passing in agent metadata (a field that's already used by other presets for the same purpose) that will point to a JSON file that will contain the latest version of the transcript. Update post commit to check for this in metadata and update transcripts accordingly. 2. Add custom logic by tool name for updating prompts from the given agent's custom transcript storage location. Agent metadata could also be used for storing the path. This somewhat breaks the generic philosophy of the preset, but it doesn't prevent generic usage/options 3. Add a way for agents to send updated transcripts by conversation ID. Many agents have hooks for new messages/etc., so we could just update the latest checkpoint with the given conversation ID with the latest transcript on receipt of this new hook.