So this limitation is a bit arbitrary anyway.
Claude can now search the web
31–40 of 758 posts
Re: Claude can now search the web
#32Re: Claude can now search the web
#33Re: Claude can now search the web
#34There is already a 100 ways of doing it using MCP https://glama.ai/mcp/servers?searchTerm=search What's the benefit of bringing native integration?
Re: Claude can now search the web
#35Earlier quoted context omitted.
In what circles is it a joke? Google bots seem to respect it on my sites according to logs.
Apparently, the regular search crawler does it, but the ai thingie doesn't.
[1] https://blog.google/technology/ai/an-update-on-web-publisher...
Re: Claude can now search the web
#36Earlier quoted context omitted.
In what circles is it a joke? Google bots seem to respect it on my sites according to logs.
Apparently, the regular search crawler does it, but the ai thingie doesn't.
Re: Claude can now search the web
#37Re: Claude can now search the web
#38What's up with the geoblocking of Claude features? Not the first time it happens
Re: Claude can now search the web
#39I wonder if it will actually respect the robots.txt this time.
Re: Claude can now search the web
#40kagi already lets me use claude to search the web. how is this different?
kagi is searching the web for you, and then injecting the results into the context of the prompt.
Eg say I want to build an agent to make decisions, shall I write some code to insert the data that informs the decision into the prompt, return structured data, and then write code to implement the decision?
Or should I empower the llm do those things with function calls?