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
Safe output: create-issue or noop, just to confirm the agent ran with the dynamic-workflow extension available
Variant: standard
Minimal test prompt sketch
Configure engine.dynamic-workflows: true (or rely on the new default) so the Copilot CLI session loads the targeted EXTENSIONS feature flag and project-extension discovery. Have the prompt ask the agent to invoke a project-level dynamic workflow/extension bundled in the repo (or confirm its availability) and then create an issue confirming it ran, so the test fails if the extension/workflow restore step silently breaks.
New fixtures or secrets needed
Likely needs a minimal fixture dynamic-workflow/extension file checked into this repo (e.g. under a project extensions folder) for the agent to discover and invoke — the PR mentions "prompt-mode project extension discovery" and restoring supporting files from an activation artifact. Exact fixture shape is unclear without reading the gh-aw engine config docs for this feature in more detail.
Notes
Open questions: (1) what the minimal fixture file/extension needs to look like for Copilot CLI to discover it, (2) whether this is meaningfully different from the existing test-copilot-skills-frontmatter.md coverage (skills vs. dynamic workflows may be adjacent but distinct mechanisms — needs triage), (3) whether a disabled-by-default negative test is also warranted per the PR's "explicitly deny them when disabled" behavior. No existing test or open suggestion currently covers dynamic workflows.
Activity