Skip to content

[BUG] Stop does not work on OpenAI Compatible API Provider #404

Open
1 of 4 issues completed
#1309
#1311
Open
[BUG] Stop does not work on OpenAI Compatible API Provider#404
1 of 4 issues completed
#1309
#1311
Labels
bugSomething isn't working

Description

@Fuzzillogic
Fuzzillogic
opened on May 29, 2026

Problem (one or two sentences)

Stopping an in-progress question or task does not abort the underlying HTTP request to the provider. The provider continues processing / generating tokens, invisible to the user.

This bug was already reported on Roo code: RooCodeInc/Roo-Code#10779. It still is present in Zoo code 3.56.0.

Context (who is affected and when)

OpenAI API users. I use llama.cpp on a iGPU as local solution (a propos, dedicated support for llama.cpp would be welcome at some point) which now continues its lengthy process even though I hit the stop button in Zoo.

Reproduction steps

  1. Configure OpenAI API compatible provider, e.g. local llama.cpp setup
  2. Give Zoo a prompt
  3. Hit the stop button.

Expected result

Underlying HTTP request is immediatly aborted

Actual result

Underlying HTTP request continues until the end, consuming precious resources, while of no benefit to the user.

Variations tried (optional)

No response

App Version

3.56.0

API Provider (optional)

OpenAI Compatible

Model Used (optional)

N/A

Zoo Code Task Links (optional)

No response

Relevant logs or errors (optional)

If I quit VS Code, the (stopped, but continuing) request is immediately terminated, as is shown in the log of llama.cpp:


1332.16.787.326 W srv          stop: cancel task, id_task = 153
1332.20.921.482 I slot      release: id  0 | task 153 | stop processing: n_tokens = 4096, truncated = 0
1332.20.921.542 I srv  update_slots: all slots are idle

Activity

  1. Fuzzillogic
    added
    bugSomething isn't working
    on May 29, 2026

  2. proyectoauraorg commented on Jun 1, 2026

    @proyectoauraorg
    proyectoauraorg
    on Jun 1, 2026
    Contributor

    Claiming.

    I've identified the root cause: the and do not create an or pass an abort signal to the underlying OpenAI SDK / AI SDK requests. When the user hits Stop, the Task-level breaks out of the stream loop, but the HTTP request continues running server-side until it finishes naturally.

    In contrast, and both correctly create an and pass to their API calls.

    Fix plan:

    1. Add to both and
    2. Create the controller in / , pass to the SDK calls
    3. Check in the stream iteration loop
    4. Add abort support
    5. Regression tests

    Will follow up with a PR shortly.

  3. easonLiangWorldedtech
    added 11 commits that reference this issue on Jun 1, 2026

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    8783455

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    161c06a

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    d03f46c

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    1c0b6ed

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    50500de

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    299c474

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    d1a3c41

    fix(api): pass abortSignal to streamText() for OpenAI Compatible prov…

    55673a2

    fix(api): pass abortSignal to streaming API calls for all providers (Z…

    ee47fbb

    fix(tests): remove unused createMockStream helpers from abort signal …

    4e0b0e7

    feat(api): pass abortSignal to streaming API calls for all providers (Z…

    c52904d
  4. edelauna
    added sub-issues on Jun 14, 2026

  5. 175 remaining items

  6. HappyLiang12
    added 7 commits that reference this issue on Jun 22, 2026

    ✅ test: close final coverage gap (Zoo-Code-Org#404)

    dba465d

    🐛 fix(providers): fix prefer-const lint warnings after rebase (Zoo-Co…

    c7605b5

    🐛 fix(test): add missing signal assertion in unbound completePrompt (Z…

    db8c76c

    🐛 fix(test): update opencode-go spec assertions for upstream provider…

    ad65bb1

    🐛 fix(e2e): update glm-5-turbo max_tokens assertion (Zoo-Code-Org#404)

    1a8598f

    🐛 fix(providers): clean up abort listeners to prevent MaxListenersExc…

    893bf2a

    🐛 fix(e2e): fix zai fetch interceptor request capture and timing (Zoo…

    5538078
  7. edelauna
    added 3 commits that reference this issue on Jun 23, 2026

    🐛 fix(e2e): update glm-5-turbo max_tokens assertion (Zoo-Code-Org#404)

    8bf7a86

    🐛 fix(providers): clean up abort listeners to prevent MaxListenersExc…

    77d6575

    🐛 fix(e2e): fix zai fetch interceptor request capture and timing (Zoo…

    2418405
  8. ivanarifin
    added a commit that references this issue on Jun 23, 2026

    🐛 test(mcp): fix McpHub Windows command wrapping test ordering (Zoo-C…

    e8acc6a
  9. easonLiangWorldedtech
    added a commit that references this issue on Sep 6, 2026

    feat(api): abort signal support for openrouter (completePrompt + crea…

    470c453
  10. easonLiangWorldedtech
    added a commit that references this issue on Sep 16, 2026

    feat(api): abort signal support for opencode-go

    8bc6366
  11. myk1yt
    added a commit that references this issue on Oct 3, 2026

    feat(api): shared abort-signal cancellation-scope helpers (Zoo-Code-O…

    05d683a

  12. EuphoricPenguin commented on Oct 5, 2026

    @EuphoricPenguin
    EuphoricPenguin
    on Oct 5, 2026

    #1651 was supposed to fix this issue, but unless it isn't on the prerelease version of Zoo Code yet, this is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions