Download a managed agent’s saved configuration as JSON, from the dashboard or the API.
You can download a managed agent’s saved configuration as a JSON file, from the
dashboard or the API. The file holds the agent’s full config, including its name,
prompt, greeting, language, region, models, idle nudges, and tool and MCP
references, so you can back it up, review changes, or re-apply it with the API.
It reflects the last saved configuration and leaves out secrets and call
credentials.
Open the project, click the ⋯ menu in the top right, and choose
Download configuration. The browser saves the agent’s config as
agent-<id>.json.The file always holds the last saved configuration, so save any pending
edits first if you want them included.
The project's ⋯ menu, with Download configuration.
Request the agent’s config. The response is the JSON file, named from the
Content-Disposition header.
-OJ saves the file with the server’s name (agent-<id>.json). Drop it to
print the JSON to the terminal instead.To download a specific saved version, add its number:
The download is the agent’s full configuration, the same object the API returns
when you create or read an agent:
its name, system_prompt, greeting, language, region, the models block,
idle_nudges, and its tool and MCP references.It leaves out secret values, such as tool or webhook secrets, and the temporary
credentials from a call or test session. Those stay server-side.
Use a downloaded file as the body of a full update, then send it back with PUT
to replace the agent’s configuration in one request. See
Update an agent.
Download configuration is available for agents that run on SLNG. A project that
improves an agent in your own code has no managed agent to download.
