Skip to content

[codex] Add friendly scheduled task templates to public plugins#382

Draft
abhinav-oai wants to merge 1 commit into
mainfrom
codex/friendly-scheduled-tasks-public-20260709
Draft

[codex] Add friendly scheduled task templates to public plugins#382
abhinav-oai wants to merge 1 commit into
mainfrom
codex/friendly-scheduled-tasks-public-20260709

Conversation

@abhinav-oai

@abhinav-oai abhinav-oai commented Jul 9, 2026

Copy link
Copy Markdown

Summary

Adds one weekday scheduled-task template to each plugin whose canonical source is openai/plugins, using the friendlier task titles from the scheduled-tasks UX feedback. This is the public-source half of the replacement for the stale combined draft openai/plugins#366; the maintained-source half is openai/oai-maintained-plugins#356.

The stable template filenames, prompts, and schedules are unchanged from the reviewed combined draft. Only the user-visible name values were made friendlier, and every affected manifest receives a patch bump so the new templates can ship.

Plugin New task title Version bump
Asana Daily task update 0.1.40.1.5
Canva Daily design follow-ups 1.0.21.0.3
ClickUp Daily task update 1.0.31.0.4
Datadog Morning service update 0.1.20.1.3
GitHub Daily PR update 0.1.60.1.7
Granola Today's meeting follow-ups 1.0.31.0.4
Linear Daily issue update 0.0.30.0.4
Supabase Daily backend update 0.1.100.1.11
Vercel Daily deployment update 0.21.30.21.4

Why this split

The live global plugin registry maps these nine plugin IDs to openai/plugins. The other eleven scheduled-task plugins now map to the maintained source, so they should not be added here.

Validation

  • Parsed every new scheduled JSON file with jq and checked the staged diff with git diff --check.
  • Compared all 20 replacement templates across both split branches against the old draft after removing only .name: 20/20 are identical (same prompt and schedule).
  • Confirmed this PR contains exactly nine new scheduled files and nine manifest version edits, with no unrelated files.
  • cloud-plugin-admin is not installed in this local workspace, so the publisher-side validator still needs to run in the normal release environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant