@Rivonn@subnetmarco PR by default. it reads your runtime logs + deployed source figures out what broke and opens a fix PR on your repo for you to review and merge like any other
you can opt into auto-merge but only after its reviewers and your required checks pass.
@BoringBiz_@subnetmarco Not our token spend! Half a quadrillion a year is Kong's customers' AI traffic through Kong AI Gateway, which governs and secures it (routing, auth, rate limits, guardrails etc)
Talking to the teams running that volume is how we saw agents stuck on clouds built for websites
@ThePeterMick@subnetmarco depends how you run it
one-off commands → wiped after
sessions → files stick around across commands, and you can suspend + resume with state intact
sessions do have a max lifetime though (up to 8h), so anything long-term goes in storage or postgres
@TTrimoreau@subnetmarco good q. it doesn't skip the human by default
prod error → lavaflow reads your logs + code → finds the root cause → writes a fix → opens a PR
you merge it. or flip on auto-merge and it ships once its reviewers + your CI pass
At Kong we run half a quadrillion AI tokens a year, and I kept seeing agents stuck on clouds built for websites.
So we built a cloud for agents.
Volcano is live today: the self-healing agent cloud. Sandboxes, durable workflows, Postgres, hosting.
At Kong we run half a quadrillion AI tokens a year, and I kept seeing agents stuck on clouds built for websites.
So we built a cloud for agents.
Volcano is live today: the self-healing agent cloud. Sandboxes, durable workflows, Postgres, hosting.