Conversation
MrXnneHang
force-pushed
the
refactor/issue-626-shared-schedule-prompt
branch
from
August 11, 2026 03:36
b424d47 to
3cbc650
Compare
Select platform-specific bridging task guides for Claude Code, Cursor, and Hermes while leaving native and generic hosts unchanged. Add focused Windows/Unix selection coverage without changing scheduler behavior. Closes NevaMind-AI#626 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
MrXnneHang
force-pushed
the
refactor/issue-626-shared-schedule-prompt
branch
from
August 11, 2026 03:43
3cbc650 to
3a9aa8c
Compare
Collaborator
|
not ready yet. 这个 PR 大概率会沉底到 codex OS scheduler 完成后才接着写。 |
This branch has not been deployed
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.
📝 Pull Request Summary
Split the Agent-facing bridging scheduler guides by OS for Claude Code, Cursor, and Hermes, so each agent sees only the registration flow that applies to its current platform.
Closes #626.
✅ What does this PR do?
BRIDGING_TASK.windows.mdandBRIDGING_TASK.unix.mdfor the three OS-scheduled hosts.docs taskselect the platform-specific resource, including its remote-doc URL and cache key.🤔 Why is this change needed?
The combined guides exposed both complete registration paths at once. Windows agents saw cron, launchd,
bridge.sh, and Unix PATH setup, while Unix agents saw Task Scheduler, S4U, PowerShell, andschedule install. This widened the decision surface and made selecting an inapplicable registration path more likely.Related issue: #626.
🔍 Type of Change
✅ PR Quality Checklist
feat:,fix:,docs:,memory base:)📌 Optional
Follow-ups remain intentionally out of scope: pipeline-prompt deduplication (#628) and wrapper-contract discussion (#629).
Verification:
uv run pytest tests/test_scheduling_windows.py tests/test_bridging_self_sessions.py tests/test_cursor_self_sessions.py tests/test_events.py -k \"scheduling_windows or bridging_self_sessions or cursor_self_sessions or only_the_install_guide_reports_an_attempt\"— 63 passeduv run ruff check ...— passeduv run mypy ...— passeddocs taskCLI smoke tests passed.🤖 Generated with Claude Code