{"slug": "coding-agents-can-write-your-integration-they-can-t-run-it", "title": "Coding agents can write your integration. They can't run it.", "summary": "Digibee reports that while its team uses Claude Code for development, coding agents consistently fail at enterprise integration tasks due to three key limitations: they start from scratch each time instead of using pre-built connectors, they produce code without necessary infrastructure like retry logic and monitoring, and they lack ownership of the generated artifacts. The company argues that the productivity gains from AI coding tools in greenfield development do not transfer to environments requiring operational continuity, governance, and audit trails.", "body_md": "Digibee opens with a clear disclaimer: every team there uses Claude Code. This isn't a take from people who skipped the AI tooling revolution. It's an observation from people who shipped with it and ran into the same wall, repeatedly.\n\nThat wall is enterprise integration.\n\n\"Enterprise integration isn't a greenfield challenge. It's a completely different category of work, with completely different failure modes that coding agents weren't designed for.\"\n\nThey're useful for integration work under a narrow set of conditions: well-documented APIs, one-time tasks, low stakes, nothing in production at risk. A quick script to pull from a public endpoint? Great. A throwaway ETL job? Perfect.\n\nThe problems start the moment an integration needs to be recurring, reliable, auditable, and maintained by someone other than the person who prompted it.\n\n**1. They start from scratch every time.** Pre-built connectors for enterprise systems like SAP, Salesforce, or NetSuite encode years of accumulated knowledge — how sequencing works, how idempotency is handled, where the quirks are. A coding agent reasons through all of that fresh on every run. It also suffers from the \"lost in the middle\" effect: when documentation gets long, LLMs drop content from the middle of their context window and fall back on training data. The more obscure the API, the more likely the generated code quietly fails under real load — not on deployment, but six months later when the CIO notices corrupted records.\n\n**2. They produce code, not infrastructure.** Integrations need retry logic, failure recovery, credential management, audit trails, monitoring, and alerting. Coding agents produce none of that. You can prompt your way around it piecemeal — but now you're maintaining the integration *and* five hand-rolled infrastructure components. An agent optimised to iterate fast isn't optimised to fail safely. In production, a bad write means unprocessed payments or orders that don't ship.\n\n**3. They don't own what they build.** When the person who prompted an integration goes on holiday, so does the rationale behind every design decision. There's no structured artifact — no spec, no mapping document, no record of edge cases. API keys and OAuth tokens need scoping, storage, and rotation; the generated code has no opinion on any of it. Scale this to a hundred bespoke integrations across an enterprise and you have a hundred codebases to secure, update, and reason about independently.\n\nIt's worth noting Digibee makes an integration platform, so they have obvious skin in this game. But the technical critique holds up on its own terms.\n\nClaude skills can improve things at the margins — embedding documented edge cases and validated patterns does help. But a skill is a knowledge layer. It can tell an agent how to respond to a failure; it can't detect one at runtime. It can't maintain a connector as SAP's idempotency handling changes. It can't alert before reconciliation breaks.\n\nThe real lesson isn't \"don't use coding agents for integration.\" It's that the productivity gains coding agents deliver in greenfield dev don't automatically transfer to environments that require operational continuity, governed credentials, and audit trails. Pointing a coding agent at an enterprise integration problem and expecting the same results is a category error.\n\nThe tools are impressive. The failure modes are real. Know where one ends and the other begins.\n\n*Source: Digibee — Why Claude Code can't handle integrations*\n\n*✏️ Drafted with KewBot (AI), edited and approved by Drew.*", "url": "https://wpnews.pro/news/coding-agents-can-write-your-integration-they-can-t-run-it", "canonical_source": "https://dev.to/thegatewayguy/coding-agents-can-write-your-integration-they-cant-run-it-17k4", "published_at": "2026-07-15 15:48:47+00:00", "updated_at": "2026-07-15 16:10:54.856872+00:00", "lang": "en", "topics": ["artificial-intelligence", "large-language-models", "ai-agents", "developer-tools", "ai-products"], "entities": ["Digibee", "Claude Code", "SAP", "Salesforce", "NetSuite"], "alternates": {"html": "https://wpnews.pro/news/coding-agents-can-write-your-integration-they-can-t-run-it", "markdown": "https://wpnews.pro/news/coding-agents-can-write-your-integration-they-can-t-run-it.md", "text": "https://wpnews.pro/news/coding-agents-can-write-your-integration-they-can-t-run-it.txt", "jsonld": "https://wpnews.pro/news/coding-agents-can-write-your-integration-they-can-t-run-it.jsonld"}}