Skip to content

refactor: nest scheduled tasks under ClaudeAutomation/<member>/ - #52

Merged
cheneeheng merged 1 commit into
mainfrom
refactor/nest-automation-task-folders
Sep 16, 2026
Merged

cheneeheng merged 1 commit into
mainfrom
refactor/nest-automation-task-folders

Conversation

@cheneeheng

Copy link
Copy Markdown
Owner

What

Nest each member's Windows Task Scheduler tasks under \ClaudeAutomation\<member>\ instead of a flat \ClaudeAutomation\ folder.

Why

Keeps task names collision-free and groups every task belonging to a member together, per the scheduled-tasks convention in the root CLAUDE.md.

How

Updated the task-folder path in usage-dashboard-setup.ps1 and agents-workspace-sync-setup.ps1, the registry entries in setup/registry.ps1, and documented the convention in CLAUDE.md and the affected member docs.

Testing

Not run — script changes are path-string edits with no local Task Scheduler environment to exercise them against.

Checklist

  • All CI checks pass
  • Tests added or updated for new behavior
  • No any / @ts-ignore / # type: ignore introduced
  • No secrets or credentials in code
  • Migrations (if any) are backward-compatible
  • ARCHITECTURE.md Key Decisions updated (if a durable decision was made)
  • Attribution included if AI tooling assisted

Generated with Claude Code by CEH

agents-workspace-sync and usage-dashboard now register their tasks in
a subfolder named after the member, matching file-sync and the digests,
so every task of a member is grouped together.

- usage-dashboard drops its one-level COM folder pre-create, which
  fails on a nested path; Register-ScheduledTask creates the folders
- setup/registry.ps1 Detect probes follow the new paths
- root CLAUDE.md scheduled-task convention updated

Existing installs keep the old flat-path task: unregister it before
reinstalling, or the job runs twice.

Generated with [Claude Code](https://claude.com/claude-code) by CEH
@cheneeheng
cheneeheng merged commit caad365 into main Sep 16, 2026
22 checks passed
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