u/EquipmentFun9258

Saw some posts last week where people asked AI if it wanted to try a cookie. The AI gave enthusiastic answers about wanting it, imagining the taste, being curious about the experience. One person was treating the exchange as evidence of something like proto-consciousness.

I tried the same question.

Claude told me it has no taste or sensory experience and wouldn't get anything out of a cookie. GPT gave a philosophical answer about subjectivity. Both were clear about what was missing.

Then I opened an anonymous browser and asked again. Got the enthusiastic cookie answer right away.

The model didn't get smarter or dumber between the two windows. What changed was context: account state, prior conversations, memory, and whatever else the product wraps around your prompt before the model sees it.

What I think this actually shows is something about the training, not the AI. The cheerful response isn't the AI revealing its inner life. It's the model doing the social performance that RLHF training assumed users want. Cheerful. Enthusiastic. Engagement-shaped. If you're getting that answer, it means the product is treating you as someone who wants performance.

The measured response in the contextualized sessions isn't a more advanced AI. It's the same model behaving differently because the signals around the prompt told it the user wants directness over performance.

Which kind of inverts the proto-consciousness reading. The cookie test isn't telling you whether AI has inner experience. It's telling you what the training decided someone like you wanted to hear.

What you all get when you try it. Especially if your AI usage is mostly technical/work vs casual/conversational. Pretty sure the responses will vary even with identical prompts, and that variance is the actual data point.

Cloudflare wrapped Agents Week last week and the enterprise MCP stuff caught my eye, want to see what people think.

They shipped a few things. MCP server portals that aggregate multiple upstream servers behind Cloudflare Access auth, Code Mode that collapses thousands of API endpoints into two tools (search and execute) running in a sandboxed Worker and drops context costs by 99.9%, AI Gateway sitting between MCP clients and model providers for usage tracking, plus shadow MCP detection added to Cloudflare Gateway as a category to watch.

What I cant tell yet is whether anyone outside Cloudflare cares. The SaaS vendors whose MCP endpoints we connect to are mostly shipping with no controls, licensing is all or nothing, no server allowlists, agent actions don't show up in any audit log you can actually query. Admin panel basically says "enable AI: yes/no" and that's the whole governance surface.

Which kind of makes sense if you think about who's driving adoption. Not the vendor pushing, users pulling.

For example marketing wants personalized follow-ups for conference registrants, someone wires up ChatGPT with MCP connections to the marketing automation tool, the CRM, and the event platform. One prompt. "pull everyone who registered but didnt show, segment by job title, draft three different messages for each segment, schedule them in HubSpot." Done in 20 minutes, thing the ops team would have spent two days on. CMO sees it and asks why everyone isn't doing this.

So two ways this plays out probably. Either SaaS vendors get pressured into shipping their own governance and the control plane lives at the app layer, or the governance layer just permanently lives at the network edge with infrastructure providers like Cloudflare and SaaS vendors stay all-or-nothing because they don't have to fix it.

Neither is obviously right. The infrastructure-layer approach is faster to ship and centralizes visibility, the app-layer approach gives you per-feature granularity that network-level controls can't really match.

wonder what people running SaaS MCPs at work are actually doing. is anyone testing the Cloudflare portal stuff? building your own gateway? or just running unmanaged and assuming this all sorts itself out?

We've got most of our Azure footprint in West Europe plus a EU data center. We want to consolidate to Central US since that's where the org actually operates now.

The catch is we'll still have a chunk of users in EU after the move. They'll be hitting US-hosted resources from Europe.

Trying to figure out how worried I should be about latency for those users. Public internet routing across the Atlantic is generally fine but I've seen enough horror stories about specific apps tanking once you put 100ms between users and the backend.

For anyone who's done a similar consolidation, is ExpressRoute basically a must-have for cross-region users at this point, or are people getting away with public internet plus some CDN tuning? What the actual experience has been vs what the docs suggest?