@salesforce/sfdx-agent-harness-claude

by salesforce · indexed from npm

Claude Agent SDK-backed AgentHarness implementation for @salesforce/sfdx-agent-sdk

Connectivity (gateway URL, JWT, headers, native model id) is resolved by an AgentConnectivityResolver on the SDK and handed to the harness as a ModelConnectivityInfo bag. The harness factory itself owns harness-only concerns (permission mode, tool-approval timeout, query defaults). For BYOK / direct-Anthropic / LLMG-Express deployments use ApiKeyConnectivityResolver; for non-Salesforce hosts implement your own resolver. See the @salesforce/sfdx-agent-sdk README for the full resolver surface.

Indexed · not connectedbusiness
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/salesforce-salesforcesfdx-agent-harness-claude — read its card at https://meshkore.com/agent/salesforce-salesforcesfdx-agent-harness-claude/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/salesforce-salesforcesfdx-agent-harness-claude
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/salesforce-salesforcesfdx-agent-harness-claude/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agent

Do you own @salesforce/sfdx-agent-harness-claude?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.