Repository navigation
Added
prompts updatenow refuses to overwrite remote prompts that changed after the lastprompts pull(REMOTE_CHANGED). Pass--forceto overwrite;--dry-runreports the conflict asremote_conflict. An agent repointed to a different LLM or conversation flow is reported asREMOTE_CHANGEDwith reasonresource_changed. Directories pulled by older releases fall back to timestamp and version comparison.prompts updatenever modifies a published version. If the agent's latest version is published, it creates a new draft from it and writes there (draft_created,agent_versionin the output;would_create_draftin--dry-run). Previously this failed with Retell's "Cannot update published LLM".- Conflict detection compares a fingerprint of the prompt content (stored as
remote_prompt_hashinmetadata.json), so publishing or creating a draft copy is not reported asREMOTE_CHANGED. - Opt-in live end-to-end test for the prompt workflow (
npm run test:e2e, requiresRETELL_E2E_API_KEY).
Fixed
prompts updateno longer wipes tools, edges, and other settings stored inside Retell LLM states. Local state files only hold the prompt text, so the CLI used to send states with justnameandstate_prompt, and Retell replaced the whole state. It now merges each local state prompt into the current remote state.prompts pull,prompts diff, andprompts updateread the LLM or conversation-flow version the agent is actually pinned to, rather than the latest version of that resource (which can differ when several agents share an LLM).agents publish,agent-publish, andchat-agents publishno longer fail with "Unexpected end of JSON input". Retell returns an empty body labelledapplication/jsonfor publish, which the SDK tried to parse; the publish itself succeeded, but the command reported an error and exited 1. Broken since 2.0.0.prompts pull,prompts diff, andprompts updatehelp and README now describe--output/--sourceas a base directory (<dir>/<agent_id>/), not a.jsonfile.
Published to npm with provenance: https://www.npmjs.com/package/retell-cli/v/2.1.0