Before filing
Closest existing issue
None found.
Is this new, or an improvement?
Improvement — Berd provides terminal access, but it becomes difficult to discover when Multi-workspace support is enabled.
The problem, in your terms
I was trying to open the terminal from a chat after enabling Multi-workspace support. The previously visible top-right terminal button was gone, so terminal access appeared to have disappeared. It was eventually found inside the hamburger/overflow menu in the right-side context toolbar, but the interface gave no indication that the control had moved there.
What you do today
Open the right-side context toolbar's hamburger/overflow menu and select Terminal. This works after the location is known, but it is difficult to discover without prior knowledge.
What you'd like to see
Keep terminal access visibly discoverable when Multi-workspace support is enabled. Possible approaches include retaining a visible terminal button, showing an onboarding hint when the control moves, or otherwise signaling that Terminal is available in the context-toolbar overflow menu.
Why this belongs in Berd itself
This is navigation and discoverability within Berd's built-in chat and workspace UI. A skill, agent, extension, or automation cannot change where Berd places its native terminal control or tell users where a control has moved before they can find it.
Non-goals
This request does not ask for changes to terminal behavior, shell configuration, workspace semantics, or the Multi-workspace feature itself. It only concerns discoverability of the existing Terminal entry point.
Alternatives you considered
- Leave the control in the overflow menu without a hint: rejected because users can reasonably conclude the terminal was removed.
- Document the location externally: less effective than making the built-in control discoverable at the point of use.
- Disable Multi-workspace support: restores the visible control but gives up the feature.
Mockups, prior art, or other context
Observed on Berd 0.6.2 for macOS (Apple Silicon). With Multi-workspace support disabled, Terminal is visible at the top right; with it enabled, Terminal is under the right-side context toolbar's hamburger/overflow menu.
Before filing
Closest existing issue
None found.
Is this new, or an improvement?
Improvement — Berd provides terminal access, but it becomes difficult to discover when Multi-workspace support is enabled.
The problem, in your terms
I was trying to open the terminal from a chat after enabling Multi-workspace support. The previously visible top-right terminal button was gone, so terminal access appeared to have disappeared. It was eventually found inside the hamburger/overflow menu in the right-side context toolbar, but the interface gave no indication that the control had moved there.
What you do today
Open the right-side context toolbar's hamburger/overflow menu and select Terminal. This works after the location is known, but it is difficult to discover without prior knowledge.
What you'd like to see
Keep terminal access visibly discoverable when Multi-workspace support is enabled. Possible approaches include retaining a visible terminal button, showing an onboarding hint when the control moves, or otherwise signaling that Terminal is available in the context-toolbar overflow menu.
Why this belongs in Berd itself
This is navigation and discoverability within Berd's built-in chat and workspace UI. A skill, agent, extension, or automation cannot change where Berd places its native terminal control or tell users where a control has moved before they can find it.
Non-goals
This request does not ask for changes to terminal behavior, shell configuration, workspace semantics, or the Multi-workspace feature itself. It only concerns discoverability of the existing Terminal entry point.
Alternatives you considered
Mockups, prior art, or other context
Observed on Berd 0.6.2 for macOS (Apple Silicon). With Multi-workspace support disabled, Terminal is visible at the top right; with it enabled, Terminal is under the right-side context toolbar's hamburger/overflow menu.