Skip to main content

Override runtime parameters

Agent and Sandbox Jobs accept repeatable --params values:

el job submit --profile org/name@version --params '{"AGENT_NAME":"oracle","AGENT_TIMEOUT_SEC":"600"}'
el job submit --profile org/name@version --params AGENT_NAME=oracle --params AGENT_TIMEOUT_SEC=600

Each value is a strict JSON object or KEY=VALUE. KV splits at the first = and keeps a string; JSON preserves types. Later occurrences override earlier values with the same case insensitive key. Runner defaults < Profile < specification / request overrides < explicit params. Use only parameters declared by the selected Runner. This does not edit the stored Profile or select a different Runner, image, command, execution backend, project or budget. Train/Inference reject this flag.

v2 object parameter values replace the whole value; historical v1 objects merge recursively. Omitted fields persist; null does not delete. Changing only AGENT_NAME to oracle retains model/version fields and may still be rejected. Duplicate JSON keys, invalid/protected names and nonfinite numbers fail before submission.

Do not put credentials in command arguments: shell history and process listings can expose them. SDK equivalents: client.jobs.submit(..., params={...}) and client.jobs.submit_spec(body, params={...}). Requires a client and platform version supporting this interface.