Enhancement: Add Protection Against Multiple Simultaneous Command Executions

[mithilP007]

Describe the issue

The application currently appears to allow multiple command executions simultaneously without proper request locking or execution state management.

Users can repeatedly trigger command execution while previous commands are still running.

This may lead to:

• duplicated processes
• overlapping terminal output
• resource overconsumption
• inconsistent execution state
• UI freezing or race conditions

To Reproduce

1. Open the command execution page
2. Run a long-running bash command

Example:

sleep 10

3. Rapidly click the execute/run button multiple times
4. Observe duplicated execution behavior

Expected Behavior

The application should:

• disable execution while a command is already running
• prevent duplicate process spawning
• maintain a single active execution state
• clearly show running status

Example:

if (isRunning) return;

Suggested Fix

Implement:

• execution locking
• button disabling during active execution
• process state tracking
• duplicate request prevention
• optional command queue support

Impact

Fixing this improves:

• application stability
• process management reliability
• frontend responsiveness
• resource efficiency
• UX consistency

Labels Suggested

• enhancement
• performance
• backend
• frontend
• GSSoC2026

[mithilP007]

Hi maintainers,

I would like to work on this issue under GSSoC 2026.

I plan to implement execution-state protection and duplicate request prevention to avoid multiple simultaneous command executions and improve application stability.

Please assign this issue to me. Thank you!