Skip to content

refactor(hosts): isolate scheduler guides by OS - #635

Open
xnne-bot wants to merge 1 commit into
NevaMind-AI:mainfrom
XnneHangLab-Mirror:refactor/issue-626-shared-schedule-prompt
Open

xnne-bot wants to merge 1 commit into
NevaMind-AI:mainfrom
XnneHangLab-Mirror:refactor/issue-626-shared-schedule-prompt

Conversation

@xnne-bot

Copy link
Copy Markdown
Contributor

📝 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?

  • Adds BRIDGING_TASK.windows.md and BRIDGING_TASK.unix.md for the three OS-scheduled hosts.
  • Makes docs task select the platform-specific resource, including its remote-doc URL and cache key.
  • Keeps the existing Windows Task Scheduler and Unix cron/launchd implementations unchanged.
  • Preserves native-scheduler and generic host behavior; generic only updates a link to the renamed Claude Code Unix guide.
  • Adds focused Windows/Linux/macOS selection, platform-isolation, prompt-parity, cron-line-length, and wrapper-marker coverage.

🤔 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, and schedule install. This widened the decision surface and made selecting an inapplicable registration path more likely.

Related issue: #626.


🔍 Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Refactor / cleanup
  • Other (please explain)

✅ PR Quality Checklist

  • PR title follows an allowed format (for example feat:, fix:, docs:, memory base:)
  • Changes are limited in scope and easy to review
  • Documentation updated where applicable
  • No breaking changes (or clearly documented)
  • Related issues or discussions linked

📌 Optional

  • Screenshots or examples added (if applicable)
  • Edge cases considered
  • Follow-up tasks mentioned

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 passed
  • uv run ruff check ... — passed
  • uv run mypy ... — passed
  • Built wheel contains all six platform guide resources; all three Windows docs task CLI smoke tests passed.

🤖 Generated with Claude Code

@MrXnneHang
MrXnneHang force-pushed the refactor/issue-626-shared-schedule-prompt branch from b424d47 to 3cbc650 Compare August 11, 2026 03:36
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
MrXnneHang force-pushed the refactor/issue-626-shared-schedule-prompt branch from 3cbc650 to 3a9aa8c Compare August 11, 2026 03:43
@MrXnneHang

MrXnneHang commented Aug 12, 2026 •

Copy link
Copy Markdown
Collaborator

not ready yet.

这个 PR 大概率会沉底到 codex OS scheduler 完成后才接着写。

This branch has not been deployed

No deployments
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.

[REFACTOR] Isolate OS-specific bridging scheduler instructions

2 participants