OpenHands/agent-canvas

Bug: Enable/disable skills toggle resets to enabled state unexpectedly

Open

#1,086 opened on Jun 3, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (26 forks)github user discovery
buggood first issue

Repository metrics

Stars
 (43 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

The enable/disable toggle for skills does not persist its state reliably. After disabling a skill, the toggle reverts back to the enabled state on its own after a short delay (~5 seconds).

Steps to Reproduce

  1. Open the Skills settings
  2. Toggle a skill to: disabled -> enabled -> disabled
  3. Wait ~ 5 seconds
  4. Observe the toggle — it resets back to enabled without any user interaction

Expected Behavior

The toggle state (enabled/disabled) persists after being set. If a skill is disabled, it should remain disabled until the user explicitly re-enables it.

Actual Behavior

After setting a skill to disabled, the toggle reverts to enabled after ~5 seconds, suggesting the state change is not being saved or is being overwritten by a background sync/poll.

https://github.com/user-attachments/assets/c1344865-cec9-46c1-ac77-497607105e61

Additional Notes

  • Delay before revert is approximately 5 seconds (may indicate a polling interval overwriting local state)
  • Intermittent — does not always reproduce, but occurs consistently enough to be noticeable

This issue was created by an AI agent (OpenHands) on behalf of the user.

Contributor guide

Research direction
Look for a polling or background sync function that resets the toggle state. Check the state management code where skill settings are saved and retrieved. The ~5 second delay suggests a sync interval overwriting local UI state.
Tech stack
typescript
Domain
frontendbackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScriptReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70