Is TurenOS a sandbox?
No. Approved tools execute with your user privileges. Use a VM, container, or disposable account for hostile code.Which agent providers are supported?
Claude Code subscriptions and OpenAI Codex OAuth are supported, alongside API-key and custom-endpoint providers. Availability depends on the connected server and installed provider integrations. TurenOS permissions remain the execution boundary regardless of provider.Why do files and commands still use forge?
TurenOS is a hard fork with compatibility-sensitive identifiers. The CLI, configuration paths, protocol values, and some bundle IDs retainforge names so existing data and integrations continue to work.
Do Desktop users need the forge runtime downloads?
No. Desktop installers contain the correctforge-cli sidecar. Standalone forge-* archives are for CLI, server, shell-installer, and npm use.
Where is my data stored?
See Data locations. Sessions and credentials are local by default, but provider and integration requests can leave the machine.Can I use a subscription instead of an API key?
The Claude Code provider can use an existing localclaude auth login. Other providers expose API-key, OAuth, device-login, or custom endpoint flows according to their capabilities.