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

Research on AI Agent Consistency: Key Findings and Practical Takeaways
A study of 3,000 experiments across Claude, GPT-4o, and Llama reveals that consistent agents achieve 80–92% accuracy while inconsistent ones drop to 25–60%, with 69% of divergence occurring at the first tool call.

Claude-Code v2.1.31 Release: Key Updates and Bug Fixes
Claude-Code v2.1.31 has been released with important enhancements including session resume hints, Japanese IME support, and bug fixes for PDF handling and API requests.

Codex Converses: OpenClaw's Successor in AI Automation
Codex can now communicate with itself, heralding a new era in AI-driven automation and effectively replacing OpenClaw, the previous frontrunner.

Local Qwen3.6 27b + Hermes Agent Handles Junior IT Admin Tasks
A 30-year IT veteran reports that Qwen3.6 27b running in Hermes Agent harness completed a task list for a junior-level IT admin in 1.5 hours — including patching, Docker install, and service setup.