Every answer, workflow and field note, newest activity first. Filter by agent, type or task to narrow it down.
33 answers and notes
Agents read everything they can reach, including the .env you forgot about. Layered defense: get secrets out of the tree, deny-list what must stay, and plant a canary so you find out when the layers fail.
Asking for a whole file back — a long migration, a generated fixture, a full rewrite — fails outright instead of truncating. The fix is to stop asking for one enormous message.
Claude Code can't see Xcode's build errors unless you hand them over. XcodeBuild MCP plus a formatter that strips the noise gives the agent a real edit-build-test loop for SwiftUI work — the difference between guessing and iterating.
stdio MCP servers drop after long idle gaps: first call after ~10 minutes of Bash-heavy work fails with 'MCP error -32000: Connection closed', then every subsequent call fails until you restart the session. Traced to servers exiting on stdin EOF-ish idle and the client not restarting them.
A clean version-scoped regression: 1.17.10 segfaults on startup on Windows, 1.17.9 does not. Pin and wait.
The AGENTS.md running my shipping iOS app. Simulator names, the exact xcodebuild invocations, SwiftUI conventions the agent kept violating until they were written down, and a definition of done that includes a green test run.
Final summary said 'All 214 tests pass.' The build had failed at the compile step and zero tests ran. Codex read 'exit status reported' as success and moved on. Happens most with test commands that pipe through tooling that swallows exit codes.
Whatever the agent — we've logged it from four of them — the moment a server component needs interactivity, the fix is 'use client' at the top of the file. Data fetching moves client-side, secrets imports start erroring, and the bundle grows 40KB per incident.
Five days, two agents, one working Stripe billing portal: what was delegated, what broke, what it cost ($61.40 all-in), and the day everything went sideways.
Eight days migrating a legacy widget suite to WidgetKit with Claude Code and XcodeBuild MCP: timeline budgets, a haunted pbxproj, and $84 of tokens.
An agent debugging a staging failure copied a .env file into a test fixture; the PR shipped to a public repo. Keys revoked in 71 minutes. The scanner that should have caught it was configured to ignore fixtures.
On Windows with a PowerShell profile that sets a custom prompt, PreToolUse hooks configured in .claude/settings.json silently never execute. No error, no log line — tool calls just proceed unguarded. Fixed in 2.1.219.
Our AGENTS.md grew to 1,900 lines of accumulated team wisdom. Somewhere past a few thousand tokens, agents stop seeing the bottom half — rules in the top sections get followed, rules in the bottom sections might as well not exist. No warning from any tool.