Workflows inventory flags the workflows-dispatcher (the Workflows clock) as an orphan
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 80/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- tooling
Research direction
Read LIFEOS/WORKFLOWS/Inventory.ts around line 161, where the orphan finding is raised, and compare it with outsideWorkflows(), which already skips the dispatcher via WORKFLOWS_CLOCK_ID. Then choose between adding an always-on dispatcher row to the Services.ts registry or adding the same id exemption to the orphan condition. Done means bun ~/.claude/LIFEOS/WORKFLOWS/Workflows.ts attention no longer prints the "installed without a declaration" line while other orphan findings still work.
Written by the indexing model from the issue text.
Description
Version
LifeOS 8.761.0 · attestation: not run
What is broken
The Workflows inventory raises a medium-severity orphan finding, "workflows-dispatcher is installed without a declaration", for com.lifeos.workflows-dispatcher on every install that schedules local workflows. WorkflowsSystem.md names the dispatcher as the one exemption ("the Workflows clock"), and outsideWorkflows() already skips it via WORKFLOWS_CLOCK_ID, but the orphan check does not: the dispatcher is not in the Services.ts registry, so declared is false and it is flagged. The Pulse Workflows page therefore always shows one attention item the user cannot resolve, and acknowledging it is the only way to quiet it.
Where (file:line)
LIFEOS/WORKFLOWS/Inventory.ts:161
Repro on a clean tree
1. On a v8.761.0 install, have at least one local workflow with a schedule or interval trigger, so `com.lifeos.workflows-dispatcher` is loaded (`launchctl list | grep workflows-dispatcher`).
2. Run `bun ~/.claude/LIFEOS/WORKFLOWS/Workflows.ts attention`.
3. The list contains "workflows-dispatcher is installed without a declaration. (launchd:com.lifeos.workflows-dispatcher)".
Negative control: the captured probe exits 1 because that line is present.
Negative control
Probe: bun $HOME/.claude/LIFEOS/WORKFLOWS/Workflows.ts attention | grep 'workflows-dispatcher'; ! bun $HOME/.claude/LIFEOS/WORKFLOWS/Workflows.ts attention | grep -q 'workflows-dispatcher is installed without a declaration' · exit 1 · captured 2026-11-15T07:44:48.517Z
Red looks like: workflows-dispatcher is installed without a declaration
! workflows-dispatcher is installed without a declaration. (launchd:com.lifeos.workflows-dispatcher)
Suggested fix
Either declare the dispatcher in the Services.ts registry (an always-on service row), or exempt it in the orphan check the same way outsideWorkflows() does: add && r.id !== WORKFLOWS_CLOCK_ID to the condition at Inventory.ts:161.
Environment
- OS: macOS 26.6.2 (arm64)
- Harness: claude-code
- bun: 1.3.8 · git: 2.39.5
- Doctor broken: none
- Dominant language
- TypeScript
- Stars
- 19.8k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
danielmiessler/LifeOS#2824 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
danielmiessler/LifeOS#2822 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
danielmiessler/LifeOS#2817 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
danielmiessler/LifeOS#2808 ·
Maintainers usually reply within 6 days
All issues in danielmiessler/LifeOS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day