Desktop: turn help button into a help menu (docs, feedback, GitHub, Discord) · Issue #54264 · anomalyco/opencode · GitHub
Skip to content

Desktop: turn help button into a help menu (docs, feedback, GitHub, Discord) #54264

Open

Description

@opencode-agent

Summary

The help button in the desktop app currently links straight to Discord. It should instead open a small help menu that acts as a jump-off point to the various support/feedback destinations, similar to Figma's help menu (though with fewer options).

Proposed options

  • Docs
  • Send feedback (feedback form)
  • Report a bug / GitHub issues
  • Discord community

Context

Raised in Slack by Kit while dogfooding desktop; David noted this was the original plan (Figma-style help menu). Low priority.

Activity

  1. argszero commented on Oct 10, 2026

    @argszero
    Contributor

    I'd like to work on this.

    I went looking for the current state before claiming it, and there is one thing worth settling first, because the report and dev disagree about where the button points today.

    What I found in the current source. There are two in-app help entry points, and neither opens Discord right now:

    • the Home navigation button — packages/app/src/home/projects/view.tsx (onOpenHelp), wired in packages/app/src/home/projects/controller.tsx to platform.openExternal("https://opencode.ai/desktop-feedback");
    • the mobile tabs drawer button — packages/app/src/shell/titlebar/titlebar.tsx (data-action="mobile-tabs-help"), which opens the same feedback URL.

    The only Discord link in the app is the native menu bar item at packages/app/src/shell/commands/desktop-menu.ts (the help menu, desktop.menu.supportForum → https://discord.com/invite/opencode). So the "links straight to Discord" detail looks like it describes an older release; the feedback page is what the in-app buttons open on dev today.

    What that means for the fix. The menu requested here already exists in the native menu bar, and it declares exactly the four destinations:

    desktop.menu.documentation  -> https://opencode.ai/docs
    desktop.menu.supportForum   -> https://discord.com/invite/opencode
    desktop.menu.shareFeedback  -> .../issues/new?template=feature_request.yml
    desktop.menu.reportBug      -> .../issues/new?template=bug_report.yml
    

    So the smallest correct change is to make the in-app help buttons open a small menu over that same list, reusing those URLs and the existing label keys rather than inventing a second set of destinations. That also keeps the button and the menu bar from drifting apart later.

    Two questions before I start, so I build the right thing:

    1. Which entry point did you mean — the Home nav button, the mobile drawer button, or both? My read is both, since they share the sidebar.help label, but I'd rather not convert one you didn't mean.
    2. Is docs / send feedback / report a bug / Discord the list you want, or should it follow Figma a little less literally (for example dropping Export logs, which the menu bar already has but would be odd in an in-app popover)?

    Unless you say otherwise I'll take the shared menu across both entry points and mirror the native help menu's destination list.

  2. argszero commented on Oct 11, 2026

    @argszero
    Contributor

    Opened #54637 for this.

    You were right about the current behaviour and I was wrong when I claimed it: https://opencode.ai/desktop-feedback answers 302 with location: https://discord.gg/h5TNnkFVNy, so the button does go straight to Discord — the old destination never offered a way to send feedback at all.

    The PR turns the home sidebar help button into the menu the issue asks for, over the same four destinations (and labels) the desktop menu bar's Help group already declares in shell/commands/desktop-menu.ts. The mobile tabs drawer has a second help button with the same redirect; I left it out of this PR and explained why, and I'm happy to do it as a follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions