Pulse Today shows a disabled [modules] entry as an HTTP 404 error in Blockers

Open Beginner friendly
#2,817 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, typescript
Domain
api, backend

Research direction

Start at LIFEOS/PULSE/modules/today.ts:642 and read getJson, unavailableFrom and the per-module probe loop that feeds the Today aggregator, then find where resolveModules decides a module is off from [modules] in PULSE.user.toml. Pick one of the two suggested fixes and keep it in one place. Done looks like the repro's negative control passing: curl -s 'http://localhost:31337/api/today?fresh=1' | jq .errors has no HTTP 404 entry for a disabled module, while an enabled module still surfaces real errors.

Written by the indexing model from the issue text.

Description

Version

LifeOS 8.761.0 · attestation: 3 system file(s) differ from danielmiessler/[email protected]:

  • LIFEOS/TOOLS/models.ts
  • LIFEOS/TOOLS/model-pricing.json
  • LIFEOS/DOCUMENTATION/ARCHITECTURE_SUMMARY.md
What is broken

When a Pulse module is switched off in USER/CONFIG/PULSE.user.toml under [modules] (for example vigil = false or work = false), its API route stops answering and returns HTTP 404. The Today page's aggregator (/api/today) does not recognise that as "module off": getJson only maps a body with available: false or setup_required: true to an unavailable source, so a plain 404 falls through to throw new Error(...). The result is a red error line in the Blockers panel ("/api/work → HTTP 404 · /api/vigil → HTTP 404") for a module the user deliberately disabled. The [modules] comment in PULSE.toml says disabling a module hides its tab instead of leaving an empty page; Today should treat a disabled module the same way (skip it, or show the designed not-installed state), not as a failure.

Where (file:line)

LIFEOS/PULSE/modules/today.ts:642

Repro on a clean tree
1. On a v8.761.0 install with Pulse running, add `vigil = false` under `[modules]` in `LIFEOS/USER/CONFIG/PULSE.user.toml`.
2. Restart Pulse: `launchctl kickstart -k gui/$(id -u)/com.lifeos.pulse`.
3. `curl -s 'http://localhost:31337/api/today?fresh=1' | jq .errors` shows `{"vigil": "/api/vigil → HTTP 404"}`.
4. Open Pulse → Today: the Blockers panel shows the red error line.

Negative control: the captured probe exits 1 because `.errors` contains an HTTP 404 entry for the disabled module.
Negative control

Probe: out=$(curl -s --max-time 30 'http://localhost:31337/api/today?fresh=1'); echo "$out" | jq -c .errors; echo "$out" | jq -e '[(.errors // {})[] | select(test("HTTP 404"))] | length == 0' >/dev/null · exit 1 · captured 2026-11-15T07:42:54.539Z

Red looks like: /api/vigil → HTTP 404

{"work":"/api/work → HTTP 404","vigil":"/api/vigil → HTTP 404"}
Suggested fix

Two possible places, maintainer's choice: (a) have a disabled module's routes answer { available: false, reason: "module disabled" } instead of 404, which unavailableFrom already handles; or (b) in modules/today.ts skip the probe for any module that resolveModules reports as off, so it never reaches getJson.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.