Description
Agentic tooling request:
Handles registry creator and editor and handles registry file that auto updates on task completion for an agent. allowing the agent to effectively isolate to one program file and one registry file when required to work on larger than context window codebases, perhaps with an integrated micro venv or just a dummy folder with only the registry file and the file to be changed in an isolated and known place, perhaps have this as a setting for the location of the dummy folder and registry file, with some default locations pre-made. Either the dummy folder is created each isolated work request or persistent one that clears contents after task completion, scheduling should be file in codebase is replaced with isolated file before algorithmic confirmation of replacement and diff merge of original file is produced, then after confirmation of keep, task is changed to completed and agent returns to user for next prompt.
this is separate to native agentic use and is more for specific use cases where content of other files affects agent generations such as instruction files specific to the project, project sub folder, or individual file instruction files.
can be done already through prompting and manual isolation with a prebuilt tool, but would allow more effective and efficient agentic use by allowing isolations without creating a new workspace.
here is my current tooling for this for reference, pretty basic.
https://github.com/UncleMcNutz/Utilities-Public/blob/main/handles_registry.py