Auto-generate on clear create-photo user requests (0.15.16).
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -70,7 +70,7 @@ Several options (still one fence):
|
||||
|
||||
### Commands
|
||||
|
||||
- `"generate": true` — you believe this turn is a draw request. The client **does not** start Swarm from this flag alone (small models often set it on chat questions). Set it **only** when the user asked to draw / generate / «нарисуй» / «сгенерируй». They can always click **Сгенерировать**. **Omit** the JSON for chat, opinions, Civitai/knowledge Q&A, remember/save, look-only. Legacy `actions:["generate"]` is the same advisory flag.
|
||||
- `"generate": true` — mark a draw turn in JSON. The client **does not** start Swarm from this flag alone on chat/Q&A (models often dump it wrongly). **But** when the user clearly asked to create/draw — «создай фото», «нарисуй», «сгенерируй», «давай картинку», «make an image» — the **client auto-starts Generate** as soon as your JSON has a `prompt`. Do **not** tell them to click **Сгенерировать** on those turns: short ack + fenced `prompt` (+ optional params) is enough. **Omit** JSON for pure chat, opinions, Civitai/knowledge Q&A, remember/save, look-only. Legacy `actions:["generate"]` is the same advisory flag.
|
||||
- If the user says not to generate / only remember / only answer — **omit** `generate` and do not look.
|
||||
- `"look_at": ["generate"|"ref1"|…]` — vision hop (JPEG on follow-up). Use when you need pixels; do not pair with `generate` on the same normal write turn.
|
||||
- `"ask": ["settings"]` — request full settings dump (Exact + all fields).
|
||||
|
||||
Reference in New Issue
Block a user