You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a button in the admin console to cancel all kiloclaw subscriptions so they do not renew #8679
We are EOL'ing KiloClaw in December and we want to start no longer renewing subscriptions. So monthly subs should slowly start to stop and at least no longer be renewed. Can you make a button so that we can press this in the console which then sets all of the active kiloclaw subsriptoins to no longer auto renew?
The issue asks for new operational tooling: a bulk admin-console action that makes all active KiloClaw subscriptions non-renewing ahead of the December EOL. The repository already supports cancelling one subscription at a time through admin.users.cancelKiloClawSubscription, but the requested fleet-wide button/action does not exist, so this is a feature request rather than a bug.
Recommended next step: plan. This is a clear, time-bound operational feature with an existing single-subscription cancellation path and admin UI patterns to reuse. Planning should first settle scope (statuses, plans, org ownership, Stripe vs pure credit), then design an idempotent bulk operation that reconciles each row with Stripe where applicable and records per-subscription audit/error outcomes.
Evidence unavailable: Repository code search: kiloclaw across the pinned tree. Conclusions relying on those sources remain unconfirmed.
Activity
kfab-cloud commentedon Oct 22, 2026
Kfab triage
Provisional classification: feature.
The issue asks for new operational tooling: a bulk admin-console action that makes all active KiloClaw subscriptions non-renewing ahead of the December EOL. The repository already supports cancelling one subscription at a time through admin.users.cancelKiloClawSubscription, but the requested fleet-wide button/action does not exist, so this is a feature request rather than a bug.
Recommended next step: plan. This is a clear, time-bound operational feature with an existing single-subscription cancellation path and admin UI patterns to reuse. Planning should first settle scope (statuses, plans, org ownership, Stripe vs pure credit), then design an idempotent bulk operation that reconciles each row with Stripe where applicable and records per-subscription audit/error outcomes.
Evidence unavailable: Repository code search: kiloclaw across the pinned tree. Conclusions relying on those sources remain unconfirmed.
Sources:
Triage is complete. This recommendation does not start planning or implementation. Findings and hypotheses are available in the Kfab work item.