salvacybersec/opencode-obsidian
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Create spec for better process management

Browse Source
This commit is contained in:
Mateusz Tymek
2026-02-14 16:53:49 +01:00
parent f52ee2510d
commit f2c31a0c6f
7 changed files with 492 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
openspec/changes/improved-opencode-process-management/specs/custom-command-launch/spec.md Normal file
View File

@@ -0,0 +1,50 @@
## ADDED Requirements
### Requirement: Custom shell command execution
The system SHALL support executing user-defined shell commands with full control over arguments and environment.
#### Scenario: Execute custom command with shell
- **GIVEN** useCustomCommand setting is true
- **AND** customCommand setting contains a shell command string
- **WHEN** the server is started
- **THEN** the system SHALL spawn the process with shell: true option
- **AND** execute the exact command string as provided by the user
#### Scenario: Custom command with environment variables
- **GIVEN** customCommand is "FOO=bar opencode serve --port 14096"
- **WHEN** the server is started
- **THEN** the system SHALL execute the command with shell: true
- **AND** the environment variable FOO SHALL be set to "bar"
#### Scenario: Custom command with custom arguments
- **GIVEN** customCommand is "opencode serve --port 9999 --verbose"
- **WHEN** the server is started
- **THEN** the system SHALL execute the command with shell: true
- **AND** pass exactly "--port 9999 --verbose" as arguments
- **AND** NOT append any default arguments (port, hostname, etc.)
#### Scenario: Custom command with wrapper script
- **GIVEN** customCommand is "/path/to/my-wrapper.sh"
- **WHEN** the server is started
- **THEN** the system SHALL execute the wrapper script via shell
- **AND** the wrapper script SHALL have full control of opencode invocation
### Requirement: No validation for custom commands
The system SHALL NOT validate custom commands before execution.
#### Scenario: Invalid custom command fails naturally
- **GIVEN** customCommand is "invalid-command-that-does-not-exist"
- **WHEN** the server is started
- **THEN** the system SHALL attempt to execute it
- **AND** let the spawn fail naturally with ENOENT error
- **AND** NOT perform pre-flight validation
### Requirement: User controls all arguments in custom mode
The system SHALL NOT append any default arguments when using custom command mode.
#### Scenario: User provides complete command
- **GIVEN** useCustomCommand is true
- **AND** customCommand is "opencode serve"
- **WHEN** the server is started
- **THEN** the system SHALL execute exactly "opencode serve"
- **AND** NOT append --port, --hostname, or --cors arguments