Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] Team/Enterprise: shared routines (org-owned scheduled agents) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48322•Fetched 2026-04-16 07:03:01
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
1
Author
armujahidarmujahid
Participants
armujahidarmujahid
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • 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

  1. I'm on a team account.
  2. I create a daily routine that reads #team-alerts Slack channel and posts a summary to #team-internal
  3. The whole team relies on this daily digest
  4. If I leave the org, the routine disappears and no one can recreate it without knowing the exact config
  5. 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

extent analysis

TL;DR

Implementing team-owned routines would allow for seamless transfer of ownership and prevent workflow disruptions when team members leave.

Guidance

  • Introduce a "team-owned" flag for routines, enabling team admins to manage them.
  • Develop a system for transferring ownership of routines between team members.
  • Create a "Team Routines" section for easy access and management of shared routines.
  • Ensure that team-owned routines survive individual account removal and can be edited or deleted by team admins.
  • Consider implementing role-based access control to restrict access to team-owned routines.

Example

No code example is provided as the issue focuses on the feature request and high-level design.

Notes

The proposed solution requires significant changes to the existing routine management system, including updates to the database schema, API, and user interface. The implementation should consider security and access control to prevent unauthorized access to team-owned routines.

Recommendation

Apply a workaround by implementing team-owned routines, as this would address the core issue of routine ownership and transferability, and prevent workflow disruptions when team members leave.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE] Team/Enterprise: shared routines (org-owned scheduled agents) [1 participants]