You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When you select a non-default context window with memgpt configure, then do memgpt run and create a new agent, the new agent does not use the selected context window size.
To Reproduce
memgpt configure, set context window to 4k:
% memgpt configure
? Do you want to enable MemGPT with OpenAI? No
? Do you want to enable MemGPT with Azure? No
? Select default inference endpoint: http://localhost:1234
? Select default embedding endpoint: local
? Select default preset: memgpt_chat
? Select your model's context window (for Mistral 7B models, this is probably 8k / 8192): 4096
? Select default persona: sam_pov
? Select default human: cs_phd
? Select storage backend for archival data: local
Saving config to /Users/loaner/.memgpt/config
memgpt run, create a new agent:
% memgpt run
? Would you like to select an existing agent? No
Creating new agent...
Created new agent agent_33.
Hit enter to begin (will request first MemGPT message)^C
Aborted.
context_window is also not present in the base config:
% cat ~/.memgpt/config
[defaults]
model = local
preset = memgpt_chat
model_endpoint = http://localhost:1234
persona = sam_pov
human = cs_phd
[embedding]
model = local
dim = 384
chunk_size = 300
[archival_storage]
type = local
[client]
anon_clientid = 00000000000000...
Expected behavior
config.json should show 4096, not 8192.
The text was updated successfully, but these errors were encountered:
Describe the bug
When you select a non-default context window with
memgpt configure
, then domemgpt run
and create a new agent, the new agent does not use the selected context window size.To Reproduce
memgpt configure
, set context window to 4k:memgpt run
, create a new agent:Check the
config.json
of the new agent:context_window
is also not present in the base config:Expected behavior
config.json
should show 4096, not 8192.The text was updated successfully, but these errors were encountered: