Artifact pages open once
What changed
Each page opens in the browser once. After that, the agent updates the same page and the open tab reloads itself.
| Before | Now |
|---|---|
| Every render opened a new tab | First page of a session opens; later turns do not |
| Re-render of the same page opened it again | Same page: no new tab; the published tab reloads in place |
--open in the rules forced a tab every turn |
Rules drop --open; the CLI enforces open-once, --open included |
| Plan hook page + a second rendered plan page | The hook's plan page is the plan's page; no second render |
Different page, same session
A page with a different title in the same session does not open. The agent puts its link in the reply.
| Case | Opens a tab? |
|---|---|
| First page of a session | Yes |
| Same page again | No, the open tab reloads |
| New title, same session | No, link in the reply |
| New terminal or agent session | Yes, once |
| Same session after 12 hours | Yes, once |
| Plan approval page (plan hook) | Yes, it needs your answer |
Gap closed: a run with no session variable fell back to "no session", so every new title opened. Now the terminal's tty is the key, and runs with no tty share one key.
How the open tab updates
If you typed a reply or comment on the page, it shows a "Page updated · Reload" button instead of reloading.
Bug fixed on the way
Each publish deployed only the new page and the index, so every older artifact link showed the index. Publish now keeps all pages in ~/.answer-me-with-html/published/ and deploys the whole set. 12 of 13 older pages came back from local sources. Live-artifacts-glitch-fix has no local source left.