Skip to main content
This agent gets a CSV file, works on it with Python in a managed sandbox, and writes a Markdown report. It computes every number with code instead of estimating, and the sandbox has no internet access, so the data stays put. You will use: a managed sandbox and files and artifacts.
A managed sandbox uses machine time while it runs and needs your plan’s minimum balance of Orca credit in your wallet.

How it works

The instructions name the input folder, the output paths, and the report’s sections. Specific paths are what make the files show up as artifacts.

The program

Examples on this page assume the settings from the shared setup. It uploads sales.csv from the current folder, so make one first, or point it at your own file.
You get analysis-output/report.md and analysis-output/analysis.py. The script lets you rerun or check the analysis yourself.

Make it yours

  • Ask follow-ups in the same session. The sandbox keeps its files between turns, so “Now split it by region” builds on the work already done. Each turn’s outputs become new artifacts.
  • Add libraries. To use pandas or plotting, list them under packages in the environment, for example {"python": ["pandas", "matplotlib"]}, set network access to enabled so they can be installed, and ask for charts saved as PNG files in /workspace/outputs. See configure the sandbox.
  • Reuse the setup. If many sessions need the same packages and files, save them once as an environment template.
  • Treat outputs as untrusted. The report was written from your data, but read it before you send it on, and do not run scripts it produced without reviewing them.