Skip to content

FAQ

It can use a local model server such as Ollama, but local-first does not require offline inference. A configured cloud provider receives the request content sent to its API.

No embedded model is bundled in v0.4.0-beta.3. Connect a provider or an existing local model server.

There is no built-in product telemetry. External providers and websites still receive normal request traffic when you use them.

Runtime state lives in the configured local state directory by default. It contains configuration, memory, conversations, audit records, credentials, browser state, and recovery data. Treat it as private.

Can I expose the local console over my network?

Section titled “Can I expose the local console over my network?”

No. The single-user gateway is loopback-only. Remote use requires the dedicated TLS multi-user host.

No. It provides application-level tenant separation. Mutually hostile users require OS, container, VM, or machine isolation.

No. Proof, Sentinel, Capability Tokens, Rewind, Capsules, Counterfactuals, and Darwin are individually gated and off by default.

No. Automatic improvements is a separate bounded feature that starts enabled by default. It can apply only predefined reliability tuning and keeps a restore point.

Can Ódinn undo a sent message or purchase?

Section titled “Can Ódinn undo a sent message or purchase?”

No guarantee is made for external effects. Approval and recovery records improve operator control, but remote systems remain outside full replay and rollback.

Ódinn includes presets for many API, OAuth, device, CLI, and local OpenAI-compatible paths. Run odinn config provider catalog for the installed catalog. A preset does not guarantee live availability.

The beta includes Windows installation and automated cross-platform coverage. Real-host Windows validation remains an open stable-release gate.

No. It is the current public beta. See Public beta status for the remaining evidence.