Skip to content

Conversation

@JannikSt
Copy link
Member

@JannikSt JannikSt commented Jan 21, 2026

Adds support for passing run_config through the CLI via TOML config files.

  • Parses [run_config] section in TOML
  • Passes it to the backend API (admin-only field)
  • Updated config template with example

Note

Introduces advanced run_config support in RL workflows.

  • Parse [run_config] in CLI TOML via new RLConfig.run_config and include example in the generated template
  • Add run_config parameter to RLClient.create_run and include it in the request payload when provided
  • Minor formatting/print cleanups and a small request formatting tweak in get_distributions

Written by Cursor Bugbot for commit 02e1ecd. This will update automatically on new commits. Configure here.

- Add run_config field to RLConfig for TOML parsing
- Add run_config parameter to RLClient.create_run()
- Pass run_config from CLI to API
- Update config template with example
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

payload["max_async_level"] = max_async_level

if run_config:
payload["run_config"] = run_config
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent payload key breaks config naming pattern

Medium Severity

The run_config parameter uses payload["run_config"] as its key, but the established pattern for similar configs uses shortened names without the _config suffix: eval_config"eval", val_config"val", buffer_config"buffer". If the backend API follows this same naming convention, it would expect "run" as the key rather than "run_config", causing the configuration to be silently ignored.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants