[FEATURE] : Organize routines into user-defined groups
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
What problem are you trying to solve?
As I create more routines, the list at claude.ai/code/routines becomes hard to work with. Every routine shows up in one flat list identified only by its name, so there's nothing that tells me which routines belong to which project.
Why do you need this feature?
In my workflow I run several routines against the same repository.
For example, one routine watches a repo for changes and another acts on what it finds, so they only make sense as a pair tied to that repo.
I also have routines pointed at completely different repositories.
When I open the routines page to check status, re-run one, or edit it, I have to visually scan every routine and mentally match it back to its project.
With only a handful of routines this is already awkward, and it clearly gets worse as the number grows and as more teammates add their own.
The core problem is that there's no notion of which project a routine belongs to in how the list is presented, even though each routine already targets a specific repository.
I need to be able to look at my routines organized by the project they serve, so I can quickly find and manage the ones related to a given repo instead of parsing a long undifferentiated list.
Proposed Solution
I'd like to be able to create my own named groups and put routines into them, then have the routines list displayed grouped by those names.
Ideal experience:
- I can create a group and give it any name I want (for example "Docs" or "Nightly jobs").
- When creating or editing a routine, I pick which group it belongs to (and I can move a routine to a different group later).
- On the routines page, routines are shown under their group's name as collapsible sections, so everything in the same group sits together instead of in one flat list.
- Ungrouped routines just appear under a default "Ungrouped" section.
- The naming is fully up to me, so I decide how to organize them rather than relying on any fixed or automatic category.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_