Tracking: Session Limits + Codex Persistence and Signaling

[Camaraterie]

✨ Summary
Standardizes session-limit detection and surfacing, improves local/remote session signaling, and adds tests for Codex flows and session persistence. Tracks PRs #26 and #27 to land the full set safely.

🐛 Context

• Users hit Claude’s hourly and 5-hour session limits without clear signaling.
• Session state needed better persistence and verification across runs.
• Goal: clearer, test-backed behavior with cross-platform confidence.

🧰 Scope

• Session limit detection and alerting via scanner + app event.
• Metadata/state update refinements and usage reporting.
• Codex/MCP client tweaks and more robust test coverage.

🔗 Linked PRs

• Codex session fixes: persistence, metadata.flavor, and comprehensive testing - more incoming #26
• Fix/voice naming (calling codex -> claude repeatedly) and session limit (had no indicator for claude session limit) #27

🔧 Changes (high-level)

• src/claude/utils/sessionScanner.ts: Detects “hour limit reached” and “5-hour limit” assistant messages; emits callback.

• src/api/apiSession.ts: Adds sendSessionLimitAlert() to notify the app; usage reporting; metadata/state update refinements.

• src/claude/claudeLocalLauncher.ts: Wires session-limit detection to app alert.

• Codex: Minor updates in src/codex/codexMcpClient.ts and src/codex/runCodex.ts.

• Tests: sessionLimitDetection.test.ts, codexMcpClient.test.ts, integration.test.ts, sessionPersistence.test.ts, simpleFixVerification.test.ts.

• Misc: Small updates in src/daemon/run.ts. .gitignore now matches main.

• Reference commit: 0805e3a.

✅ Success Criteria

• App logs clear session-limit events and emits session_limit_alert.
• All added tests pass locally and in CI.
• Verified behavior on Windows/macOS to catch watcher quirks.

🧪 How To Test

• Unit: run pnpm test or yarn test — verify all suites pass.
• Manual:

1. Run a Claude session.
2. Simulate a limit message in the session JSONL.
3. Confirm the app logs [SESSION_LIMIT] and receives a session_limit_alert event.

Expected log snippet

text [SESSION_LIMIT] hour limit reached (emitted via session_limit_alert)

⚠️ Impact / Risks

• Low risk; changes localized to scanning/alerts and Codex tests.
• Watch for file-watcher differences across platforms.

☑️ Checklist

• Session-limit alert emits and is logged
• Tests green locally and on CI
• Cross-platform sanity check (Windows/macOS) [ran in WSL ✅ ]
• PRs Codex session fixes: persistence, metadata.flavor, and comprehensive testing - more incoming #26 and Fix/voice naming (calling codex -> claude repeatedly) and session limit (had no indicator for claude session limit) #27 linked to this issue

🔮 Follow-ups

• Consider an in-app banner or retry guidance for limit events.
• Decide on telemetry for limit events (opt-in, privacy-reviewed).

[Camaraterie]

I struggle to actually read what my own bots make sometimes.
Essentially:
Issues were:

• codex crashes if you deny a command, like full session crash and unrecoverable
• Happy calls codex claude
• if session was started remotely (via app or web), it always started as claude even if codex was selected
• no limit message when at limit for claude, he just stops responding and you don't know if something is actually broken or if you're at limit (I thought this used to work but it hasn't worked for me for awhile)

Edit: sorry didn't mean to close this! lol

[bra1nDump]

First of all, thank you for your contributions!

Sorry, we did not get to reviewing your changes sooner. I believe at this time most all the issues you raise, other than the limit reaching issue are solved. Not sure what happens currently if we reach the limit.

I want to close the PRs because I think they are stale at this point with these prs addressing parts of what you accomplished here:

• fix: preserve conversation context across mode changes (#143) #37
• Fix Codex sessions hanging after task completion #32

Let me know if you are ok with closing the prs. Maybe we can open a new one to address the running out of 5 hour quota issue?