ERROR - Config file not found at /configs/memgpt_hosted.json [pip install pymemgpt 03.14]

[quantumalchemy]

Describe the bug
ERROR:
Config file not found at /usr/local/lib/python3.11/site-packages/memgpt/cli/../../configs/memgpt_hosted.json

Please describe your setup

• pip install pymemgpt
• Describe your setup
  linux (docker)
  files not being installed for pip install
  ok in local devel. install e .

[aBaldoqui]

I'm experiencing the same problem.
There was a bug closed regarding this yesterday: #1320.

[quantumalchemy]

works with Devel mode:
git clone https://github.com/cpacker/MemGPT.git
pip install -e .

[MEllis-github]

Same error for macOS running

pip install -U pymemgpt
memgpt quickstart --backend memgpt

Not triggered with

pip install -e .
memgpt quickstart --backend memgpt

Git branch: main
Git revision: e8eed7b

[datashaman]

I've got it working by using the code on branch tutorials which includes a fix for this.

MacOS doesn't like installing python packages in the system folders, and I don't want to be in a virtualenv whenever I use this.

pipx to the rescue. The following got me up and running:

pipx install git+https://github.com/cpacker/MemGPT.git@tutorials

[twilwa]

I've got it working by using the code on branch tutorials which includes a fix for this.

MacOS doesn't like installing python packages in the system folders, and I don't want to be in a virtualenv whenever I use this.

pipx to the rescue. The following got me up and running:

pipx install git+https://github.com/cpacker/MemGPT.git@tutorials

Will open my own ticket, but I was able to get this up and running out of a desire to use pipx as opposed to making a venv/local folder. Ran into the same problem, but the tutorials branch did fix it -- however, I'm running into a different issue. When I use the --stream flag, I get repeated attempts that don't involve the thinking step, when I don't I get inifinite loop on retries until it times out for too many attempts. Additionally, the persona and human profile information is incorrect in the terminal, but correct when interacting with the agent. maybe helpful info on this ticket