chaitin / chaitin/MonkeyCode

Pro subscriber lost project "APP DE CARROSSEL" — workspace deleted and "Insufficient credits" error

Open
#1,297 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4.7k
Forks
719
Avg merge
4h 30m
Merged PRs (30d)
83

Description

I am a Pro subscriber (Rodrigo Baladan), UID 682c86da-083e-4abd-a3e5-f3445c68a6d8.

Task: "APP DE CARROSSEL" / "APLICATIVO DE CARROSSEL", created 24/08/2026 19:32:37, model basic/deepseek, 113.1M tokens used.

Problems:

The task ended and cannot be resumed ("Task ended"). The message input box is gone.
The "Files" tab is EMPTY. My source code is inaccessible.
The last execution failed with the exact error: [EXECUTION_FAILED] task execution failed: Payment Required: Insufficient credits, request failed
The project contained at least: server.js, carousel.js, /api/carousel, /api/render-slide (titleFont/bodyFont), background removal (rembg), zip extraction, and fonts Poppins, Montserrat, Open Sans, Oswald, Anton, Roboto Slab, Playfair.

Important context: NEW tasks run normally now, so my Pro subscription/credits are active. The "Insufficient credits" error appears to be specific to this task after it exceeded the token/context limit (113.1M tokens).

Requests:

Restore the workspace/snapshot/volume of task "APP DE CARROSSEL" and tell me how to download my source files.
Or re-activate that task environment so I can continue the app.
Confirm whether a snapshot of the task volume still exists on your side.
Explain the per-task token limit so I can avoid this in the future.
Review my subscription/refund for the lost project if recovery is impossible.
Expected result:

I get my source code back (via restored workspace/snapshot download), or clear confirmation that the volume was permanently deleted. I also want the per-task token limit explained, and a review of my subscription.

Current UID: 682c86da-083e-4abd-a3e5-f3445c68a6d8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report mentions server.js, carousel.js, /api/carousel, and /api/render-slide, but it does not identify repository files or tests for workspace recovery. Start by tracing the task workspace/volume lifecycle and the reported Payment Required: Insufficient credits failure; done means restoring or clearly confirming deletion, with the source download path and per-task limit explained.

Written by the indexing model from the issue text.

Assessment

Domain
backend, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.