find

Find the Session Behind a Change

More on these workflows: photostructure.com/coding (no dedicated find article yet)

Report which local agent session wrote a change that is still uncommitted, and give the user a command that resumes it.

Run the finder

Resolve the bundled scripts/find_session.py relative to this skill directory. Run it with the host's Python 3 launcher from inside the repository that holds the change:

python3 scripts/find_session.py <path-or-snippet>

• A path to a file with uncommitted changes attributes that file's whole diff against HEAD.
• Any other argument is a snippet of changed text. The finder locates it in the diff against HEAD, untracked files included, and attributes only the lines it spans. Indentation, line breaks, and leading comment markers are ignored, so a comment copied across wrapped lines still matches. Pass a multi-line snippet as one quoted argument.
• --days N searches transcripts modified in the last N days (default 14). --limit N caps the candidates shown (default 5).

On Windows, py -3 is a common equivalent.

How it attributes a change

The finder reads the transcripts that both supported agent CLIs keep under the user's home directory; the script's docstring names the directories and the environment variables that relocate them. It keeps only writes that succeeded, and scores each session by how many of the target's changed lines its writes added or removed. It counts:

• patches recorded by the file-editing tools;
• patch envelopes applied through a code-execution tool;
• shell commands that write the file and either name its absolute path or run inside its checkout, as weaker evidence, reported as "only through shell commands";
• writes to a path that no longer exists but has the target's file name and lies inside the same checkout, outside git-ignored directories, because the file was moved after them.