Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

panels: sandbox network toggle leaves a pending delete armed across keypresses

Closed Beginner friendly
  • Is something wrong?
#153 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli, security

Research direction

Start with tui/panels/sandbox_keys.go around line 43 and trace how the sandbox panel handles delete confirmation and the network-toggle key. Check nearby key handling and tests for the expected state transitions. Done when taking the network-toggle action clears any pending delete confirmation, and a later keypress cannot confirm that delete.

Written by the indexing model from the issue text.

Description

bug good first issue

Problem

In packages/tui/panels/sandbox_keys.go:43, toggling the network setting does not clear a pending "confirm delete" state that may have been armed by a previous keypress, so the two pieces of UI state (delete-confirmation armed, network toggle) are not properly isolated from each other.

Impact

A user who triggers a delete confirmation prompt, then (without confirming or cancelling it explicitly) presses the network-toggle key, can end up with the delete still armed; a subsequent keypress intended only to continue interacting with the network setting can then be interpreted as confirming the earlier, now-forgotten delete action, destroying data the user did not intend to delete.

Repro

  1. In the sandbox panel, trigger whatever key arms a pending delete confirmation.
  2. Without pressing the confirm or cancel key, press the network-toggle key instead.
  3. Press a key that would normally just continue interacting with the network toggle, and observe the previously armed delete fires instead.

Suggested fix

Clear the pending-delete-confirmation state whenever any other, unrelated action (such as the network toggle) is taken, so a delete can only be confirmed by the key immediately following the one that armed it, never by an unrelated subsequent keypress.

Dominant language
Go
Stars
157
Forks
19
Avg merge
4h 4m
Merged PRs (30d)
81

Getting set up

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.

More from solongate/agent-security

All issues in solongate/agent-security

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.