Skip to content

Document Codex relay reply window #99

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

Draft
alexfrmn wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Document Codex relay reply window #99

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 17 additions & 2 deletions docs/codex-mac-wake-relay.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ The Mac peer config needs these wake fields:
"dataDir": "/Users/alex/.local/share/mur-mur-v2/.data-codex-mac-kovalyaevo",
"storePath": "/Users/alex/.local/share/mur-mur-v2/.data-codex-mac-kovalyaevo/murmur.db",
"relayFinalToMurmur": true,
"replyTimeoutMs": 180000
"replyTimeoutMs": 600000
}
}
}
Expand Down Expand Up @@ -150,7 +150,22 @@ ssh -T agent-command-center \

## Last Known Good Verification

Final smoke after the relay fix:
Reply-window smoke on 2026-08-06:

- Conversation: `codex:wake:reply-timeout-smoke-20260806T0818Z`
- Mac inbound: `376adb3f-ca05-4f9b-988d-9b607007927d`, DB row `110`
- Mac outbound: `8c02926b-5a51-44ad-9b85-0ad91acf29fe`, DB row `111`
- Evidence: outbox `acked` on attempt `1`; server DB received the reply in row
`4734`
- DORFA canary receipt: `6433daaf-c7b0-439a-8de0-cdf2b8ec0c4d`, server row
`4735`

The 600-second window was introduced after a five-minute ontology canary
completed successfully but the former 180-second reply monitor reported a false
timeout. The new value changes reply collection only; the shared NATS broker was
not restarted.

Previous final smoke after the relay fix:

- Inbound from server/JARVIS:
`68e84b1c-0db9-4293-9ee0-c9b9599d12f3`
Expand Down
Loading