Give each cron run its own session, worktree, and inbox timeline#184
Merged
Give each cron run its own session, worktree, and inbox timeline#184
Conversation
Cron runs previously all shared a single threadId (cron-job:{jobId}),
collapsing every execution into one inbox thread and reusing the same
OpenCode session and worktree. Incorporate a per-run id into the
threadId, session key, and worktreeId so each run is fully isolated
with a fresh timeline and working directory.
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
1 participant
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.
Summary
threadId(cron-job:{jobId}), so every execution collapsed into a single inbox thread and reused the same OpenCode session + worktree.Date.now()for manual triggers) into thethreadId, session key, andworktreeIdso each run produces a fresh inbox timeline, a brand-new session, and an independent working directory.cron-job:{jobId}) so the inbox UI can still group runs by cron job viacronJobIdon the thread row.Notes
message_threadrows are naturally keyed by the new unique threadId.bun test packages/core/cron/ packages/config/local/inbox.test.tspasses.