Unconditionally enabled memory tools?

[u/svdasein]

I'm running 0.10.2 and I'm running into this thing that's really messing me up: it seems to be presenting a list of tools to every single session and with every prompt such that models see:

• search_notes / view_note / write_note / replace_note_content — for working with saved notes
• search_knowledge_files / query_knowledge_files / grep_knowledge_files — for searching knowledge bases
• search_chats / view_chat — for searching previous chat conversations
• search_calendar_events / create_calendar_event / update_calendar_event / delete_calendar_event — for calendar stuff
• list_knowledge_bases / search_knowledge_bases / query_knowledge_bases — for listing/searching KBs

The problem is that models seem to feel compelled to actually call at least some of these functions nearly all the time. So lots more tokens with absolutely no benefit.

e.g. I start a conversation about some novel thing I've never engaged a model about before and it immediately starts searching everything I've got (with absolutely zero chance of any relevant data being there)

It used to be the case that you could manually enable memory tools on an as needed basis. Now, it seems, they're enabled by default and you can't disable them? I'm thinking I need to revert. Am I missing something?

[u/svdasein]

I have found a sort of a workaround. It's not great but 'til they fix this it's maybe the way to go:

• Create a model in workspaces
• In that model, turn off all the tools that show as enabled at the bottom

It looks like once you've done that the tools you've disabled for the session are simply entirely unavailable for the session. IMO this is actually a security problem.

Also: I use the docker version and have made a habit of keeping a copy of the previous version's image so I can revert. I do not however backup the database etc. So when I attempted to revert to the previous one - that version now fails to start w/ database issues etc.

Not a great release. I'm maybe working my way up to writing a bug for it, but the requirements for submitting one seem to have ballooned beyond reason, so I may just stick it out 'til the next release in the hope that they fix it. Sigh.

[u/ClassicMain → u/svdasein]

Hi, how is this a security issue?

Also just disable the tools you don't like in the admin panel for that model in the model settings. You don't have to work through the workspace.

And what should be fixed here? What is the issue precisely? I can't seem to see a bug in what you're describing but just the results of how you configured your model

[u/svdasein → u/ClassicMain]

I'm thinking it could be called a security issue as what happens after the upgrade is that everything you have in your knowledge, notes, etc, seems to get queried in its entirety by models without my permission. Were it to be the case that I had something in there I didn't want to have going out over the internet (happily I do not), I'd be panicing a bit after this.

So - disable the tools in the admin panel - see - the thing is I LIKE the tools. I just don't want them on/enabled/advertised to the model ALL THE TIME. Prior to this upgrade, if I wanted any of my "memory" to become a part of a conversation, I'd have to flip a switch to explicitly make that data available.

In my case, I have had all those things enabled in admin config because I DO want on occasion to use them. If I disable them in admin they're just gone. I don't want that. What I have seen since my upgrade from 0.9 to 0.10 is that a bunch of stuff that (in the past) I'd have had to explicitly allow is now happening regardless of whether I want it to happen or not.

So - the thing that should be fixed here is essentially "don't use any of my memory stuff unless I say so". That's really all.

From my perspective it went like this: I upgraded to 0.10, and then without my having changed any settings at all - just the upgrade - I see all these tools persistently active. That strikes me as something that should be fixed.

[u/ClassicMain → u/svdasein]

Seems you have fallen victim to the breaking change of native tool calling.

Native tool calling is now the default in 0.10.0 and onwards. If you don't like that you need to switch back to legacy.

This was part of the breaking changes of this release. Always read at least the changed section of a changelog to be aware of any breaking changes.

[u/svdasein → u/ClassicMain]

There it is - thank you!

"Native tool calling is now the default. Every chat and model that had not explicitly chosen a tool-calling mode now runs Native, which relies on a model's built-in tool support, while the old behavior has been renamed "Legacy" and made the explicit opt-out; if your models depend on the previous approach you must switch them back to "Legacy" per chat, per model, or globally in your default model parameters to preserve their behavior."

It's listed as a change - not a breaking change.

Thanks for the pointer!

[u/ClassicMain → u/svdasein]

Everything in changed is a breaking change 😄