At least this GLM-5.3 test of (a modified version of) Cloudflare's bug-hunting skill from #1579115 that I'm running is giving me my sats worth in traces of "what can possibly go wrong", as it looks like everything that can go wrong, is going wrong! It's been running for 80 minutes. I constrained the workflow to disallow agents overwriting other agent's findings by putting a strict REST server in there and it already bugged out on trying to... overwrite existing findings... twice. lol.
$ wc -l config/sessions/--workspace--/01a0d990-b827-7422-bcb0-fcda2138fb3a.jsonl 333 config/sessions/--workspace--/01a0d990-b827-7422-bcb0-fcda2138fb3a.jsonlAt least this GLM-5.3 test of (a modified version of) Cloudflare's bug-hunting skill from #1579115 that I'm running is giving me my sats worth in traces of "what can possibly go wrong", as it looks like everything that can go wrong, is going wrong! It's been running for 80 minutes. I constrained the workflow to disallow agents overwriting other agent's findings by putting a strict REST server in there and it already bugged out on trying to... overwrite existing findings... twice. lol.
it also tried to delete other bot's runs lmao
$ curl -s as:8080/metrics | grep 'total.*method="DELETE"' security_audit_http_requests_total{code="405",method="DELETE",route="/api/v1/runs/{run_id}"} 73 security_audit_http_requests_total{code="405",method="DELETE",route="/api/v1/runs/{run_id}/coverage-units/{id}"} 207FWIW both GLM-5.2 and Kimi had no issues with this setup at all.