The Agno CLI command agno connect adds your AgentOS to local MCP clients by editing their config files, and it now uses UTF-8 for every one of them, Codex's TOML config included. It used the operating system's default encoding for those files. On a system whose default isn't UTF-8, such as many Windows setups, a config with non-ASCII text could fail to read or end up in the wrong encoding.
Writes are still atomic and keep the file's permissions.
Learn more about connecting your clients in the documentation.
Frequently asked questions
agno connect used the operating system's default encoding, and many Windows setups don't default to UTF-8. A config with non-ASCII text could fail to read or be written in the wrong encoding. agno connect now reads and writes client configs as UTF-8.
Yes. agno connect still writes client configs atomically and keeps the file's permissions, including for Codex's TOML config.
