after update, includedTools missing, latest config version not recognized, actions disabled #9386
Unanswered
krahnikblis
asked this question in
Troubleshooting
Replies: 2 comments 1 reply
-
Same here. "Tools" list in AgentBuilder is empty now after the last "git pull origin main". All was operational just before. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This is already fixed on the latest dev image and on next RC release |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
i had installed v0.7.9 a few weeks ago on my home system ahead of upgrading at work, today i (multiple times) ran
git pull
anddocker compose pull
. verified i'm now on v0.8.0-rc3. my.env
has keys for google and youtube (for the built-in tools). i've tried all combinations of the ENDPOINTS in.env
(including/excluding "assistants" and "gptPlugins"). i've included/excluded "actions" in theyaml
file, as well as mcpServers (i have one LightRAG MCP server i can't get to work, so without that i have nothing to include here so it's currently commented out).i did run the agent-migrate script, but this need was not apparent until i opened up docker desktop and went into the container logs (should be an alert in the UI or something?)
with
docker compose up -d
i see some interesting stuff in the logs, searched all over here but can't find clues as to what's not up-to-date:yaml.interface
: everything's true (including the use marketplace) except the things i don't have keys or configs for (runCode and presets are false)so something i pulled didn't get the memo about 1.2.9?
next up in the logs is the Tools:
yaml.includedTools
commented out, or including the list of goodies as documented (grab the names from the js files linked in docs)yaml.agents.capabilities
includes "tools"in the chat interface:
in the agent builder,
/query
API as an action, instead of trying to force it to work as MCP. works well! very handy that multiple parallel actions can be made!some other log suspects:
in today's error log:
^ i don't have a custom endpoint defined, so that's an odd error. also, not sure why it's not able to calculate a timestamp?
in the search log:
^ perhaps this is related to the temporary chat and its time-telling error? or maybe reloading the page after restarting, when i had a temp chat?
compose-override
only has theyaml
setting; everything else is default.in short:
how can i ensure the "actions" feature works in all agents, not just my 2 existing/migrated tests?EDIT: this appears to be a feature (must save agent first, then add actions); would be nice to have a little 'i' tooltip about this in the UI. also, would be nice to give each 'action' a name, as the resulting button/item is just named for its host (in my case i'll end up with a bunch of "host.docker.internal" items)Beta Was this translation helpful? Give feedback.
All reactions