Hey @bryantgillespie thanks for your reply. I think a big part of my issue was the fact that I was unwittingly trying it out literally hours before Sonnet 4.5 came out, so suspect Claude was just being generally flakey on that day!
I was also doing lots of prompts that involved counting things and adding things up, which exposed me to this bug which I understand has now been fixed, plus I was asking it for things related to Directus users (“How many Projects are assigned to John Smith?” etc), and I think it doesn’t seem to have access to query the directus users so it gets stuck and goes a bit mad trying to answer.
Trying it out again right now, I am still seeing it occasionally getting stuck for like 5-10 minutes on some steps of its answers where it has to query the database for further schema info.
It seems to get very confused with upper / lower case of collection names and fields. We have a convention (don’t ask me why) where Collection names are Capitalised, but field names are lower-case, and it often seems to fetch the schema, but then proceed to make follow-up queries against fields with the wrong capitalisation, which return with permission errors because they don’t exist. It usually gets there in the end, but takes ages.