Agent
Settings → Agent controls how OrbySystems's agent behaves while it works on a request — how much context it keeps around, what it's allowed to do in a browser, whether it can search the web, and the sandbox it runs generated code in. Browser, Web Search, and Sandbox are sub-sections of this same page.
General
How much context OrbySystems keeps around while working on a request — useful to tune if you're using a model with a smaller context window, or want tighter control over how long a query can run.
- Max tool result % of context — truncates a single tool result once it would take up more than this share of the model's context window.
- Max history messages — how many past turns of a conversation are kept before older ones are dropped.
- Max iterations — the most turns (tool calls and responses) OrbySystems will take to answer a single query, so a query can't run away indefinitely.
Each of these can be turned off (set to 0) if you'd rather not cap it.
Browser
Controls what the agent is allowed to do when it drives a browser on your behalf — for example, downloading a statement or looking up a home value. Site visits the agent wants to make can require your approval; this section is where those approvals and any remembered site decisions live.
Web Search
Controls whether — and how — OrbySystems can reach out to the web while answering a question.
Web Fetch and Web Search
Two independent toggles: Web Fetch lets OrbySystems read a specific web page you point it at, and Web Search lets it search the web for titles, links, and snippets. Both are off unless you turn them on.
Search providers
With Web Search enabled, choose which provider(s) to use — DuckDuckGo (no API key needed), or Brave, Tavily, Perplexity, or a self-hosted SearXNG instance (each configured with its own API key or URL).
Network and caching
An optional proxy applies to every provider. Search results are cached so repeated queries don't re-fetch. The similarity threshold controls how close a new query must be to an earlier query before OrbySystems reuses the cached result; higher values are stricter. Clear the cache from this page if you want the next search to pull fresh results.
Sandbox
Where you control the general sandbox OrbySystems uses to run LLM-generated Python safely, without exposing your local files to it. See Sandboxing for the concept, including how this differs from the separate, fully network-isolated sandbox statement parsers always run in (which isn't configurable here — see that page for why).
Allowed hosts
The sandbox blocks all network access by default. If you need it to reach specific external sources — for example, to install a Python library a generated script depends on — add trusted hostnames (or glob patterns) to the allowed list here, one per line.
Saving changes to this list can require rebuilding the sandbox, offered as a separate Save and Rebuild action.