EZ-B V4 Info icon EZ-B V4 Info — Displays EZ-B v4 internal temperature and battery voltage, shows built-in battery monitor and LiPo protection settings in Connection Control. Try it →
Australia
Asked
1 Participant
Openai Key Sync Issue In Arc

Openai Key Sync Issue In Arc

I have three robots that each use the OpenAI (ChatGPT-5-nano) robot skill and therefore require a unique API key. Recently OpenAI invalidated my old keys, so I created new API keys.

On my laptop I updated the OpenAI robot skill in each ARC project to use the new API keys, then copied those ARC projects to each robot's computer (each robot runs the runtime version of ARC). I expected the new keys to be used on the robots, but each robot returned an error saying the API key was invalid - and the error referenced the old API key.

The only way I could get the new API keys to take effect on the robot computers was to uninstall ARC Runtime and install ARC Pro on the robot, manually enter the new API key in the OpenAI Robot Skill, test it, then uninstall ARC Pro and reinstall ARC Runtime. I had to repeat this process three times (one per robot). I also had to remove an ARC token a couple of times because I am only allowed two tokens.

I’m uncertain why the new API keys, which are set up and working in the ARC projects on my laptop, do not copy across and take effect on the robot computers when I transfer the projects. Has anyone else experienced this behavior with the OpenAI Robot Skill, ARC projects, or ARC Runtime/Pro transitions?


ARC Pro

Upgrade to ARC Pro

Become a Synthiam ARC Pro subscriber to unleash the power of easy and powerful robot programming

#1  

The API key isn't stored in the ARC project. It's saved per-PC (encrypted) in ARC's data folder under OpenAI Dall-e\data.cfg, so copying a project never brings the key with it, and ARC Runtime can't open the config dialog to change it. That's why the robots kept using the old key. Note that all OpenAI skills on one PC share this key file.

Easier workaround: on your laptop, enter Robot 1's key, then copy data.cfg from that folder to the same folder on Robot 1. Repeat for each robot. No ARC Pro reinstall or token juggling needed. We'll look at adding a ControlCommand so the key can be set from a script on ARC Runtime. But note that including an API key in plain text in your project is a huge security risk, and we absolutely do not suggest anyone ever do that. The API Key is encrypted in a per-machine file, so your workaround should honor that process to keep your API key secure.

It is absolutely important that you understand that API keys are like gold to hackers today - once they have access to your API key, they can ring up thousands or hundreds of thousands of dollars in charges before you notice.