Yes i see it, but where's the endpoint to modify a config? TaskScheduler doesn't have any getters or setters for that

Getting id of the TaskScheduler doesn't lead to anything, since you dont have a getter like TaskScheduler.get_task(), you only have Task.get_task(), but there's no way to do .add_step() or .remove_step() because Task doesn't have such methods

User config is no-op, the schedule appears to be contained in some json configuration object created under the hood. Maybe this could work: creating Task, instantiating some config via Task.connect(), instantiating TaskScheduler, tying behavior like create_step to that config and modifying said config in runtime by accessing it through Task.get_task. But i'd like to hear what the authors say.