403 Forbidden mid-session with no cause given; "continue" retry prompt (CLI 1.86.3, Windows)

Ouverte
  • Quelque chose ne va pas ?
#1,054 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
1-2 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Domaine
cli

Piste de recherche

Start by tracing where the CLI handles HTTP 403 responses and displays the retry prompt; the issue does not name a file or test. Compare this generic response with the model-specific errors mentioned in #930 and #736, then check whether the trace ID or session sequence narrows the cause. Done means the denial reason is surfaced clearly when available and the behavior is covered by a test.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Summary

Command Code stopped mid-session with a bare 403 Forbidden and the prompt Type "continue" to try again. The error gives no cause (auth, plan, quota, permissions), so there is no way to tell what to fix.

⚠ Error: 403 Forbidden

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: ccd031590f1d2d9d981332b79202560a

This is different from #930 and #736. Those return 403 "Authentication failed" for specific models. Here the message is a plain 403 Forbidden with no model-specific text.

Expected Behavior

The request succeeds, or the error states why access was denied.

Actual Behavior

A bare 403 Forbidden with only a trace ID.

Steps to reproduce the issue

Updated from the session transcript (see the comment below for the raw evidence). This is not a one-off: 18 occurrences in one session.

  1. Start a session with a long tool-heavy conversation.
  2. Either send a prompt, or complete a turn that runs tool calls and returns tool results.
  3. The request immediately following that point 403s.

The transcript shows the error arriving at two specific points in a turn's lifecycle and not others:

  • at the same timestamp as an outgoing user prompt, before any assistant turn is produced, or
  • within ~1s of an assistant turn finishing its tool calls and returning tool results.

Turns in between succeed, so it is intermittent rather than a dead credential or a plan limit. A full turn can complete normally and the very next request 403s.

Confirmed: continue clears it and preserves the full conversation context. That held on all 18.

Not confirmed: what the two landing points have in common at the request level. My earlier note here suggested a 60s shell timeout was the trigger; the transcript does not support that, and I have removed it as a lead.

Command Code Version

1.86.3

Operating System

Windows 10.0.26200 (win32)

Terminal/IDE

WezTerm

Shell

MSYS2 UCRT64 bash

Model

xiaomi/mimo-v2.6-pro

Additional context

First seen 2026-10-21T03:01:18Z (11:01 MYT), last seen 2026-10-21T06:18:40Z. 18 injected events across 3h17m, each with its own trace ID, so the trace ID appears to be per-request. Failures cluster: two arrived 17 seconds apart, and six arrived inside the final three minutes.

All 18 trace IDs are in the comment below.

Also seen once in the same session: Error: 400 Request failed at 2026-10-21T23:20:29Z, trace 58ad3b29bc7a, in exactly the same shape (injected into the transcript as a role: user message rather than raised as an assistant or tool error). Possibly the same upstream path returning a different status.

Langage dominant
Aucune donnée de langage
Étoiles
4.2k
Forks
377
Merge moyen
1 j 17 min
PR mergées (30 j)
7

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de CommandCodeAI/command-code

Toutes les issues de CommandCodeAI/command-code

Issues similaires

Plus d'issues CLI

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.