Add Configuration Option to Change Session TTL

[vanshitkumar]

Description

Currently, Marimo sets a constant session TTL of 120 seconds (TTL_SECONDS = 120) in the run mode. This is hardcoded and cannot be adjusted by users. While this may work for most scenarios, it poses a challenge for long-running operations in data apps, which may exceed the default TTL and result in session timeouts.

I would like the ability to configure the session TTL for run mode through the runtime configuration part of the UI to better accommodate the requirements of my data app.

The relevant code defining the current TTL can be found here.

Suggested solution

1. Add a configuration option for session TTL in the runtime configuration section of the Marimo User settings UI, allowing users to specify the session TTL for run mode interactively.
2. Ensure the UI input validates the TTL value to be a positive integer (in seconds).
3. Update the session handling code to fetch and apply this runtime-configured TTL value.
4. Provide a fallback to the default value (120 seconds) if no value is configured.
5. Document the new feature, explaining how to set the TTL through the runtime configuration UI and the scenarios it addresses.

This approach enhances user experience by making the configuration more accessible and dynamic without requiring manual file edits or environment variable changes.

Alternative

No response

Additional context

No response

[akshayka]

Thanks for the feature request! We can make the TTL configurable via a CLI argument to marimo run.

[vanshitkumar]

@akshayka Thanks for considering the feature! A CLI argument sounds great and would work well for configuring the TTL dynamically when running Marimo. Looking forward to seeing this implemented!

[akshayka]

@vanshitkumar , version 0.10.10 has been released including this feature. Hope it helps!