Usage, Router & Proxy Profiles
Locus makes routing decisions inspectable without silently moving work to a paid or less-private provider.
Usage & Costsโ
Open the sidebar menu and choose Usage & Costs. Filter the local run history by 7, 30, or 90 days, or view all recorded activity. The dashboard groups token activity by agent, model, provider, and workspace and links expensive runs back to the Runs inspector.
Costs are estimates based on the rates saved on agent profiles. Local Ollama usage is shown as $0. Solo rows record tokens; without an explicit rate they do not invent a dollar amount. The dashboard is not a provider bill.
Model Routerโ
The Router inspector compares eligible routes across:
- quality;
- reliability;
- privacy;
- latency;
- estimated cost; and
- model footprint.
The scorecard uses bounded candidate metadata and task tags. Prompt text is not sent to the scorecard endpoint. Hosted routes remain ineligible until separately allowed, and explicit teams keep their own route and budget rules.
Solo collaboration can use reusable research helpers and isolated coding helpers. Helpers inherit the selected provider, account, model, and reasoning settings. The coordinator remains responsible for review and combined validation; simple tasks can finish without delegation. Grill is a guided interview and does not modify the project.
Proxy profilesโ
The Proxies inspector manages named HTTP, HTTPS, and SOCKS5 profiles. Assign profiles by traffic class, workspace, or provider, then choose strict tunnel and automatic failover behavior.
Health checks report latency and the externally observed exit address. With failover enabled, Locus checks the pool every minute and selects the fastest healthy standby. Strict tunnel mode ignores custom bypass entries and blocks external traffic when no configured route is available.
Loopback services and the configured Ollama host remain direct so Locus can reach its own runtime. Proxy rules apply to Locus, not to every app on the Mac.