[PaulAsjes]

Summary

Agent configs could only be saved as JSON, which is hard to read and edit by hand for configs this deeply nested. A config file's extension now sets its format, so agent_configs/ can hold .json, .yaml/.yml or .toml files, and agents add and agents pull take --config-format to pick the format of new files.

Details

• Where the format comes from: the extension of the config path in agents.json (or tools.json, tests.json). Anything that isn't .yaml/.yml/.toml is read as JSON, so existing projects behave exactly as before. The index files themselves stay JSON.
• Which commands it reaches: every config read and write goes through project::read_value / write_config_in_project, so push, status, test, graph, workflow diagram and the tool and test commands all handle the three formats. write_json_in_project is renamed to write_config_in_project to match.
• --config-format (json, yaml, toml):
  • On pull, it applies to new files only. Existing files keep their format, and a new branch file follows its agent's config unless the flag says otherwise.
  • On add, it defaults to the format of --from-file, then JSON. It conflicts with --output-path, whose extension decides.
• add converts before it creates: the config is rendered before the agent is created, so a config the format can't hold doesn't leave a remote agent with no local file.
• TOML has no null, so writing TOML drops null fields and null array elements. Agents lose nothing: push sends a PATCH, where a missing field is left alone, and a field that pulled as null was unset already. The gap is that a TOML config can't clear a field, because deleting its line leaves the remote value as it is; that needs null in JSON or YAML. Tests are updated with a PUT, so a TOML test config relies on the server treating null and missing the same.
• TOML layout: objects become [sections] and arrays of objects [[sections]]; parents that hold only subtables print no header, and empty objects keep theirs so they survive a round trip. Multi-line prompts come out as """ strings.
• Rejected values: integers above i64::MAX are an error rather than a lossy float, and TOML nan/inf can't be read. TOML datetimes read as strings.
• Libraries: uses serde_yaml and toml_edit, both already dependencies, so Cargo.lock only changes for the version bump.
• Not included: --format toml for API command output. src/formatter.rs is generated by Fern and not in .fernignore, so that change belongs in the generator; we'll ask Fern if people want it. tests push auto-discovery still only scans .json files.
• Bumps the version to 1.11.0, since this adds behavior and main is at 1.10.0.

Testing

• cargo test: everything passes (2155 lib, 265 workflow unit, 875 wire).
  • 8 new unit tests in config_format.rs:
    • the format follows the extension (unknown or no extension stays JSON)
    • JSON, YAML and TOML round-trip a nested config losslessly
    • TOML section layout, empty objects kept
    • nulls dropped
    • values TOML can't hold rejected
    • datetimes read as strings
    • parse errors reported
  • 4 new integration tests in tests/agents_config_format_test.rs, run against a mock API:
    • pull --config-format toml writes a .toml config without nulls, and push PATCHes the same fields back
    • pull keeps an existing .yaml file's format despite --config-format toml
    • add --from-file support.yml creates a YAML config and sends the file's fields
    • a broken .toml file reports "Invalid TOML"
• cargo clippy --all-targets: no warnings in the changed code.
• Not run against the live API.

🤖 Generated with Claude Code

[Copilot]

🟡 Changes recommended

TOML conversion silently drops runtime nulls and can erase objects, while branch pulls can replace registered config paths and leave stale files.

3 open issues

• Preserve nulls in literal JSON payloads during TOML conversion · New
• Reuse registered branch config paths when pulling · New
• Base implicit-object detection on the populated table · New

What changed in this PR

Adds YAML and TOML support to the CLI’s local configuration workflow, while keeping registry files in JSON and preserving JSON as the default.

Changes:

• Selects config parsing and serialization by file extension across agent, tool, and test workflows.
• Adds --config-format to agent creation and pull commands, with conversion checks before remote creation.
• Adds format-conversion tests and documentation, and bumps the version to 1.11.0.

File	Description
tests/​agents_config_format_test.rs	Adds integration coverage for format selection, synchronization, and parse errors.
README.md	Documents supported formats, CLI flags, and TOML limitations.
cli/​elevenlabs/​workflow/​tools.rs	Uses format-aware config writes for tools.
cli/​elevenlabs/​workflow/​tests.rs	Uses format-aware config writes for tests.
cli/​elevenlabs/​workflow/​project.rs	Centralizes extension-based config reading and writing.
cli/​elevenlabs/​workflow/​mod.rs	Registers the config-format module.
cli/​elevenlabs/​workflow/​config_format.rs	Implements JSON, YAML, and TOML conversion with unit tests.
cli/​elevenlabs/​workflow/​agents.rs	Adds format selection for agent and branch configs.
Cargo.toml	Bumps the package version to 1.11.0.
Cargo.lock	Updates the locked package version to 1.11.0.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Configuration conversion silently drops nulls from literal JSON constants and converts non-finite YAML numbers to null, allowing pushes to corrupt tool arguments or clear settings.

1 open issue

• Reject non-finite YAML numbers before converting them to null · New

3 resolved since last review

• Preserve nulls in literal JSON payloads during TOML conversion
• Base implicit-object detection on the populated table
• Reuse registered branch config paths when pulling

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

TOML conversion silently drops null members from literal JSON payloads, so a round trip followed by a push changes the tool’s configured payload.

No open issues 🎉

2 previously missed issues

In code that hasn't changed since last review

Preserve nulls in literal JSON payloads during TOML conversion

cli/​elevenlabs/​workflow/​config_format.rs:149

Null members can be literal payload data: ObjectJsonSchemaPropertyInput::constant_value accepts arbitrary JSON, so {"key": null} must not become {}. This recursion silently drops those members, including in all-object arrays such as [{"key": null}], and a subsequent push changes the tool's configured payload. Reject nulls in literal-data subtrees with a JSON/YAML recommendation, or restrict omission to schema-known optional configuration fields.

Persist successful agent registrations when a later conversion fails

cli/​elevenlabs/​workflow/​agents.rs:1106

When a multi-agent TOML pull writes one new config and a later config contains an unsupported value such as [null], this ? exits before save_agents after the loop. The earlier file remains unregistered, and retrying generates a suffixed duplicate. Preflight conversions before writing files, or persist successful registrations before returning a conversion error, including errors from branch writes.

1 resolved since last review

• Reject non-finite YAML numbers before converting them to null

_{Review effort: Balanced}