Allegretto user being charged 0.6% daily for idle Claw Cloud Instance — double billing without consent

Product Feedback
1

Hi team,

I’m an Allegretto plan subscriber and I just discovered something concerning about my quota usage.

The Issue:
My quota is being drained by 0.6% every single day for “Claw - Cloud Instance” — even when I am completely offline and not using Kimi at all.

  • I access Kimi only through the web browser (kimi.com)
  • I do NOT have OpenClaw installed on my MacBook
  • I do NOT use any local OpenClaw app or instance
  • I do NOT use the API

What I see every day at 16:00:
A 0.6% quota charge labeled “Claw - Cloud Instance” — like clockwork.

The Math:
0.6% × 30 days = ~18% of my monthly quota burned for zero usage

What changed:
Today when I opened Kimi Claw, I got a popup message stating:

“Kimi Claw now uses your membership quota instead of a separate Kimi Code quota.”

This confirms what I suspected:

  • Previously, Claw was charged from a separate Kimi Code quota
  • Now it’s burning my Allegretto membership quota directly
  • And it’s burning it even when I’m not using Claw at all

I use Kimi Claw occasionally and I value my chat and work history — I don’t want to lose it. But I never signed up for double billing.

This matters because:

  • That quota is what I need for Kimi agent swarming and actual usage
  • I’m being charged for infrastructure I can’t pause, shut down, or control
  • There’s no option to start/stop the instance manually when I actually need it

Charging users for idle server time they can’t control — while also charging a monthly subscription — is not fair.

My Questions:

  1. Why was this migration done without advance warning or consent?
  2. Can the Claw Cloud Instance be paused to stop the daily drain?
  3. Can users manually start/stop the instance when needed?
  4. Can the quota burned during idle time be refunded?

I love Kimi and want to keep using it, but this setup feels unfair. Paying a monthly subscription AND losing ~18% of usable quota to idle infrastructure doesn’t make sense.

I can provide screenshots of my quota usage and the migration popup if needed as proof.

Thanks for looking into this.

2

Dear Kimi support team, its been a week since I exposed this quota usage issue, and still havent received a single reply.

Are we just going to pretend that this issue never happen, despite that its still persisting and its eating up 0.6% of my very much valuable and neede quota every single day??

I would very much appreciate if you would take this case more seriously and respond with some appropriate, quality solution.

Ive been using and paying for Alegretto plan for months now and how all of a sudden moonshoot decided to charge for this kimi code, despite users are not actually using it, is not fair to say the least.

If we pay monthly for x5 quota, we do expect that we can actually use that quota, and not being deducted 20% of it for something that is idling without having an option to turn it off while not having a need of using it.

So please, give us some response on this topic.

with kind regards,
Ted Macnmire

3

Hi there,

Thank you for reaching out, and thank you for the detailed write-up — we genuinely appreciate you taking the time to document this so thoroughly. We understand how frustrating it must be to see your Allegretto quota draining daily for something you aren’t actively using, and we want to address your concerns directly.

Why the migration happened without advance notice

You’re right that the quota model for Kimi Claw changed recently. Previously, Claw ran on a separate “Kimi Code” quota, and now it draws from your main membership quota instead. We should have communicated this transition more clearly before it took effect, and we apologize for the lack of advance warning. That’s on us, and we’re reviewing our notification process to prevent this from happening again.

Why the daily 0.6% charge occurs

The recurring 0.6% daily deduction labeled “Claw - Cloud Instance” is the operational cost of keeping the Claw sandbox environment running — this includes the underlying cloud compute, storage, and environment maintenance that persists even when you are not actively using it. It is not tied to whether you have OpenClaw installed locally or whether you are logged into the web app; as long as the Claw instance exists in your account, the infrastructure remains allocated and incurs this daily cost.

Can the instance be paused or manually started/stopped?

Unfortunately, there is currently no option to pause, suspend, or manually start/stop the Claw Cloud Instance. The only way to stop the daily quota drain is to delete the Claw instance entirely. We recognize this is a significant limitation — charging users for idle infrastructure they cannot control is not ideal, and we are evaluating whether we can introduce a pause/resume feature in the future. For now, however, deletion is the only available path to stop the charges.

What to do if you want to stop the charges

If you decide to delete the Claw instance to halt the daily deductions, we strongly recommend backing up your work first:

  • Open the Claw interface in your browser
  • Review your workspace files
  • Download any important files or chat history you wish to keep

Once you’ve secured your data, you can proceed with deleting the Claw instance, which will immediately stop the daily 0.6% quota charge.

About refunds for idle-time quota usage

We understand your concern about paying for time when you were not actively using the service. At this time, quota that has already been consumed by the running Claw Cloud Instance is not eligible for refund, as it was allocated to active infrastructure costs during that period. That said, we are reviewing cases like yours on an individual basis, and if you’d like us to look into your specific account, we’re happy to do so. Please let us know if you’d like us to escalate this for a manual review.

What happens next

We hear you on the fairness of this setup, and your feedback is already being shared with the product and billing teams. The combination of a monthly subscription plus an uncontrollable daily quota drain is not the experience we want for our users. We are actively exploring:

  • A pause/resume mechanism for Claw Cloud Instances
  • Better upfront controls and visibility into infrastructure charges
  • Clearer communication before any future billing-model changes

We value your loyalty to Kimi, and we’re sorry this experience has fallen short of what you deserve. If you’d like to keep your chat and work history but stop the daily drain for now, please follow the backup steps above before deleting the instance. And if you’d like us to review your account for any possible adjustment, just reply to this email with your account details and we’ll take a closer look.

Thanks again for flagging this — it helps us build a better product.

Best regards,
The Kimi Support Team

Forwarded from my colleague

4

Essentially, Kimi Claw is a runtime (VM) — your files and the runtime are two entirely separate things.

You have two options:

  1. Keep it running — tune the VM to handle daily tasks and workflows automatically.
  2. Delete the instance — back up your data, remove the VM to stop quota drain, and spin up a new one later.

Backups are tied to your membership, not the VM. As long as your subscription is active, your backup files never expire. When you need Claw again, simply create a new instance and restore from backup — your data is preserved, only the runtime is fresh.

image
image1110×1174 127 KB