You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(omp): support integration args and options in build_exec_args - #4876
- Pass per-step integration_args straight through to the omp CLI.
- Map the named options profile, thinking, and tools to their flags.
- Add validate_runtime_config to reject unknown options, empty values,
and invalid thinking levels before the command runs.
- Reject integration_options.model so model selection stays on the
command-step 'model' field.
- Verify integration_args and integration_options are passed to omp
and ordered after SPECKIT_INTEGRATION_OMP_EXTRA_ARGS.
- Accept every documented thinking level and valid runtime configs.
- Reject malformed args, the reserved model option, and invalid,
unknown or non-string option keys and values.
integration_args can still select a model (for example, ['--model', 'gpt-5']), so a step can run a model while its top-level model field—and recorded output—remain unset. This defeats the stated invariant enforced for integration_options.model; reject OMP's model flag forms in per-step raw args as well, with a regression test.
Document OMP runtime options in the integrations reference
These new public runtime options are not documented in the supported-integrations reference, and the workflow reference still describes only Docker Agent's named options. design/integration.md:65-66 requires agent-specific options to be represented in docs/reference/integrations.md; document OMP's profile, thinking, and tools options (including accepted thinking values and argument precedence) so workflow authors can discover and use this API.
🧠 Review effort: Balanced
Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.
Model selection must go through the command-step `model` field, so a
`--model` flag in `integration_args` now fails validation before OMP is
launched. This matches the existing rejection of `integration_options.model`
and avoids two competing model sources on the command line.
- Reject `--model` and `--model=...` in `integration_args`; `--models`
(Ctrl+P cycling scope) stays allowed.
- Document `profile`, `thinking`, and `tools` options, `integration_args`
passthrough, and argument ordering in the integrations reference.
- Link the OMP options from the workflows per-step configuration section.
- Add tests for rejected `--model` forms and the allowed `--models` flag.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
triage-nice-to-haveVerdict: evidence-backed fix or greenlit feature — land after review
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Testing
uv run specify --helpuv sync && uv run pytestAI Disclosure
AI disclosure: N/A