Settings overview
Understand all six 9Miho Settings sections, which machine owns each value, and which changes require a server restart.
One control surface, several kinds of state
Open Settings from the application shell. The modal brings browser preferences, server settings, provider credentials, installation help, and agent readiness into one place. Those values do not all live in the same process, so the machine and account running the 9Miho server matter.
The old shortcuts remain useful: the canvas gear opens Canvas, while the key shortcut opens Providers.
| Section | What it controls | Where the effective state lives |
|---|---|---|
| General | UI scale, font, language, and the server artifact location | Interface choices in this browser; storage path on the server |
| Canvas | Background, grid, snap, wire style, graph lock, minimap, tooltips, stacked cards, and shake-to-disconnect | This browser |
| Runs | Reuse of unchanged node results | The running 9Miho server process |
| Providers | Named authentication and execution profiles, defaults, API keys, endpoints, local services, and readiness | Server profile state plus the server machine’s OS credential store |
| Installation guide | Bundled local ComfyUI, GCP, and Runpod instructions | Read-only guide in the app; approved work happens in a separate terminal |
| Agent | Agent backend, model, connection guidance, and prompt assistance | Availability on the server; selection remembered by this browser |
General
UI size scales the rails, panels, toolbar, and drawers. It does not resize nodes; use Canvas zoom for the graph. Choose the interface language and one of the available font families from the same section.
Artifact location is an absolute path on the server machine. A NAS must already be mounted there, and a Docker path must be mounted into the container. Saving a new path does not move old assets: existing Krefs remain readable, while new registrations use the new location after the server restarts. Flow, Run, and settings state remains in the separately reported state path.
Canvas and Runs
Canvas settings change how the graph looks and responds. Lock graph makes it view-only; Snap, wire style, minimap, tooltips, and shake-to-disconnect change authoring behavior without changing the saved model contract.
Reuse unchanged node results is different. It is server-process state and can change whether an otherwise identical node is executed and billed again. Read the live status text before changing it; do not treat it as a cosmetic browser preference.
Providers, installation, and Agent
- Use Provider profiles and API keys to configure the service that will execute a generation.
- Use Google Cloud ADC and Vertex AI when Gemini or Veo should run through your Google Cloud project instead of an AI Studio API key.
- Use ComfyUI and GPU setup for the bundled local, GCP IAP, and Runpod setup paths.
- Use Agent backends and models for the CLI that powers agent turns and prompt assistance.
- Use Claude and Codex through MCP when an external agent should browse assets, author or validate Flows, and work with Storyteller through a running 9Miho.
An agent login does not configure a generation provider, and a provider API key does not connect an agent backend. Configure and verify both surfaces when a Flow uses both.
Recommended first-run order
- Set language, UI size, and the artifact location in General.
- Connect an agent backend if you want Agent turns or Assistant-driven prompt work.
- Create the required provider profile and make the intended profile the vendor default.
- For local or remote ComfyUI, read the bundled installation guide before opening a launcher.
- Use Re-check after saving provider settings, then select a compatible catalog Variant in Canvas.
- Validate the graph and review the spend card before dispatch.
The active server catalog is the final authority for available providers, modes, models, and controls. A newer or differently installed server can advertise a different set than an older screenshot or document.