Bug list 02/07/26 Openeral

[ankurshashwat]

OpenWork — Skills

• Skills tab: unknown functionality state
  Skills in OpenWork do not have clear feedback on whether they are working or not. No success/error indicators are shown after triggering a skill action.

• "Import Local Skills" button does nothing
  Clicking the "Import Local Skills" button produces no response — no file picker, no error message.

• "Open Skill Folder" button does nothing
  Clicking the "Open Skill Folder" button produces no response — the folder does not open.

• "Create New Skill" button does nothing
  Clicking the "Create New Skill" button produces no response — no dialog, no file is created.

---

OpenWork — Git Integration

• "Add Git Repo" button has broken/poor UI
  The UI for the "Add Git Repo" button is visually broken or unstyled. Needs design and layout fixes to match the rest of the interface.

---

OpenWork — Extensions / Hub

• "Add" button in "Available from Hub" does nothing
  On the hub/extensions discovery panel, clicking the "Add" button next to any available extension produces no response — nothing is installed or queued.

• Extension page: multiple buttons non-functional
  On the Extensions page, several buttons do not trigger any action. Needs an audit of all button click handlers on that page to identify which are unimplemented.

---

OpenWork — File Menu

• File menu tab shows "Exit" instead of expected options
  When the "File" option is clicked in the top/above tab bar, the menu only shows "Exit". Expected file-related options (e.g. New, Open, Save) are missing.

---

OpenClaw — Gateway

• OpenClaw gateway fails to start on launch
  When running OpenClaw, the background gateway process errors out and does not come up. As a result, no communication with the OpenClaw agent is possible and chat is broken. The error message should be captured and surfaced to the user clearly, and the root cause in setup.sh / the gateway startup sequence should be fixed.

  Steps to reproduce:

  1. Launch OpenClaw via the sandbox or CLI
  2. Observe that the gateway process exits with an error
  3. Attempt to send a chat message — no response is received

  Expected: Gateway starts successfully and chat works end-to-end.
  Actual: Gateway crashes on startup; chat is completely non-functional.

---