Shell completion probes run full CLI startup and feel slow #25692

Activity

1. github-actions

   assigned

   jlongster

   on May 4, 2026
2. github-actions commented on May 4, 2026

   

   github-actionsBot

   on May 4, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • No issue template was used. Please resubmit using one of the three required templates: Bug Report, Feature Request (title must start with [FEATURE]:), or Question. This issue appears to combine a bug report (completion probe slowness) and a feature request (documentation + optimization), so please split or choose the most appropriate template.

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

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

   • Feature request: cli tab completions for bash, fish, and zsh #1515: Feature request for CLI tab completions for bash, fish, and zsh — covers the same shell completion support and opencode completion command

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on May 4, 2026
4. luojiyin1987

   changed the title [-]Document shell completion setup and avoid full CLI init for completion probes[/-] [+]Shell completion probes run full CLI startup and feel slow[/+] on May 4, 2026
5. luojiyin1987 commented on May 4, 2026

   

   luojiyin1987

   on May 4, 2026

   ContributorAuthor

   More actions

   Reformatted this as a bug report. #1515 is about shell-completion support existing at all; this issue is specifically about the hot-path latency of opencode --get-yargs-completions. Fix is in #25693.
6. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on May 4, 2026
7. github-actions commented on May 4, 2026

   

   github-actionsBot

   on May 4, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for updating the issue! It now follows the Bug Report template with clear reproduction steps and context. Removing the compliance flag.
8. github-actions commented on Jul 4, 2026

   

   github-actionsBot

   on Jul 4, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
9. github-actions

   closed this as not plannedon Jul 4, 2026