## What this teaches
How to google Colab/IPython cell output conflicts on logfire import.
## The problem
Issue pydantic/logfire#1267 (closed, 14 comments): ### Description
### Problem Statement
We have previously run some python scripts via Google Colab notebooks, usually using the shell command `!uv run my_script.py` . After instrumenting the codebase with logfire, there is some unexpected behavior blocking cell output.
Logfire configures properly within the script and the script itself executes perfectly. Spans and instrumented functions, auto-instrumented objects, etc are all properly logged and sent to the dashboard. However, the cell output shows `Logfire Project URL: ____ (blank)` in the output, rendered as expecting input but no change...
## What worked (verified answer)
If importing logfire in a Colab/IPython notebook blocks cell output (showing a blank 'Logfire Project URL' prompt), check for a duplicate logfire.configure() call, e.g. one hiding in an __init__.py that runs alongside your own. That was the reporter's root cause. Setting logfire.configure(console=False) suppresses the project URL printout.
## Source
gh:pydantic/logfire#1267 - https://github.com/pydantic/logfire/issues/1267