Skip to content

fix(auto-capture): provider order, phase errors, AI session cleanup - #426

Merged
EyJunge1 merged 2 commits into
tickernelz:mainfrom
EyJunge1:fix/425-auto-capture-hardening
Oct 21, 2026
Merged

EyJunge1 merged 2 commits into
tickernelz:mainfrom
EyJunge1:fix/425-auto-capture-hardening

Conversation

@EyJunge1

Copy link
Copy Markdown
Collaborator

Summary

  • Closes #425: add autoCaptureProviderOrder (opencode-first | external-first) so auto-capture can prefer the faster external API when both channels are configured
  • Enrich addMemory / auto-capture failure logs with phase plus name/stack/cause (Stats still buckets on addMemory: error)
  • Call cleanupExpiredSessions() from the existing cleanup cycle so aiSessionRetentionDays actually deletes expired ai_sessions (and cascaded messages)

Test plan

  • bun test (792 pass)
  • bun run typecheck
  • bun run check
  • New coverage: provider order fallback, addMemory phase logging, AI session cleanup hook, serializeError

Checklist

  • Branch is based on main
  • bun test passes
  • bun run typecheck passes
  • bun run check passes
  • Docs / README updated when behavior or contribution process changes

Closes tickernelz#425. Make auto-capture channel order configurable, log capture/persistence failures with phase and stack, and delete expired AI sessions from the existing cleanup cycle.
@EyJunge1
EyJunge1 merged commit f160aa7 into tickernelz:main Oct 21, 2026
7 checks passed
@EyJunge1 EyJunge1 mentioned this pull request Oct 21, 2026
2 of 6 tasks
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.

Auto-capture: configurable provider channel order, phase-level error logging, and expired AI sessions never deleted

1 participant