Not to demerit the recording, but I felt more nostalgic for the last sentence of the article "Sometimes, the internet is good" than for the musics itself.
We all know it... but I think they were very bold in this warning about using your private messages to train public models.
_Your messages with AIs will be used to improve AI at Meta. Don't share information, including sensitive topics, about others or yourself that you don't want the AI to retain and use_
"A watchdog kernel thread monitors RAM and NVMe pressure and signals userspace before things get dangerous." - which kind of danger this type of solution can have?
I think that there may be another solution for this, that is the LLM write a valid code that calls the MCP's as functions. See it like a Python script, where each MCP is mapped to a function. A simple example:
Unfortunately, it uses Miniconda, which does not allow usage in companies with more than 200 employees. I think it conflicts with AGPL license. I created a PR to fix that.
Until GPT-4.5, GPT-4 32K was certainly the most heavy model available at OpenAI. I can imagine the dilemma between to keep it running or stop it to free GPU for training new models. This time, OpenAI was clear whether to continue serving it in the API long-term.
The file I mentioned is just the begining... there is a folder full of .dll files, renamed to .pyd.
I understand that this is the proprietary part, that limits usage for 30 minutes, but I think it is too closed for a MIT license.
Thanks for sharing this! But I have some doubts about hidden installation procedures. It imports all functions from one_click (from one_click import *), which points to a compiled file. It then runs functions like install_webui and install_extra_packages. At least suspicious.