Command autocomplete truncates after ~10 items, hiding built-in commands #3006

Closed
opened 2026-02-16 17:38:13 -05:00 by yindo · 16 comments
Owner

Originally created by @itse4elhaam on GitHub (Nov 20, 2025).

Description

When typing / to trigger command autocomplete, only the first ~10 commands are displayed. If a user has 9+ custom commands defined in .opencode/command/, many built-in commands like /export, /copy, /share, /timeline, /rename, and /thinking become inaccessible through autocomplete.

Steps to Reproduce

  1. Create 9 or more custom commands in .opencode/command/ directory (e.g., commit.md, test.md, study.md, etc.)
  2. Launch OpenCode in a project
  3. Type / in the prompt to trigger command autocomplete
  4. Observe that only ~10 commands appear in the dropdown

Expected Behavior

All available commands (both custom and built-in) should be accessible through autocomplete, either by:

  • Increasing the display limit (e.g., 20-30 items)
  • Making the limit configurable via opencode.json
  • Implementing scrollable autocomplete UI

Actual Behavior

Autocomplete displays only the first ~10 commands alphabetically, hiding any commands beyond that limit. This means built-in commands that appear later alphabetically are not shown.

Workaround

Users can type more specific filters (e.g., /exp for /export) to narrow results, but this requires knowing the command exists beforehand.

Environment

  • OpenCode version: 1.0.81
  • OS: Linux
  • Custom commands: 9 defined in .opencode/command/

Suggested Solution

  • Increase the autocomplete limit to 20-30 items, or
  • Make it configurable: "autocomplete": { "limit": 30 } in opencode.json, or
  • Implement a scrollable dropdown to show all available commands
Originally created by @itse4elhaam on GitHub (Nov 20, 2025). ## Description When typing `/` to trigger command autocomplete, only the first ~10 commands are displayed. If a user has 9+ custom commands defined in `.opencode/command/`, many built-in commands like `/export`, `/copy`, `/share`, `/timeline`, `/rename`, and `/thinking` become inaccessible through autocomplete. ## Steps to Reproduce 1. Create 9 or more custom commands in `.opencode/command/` directory (e.g., `commit.md`, `test.md`, `study.md`, etc.) 2. Launch OpenCode in a project 3. Type `/` in the prompt to trigger command autocomplete 4. Observe that only ~10 commands appear in the dropdown ## Expected Behavior All available commands (both custom and built-in) should be accessible through autocomplete, either by: - Increasing the display limit (e.g., 20-30 items) - Making the limit configurable via `opencode.json` - Implementing scrollable autocomplete UI ## Actual Behavior Autocomplete displays only the first ~10 commands alphabetically, hiding any commands beyond that limit. This means built-in commands that appear later alphabetically are not shown. ## Workaround Users can type more specific filters (e.g., `/exp` for `/export`) to narrow results, but this requires knowing the command exists beforehand. ## Environment - OpenCode version: 1.0.81 - OS: Linux - Custom commands: 9 defined in `.opencode/command/` ## Suggested Solution - Increase the autocomplete limit to 20-30 items, or - Make it configurable: `"autocomplete": { "limit": 30 }` in `opencode.json`, or - Implement a scrollable dropdown to show all available commands
yindo added the opentui label 2026-02-16 17:38:13 -05:00
yindo closed this issue 2026-02-16 17:38:13 -05:00
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

most terminal windows are kinda constrained height wise especially if u use integrated terminal in an IDE, we can ofc make it configurable but defaulting to something high would prolly be a bad experience for most people

@rekram1-node commented on GitHub (Nov 20, 2025): most terminal windows are kinda constrained height wise especially if u use integrated terminal in an IDE, we can ofc make it configurable but defaulting to something high would prolly be a bad experience for most people
Author
Owner

@itse4elhaam commented on GitHub (Nov 20, 2025):

most terminal windows are kinda constrained height wise especially if u use integrated terminal in an IDE, we can ofc make it configurable but defaulting to something high would prolly be a bad experience for most people

Makes sense but in this case, it doesn't show up even when searched.

Maybe we can show limited by default, but let the user search all of them (results can be limited as well)

@itse4elhaam commented on GitHub (Nov 20, 2025): > most terminal windows are kinda constrained height wise especially if u use integrated terminal in an IDE, we can ofc make it configurable but defaulting to something high would prolly be a bad experience for most people Makes sense but in this case, it doesn't show up even when **searched**. Maybe we can show limited by default, but let the user search all of them (results can be limited as well)
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

Oh see now that's an issue I didn't see that part

@rekram1-node commented on GitHub (Nov 20, 2025): Oh see now that's an issue I didn't see that part
Author
Owner

@itse4elhaam commented on GitHub (Nov 20, 2025):

Oh see now that's an issue I didn't see that part

Haha, yeah that's the fustrating bit.

@itse4elhaam commented on GitHub (Nov 20, 2025): > Oh see now that's an issue I didn't see that part Haha, yeah that's the fustrating bit.
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

