[FEATURE] Team/Enterprise: shared routines (org-owned scheduled agents)
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
Routines (scheduled remote agents) are currently tied to individual accounts. In a team setting, routines often serve the whole team (e.g., daily Slack summaries, automated PR checks). If the creator leaves the team, those routines become inaccessible breaking workflows the rest of the team depends on. There's no way to transfer or share ownership.
Proposed Solution
Allow routines to be optionally marked as "team-owned" so that:
- Any team admin can view, edit, enable/disable, or delete them
- They survive individual account removal
- Ownership can be transferred between team members
- They appear in a shared "Team Routines" section alongside personal ones
Alternative Solutions
- Each team member recreates the same routine on their own account (duplicates effort and usage quota)
- Move automation to GitHub Actions or external CI (loses the Claude Code integration benefits). Those integrations won't work without an API key.
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
- I'm on a team account.
- I create a daily routine that reads #team-alerts Slack channel and posts a summary to #team-internal
- The whole team relies on this daily digest
- If I leave the org, the routine disappears and no one can recreate it without knowing the exact config
- With team-shared routines, an admin could take over or the routine would simply continue running under the org
Additional Context
This becomes increasingly important as teams scale and build more routines into their workflows. Similar to how GitHub Actions belong to a repo (not a user), routines that serve a team should optionally belong to the team.
Environment Info
- Platform: linux
- Terminal: konsole
- Version: 2.1.109
- Feedback ID: 6a72c8c4-8928-46c6-9574-e59065a0da4e
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