Repository navigation
feat(projects): ask a prompt on a schedule, in a new thread each time or the same one - #605
Merged
Merged
Conversation
… or the same one Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: a project's threads started only when someone asked.
After: a project can ask a prompt on a schedule ("every Monday at 09:00, plan this week's steps"), as a brief answered in the background. Each schedule picks where it asks: a new thread each time, or the same thread, which keeps the conversation going (and skips a run while that thread is still answering the last one, saying so). A schedule can be switched off; an archived project's schedules wait until it's unarchived. On the project's page, Ask on a schedule offers presets (every morning, every weekday, every Monday) or a cron, in your browser's time zone; each schedule shows when it runs in words, its next time, a link to its thread and the last error, with a switch and Remove (with Undo). Agents set them with the MCP tool
schedule_projectand the API.How: each schedule is a timer (
project.schedule, keyproject-{pid}-{sid}) on the existing timers module, re-armed fromschedule.next_afterafter each run and cancelled when switched off, archived or deleted.POST/PATCH/DELETE /api/v1/projects/{id}/schedules[/{sid}]. Schemas are namedProjectSchedule*so they don't collide with the Schedules page's. Last of the projects PRs; listing these on the Schedules page is in "Refine later".Motivation and Context
Adeel asked for projects with scheduled threads as well as ordinary ones, like this Claude project.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.changelog.d/projects.md.Done questions (AGENTS.md)
schedule_projectand the API (test_schedules_wait_while_off_or_archived_and_agents_set_them)..env.test_a_schedule_asks_its_prompt_in_a_new_thread_or_the_same_one,projects.test.tsx, docs/projects.md, docs/mcp.md,make openapi).schedule.next_after/describe, briefs from feat(projects): the coordinator starts threads with a brief, answered in the background #593.Local CI:
ci/local-ci.shpassed the backend, Next.js, pre-commit and title jobs on this change before a clean rebase onto the latest main.Generated by Claude Code