Two AI Failures in One Demo: Claude Code Fixes Spelling Instead of Schema Error, OpenAI Mangles Custom Field Mapping

During a workshop at Prismatic, an engineer built a B2B integration end-to-end on stream. Two AI tools failed in distinct ways, illustrating that real-world agent behavior is chaotic and non-deterministic.
Claude Code: Solved the Wrong Problem
Claude Code scaffolded a config wizard using JSON Forms in about 30 seconds. The generated wizard looked fine, but a JSON schema validation error surfaced during testing — something about "must not have fewer than one items." When the engineer asked Claude to fix it, the agent spent the next few minutes fixing spelling warnings in the file instead of addressing the schema error. The engineer eventually said "sure hope it's doing more than fixing spelling issues" and bailed, pasting in code from a dry run done the night before.
OpenAI: Garbage on First Attempt at Weird Fields
The integration calls OpenAI at runtime to generate default field mappings between a customer's Salesforce schema and the destination app. For a normal Salesforce contact (email-to-email, company-to-company), it worked fine — "boring" according to the author. But on a custom record type with deliberately weird field names — Group name, Internet address, Physical place, Internet email address — the first call returned garbage. A second try got it all right.
Key Takeaways
- Boring schemas undersell LLMs — they make agent use look like overkill. The weird, custom cases are where it earns its keep, but most demos avoid those for simplicity.
- Live failures are more useful than successes. Anyone who's worked with agents knows they're chaos. The "fixed spelling instead of schema error" behavior is something no docs would predict.
- Different failure shapes: Claude Code had everything it needed but worked on the wrong problem. OpenAI "knew" the answer but didn't surface it the first time. The shape of failure might indicate how to deploy each tool.
The author works at Prismatic but didn't share a link, focusing on the learning opportunity rather than self-promotion.
📖 Read the full source: r/ClaudeAI
👀 See Also

Anthropic DNS Activity Reveals New STT Service, API RC2, and Tunnel Infrastructure
DNS monitoring of Anthropic's subdomains shows new records for a speech-to-text service on a 'Titanium' platform, an API release candidate 2, tunnel infrastructure, and an MCP proxy in staging.

Cerebras releases Step-3.5-Flash-REAP models with 40% memory reduction
Cerebras has released Step-3.5-Flash-REAP models that use REAP (Router-weighted Expert Activation Pruning) to compress 196B parameter models to 121B while maintaining near-identical performance. The models work with vanilla vLLM and are optimized for resource-constrained environments.

NIST Seeks Public Input on AI Agent Security Standards
The National Institute of Standards and Technology has published a Request for Information on security considerations for artificial intelligence agents, with a comment deadline of March 9, 2026. The RFI is open for public comment through the Federal Register.

Anthropic disables Claude Code OAuth tokens for OpenClaw, requiring separate billing
Anthropic is removing the ability to use Claude Code CLI tokens or long-lived OAuth tokens with third-party harnesses like OpenClaw starting April 4. Users will need to enable extra usage billed separately from their subscription.