Academy
5. Limits and What OupiBox Cannot Do
Recognise the boundaries of OupiBox — no access to your machine, no cross-user data, session expiry, large-file chunking — and know when to consider alternatives.
OupiBox is powerful, but it operates within clear boundaries. Understanding these limits helps you set realistic expectations and choose the right tool for each job.
No access to your machine. OupiBox runs in an isolated, disposable environment on OUPI's infrastructure — it cannot browse your local folders, launch applications on your desktop, or interact with your operating system in any way. Everything it works with must be explicitly uploaded or attached to the conversation.
No cross-user data. Each sandbox is strictly isolated. OupiBox cannot see files, conversations, or results belonging to other users. Nothing leaks between accounts or sessions.
Sessions expire after inactivity. A sandbox is not a permanent server. Once your task is done — or after a period of inactivity — the sandbox is discarded. Your produced files are safe because they are materialized back into your file space before disposal, but you cannot return to a sandbox later to "resume" where the code left off. Your file space, not the sandbox, is the source of truth.
Large files are processed in parts. If you upload a very large file, OupiBox may need to chunk it and process it in segments rather than loading everything at once. This is normal and handled automatically, but it means some operations on massive datasets may take longer or require the AI to work iteratively.
No persistent, long-running services. OupiBox is designed for task-based execution: process a file, build a document, run a calculation, then return the result. It is not meant to host a web server, run a background job for hours, or act as a permanent execution environment. If you need persistent, local execution that stays running, consider Nexus One as the appropriate alternative.
Restricted internet access. The sandbox does not have open access to the public internet. It works with the files and data you provide, within the boundaries the platform allows.
If a task seems stuck or is taking too long, tell the AI directly — it can change its approach or break the work into smaller steps. The conversation shows live progress so you can follow along and intervene early rather than waiting in silence.
Always think of your OUPI file space as the permanent home for your work. Anything OupiBox produces is materialized there (marked "Materialized by OupiBox · sovereign"). Don't rely on the sandbox itself to store anything — it will be discarded after the task.
Cost awareness. Every OupiBox execution consumes compute-time credits on top of the model's token cost. A quick data cleanup is inexpensive; rendering a long illustrated report with charts and formatting costs more. Costs are shown alongside the message or mission, so you can monitor usage. Knowing the limits helps you plan: break very large jobs into stages, and reserve OupiBox for tasks that genuinely need execution rather than prose.
Open a chat, attach a small file, and ask the AI to process it. Then wait for the session to complete and verify that the output appears in your file space as a materialized card. This confirms you understand the full cycle: upload → sandbox execution → file materialized back → sandbox discarded.
OupiBox is isolated (no access to your machine or other users), temporary (sessions expire, sandbox is discarded), and task-oriented (not for long-running services). Large files are chunked automatically, internet access is restricted, and costs scale with compute time. Your file space is always the source of truth. When you need persistent local execution, look to Nexus One. Knowing these boundaries lets you use OupiBox confidently — and pick the right tool when a task falls outside its scope.