Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: add diagnostic logging for message flow debugging #1244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
oscargavin wants to merge 1 commit into from
Closed

feat: add diagnostic logging for message flow debugging #1244

oscargavin wants to merge 1 commit into from

Conversation

@oscargavin
Copy link

@oscargavin oscargavin commented Jan 19, 2026

Summary

  • Add diagnostic.ts with webhook stats, session state tracking, and heartbeat logging
  • Enhance telegram message processing with request timing and detailed logging
  • Add lane enqueue/dequeue logging to command queue
  • Track active embedded runs with state changes
  • Improve onboarding flow logging for iMessage and Signal
  • Add batch-gemini logging for memory operations

Why

This improves observability for debugging:

  • Message flow issues (where did a message get stuck?)
  • Stuck sessions (which session has been processing for too long?)
  • Performance problems (which webhooks are slow?)
  • Queue depth monitoring (is there a backlog building up?)

Test Plan

  • Service starts and runs without errors
  • Heartbeat logs appear every 30 seconds
  • Message processing logs timing information
  • Stuck session warnings appear after 2 minutes

🤖 Generated with Claude Code

@oscargavin
feat: add diagnostic logging for message flow debugging
475df0a 
- Add diagnostic.ts with webhook stats, session state tracking, heartbeat
- Enhance telegram bot-message.ts with request timing and logging
- Add lane logging to command-queue.ts
- Track active runs in pi-embedded-runner/runs.ts
- Improve onboarding flow logging for iMessage and Signal
- Add batch-gemini logging improvements

This improves observability for debugging message flow issues,
stuck sessions, and performance problems.
@steipete
Copy link
Contributor

steipete commented Jan 21, 2026

Summary of what I changed in this workset:

  • Moved diagnostics emission into the shared dispatch path so all channels get message queued/processed + session state transitions (gated by diagnostics config).
  • Removed Telegram-only diagnostic logging; webhook + heartbeat are now diagnostics-gated.
  • Start/stop diagnostic heartbeat with gateway lifecycle; unref heartbeat interval.
  • Tightened diagnostic event typing; updated dispatch + Telegram tests.

Full gate: pnpm lint && pnpm build && pnpm test (passed).

@steipete steipete mentioned this pull request Jan 21, 2026
Closed
@steipete steipete closed this Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@oscargavin @steipete