Hm I tested this and I can't replicate it searches just fine for me

@rekram1-node commented on GitHub (Nov 20, 2025): Hm I tested this and I can't replicate it searches just fine for me
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

Do @ completions work for you? Like searching with those? Not for commands but for files

@rekram1-node commented on GitHub (Nov 20, 2025): Do @ completions work for you? Like searching with those? Not for commands but for files
Author
Owner

@itse4elhaam commented on GitHub (Nov 20, 2025):

Do @ completions work for you? Like searching with those? Not for commands but for files

yes they work just fine

Hm I tested this and I can't replicate it searches just fine for me

How many commands do you have defined in the custom config? I have 9 custom commands.

@itse4elhaam commented on GitHub (Nov 20, 2025): > Do @ completions work for you? Like searching with those? Not for commands but for files yes they work just fine > Hm I tested this and I can't replicate it searches just fine for me How many commands do you have defined in the custom config? I have 9 custom commands.
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

@itse4elhaam I made 15

@rekram1-node commented on GitHub (Nov 20, 2025): @itse4elhaam I made 15
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

Can u show me opencode debug config are they all popping up there?

@rekram1-node commented on GitHub (Nov 20, 2025): Can u show me `opencode debug config` are they all popping up there?
Author
Owner

@itse4elhaam commented on GitHub (Nov 20, 2025):

@itse4elhaam I made 15

That's impressive, would love to see your conf.

@itse4elhaam commented on GitHub (Nov 20, 2025): > @itse4elhaam I made 15 That's impressive, would love to see your conf.
Author
Owner

@itse4elhaam commented on GitHub (Nov 20, 2025):

Can u show me opencode debug config are they all popping up there?

On second attempt, it's working as expected on reopening the terminal session, maybe it was a one off issue.

We can close it for now and reopen if it comes up again

@itse4elhaam commented on GitHub (Nov 20, 2025): > Can u show me `opencode debug config` are they all popping up there? On second attempt, it's working as expected on reopening the terminal session, maybe it was a one off issue. We can close it for now and reopen if it comes up again
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

@itse4elhaam no i don't actually use 15 I just made 15 to test this :)

I should make more but rn I mostly use:
https://github.com/sst/opencode/blob/dev/.opencode/command/issues.md

@rekram1-node commented on GitHub (Nov 20, 2025): @itse4elhaam no i don't actually use 15 I just made 15 to test this :) I should make more but rn I mostly use: https://github.com/sst/opencode/blob/dev/.opencode/command/issues.md
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

What commands do you have?

I think I have a /review one too that we should prolly make into opencode automatically

@rekram1-node commented on GitHub (Nov 20, 2025): What commands do you have? I think I have a /review one too that we should prolly make into opencode automatically
Author
Owner

@itse4elhaam commented on GitHub (Nov 20, 2025):

@itse4elhaam no i don't actually use 15 I just made 15 to test this :)

I should make more but rn I mostly use:
https://github.com/sst/opencode/blob/dev/.opencode/command/issues.md

Haha Okay :)

Sure, I'll take a look

@itse4elhaam commented on GitHub (Nov 20, 2025): > @itse4elhaam no i don't actually use 15 I just made 15 to test this :) > > I should make more but rn I mostly use: > https://github.com/sst/opencode/blob/dev/.opencode/command/issues.md > > Haha Okay :) Sure, I'll take a look
Author
Owner

@itse4elhaam commented on GitHub (Nov 20, 2025):

What commands do you have?

I think I have a /review one too that we should prolly make into opencode automatically

I had a few but stumbled upon this gem and copied over a few:

https://github.com/darrenhinde/OpenAgents

My existing ones:
https://github.com/itse4elhaam/dotfiles/tree/master/.opencode%2Fcommand

And Yeah I think it can make it in there.

Also, a bit off topic but I think it might be useful to make mcps a bit more apparent if you will.

Maybe some auto complete can help there, as of now you have to nudge it directly towards the use or as I have done, refer the mcps in the base file prompts and create a tool to list the MCP servers from the file using jq.

@itse4elhaam commented on GitHub (Nov 20, 2025): > What commands do you have? > > I think I have a /review one too that we should prolly make into opencode automatically I had a few but stumbled upon this gem and copied over a few: https://github.com/darrenhinde/OpenAgents My existing ones: https://github.com/itse4elhaam/dotfiles/tree/master/.opencode%2Fcommand And Yeah I think it can make it in there. Also, a bit off topic but I think it might be useful to make mcps a bit more apparent if you will. Maybe some auto complete can help there, as of now you have to nudge it directly towards the use or as I have done, refer the mcps in the base file prompts and create a tool to list the MCP servers from the file using jq.
Author
Owner

@rekram1-node commented on GitHub (Nov 20, 2025):

yeah interesting idea, I think claude code does something like that

@rekram1-node commented on GitHub (Nov 20, 2025): yeah interesting idea, I think claude code does something like that
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3006