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

Concerns Arise Over OpenClaw's Usability and Economic Viability
OpenClaw has been criticized for its high barriers to entry, prohibitive costs, security issues, and misleading memory capabilities. Alternative solutions like the MemU Bot have been recommended.

Claude Code v2.1.160: Safety Prompts for Shell Config, acceptEdits File Protection, and Dozens of Bug Fixes
Anthropic released Claude Code v2.1.160 with safety prompts before writing to shell startup files and build-tool configs in acceptEdits mode, improved Windows clipboard support, and fixed session history loss.

Claude-Code v2.1.84 adds PowerShell tool, environment variables, and multiple fixes
Claude-Code v2.1.84 introduces a PowerShell tool for Windows as an opt-in preview, adds environment variables for model configuration and streaming timeouts, and includes numerous bug fixes and performance improvements.

OpenClaw users report high API costs from vague prompts, developer advises structured workflows
A Reddit user reports a $300 Anthropic bill from OpenClaw due to vague prompting, with the community noting the orchestrator works best with clear intentions and structured workflows rather than acting as a 'genie' for wishful thinking.