[Question]: Special permission for memory

[mansiibm]

Hi, I have setup memory as

memory:
  disabled: false # Set to true to completely disable memory
  personalize: true # Gives users the ability to toggle memory on/off, true by default
  tokenLimit: 3000 # Maximum tokens for memory storage
  messageWindowSize: 5 # Number of recent messages to consider
  agent:
    provider: "openAI"
    model: "gpt-4.1-mini"

now in my UI it is not appearing . Loaded in backend but not appearing in the UI.

I am using the version 0.8.3-rc1 ando it is not appearing , loading in the backend but not appearing in frontend.

[mansiibm]

Some special permission is required for it? from the new version?

[manc1211]

I am facing the same issue. What version is compatible with memory?

[mansiibm]

Hi Danny, we experience this problem whenever the image - v0.8.3-rc3 is deployed. The memories does not show up. I am aware that migration has to be performed, for the agents and prompts, but for memories I believe no particular migration is required and it should appear out of box. The admin is also not able to see the memory in the UI, so if it has to be enabled for all users. Can you please help in here ...

Steps followed -

1. Deployed the image- v0.8.3-rc3 for the azure container app
2. Then went to console option
3. navigated to /app
4. ran the commands for the migration of agents and prompts (as a user)
5. then stopped the container and then cleared the cache (redis)
6. Restarted the container , everything works fine, all things show up as mentioned in yaml , apart from memories.
7. The yaml is valid and getting perfectly loaded in backend.

[mansiibm]

Also this migration was one time thing we did not do it again. After this memories not showing up , even for admin .

[mansiibm]

Hello, after introspection on the database we found certain points which might help users to overcome the challenge. In the database there is the table for - roles . If after you have applied the v0.8.3-rc3 version, run the migration commands as -

npm run migrate:agent-permissions
npm run migrate:prompt-permissions

there are high chances that you might still not see the memory section . The reason being that in the database for roles table the following upgrade does not happpen automatically.

The memory section is false for all actions that can be done for memory by an Admin, as a result of which the memory tab does not even appear in the right-hand side panel even for the admin so that she/he can enable or disable it for all the users.

This is after when migration is done and new version is applied, so we had to manually modify the columns for roles for admin and set memory to true and for all the sub parts of memory as well. After this done the fields for the admin roles appear as -

and now on the UI the memory tab will appear only for the Admin. Now the admin can enable or keep it disabled for other users.

Also pls after the changes are done, do flush the cache.

Its this db thing which did not update automatically, reason unknown.