OpenHands / OpenHands/software-agent-sdk

[Bug]: New added Global Skills dont get loaded into OpenHands (CLI install) and not available in WebUI

Open
#4,252 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-triage
Dominant language
Python
Stars
1.1k
Forks
539
Avg merge
1d 19h
Merged PRs (30d)
137

Description

Is there an existing issue for the same bug?
  • I have searched existing issues and this is not a duplicate.
Bug Description

The issue is simple and also was discussed here (but closed with just documentation update for docker flag, which doesnt fixes the main issue I am experiencing): https://github.com/OpenHands/software-agent-sdk/issues/2417

When placing new global skills into folder .opencode structure, it doenst get loaded into OpenHands at all. Even after server/application restart.
I tried .openhands/skills/installed/new-skill/SKILL.md
aswell .openhands/skills/new-skill/SKILL.md

None of them gets loaded into OpenHands (so it also doesnt show up as usable or available in WebUI)

Tags:
@VascoSch92

Expected Behavior

Place new global skill into folder .openhands/skills/new-skill/SKILL.md
Restart Server or application
Open WebUI and see new global Skill visible

Actual Behavior

Not visible in WebUI and not usuable inside OpenHands

Steps to Reproduce
  1. place new skill to .openhands/skills/new-skill/SKILL.md
  2. reload application (exit docker containers manually from running) or restart server
  3. run openhands serve
  4. Open OpenHands WebUI and look for available global skills
OpenHands Installation Method

CLI (uv tool install)

If you selected "Other", please specify

No response

OpenHands Version

Current

Version Confirmation
  • I have confirmed this bug exists on the LATEST version of OpenHands
Model Name

Claude, MiniMax 2.5, Qwen 3.6 27B

Operating System

Linux

Browser (if using web UI)

Firefox newest

Logs and Error Messages

No response

Screenshots and Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with a CLI installation by placing a skill at .openhands/skills/new-skill/SKILL.md, restarting the application, running openhands serve, and checking the WebUI. Trace how global skills are discovered during startup and exposed as available skills. Done means a newly added global skill appears in the WebUI and can be used after restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
backend, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.