Make the default /image workflow ask the user for their preferred generation mechanism before running a request when no mechanism is already selected: hosted API or local GPU. Present the choices and relevant constraints concisely, then collect only the options needed for the selected mechanism.
Support an explicit per-request override and a clearly scoped remembered preference only where existing session/config conventions support it. Never silently fall back from hosted to local or local to hosted.
Acceptance criteria
/image with no mechanism produces a clarification prompt and does not invoke a provider.
Hosted and local selections route to the correct provider with the selected options.
The flow supports generation and edit requests, including input-image validation.
Invalid choices, missing credentials, unavailable GPU backends, and cancellation produce actionable replies.
Channel-neutral tests cover the state machine; Telegram/web behavior is covered at the adapter boundary where applicable.
Design
See docs/prds/image-capability-contract.md#image-routing-and-clarification-flow-500 for the settled design: Router.handleImage beside handleModel, per-request (not session-persisted) mechanism selection, and the exact flow steps.
Suggested /council lenses
lens-boundary, lens-maintainer -- run /council --lenses boundary,maintainer once gate-clean, before opening the PR.
Close reason
Closed
Imported from beads archie-core-1786748942193-4-5072b564 · GitHub #500 · type task · priority P2 · created 2026-08-14 · closed 2026-10-08
## Scope
Make the default `/image` workflow ask the user for their preferred generation mechanism before running a request when no mechanism is already selected: hosted API or local GPU. Present the choices and relevant constraints concisely, then collect only the options needed for the selected mechanism.
Support an explicit per-request override and a clearly scoped remembered preference only where existing session/config conventions support it. Never silently fall back from hosted to local or local to hosted.
## Acceptance criteria
- `/image` with no mechanism produces a clarification prompt and does not invoke a provider.
- Hosted and local selections route to the correct provider with the selected options.
- The flow supports generation and edit requests, including input-image validation.
- Invalid choices, missing credentials, unavailable GPU backends, and cancellation produce actionable replies.
- Channel-neutral tests cover the state machine; Telegram/web behavior is covered at the adapter boundary where applicable.
## Design
See docs/prds/image-capability-contract.md#image-routing-and-clarification-flow-500 for the settled design: Router.handleImage beside handleModel, per-request (not session-persisted) mechanism selection, and the exact flow steps.
## Suggested /council lenses
lens-boundary, lens-maintainer -- run `/council --lenses boundary,maintainer` once gate-clean, before opening the PR.
### Close reason
Closed
---
_Imported from beads `archie-core-1786748942193-4-5072b564` · GitHub #500 · type task · priority P2 · created 2026-08-14 · closed 2026-10-08_
sam
added the mediumtask labels 2026-10-27 13:34:38 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Scope
Make the default
/imageworkflow ask the user for their preferred generation mechanism before running a request when no mechanism is already selected: hosted API or local GPU. Present the choices and relevant constraints concisely, then collect only the options needed for the selected mechanism.Support an explicit per-request override and a clearly scoped remembered preference only where existing session/config conventions support it. Never silently fall back from hosted to local or local to hosted.
Acceptance criteria
/imagewith no mechanism produces a clarification prompt and does not invoke a provider.Design
See docs/prds/image-capability-contract.md#image-routing-and-clarification-flow-500 for the settled design: Router.handleImage beside handleModel, per-request (not session-persisted) mechanism selection, and the exact flow steps.
Suggested /council lenses
lens-boundary, lens-maintainer -- run
/council --lenses boundary,maintaineronce gate-clean, before opening the PR.Close reason
Closed
Imported from beads
archie-core-1786748942193-4-5072b564· GitHub #500 · type task · priority P2 · created 2026-08-14 · closed 2026-10-08