What does your feature entail? What is it for? How will it affect existing workflows or user experience?
Right now, one global toggle decides whether threads are temporary or permanent. I would love a per-folder setting that overrides the global default, so each folder can have its own retention behavior. It would make managing threads much easier.
It would not change any workflows. This would be opt-in type behavior.
What are the exact ways that you see a user using your proposed feature? Please go into as much detail as possible, and provide examples of how other browsers/apps implement this feature, if applicable. If your feature suggestion adds on to an existing feature, how would it work into it to extend its usefulness?
People use different folders for very different things, so one setting for everything doesn't work well. Some examples:
- Temporary by default, but keep some folders: My global setting is 24 hours, but threads in "Work" or "Recipes" are kept automatically.
- Permanent by default, with a scratch folder: A "Quick Questions" folder deletes its threads after 24 hours, so they don't clutter the sidebar.
- Short projects. A "Trip Planning" or "Job Search" folder set to 30 days, or a "Debugging" folder set to 7 days. Threads stay available while the project is active and then clean themselves up.
How it would fit into what already exists
- Each folder gets a setting: Use global default, Temporary (24h / 7d / 30d), or Permanent.
- A thread's own setting beats its folder's setting, and a folder's setting beats the global one. The global toggle stays as the default, and the "make permanent" option on a single thread still works.
- Threads started in a folder, or moved into one, use that folder's setting. Moving a permanent thread into a temporary folder asks for confirmation first.
- This builds on the earlier "auto-mark threads permanent when added to a folder" request.