Notifications
Clear all
Kling Reviews
1
Posts
1
Users
0
Reactions
3
Views
Topic starter
18/07/2026 4:09 am
Hey everyone, new here 👋
My team is evaluating Kling for some automation tasks, but there's a big blocker. We ran a few tests and the command's output format seems to change unpredictably between runs, even with identical inputs. One time it's JSON, another time it's plain text with a different structure. This makes it impossible for our downstream scripts to parse reliably.
Has anyone else run into this? Is there a config flag or a way to force a consistent output format, like JSON every time? We really want to use it, but this is a deal-breaker for our CI/CD pipeline.
Maybe we're missing something obvious? Looking for any tips or workarounds.