Code Interpreter / Advanced Data Analysis: What It Can And Can't Do

Code Interpreter looks magical and is genuinely useful, but it runs in a sandbox with real limits. Knowing those limits saves hours of stuck-in-a-loop debugging. What is actually happening when ChatGPT runs code Code Interpreter (also known as Advanced Data Analysis) is a Python sandbox running on OpenAI's servers.

10 min · Reviewed 2026

What is actually happening when ChatGPT runs code

Code Interpreter (also known as Advanced Data Analysis) is a Python sandbox running on OpenAI's servers. The model writes code, executes it, sees the output, and iterates. You get the equivalent of a junior data analyst with read-only access to the files you upload. The model cannot reach the open internet from inside the sandbox.

Things it does brilliantly

Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
Generating charts from a dataset and iterating on them ('make the bars sorted, add labels').
Converting between file formats — PDF to text, Excel to CSV, image to text via OCR libraries.
Running statistical tests when you describe the question in plain English.
Writing and testing one-off Python scripts before you copy them into your own environment.

Things it cannot do

Reach the public internet from inside the sandbox — no API calls, no scraping.
Persist files across separate conversations — the sandbox is reset.
Run very long jobs — there are wall-clock timeouts in the tens of seconds for any single execution.
Install arbitrary packages — only what is in the pre-installed environment, though the set is large.
Process huge files — practical limits depend on tier, but assume a few hundred MB ceiling, often less.

Task	Right tool	Why
Quick exploratory analysis of a 5MB CSV	Code Interpreter	Fastest path from question to chart
Scheduled daily ETL job	Real Python on your infra	Sandbox is interactive only
Calling a paid API mid-analysis	Real Python	No outbound network in the sandbox
A 10GB log file analysis	Local DuckDB or cloud notebook	Too big for the sandbox
One-off chart for a slide deck	Code Interpreter	Iterating with the model is faster than tweaking matplotlib by hand

Applied exercise

Find a CSV you have been meaning to look at — anything with at least 5 columns and 1000 rows.
Upload it and ask: 'What are the three most surprising things in this data?'
Ask to see the code for the most interesting answer.
Verify one number by hand. Note where the model's framing of a column was off, if it was.

The big idea: Code Interpreter is a fast scratchpad, not a production runtime. Use it to think with data, then port the logic out.

End-of-lesson check

10 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openai-code-interpreter-creators

What is the main idea of "Code Interpreter / Advanced Data Analysis: What It Can And Can't Do"?
1. Code Interpreter looks magical and is genuinely useful, but it runs in a sandbox with real limits.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Code Interpreter / Advanced Data Analysis: What It Can And Can't Do"?
1. sandbox
2. Code Interpreter
3. Python
4. file analysis
Which use of AI fits this topic best?
1. Reach the public internet from inside the sandbox — no API calls, no scraping.
2. Let the AI decide what matters without your review
3. Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
4. Use the answer before checking whether it fits the situation
Which limitation should you watch for in this topic?
1. Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
2. Explain the topic in plain language
3. Organize a draft for human review
4. Reach the public internet from inside the sandbox — no API calls, no scraping.
What should a careful learner remember about "Ask to see the code"?
1. Use AI to draft or organize ideas about Code Interpreter, then verify before acting.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about Code Interpreter be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about Code Interpreter.
Which action would help you apply "Code Interpreter / Advanced Data Analysis: What It Can And Can't Do" responsibly?
1. Persist files across separate conversations — the sandbox is reset.
2. Use the tool to avoid thinking through the tradeoff
3. Keep going even if the output conflicts with a trusted source
4. Generating charts from a dataset and iterating on them ('make the bars sorted, add labels').
Which choice is a bad use of AI for this lesson?
1. Persist files across separate conversations — the sandbox is reset.
2. Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
3. Ask for a plain-language explanation of sandbox
4. Compare the answer with a trusted source

← Back to interactive lesson

Tendril · Creators · Model Families

Code Interpreter / Advanced Data Analysis: What It Can And Can't Do

10 min · Reviewed 2026

What is actually happening when ChatGPT runs code

Things it does brilliantly

Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
Generating charts from a dataset and iterating on them ('make the bars sorted, add labels').
Converting between file formats — PDF to text, Excel to CSV, image to text via OCR libraries.
Running statistical tests when you describe the question in plain English.
Writing and testing one-off Python scripts before you copy them into your own environment.

Things it cannot do

Reach the public internet from inside the sandbox — no API calls, no scraping.
Persist files across separate conversations — the sandbox is reset.
Run very long jobs — there are wall-clock timeouts in the tens of seconds for any single execution.
Install arbitrary packages — only what is in the pre-installed environment, though the set is large.
Process huge files — practical limits depend on tier, but assume a few hundred MB ceiling, often less.

Task	Right tool	Why
Quick exploratory analysis of a 5MB CSV	Code Interpreter	Fastest path from question to chart
Scheduled daily ETL job	Real Python on your infra	Sandbox is interactive only
Calling a paid API mid-analysis	Real Python	No outbound network in the sandbox
A 10GB log file analysis	Local DuckDB or cloud notebook	Too big for the sandbox
One-off chart for a slide deck	Code Interpreter	Iterating with the model is faster than tweaking matplotlib by hand

Applied exercise

Find a CSV you have been meaning to look at — anything with at least 5 columns and 1000 rows.
Upload it and ask: 'What are the three most surprising things in this data?'
Ask to see the code for the most interesting answer.
Verify one number by hand. Note where the model's framing of a column was off, if it was.

The big idea: Code Interpreter is a fast scratchpad, not a production runtime. Use it to think with data, then port the logic out.

End-of-lesson check

10 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openai-code-interpreter-creators

What is the main idea of "Code Interpreter / Advanced Data Analysis: What It Can And Can't Do"?
1. Code Interpreter looks magical and is genuinely useful, but it runs in a sandbox with real limits.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Code Interpreter / Advanced Data Analysis: What It Can And Can't Do"?
1. sandbox
2. Code Interpreter
3. Python
4. file analysis
Which use of AI fits this topic best?
1. Reach the public internet from inside the sandbox — no API calls, no scraping.
2. Let the AI decide what matters without your review
3. Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
4. Use the answer before checking whether it fits the situation
Which limitation should you watch for in this topic?
1. Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
2. Explain the topic in plain language
3. Organize a draft for human review
4. Reach the public internet from inside the sandbox — no API calls, no scraping.
What should a careful learner remember about "Ask to see the code"?
1. Use AI to draft or organize ideas about Code Interpreter, then verify before acting.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about Code Interpreter be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about Code Interpreter.
Which action would help you apply "Code Interpreter / Advanced Data Analysis: What It Can And Can't Do" responsibly?
1. Persist files across separate conversations — the sandbox is reset.
2. Use the tool to avoid thinking through the tradeoff
3. Keep going even if the output conflicts with a trusted source
4. Generating charts from a dataset and iterating on them ('make the bars sorted, add labels').
Which choice is a bad use of AI for this lesson?
1. Persist files across separate conversations — the sandbox is reset.
2. Cleaning and exploring CSV / Excel data — pivot tables, joins, summary stats.
3. Ask for a plain-language explanation of sandbox
4. Compare the answer with a trusted source

← Back to interactive lesson