Add deterministic announcement demo workspace#1967
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3b032d4f1b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const isAnnouncementDemo = | ||
| url.searchParams.get("demo") === ANNOUNCEMENT_DEMO_QUERY_VALUE || | ||
| import.meta.env.VITE_ANNOUNCEMENT_DEMO === "1"; |
There was a problem hiding this comment.
When a production/web build is opened with ?demo=announcement, this branch now treats it as the announcement demo, installs the E2E mock bridge, and then rewrites persistent localStorage like buzz-communities/buzz-active-community-id to the fake Honeycomb workspace. A shared link with that query can therefore switch real users away from their saved communities and load test-only mocks; the query-triggered path should be limited to import.meta.env.DEV or an explicit build-time demo flag.
Useful? React with 👍 / 👎.
e6938be to
e1801db
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e1801db5b1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| The local demo relay also includes a running agent named **Scout**. Configure | ||
| OpenAI or Anthropic in the Agents screen, then `@mention` Scout in |
There was a problem hiding this comment.
When someone follows this runbook and @mentions Scout, no demo agent will autocomplete or respond: the seeded announcement agents are Fizz, Honey, and Bumble in desktop/src/testing/announcementDemoFixtures.ts, and the e2e flow also mentions Fizz. Please update the instructions to match the seeded agent names or add a Scout agent fixture.
Useful? React with 👍 / 👎.
e1801db to
d16d405
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d16d405a64
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| for (const channelId of channelIds) { | ||
| maybeStartAnnouncementDemoLiveConversation(channelId); |
There was a problem hiding this comment.
When the announcement demo loads, the app-level unread hook (useLiveChannelUpdates) opens live-* subscriptions for every channel, not just the timeline the user is viewing. Starting scripted conversations from every live subscription here means channels like #flight-path begin emitting messages a few seconds after startup while the user is still on Home/another channel, which can flip the seeded read state/unread dot and consume the staged reveal before the recorder opens that channel. Gate this trigger to the active timeline subscription or another explicit demo start signal.
Useful? React with 👍 / 👎.
1 participant
No description provided.