← Retour au plan
OupiBox: The Sandbox Behind the AI · Leçon 3 sur 7

3. Files In, Files Out

Trace the full lifecycle of a file — from attachment or file space into the sandbox, through processing, and back as a materialized output card.

Every file you work with in OupiBox follows a clear three-stage lifecycle: In → Process → Out.

In: When you attach a file to your message or select one from your file space, it is uploaded into an isolated, disposable sandbox created just for that task. Nothing runs on your machine — the file lives temporarily inside OupiBox.

Process: Inside the sandbox, the AI executes real code against your file — reading, transforming, calculating, converting formats, extracting data, or building entirely new documents. This is genuine execution, not guesswork.

Out: Everything the AI produces is brought back into your file space and displayed as cards in the conversation, tagged "Materialized by OupiBox." Once the task is done, the sandbox is discarded. Your file space — not the sandbox — is the permanent source of truth.

Getting files in: two paths

You can feed files into OupiBox in two ways:

  1. Direct attachment — drag-and-drop or attach a file directly in the chat message where you describe the task.
  2. File space selection — pick an existing file already stored in your OUPI file space.

Either way, the file is copied into the sandbox environment for the duration of the task. The sandbox is isolated: no other user can see your files, and the environment has no access to your local machine or the open internet beyond what the platform permits. Very large files are handled in parts automatically.

What happens inside the sandbox

Once your file is in, OupiBox does real work — not prose descriptions. The AI can:

• Read and parse spreadsheets, PDFs, text files, and archives • Run calculations, clean data, and apply transformations • Convert between formats (e.g., PDF to text, CSV to Excel) • Build fully formatted Word documents, Excel spreadsheets, PowerPoint decks, and charts

If the task matches a known pattern — like building a professional Word report — OupiBox automatically applies Skills: house-standard procedures that ensure consistent formatting regardless of which AI model is running. You don't need to request them; the AI picks the right ones.

You can follow progress live in the conversation. If something fails, the AI sees the error and retries on its own.

Files out: materialized output cards

When the sandbox finishes, every produced file is materialized — saved back into your OUPI file space and surfaced in the conversation as a downloadable card labeled "Materialized by OupiBox · sovereign."

The sandbox itself is then discarded. This is by design: the sandbox is ephemeral work space, while your file space is the durable record. If you need a file again later, you find it in your file space, not in the sandbox.

This also means sovereignty is maintained throughout: sandboxes run in isolated environments controlled by OUPI with no external provider keys inside, and your files remain in your OUPI file space.

Astuce

Ask for the file, not a description of the file. Instead of "Describe how to format this data," say "Clean this spreadsheet, add a chart, and give me the Excel file." OupiBox will execute the work and hand you a real, downloadable document.

À vous de jouer

Open a Pro chat, attach a small spreadsheet or CSV, and type: "Clean this data, highlight duplicates, add a summary chart, and return the Excel file." Watch the live progress, then check the output card — it should say "Materialized by OupiBox." Open your file space to confirm the file is stored there permanently.

Suivre ce cours dans OUPI → Cet exercice se fait dans la plateforme OUPI.
À retenir

A file's lifecycle in OupiBox has three stages: In (attached or selected from your file space into an isolated sandbox), Process (real code execution — transformations, conversions, document building — with Skills applied automatically for consistent formatting), and Out (materialized as downloadable cards in the conversation and saved to your file space). The sandbox is then discarded; your file space is the source of truth. Sovereignty is preserved end to end, and costs reflect compute time plus tokens.