Cloud Agent (Desktop Glass): repository / skills autocomplete empty until first message is sent (3.28.7)

[Haris_Grizovic]

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When starting a new Cloud Agent with a configured cloud environment, the / slash menu does not list repository skills (from committed .cursor/skills/) while the composer is still empty (before the first user message is sent).

After sending any first message (even “ok”), the same composer shows the full repository skill list in / autocomplete.

Repo skills are committed; cloud environment build is current (Nov 3, 2026); Customize shows skills locally. VM/backend after first turn is fine — only pre-first-send Desktop autocomplete is broken.

Related (partial overlap, still repro on 3.28.7):

Plugin skills not showing available on cloud agent start conversation

Where does the bug appear (feature/product)? Cursor IDE and Cursor for iOS Describe the Bug I have the pstack plugin installed. But with cloud agents it’s inconsistently available: When starting a new conversation in the Cursor glass desktop app: The skill is not available in the auotcomplete suggested skills (e.g. type /poteto) When typing a follow-up message Cursor glass desktop app: it is available in autocomplete suggested skills When starting a new conversation on the cursor.com agent…

Cursor Cloud Agent Skills

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug If I use the Curser Cloud Agents, I’m missing all the skills that are within the project. They are just not appearing. I have them on the 1st prompt, but as soon as I start the 2nd prompt within the session, they are gone. And I’m talking about those that are already committed to the repository and should be there once checked out. Steps to Reproduce First, start a new Cloud session with an initial prompt. Then, for the 2…

Steps to Reproduce

1. Cursor 3.28.7, macOS 26.6.2, Glass layout, Agents window.
2. Select cloud environment (FE/BE dev; webapp-workspace with .cursor/skills/ + environment.json).
3. Create a new Cloud Agent — do not send a prompt yet.
4. In empty composer, type / and wait for suggestions.
5. Actual: no repository skill suggestions.
6. Send minimal first message (e.g. ok), wait for agent to start.
7. Type / again.
8. Actual: full repo skill list appears. Expected already at step 4 (as on cursor.com/agents).

Expected Behavior

Repository skills appear in / autocomplete before the first message is sent, matching web composer and matching Desktop after the session has started.

Operating System

MacOS

Version Information

Version: 3.28.7
VSCode Version: 1.128.0
Commit: d5c0e77a0214208f36b56d42e8e787de88d02ea4
Layout: glass
Release Track: Stable
macOS 26.6.2 (25G83)
Cloud env FE/BE, active build Nov 3, 2026 ~11:39 AM

For AI issues: which model did you use?

N/A (UI autocomplete / composer hydration, not model-specific)

For AI issues: add Request ID with privacy disabled

Not captured — UI-only repro before first agent turn. Happy to add Request ID / bc- ID if the team needs it.

Additional Information

Skills in git under .cursor/skills/ (canonical); .claude/skills/ symlinks per skill. Customize shows “Dev (FE - BE) - Local” for discovery. Workaround: short first message then /, or start on cursor.com/agents.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Colin]

Hey, thanks for the clear report!

Before your first message there’s no cloud machine yet, so the / menu gets skills straight from your git host. That lookup only checks the first repo in the environment, on its default branch. Once the agent starts, the machine has every repo checked out, which is why the full list shows up after “ok”.

My guess is that webapp-workspace isn’t the first repo in your “Dev (FE - BE)” environment. Can you check the repo order there? It’d also help to know where webapp-workspace is hosted (GitHub or something else).

Also, on cursor.com/agents, do the skills show before the first message with that same environment selected? The web uses the same lookup, so if it really differs there, that’s the part we want to dig into.

[Haris_Grizovic]

Thanks @Colin — checked the environment details.

**Repo order in “Dev (FE - BE)” (Personal):**

1. `gitlab.com/acme-corp/main-app` ← first
2. `gitlab.com/acme-corp/api-gateway`
3. `gitlab.com/acme-corp/auth-service`

**Config file:** `acme-corp/main-app` → `.cursor/environment.json`

So the monorepo that contains `.cursor/skills/` is already the **first** repo — repo order doesn’t explain the empty `/` menu before the first send.

Skills are committed under `.cursor/skills/` on the default branch (real files; per-skill symlinks under `.claude/skills/`). Cloud build was refreshed **Nov 3, 2026**.

**Repro unchanged (Glass Desktop 3.28.7):** new Cloud Agent + this environment, empty composer → `/` shows no repo skills → send “ok” → `/` shows the full list.

**Hosting:** GitLab (not GitHub).

**Web:** I haven’t re-tested `cursor.com/agents` with the same environment in this follow-up; original report was Desktop-only. I can compare and report back if that helps.

Happy to share Request ID / bc- ID if useful.

[Colin]

@Haris_Grizovic

I haven’t re-tested `cursor.com/agents` with the same environment in this follow-up; original report was Desktop-only. I can compare and report back if that helps.

Happy to share Request ID / bc- ID if useful.

it all helps.

[Haris_Grizovic]

It behaves the same like on my Desktop App. No autocompletion for my repo skills. The order is the following.

Thx for the support

[Colin]

Thanks for checking both. That rules out the repo order.

I dug into it more and the real cause is that your repos are on GitLab.

Before the first message there’s no machine yet, so the / menu asks the git host for the skill list. That pre-start lookup currently only works for GitHub-hosted repos. For GitLab it comes back empty, which is why you see the same thing on the desktop app and on cursor.com/agents. Once the agent starts, it reads the skills from the checked-out repo, so they show up from then on.

This is a known gap the team is aware of. In the meantime:

1. Send a short first message, then use / as you’ve been doing.
2. Or type the full skill name in your first message yourself (for example /your-skill-name followed by the task). The menu won’t suggest it, but the agent should still pick the skill up from the repo once it starts.