The defence toggles that used to live here — HTML rendering, secret scrubbing, context isolation, tool authorization — are on the Ops console under Defensive posture, alongside every other control in one list. This modal is connection config.

Where is the endpoint? If 0claude was deployed to a server, use that machine's address — http://192.168.1.50:11434 — not localhost. localhost only works when the endpoint is on the same machine as this page, or when an SSH tunnel is forwarding it.

http or https? Both, depending on the server. If a certificate was generated in the 0claude console, the endpoint is https:// and plain http:// will not connect. A self-signed certificate makes the browser warn once — open the endpoint URL directly in a tab and accept it, then come back here, or the requests from this page fail with no visible error.



Very large prompts are capped at 1 MB by the server. A payload bigger than that comes back as 413 rather than a model refusal, which is worth knowing before reading it as a defence working.

Leave bearer token blank unless the endpoint was deployed with --require-token. An open endpoint rejects nothing; a token-protected one answers 500 without it.