Scout sub-agent not appearing in @ autocomplete on Desktop v1.15.4

[John-Brother]

Question

Description

The Scout sub-agent is documented as a built-in sub-agent but does not appear in the @ autocomplete menu on OpenCode Desktop v1.15.4 (Windows).

Steps to Reproduce

1. Open OpenCode Desktop v1.15.4 on Windows
2. Start a new session
3. Type @ in the input box
4. Only explore and general appear in the autocomplete list
5. Typing @scout directly has no effect

Expected Behavior

According to the official documentation, OpenCode has 3 built-in sub-agents:

• General ✅ (appears)
• Explore ✅ (appears)
• Scout ❌ (missing)

Environment

• OS: Windows 10/11
• OpenCode Desktop: v1.15.4
• No custom agent configuration files

Additional Info

• ~/.config/opencode/agents/ directory does not exist (no custom agents)
• No agent-related configuration in opencode.json
• Scout is listed as a built-in agent in docs, not a hidden system agent

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Desktop app: @mention subagent routing not implemented #27311: Desktop app @mention subagent routing not implemented — discusses subagents appearing in the @ autocomplete on Desktop but not working correctly; your issue (scout not appearing at all) may be related to the same underlying Desktop implementation gap

[Hona]

@nexxeln did you remove it?

[John-Brother]

how's going?

[tadurham]

I have the same issue using TUI and Desktop on MacOS. I am able to create other subagents that will populate with an '@'.

[John-Brother]

Update: v1.15.7 still has this issue.

[koyabr]

try set env var OPENCODE_EXPERIMENTAL_SCOUT=1, this works for me.

[gregharvey]

For me it doesn't autocomplete, but it does work:

[Benjoyo]

#30435

But why, it seems very useful?

[rekram1-node]

Automated: closing question issues.

GitHub Issues are for bug reports and feature requests only — questions / support are no longer tracked here.

• For help & questions: https://discord.gg/opencode
• Billing issues with Opencode Go / Zen: help@anoma.ly

If this is a bug or feature request, please open a new issue with the appropriate template.