When AI goes south

In poker, "going south" means secretly taking chips off the table in a cash game, which, of course, is frowned upon. I am using "going south" in a similar negative connotation after hitting my first big roadblack with the AI Surfer OS.

It's still beta software, so I know there will be bugs and annoyances. The good news is that the team regularly provides updates for those of us on the maintenance plan. Unfortunately, the solutions to my latest snags will likely take longer to develop.

The first major issue is that my coding agent, Cody, has lost visibility into APIs and tokens for the primary tools he's using, e.g., Vercel and Supabase. Without these connections, Cody is basically dead in the water for prod deployments. Not good. 

The second major issue is conversation corruption, which the built-in repair feature could not fix. This issue affects all the agents and leads to conversations without replies and amnesia. Perhaps this issue is worse because now I have to wonder whether the agents will remember the work we're doing. 

I've submitted the bug reports and have had contact with Zach, the AI Surfer OS creator. He assures me they're working on the fixes, and I hope to be back in full action soon.

This is a great reminder to be careful about putting anything mission-critical on a platform that is still a bit shaky.