Issue-Shorts Cloud Environment Save fails with 400 after Session expired

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cannot save a Cloud Agent Environment for my Issue-Shorts repository.

Setup fails mid-way with unreachable or Session expired, then Save shows Failed to save: 400.

Tried on both mobile and PC. Same result.
ICU-Scheduler Cloud works fine on the same account. Only Issue-Shorts is broken.

Environments was empty with No environments configured after previously archiving or removing the old environment.

Steps to Reproduce

  1. Open Dashboard, then Cloud Agents, then Environments
  2. Click Start Setup or New
  3. Select repository mjisbest588-debug/Issue-Shorts
  4. Click Start Agent
  5. During setup see difficulties reaching execution environment, unreachable, Retry
  6. After Retry see Session expired or Environment expired
  7. UI still shows Environment is ready to be saved
  8. Click Save
  9. Name IssueShorts, also tried Issue-Shorts, Scope Personal
  10. Result Failed to save: 400

Expected Behavior

Environment setup should complete successfully and Save should create a usable Cloud Environment for Issue-Shorts on main.

If setup fails, Save should not offer a broken state, or should show a clear recoverable error instead of 400.

Screenshots / Screen Recordings

3.png
3.png127×277 9.67 KB
4.png
4.png525×343 5.19 KB
2.png
2.png127×277 9.61 KB

Operating System

Windows 10/11

Version Information

Version: 3.15.19 (user setup)
VS Code Extension API: 1.128.0
Commit: de07bee81cefe43461ebf4f40c3d2d78d15052a0
Date: 2026-08-11T05:22:54.627Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.22621

For AI issues: which model did you use?

Auto / default environment setup agent

For AI issues: add Request ID with privacy disabled

bc-e5529597-1392-4ee4-bc55-fe47741597e5
setupSessionId 2ae091ce-8047-46ff-a9a7-7bcc99fc2ebe

Additional Information

Repository mjisbest588-debug/Issue-Shorts
Default branch is currently main
Previously default was cursor/tts-sync-match-41dd then switched back to existing main
Same Save 400 on mobile and PC
Without saved environment, simple Issue-Shorts chats sometimes work
Photo or library related agent runs often hit Agent encountered an error

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

Hey there!

Every setup attempt for Issue-Shorts fails at git checkout because a file or folder in that repo has an oversized name (it starts with 방법: 일회성 workflow_dispatch (기존 GCP_SA_KEY 재사용)…). That exceeds the Linux filename limit, so Cloud Agents can’t check the repo out. ICU-Scheduler works because it doesn’t have that path.

Delete or rename that path on GitHub (web UI is fine even if a local Windows checkout can’t create it), including any other branch agents use, then re-run setup from Dashboard → Cloud Agents → Environments.

Separately, Failed to save: 400 and the Save button staying available after the session ended aren’t intended. That’s an issue we’re tracking.

Let me know how setup goes once that path is gone.