1. Three Workflow Bottlenecks This Part Solves
Sending a prompt forces you to wait before queuing follow-up instructions. Prompt Queue enables continuous batching.
Trying alternative prompt directions can ruin a working thread. Forking creates non-destructive branch points.
If a request fails, check the provider error, select another equipped model, and retry manually. Saved model fallback order is not currently applied by request execution.
2. Prompt Queue — Your Assembly Line
While an active generation is running, type your next instruction into the composer input. The main action button shifts to an indigo Queue Response button.
- Isolated Staged Assets: Each queued prompt preserves its own attached files, screenshots, or CSVs independently.
- Reorder & Delete: Drag queued cards to adjust execution order or click trash to remove.
- Pause Queue: Complete current active turn and temporarily halt remaining queued tasks.
- Queue Backoff Interval: Configure a 0–60 second delay in Settings → AI Engine to pace execution and prevent rate limits.
- Last Failed Recovery: Failed queued tasks are moved to a recovery drawer for instant 1-click retry.
3. Forking / Branching — Never Lose a Good Version
Hover under any user or assistant message and click Fork (GitBranch icon).
Non-Destructive Branching: Creates a new chat thread containing history up to that exact fork point while preserving your original chat intact.
Comparison Workflows: Fork a prompt 3 times to test different design directives (e.g. Minimal vs Brutalist vs Glassmorphic) or compare multiple LLM models side by side.
4. Saved fallback order and current limits
The Model Organizer can save an ordered list of alternate models, but request execution does not currently read that list to retry a failed request. Do not rely on it for automatic failover.
- Saved order: The Model Organizer stores the preferred sequence for a model; this is configuration data only.
- Current retry behavior: A failed request reports its provider error. Select another model and retry manually.
- Provider sign-in: Authentication prompts and retry behavior depend on the provider integration in use.
5. Putting All Three Together — A Real Workflow
- Equip the models you plan to use. Saved fallback order does not automatically switch requests between them.
- Create a Folder (e.g., Client Landing Pages) with Folder Memory:
React + Tailwind + lucide-react. - Stage
client1.pdf+ prompt "Build landing page for Client 1" → click Queue Response. - Stage
client2.png+ prompt "Build landing page for Client 2" → click Queue Response. - Review queued prompts and results as they finish. If a request fails, choose another model and retry it.