Manually stopping a running Quest does not correctly stop the underlying agent — leading to double credit consumption

Issue Description

Manually stopping a running Quest does not correctly stop the underlying agent — leading to double credit consumption

On September 3, 2026 (UTC+8), I created a Quest to analyze documents from multiple exchanges — the task involved reading a large volume of documents, summarizing and analyzing them, and finally generating wikis. This is a long-running, credit-intensive task.

Here is the timeline:

Time (UTC+8) Action
~10:16, Sept 3 Started the Quest.
~10:19, Sept 3 Stopped the Quest manually to adjust some settings, then typed “继续” to resume it.
Sept 3 (afternoon) Monitored the resumed Quest. Everything seemed fine, except sub-agents kept encountering file write conflicts.
~17:47, Sept 3 Stopped the Quest again to prevent excessive credit consumption.

On September 4, I attempted to use Qoder and was informed that all of my credits had been exhausted. I checked my credit usage and found two suspicious high-consumption records:

  • 4,989.39 credits — billed from 10:19 to 17:46, Sept 3
  • 14,155.77 credits — billed from 10:16, Sept 3 to 04:55, Sept 4

I have no other tasks that would account for this level of consumption.

I suspect that when I manually stopped the Quest at ~10:16 on Sept 3, the underlying agent was not actually terminated. This “orphaned” agent continued running silently from 10:16, Sept 3 through 04:55, Sept 4 — and likely conflicted with the normally resumed agent (started at ~10:19), which would explain the persistent file write conflicts I observed among sub-agents.

In other words, two agents may have been running simultaneously on the same task:

  1. The resumed agent (10:19 → 17:46, Sept 3) — the one I was actively monitoring.
  2. The orphaned agent (10:16, Sept 3 → 04:55, Sept 4) — the one that was never actually stopped.

Steps to Reproduce

See above.

Expected Behavior

The orphaned agent should stop at 10:16 Sept 3.

Actual Behavior

The orphaned agent never actually stopped. Instead, it kept running until 4:55 Sept 4 which used all my remaining credits.

Screenshots / Screen Recordings

Operating System

Current Qoder Version (Menu → About Qoder → Copy)

Inexperienced tech team. Terrible after-sales support. Unreliable and disappointing product.

Hello!
Regarding the issue you’ve reported, we recommend clicking the “Report Issue” button in the top-right corner of the Qoder interface to submit it. Please also share the generated feedback code with us. Our team will investigate and resolve the matter as soon as possible. Thank you for your support!