Skip to content

fix: apply saved todo config on next organize - #130

Merged
yujiezhang-ops merged 5 commits into
mainfrom
codex/apply-saved-todo-config
Jun 25, 2026
Merged

yujiezhang-ops merged 5 commits into
mainfrom
codex/apply-saved-todo-config

Conversation

@yujiezhang-ops

Copy link
Copy Markdown
Collaborator

Summary

  • make saved todo extractor config usable on the next organize run without telling users to restart
  • force the next todo extraction after saving config so old no-key/rules checkpoints do not skip sessions
  • cover the save -> organize request path in viewer tests

Root cause

Saving the key was already persisted and read by the backend, but the frontend still told users to restart. More importantly, if a previous organize attempt ran without an LLM key, its checkpoint could make the next non-forced organize skip the same sessions. That looked like the saved key was ignored.

Verification

  • npx vitest run test/viewer-session-id.test.ts
  • node scripts/build-viewer-html.mjs --check
  • npm run build
  • diff/secret scan for API keys

@yujiezhang-ops
yujiezhang-ops merged commit 709da24 into main Jun 25, 2026
4 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