Studio

Studio is the image workbench inside your Deek conversation’s Gallery → Studio / Image workbench, not a separate public /studio HTML page. Use the owner-routed application at deek.loca.zone.

The Direction C workbench and its corrected phone composer are available from rc.2-r8 and retained in later releases. Another owner’s instance can run an older release; see Releases.

This is a release-qualified feature reference, not provider onboarding or permission to generate. Subscription Provider Sign-in owns the restrictive DeepSeek/Codex/Claude onboarding scope. A visible image backend does not extend that policy: Google/xAI image routes are outside approved onboarding and require separate, explicit provider-specific permission for the intended action. Opening Studio, selecting a backend, or reviewing a batch grants no quota or dispatch permission.

Compose and compare

1. Open Gallery from an existing conversation, then choose Studio.
2. Only with separate permission for the intended image provider/action, choose a backend and one of its offered aspect labels. Describe the image in the bottom prompt composer; recent prompts help recover earlier work.
3. For editing, choose or drop one to three PNG, JPEG, or WebP references, up to 2 MiB each. The original images are preserved.
4. Use Review batch to inspect the requested sequence before dispatch. Generation consumes the selected provider’s quota; opening the workbench is not permission to generate.
5. Inspect results in the filmstrip. Use the canvas’s split comparison handle, open a result in the lightbox, download it, or use it as an edit reference.

The desktop composer stays at the bottom of the workbench. On a phone it follows normal document flow so failed and held counts remain reachable instead of being covered by the composer.

Queue panel and cooldowns

The queue distinguishes completed, active, failed, and held images. Batch work is sequential and interleaved per image; it is not a claim of simultaneous provider jobs. Elapsed waiting time and backend cooldown rings are honest waiting indicators, not invented server percentages.

When a backend reports Try again in N seconds, Studio displays its deadline/countdown. Queue when ready is an explicit, removable choice; a cooldown does not silently authorize a retry. Review the queue before adding work. Cancel stops remaining dispatch; an already sent provider request can still consume quota.

On the first failure, remaining dispatch stops. Partial results remain visible with the original requested total, failed/held counts, and a prompt-preserving recovery action. Retry only the remaining work deliberately rather than resubmitting the entire batch blindly.

Keyboard and recovery

• Command/Control + Enter requests generation from within Studio; use it only for a separately authorized provider/action, not as an onboarding or readiness test.
• Arrow keys move through results; the lightbox and comparison controls retain visible keyboard focus.
• Esc closes the active native layer in order, returning focus to its trigger. Studio does not consume Escape outside its own controls.
• Offline/provider errors preserve work and give next steps. Permission denial and disabled capability are not invitations to bypass configuration.

Usage totals are unavailable from the workbench’s describe API; the UI must not invent them. Reference images, result-generation metadata, and native attachments belong to the conversation. Images and Self-publishing retains release-qualified image-command and Google/Gemini catalog references outside approved onboarding; catalog documentation is not current entitlement or permission to select or call a provider. For application-wide shortcuts, use Keyboard Shortcuts.