Is this the same as deploying Claude?

No. Deploying Claude is the model decision: API, Bedrock, or Azure, with the controls your security team wants. This is the agent runtime that sits on top of whichever you choose.

Can it write to Salesforce directly?

It can call a scoped tool that writes, through the gateway, with the user’s identity. It does not get a connected app with broad object access.

Which SDK would you pick for our step?

Multi-turn tool use with reflection before a write tends to be Claude. Structured routing tends to be OpenAI. Long cyclic work with approval gates tends to be LangGraph. We classify the step first.

Claude Agent SDK

A code agent that checks its own work before it writes.

The first week is in the org, reading what already exists. The Claude Agent SDK is for the step the org cannot express: read several systems, reason across them, reflect on the structured output, then write once through the gateway. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Get the written assessment

Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks

Runtime plane

What we put in

Multi-turn tool use, then a reflection gate.

The pattern we implement is simple and it is the reason these agents survive review: never write from the first draft.

01
Plan
The agent decides which tools it needs. The tool list is an allow-list, not everything the gateway can reach.
02
Call tools
MCP tools and enterprise APIs through the control plane, with the user’s identity carried forward.
03
Draft, then reflect
The agent evaluates its own structured output against a schema and the business rules before anything is committed.
04
Write once
A single idempotent write on the durable plane, with a rollback path named in the specification.

Claude Agent SDK loop as we build it. The agent plans, calls tools through the gateway, drafts structured output, validates that draft against a schema and the policy, and only then commits a write.

Mermaid source

flowchart TD
  A["Task from a surface or a schedule"] --> B["Plan: which tools, which order"]
  B --> C["Tool calls through the gateway"]
  C --> D["Draft structured output"]
  D --> E["Reflect: schema, totals, policy"]
  E -->|"fails"| B
  E -->|"passes"| F["Write once, idempotently"]
  F --> G["Trace and hand-back to the desk"]

When it earns the seat

Long context, messy inputs, real judgement.

Governed

A code agent is not an exemption.

The same four controls apply as to anything else on the runtime plane.

Questions

What we actually say.

Is this the same as deploying Claude?: No. Deploying Claude is the model decision: API, Bedrock, or Azure, with the controls your security team wants. This is the agent runtime that sits on top of whichever you choose.
Can it write to Salesforce directly?: It can call a scoped tool that writes, through the gateway, with the user’s identity. It does not get a connected app with broad object access.
Which SDK would you pick for our step?: Multi-turn tool use with reflection before a write tends to be Claude. Structured routing tends to be OpenAI. Long cyclic work with approval gates tends to be LangGraph. We classify the step first.

The brief · one email

Send the exception the org keeps escalating.

We will tell you whether a code agent belongs on it, and what it may write.