I know that the use-case that I mentioned as well as many of the agentive aspects can be achieved using code.
But I have to admit that using the UI and easily create GPTs, whether using them just as templates/personas or full-featured with actions/plugins, makes the use-case much easier, faster, and sharable. I can just @ at specific GPT to do something.
Take the use-case that Simon mentions in his blog post, Dejargonizer, I can have a research GPT that helps with reviewin papers and I can @Dejargonizer to quickly explain a specific term, before resuming the discussion with the research GPT.
Maybe this would require additional research, but I think having a single GPT with access to all tools might be slower and less optimal, especially if the user knows exactly what they need for a given task and can reach for that quickly.
One additional feature that I would like to see: interacting with 2 or more GPTs at the same time where they could perform different tasks based on their specific expertise and capabilities either in parallel or even sequentially as long as the replies/context of the discussion is accessible for further interactions, similar to what can be achieved with the assistants API.
> The default ChatGPT 4 UI has been updated: where previously you had to pick between GPT-4, Code Interpreter, Browse and DALL-E 3 modes, it now defaults to having access to all three.
...
So I built Just GPT-4, which simply turns all three modes off, giving me a way to use ChatGPT that’s closer to the original experience.
Isn't that what they have already built-in called "ChatGPT classic". The description litteraly says "The latest version of GPT-4 with no additional capabilities"
Usually for asking questions about specific details, people are using RAG (Retrieval Augmented Generation) to ground the information and provide enough context for the llm to return the correct answers.
This means additional engineering plumbing and very specific context to query information from.
I think the chat interface is a bit restrictive when it comes to multimodal models.
A much cleaner interface would be an "AI notebook" where the user can move, compare, rerun blocks.
Also sharing, versioning and collaborating with others on notebooks is more straightforward.
A lot of teams use additional services from Github besides pushing code. They run their CI system using actions (including building docker images for prod), they keep knowledge/metadata on issues, PRs, comments, discussions, Kanban/project management, ...
We entered the machinable culture. We spent many years trying to make the machine mimic humans, now humans are mimicking the machine :)