Description
The sidebar does not show an "Automations" nav item at all — only Inicio (Home), Agentes (Agents), and Habilidades (Skills) appear, followed by Proyectos and Chats sections. This is despite the app reporting itself as up to date.
Environment
app_version: 0.6.2 (via berdctl info context)
- Sidebar language: Spanish (Inicio / Agentes / Habilidades)
Additional signal
berdctl --help on this install also has no feedback subcommand, even though the bundled berd-help skill's references/reporting-problems.md documents berdctl feedback open / berdctl feedback submit as the expected reporting path. This suggests this build may be missing more than one feature that's documented/expected elsewhere (Automations nav item + feedback CLI), possibly a channel/rollout gap rather than a single isolated bug.
Expected
Automations should appear in the sidebar (as it does in Berd's own landing/marketing screenshots), or — if it's gated behind a capability/entitlement — the app should make that gating discoverable rather than silently omitting the nav item.
Steps to reproduce
- Open Berd desktop app (v0.6.2)
- Look at the left sidebar
- No "Automatizaciones/Automations" item is present, between Habilidades and the Proyectos section
Description
The sidebar does not show an "Automations" nav item at all — only Inicio (Home), Agentes (Agents), and Habilidades (Skills) appear, followed by Proyectos and Chats sections. This is despite the app reporting itself as up to date.
Environment
app_version:0.6.2(viaberdctl info context)Additional signal
berdctl --helpon this install also has nofeedbacksubcommand, even though the bundledberd-helpskill'sreferences/reporting-problems.mddocumentsberdctl feedback open/berdctl feedback submitas the expected reporting path. This suggests this build may be missing more than one feature that's documented/expected elsewhere (Automations nav item + feedback CLI), possibly a channel/rollout gap rather than a single isolated bug.Expected
Automations should appear in the sidebar (as it does in Berd's own landing/marketing screenshots), or — if it's gated behind a capability/entitlement — the app should make that gating discoverable rather than silently omitting the nav item.
Steps to reproduce