BenderV

Well, I think they should have kept calling it function... ^^'

It feels crazy to me that we are building "tool search" instead of building real tool with interface, state and available actions. Think how would you define a Calculator, a Browser, a Car...?

I think, notably, one of the errors has been to name functions calls "tools"...

Thanks for your answer.

I guess that it's only a matter of finetuning.

LLM have lots of experience with bash so I get they figure out how to work with it. They don't have experience with custom tools you provide it.

And also, LLM "tools" as we know it need better design (to show states, dynamic actions).

Given both, AI with the right tools will outperform AI with generic and uncontrolled tool.

I'm trying to understand what does it got to do with LLM size? Imho, right tools allow small models to perform better than undirected tool like bash to do everything. But I understand that this code is to show people how function calling is just a template for LLM.

Why do humans need a IDE when we could do anything in a shell? Interface give you the informations you need at a given moment and the actions you can take.

Here, the best time is defined as the highest chance of getting "some" visibility. Most posts quickly fade away.

You are right that there is lots of way to measure this but quality comments is way harder to judge and we don't have quantity traffic info.

Hey, Funnily, I had this idea/need recently. Just a message to encourage you in this direction !

My 2 cents, building a tool in this space...

> Do you need an expert to verify if the answer from AI is correct?

If the underling data has a quality issue that is not obvious to a human, the AI will miss it too. Otherwise, the AI will correct it for you. But I would argue that it's highly probable that your expert would have missed it too... So, no, it's not a silver bullet yet, and the AI model often lacks enough context that humans have, and the capacity to take a step back.

> How is it time saved refining prompts instead of SQL?

I wouldn't call that "prompting". It's just a chat. I'm at least ~10x faster (for reasonable complex & interesting queries).

Awesome. Using Vue/Tailwind, I'm definitely interested in this. Maybe you could try to add examples of integrations with others frameworks? I'll play with it and give you my 2 cents.

Hi HN,

Over the past few weeks/months, I’ve been working on Autochat, a lightweight Python library designed to make building AI agents simple and intuitive.

The focus of Autochat is simplicity:

- Extend an AI assistant's functionality by adding Python functions directly, or even class.

- Hide all the complexities/particularities of the providers (openai, anthropic, …)

I’d love your feedback on this. If you’ve got ideas for features, use cases, or critiques, let me know!