Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unable to retrieve agent metadata using the Agent pseudo metadata type

Open
#3,405 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js
Domain
api, cli

Research direction

Start by reproducing the failure with sf project retrieve start --metadata "Agent:CR_Agent" in a fresh project and review the deploy-retrieve plugin's metadata retrieval entry point. Compare the Agent pseudo metadata type with the linked Agent metadata documentation and the reported SOAP API warnings. Done means an Employee Agent can be retrieved into the local project without the EPIPE failure.

Written by the indexing model from the issue text.

Description

area:afdx owned by another team validated
Summary

I'm trying to retrieve agent metadata via `sf project retrieve start --metadata "Agent:<Agent_Name>" but nothing is being retrieved. Instead I'm seeing an EPIPE error.

Steps To Reproduce
  1. Create a new Employee Agent
  2. Try to retrieve this agent in a fresh sf project from the cli.
Expected result

I'm expecting to have the agent metadata described in https://developer.salesforce.com/docs/einstein/genai/references/agents-metadata-tooling?utm_source=chatgpt.com retrieved to my local project.

Actual result

This is the output I'm seeing:

 ~/C/sfdc on develop ⨯ sf project retrieve start --metadata "Agent:CR_Agent"                                                                                                                                                                                                                                                                                              09:07:17

 ────────────── Retrieving Metadata ──────────────

 Retrieving v64.0 metadata from [email protected] using the v65.0 SOAP API

 ✔ Preparing retrieve request 8ms
 ✘ Sending request to org 6m 6.77s
 ◼ Waiting for the org to respond
 ◼ Done

 Status: ✘
 Elapsed Time: 6m 6.78s

Error (EPIPE): request to https://x.sandbox.my.salesforce.com/services/Soap/m/65.0 failed, reason: write EPIPE


Warning: Unable to find type MktDataConnectionParam in registry
Warning: Unable to find type MktDataConnectionParam in registry
Warning: Unable to find type PolicyRuleDefinitionSet in registry
Warning: Unable to find type PolicyRuleDefinition in registry
Warning: Unable to find type MktDataConnectionParam in registry
Warning: Unable to find type MktDataConnectionParam in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
Warning: Unable to find type ExternalDataTranField in registry
⋊> ~/C/sfdc on develop ⨯           
System Information
CLI:
@salesforce/cli/2.106.6 darwin-arm64 node-v22.19.0

Plugin Version:
@oclif/plugin-autocomplete 3.2.34 (core)
@oclif/plugin-commands 4.1.32 (core)
@oclif/plugin-help 6.2.32 (core)
@oclif/plugin-not-found 3.2.67 (core)
@oclif/plugin-plugins 5.4.46 (core)
@oclif/plugin-search 1.2.28 (core)
@oclif/plugin-update 4.7.4 (core)
@oclif/plugin-version 2.2.32 (core)
@oclif/plugin-warn-if-update-available 3.1.46 (core)
@oclif/plugin-which 3.2.39 (core)
@salesforce/cli 2.106.6 (core)
@salesforce/lwc-dev-server 2.11.0 (link) /opt/homebrew/lib/node_modules/@salesforce/lwc-dev-server
agent 1.24.13 (user)
apex 3.6.19 (core)
api 1.3.3 (core)
auth 3.9.4 (core)
code-analyzer 5.4.0 (user)
data 4.0.55 (core)
deploy-retrieve 3.23.1 (core)
info 3.4.85 (core)
lightning-dev 3.5.1 (user)
limits 3.3.66 (core)
marketplace 1.3.8 (core)
org 5.9.28 (core)
packaging 2.20.1 (core)
schema 3.3.81 (core)
settings 2.4.46 (core)
sobject 1.4.72 (core)
telemetry 3.6.55 (core)
templates 56.3.63 (core)
trust 3.7.113 (core)
user 3.6.38 (core)
@salesforce/sfdx-plugin-lwc-test 1.2.1 (user)
sfdmu 4.38.0 (user)
SF ENV. VARS.
SF_BINPATH,/Users/kevin.do/.local/share/sf/client/bin/sf
SF_AUTOUPDATE_DISABLE,true
SF_DISABLE_AUTOUPDATE,true
SF_UPDATE_INSTRUCTIONS,Use "npm update --global @salesforce/cli" to update npm-based installations.
Windows: false
Shell: zsh
Channel: stable

Diagnostics

✅ pass - salesforcedx plugin isn’t installed
❌ fail - you have at least one linked plugin
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
✅ pass - using latest or latest-rc CLI version
✅ pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
❌ warn - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches default target org max apiVersion
✅ pass - can access: https://test.salesforce.com
✅ pass - can access: https://appexchange.salesforce.com/services/data
✅ pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
❌ fail - [@salesforce/plugin-auth] CLI supports v2 crypto

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.106.6",
  "nodeVersion": "node-v22.19.0",
  "osVersion": "Darwin 24.6.0",
  "rootPath": "/Users/kevin.do/.local/share/sf/client/2.106.6-c2615ca",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.34 (core)",
    "@oclif/plugin-commands 4.1.32 (core)",
    "@oclif/plugin-help 6.2.32 (core)",
    "@oclif/plugin-not-found 3.2.67 (core)",
    "@oclif/plugin-plugins 5.4.46 (core)",
    "@oclif/plugin-search 1.2.28 (core)",
    "@oclif/plugin-update 4.7.4 (core)",
    "@oclif/plugin-version 2.2.32 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.46 (core)",
    "@oclif/plugin-which 3.2.39 (core)",
    "@salesforce/cli 2.106.6 (core)",
    "@salesforce/lwc-dev-server 2.11.0 (link) /opt/homebrew/lib/node_modules/@salesforce/lwc-dev-server",
    "agent 1.24.13 (user) published 2 days ago (Mon Sep 22 2025)",
    "apex 3.6.19 (core)",
    "api 1.3.3 (core)",
    "auth 3.9.4 (core)",
    "code-analyzer 5.4.0 (user) published 28 days ago (Tue Aug 26 2025)",
    "data 4.0.55 (core)",
    "deploy-retrieve 3.23.1 (core)",
    "info 3.4.85 (core)",
    "lightning-dev 3.5.1 (user) published 27 days ago (Wed Aug 27 2025)",
    "limits 3.3.66 (core)",
    "marketplace 1.3.8 (core)",
    "org 5.9.28 (core)",
    "packaging 2.20.1 (core)",
    "schema 3.3.81 (core)",
    "settings 2.4.46 (core)",
    "sobject 1.4.72 (core)",
    "telemetry 3.6.55 (core)",
    "templates 56.3.63 (core)",
    "trust 3.7.113 (core)",
    "user 3.6.38 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.2.1 (user) published 354 days ago (Fri Oct 04 2024)",
    "sfdmu 4.38.0 (user) published 269 days ago (Sun Dec 29 2024)"
  ]
}
Dominant language
No language data
Stars
571
Forks
80
Avg merge
5d 22h
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/cli

All issues in forcedotcom/cli

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.