Windows llamabot import issue

[bocekout]

On attempting to import llamabot in a marimo notebook on windows, my notebook hangs and I have to kill the notebook.

Cell output displays

"2025-07-07 10:44:37.344 | DEBUG | llamabot.recorder:store_prompt_version:334 - Storing prompt version for function: default_agentbot_system_prompt
2025-07-07 10:44:37.348 | DEBUG | llamabot.recorder:store_prompt_version:339 - Existing prompt found with hash: 8655a1d1f03e3bf76c79d9b4e1a34b0ec335508f9623b64ae6e2f8fc4d65e600:"

and then the cell continues to run and can't be killed in marimo, I have to end the whole notebook.

[ericmjl]

Hi @bocekout thank you for pinging in! Thanks for your patience as well, I've been out at the SciPy conference.

Would you be kind enough to help me get an order-of-magnitude feel for how long the import takes?

I have a few other hypotheses, but I'm also not quite sure which ones to rule out, so a bit of information could help too:

• Your hardware specs (ARM/Intel? RAM/CPU?)
• Windows version
• A minimal notebook that shows the failure

Would you be able to share that information please?

[ericmjl]

Thanks for providing those additional details! This helps narrow down the issue significantly.

Summary of New Information

Hardware & OS:

• Intel Core i9 Mac
• Windows 11

Issue Specifics:

• The hanging occurs specifically in Marimo online (not local Marimo)
• LlamaBot imports successfully in other environments (Jupyter, etc.)
• The hang happens after the second debugging statement but before the third
• The cell becomes unkillable and requires terminating the entire notebook
• Machine memory/performance is otherwise unaffected

Key Insight

This appears to be a Marimo online-specific issue rather than a general LlamaBot import problem, since you've confirmed LlamaBot works in other environments.

Next Steps

1. Environment isolation: Can you confirm if local Marimo (not online) also has this issue?
2. Marimo version: What version of Marimo online are you using?
3. Debug logs: Are there any network requests or console errors visible in browser dev tools when the hang occurs?

This suggests the issue might be related to how Marimo online handles certain imports or network requests that LlamaBot makes during initialization, rather than a core LlamaBot compatibility issue.

@marimo-team might have insights into why certain imports would hang in the online environment specifically.

[ericmjl]

Additional Performance Context

Just got some more specific timing data that helps illustrate the severity:

Environment Details:

• Windows machine with 16GB RAM
• uv-based virtual environment
• llamabot 0.12.11

Import Performance Comparison:

• Jupyter notebook: completes in 3.9 seconds
• Marimo notebook: takes >2 minutes (often hangs completely)

Test Case:

• Notebook contains only:
• No other code or dependencies

This 30x+ performance difference (3.9s vs >120s) between Jupyter and Marimo strongly suggests there's something specific about how Marimo handles the import process that's causing the dramatic slowdown.

The fact that it's the same environment, same Python version, same llamabot installation, but vastly different performance between notebook interfaces points to a Marimo-specific issue rather than a general import problem.