Idea: Use an existing uv project (e.g., check if one exists) or add CLI options to configure the behavior in this regard.
Current behavior: Always try to create new project from template (fail, if one already exists).
Expected behavior: Be able to generate new exploits from template either way.
It is alright to set up a minimal and isolated environment per exploit by default. However, it would be useful to be able to configure this default behavior, e.g., to generate multiple exploits in the same project.
I could imagine an option to use an existing project or something. But then again, I'm not sure what a good default would be if there's already a project in the directory. We could also implement a follow-up question for this case.
Idea: Use an existing uv project (e.g., check if one exists) or add CLI options to configure the behavior in this regard.
Current behavior: Always try to create new project from template (fail, if one already exists).
Expected behavior: Be able to generate new exploits from template either way.
It is alright to set up a minimal and isolated environment per exploit by default. However, it would be useful to be able to configure this default behavior, e.g., to generate multiple exploits in the same project.
I could imagine an option to use an existing project or something. But then again, I'm not sure what a good default would be if there's already a project in the directory. We could also implement a follow-up question for this case.