Poetry create new virtual environments after installing conda

Question

Here is the story of how I got poetry and miniconda messed up on my mac:

I cloned a project from the git hub, and PyCharm created a virtual environment (venv). I installed Peotry (not in venv) and used it to manage my packages. So far, so good. But after I installed miniconda (not in venv), when I run poetry install (with venv activated), it created a new virtual environment and installed all the packages there:

Virtualenv
Python:         3.12.2
Implementation: CPython
Path:           /Users/XinNiuAdmin/Library/Caches/pypoetry/virtualenvs/convert_neuralynx_to_nwb-w6GlhHFh-py3.12
Executable:     /Users/XinNiuAdmin/Library/Caches/pypoetry/virtualenvs/convert_neuralynx_to_nwb-w6GlhHFh-py3.12/bin/python
Valid:          True

The environment status is (venv) (base). Could anyone tell me how I can reset poetry within my original virtual environment (venv)? Should I reinstall poetry within my virtual environment?

My workaround for this is to create a new environment with Conda and install the packages with Poetry. It seems everything works fine. It would be great if anyone could provide more insights on how Poetry and Conda conflict in this scenario.