Web and browser work

Ódinn offers two different ways to work with the web:

• Web tools search the public web and fetch readable pages.
• Browser tools use an isolated, persistent Chromium profile for interactive sites and accounts.

The distinction matters because a page read and an account mutation carry different risk.

Public web reading

Public web search and fetch are enabled by default. Requests follow the configured domain and private-network policy. Redirects are rechecked, and resolved addresses are validated before connection.

Private, link-local, and metadata-network targets are blocked by default.

Isolated browser profile

Ódinn does not silently extract cookies from another browser. Open the isolated profile and sign in manually to any account you want it to use. The profile and its recovery journal live in local state.

Browser reads are available through the normal policy boundary. Clicks, typing, and keypresses require explicit approval by default.

Approval is control, not rollback

An approval lets a specific action proceed. It does not guarantee that a purchase, message, deletion, or other remote change can be reversed. Browser mutations are journaled before execution; an interrupted or uncertain outcome blocks later mutations until you review and resolve it.

Review the policy

odinn config security show

Advanced operators can restrict domains:

odinn config security set \
  --surface web \
  --allowed-domains docs.example.com

Allowing private networks or disabling browser approval weakens the default boundary and requires an explicit impact confirmation. Read Security controls before changing either setting.

The beta does not provide general-purpose browser file upload or download tools.