Workspace
The workspace is organized around the complete image loop rather than a single generate button. Every generation uses a model and API path allowed by the active preset, with permission and credit checks enforced on the server.
/workspace also has a read-only visitor mode. It keeps the real workspace structure while showing one complete example project and six bundled example images. Locked actions open the shared account-intent dialog and guide the visitor to create an account or sign in. Visitor mode does not call protected APIs, SSE streams, upload endpoints, generation endpoints, or thumbnail endpoints. Bootstrap remains a first-deployment authorization path and is not part of visitor mode.
| Mode | What you can do | What it never does |
|---|---|---|
| Visitor mode | Explore the complete example project, six example images, prompts, parameters, preview, gallery, and jobs | Change data, download private assets, favorite, delete, upload, generate, or edit |
| Signed-in mode | Use the real workspace and manage gallery content, jobs, and settings | Depend on demo data |
Main areas
- Prompt: write or reuse a prompt and choose supported generation parameters.
- Preview: inspect the current result and carry it into another edit.
- Jobs: follow queued, running, successful, and failed work.
- Gallery: search, filter, favorite, export, and reuse completed images.
- Settings: use the presets and product capabilities exposed by the operator.
A useful working pattern
Start with a small prompt, inspect the result, refine only the part that needs work, and save the successful prompt and parameters. This keeps the job history useful and makes repeated work faster.
The browser only calls JumpCLI product APIs. Provider credentials, billing tokens, payment keys, and SMTP secrets remain server-side.
Next: Gallery and jobs.