feat(environments): drop the Publish-as-chatbox panel from the environments page - #3616
Conversation
…nments page Product call for the environments launch: chatbox publishing lives on the Chatbox tab, not the environment editor. Publishing an environment from its management page created a second, page-dependent publish flow (live-follow pointer vs the Chatbox tab's snapshot semantics) that read as incoherent. Removes the EnvironmentChatboxSection panel, its test, and the now-unused client hooks (useEnvironmentChatbox / usePublishEnvironmentChatbox / useUnpublishEnvironmentChatbox). The Convex mutations (chatboxes:publishEnvironmentChatbox / unpublishEnvironmentChatbox) and the env-pointer chatbox model stay in the backend — a future Chatbox-tab environment picker is the intended re-entry point. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GitHub Actions
Error
dosubot
Bot
added
size:L
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_22e5ca30-5525-460a-b0de-bbead9a72538) |
📄 Knowledge reviewDosu skipped reviewing this PR because your organization has used its
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
💤 Files with no reviewable changes (6)
WalkthroughThe change removes environment chatbox publishing from the client. It deletes the environment chatbox summary and related read, publish, and unpublish hooks. It removes the publish-as-chatbox section from environment details. Archive and restore controls remain. Related component tests and mocks are deleted or updated. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
![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
Keep existing environment chatboxes manageable
For any environment published before this version, removing this panel and the only client callers of unpublishEnvironmentChatbox leaves its live share link—including an anyone-with-link URL—active with no UI for changing access or revoking it. The current ChatboxesTab is not a replacement: it selects hosts and loads useChatboxByHostId, while environment-backed rows expose their named-host fields as display-only. Retain management controls until the planned Chatbox-tab environment picker lands, or existing owners must archive the entire environment (disrupting suites and journeys) merely to stop the link.
ℹ️ 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".
1 participant
Why
Product decision for the environments launch: chatbox publishing belongs to the Chatbox tab. The environment editor's Publish-as-chatbox panel created a second publish flow whose semantics (live-follow pointer) silently differed from the Chatbox tab's (frozen snapshot) purely based on which page you started from.
What
EnvironmentChatboxSectionfromProjectEnvironmentsRouteand delete the component + its test.useEnvironmentChatbox/usePublishEnvironmentChatbox/useUnpublishEnvironmentChatbox(no other call sites).Kept: the backend mutations (
chatboxes:publishEnvironmentChatbox/unpublishEnvironmentChatbox) and the env-pointer chatbox model are untouched — the intended re-entry point is an environment picker on the Chatbox tab's publish bar (follow-up).Tests
All 10 project-environments test files pass (73 tests); no typecheck errors in changed files.
🤖 Generated with Claude Code
Note
Low Risk
UI and dead client-hook removal only; no backend or auth changes, though users temporarily lose in-page publish until the Chatbox tab re-entry ships.
Overview
Removes the Publish-as-chatbox flow from the project Environments detail view so chatbox publishing is not offered in two places with different semantics (live-follow on Environments vs snapshot on the Chatbox tab).
EnvironmentChatboxSectionis deleted along with its dedicated test file, andProjectEnvironmentsRouteno longer renders that block (including for non-archived environments). Client-only hooksuseEnvironmentChatbox,usePublishEnvironmentChatbox, anduseUnpublishEnvironmentChatbox(andEnvironmentChatboxSummary) are removed fromuseProjectEnvironments.tsbecause nothing else called them. Route tests drop mocks for the removed section.Environment editing, archive/restore, and archive-confirm consumer copy (including published chatbox warnings) are unchanged. Backend chatbox mutations and the env-pointer model are out of scope for this diff.
Reviewed by Cursor Bugbot for commit 9c46fdd. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by cubic
Removed the Publish-as-chatbox panel from the Environments page. Publishing now happens only from the Chatbox tab to avoid two conflicting flows (live-follow vs snapshot).
EnvironmentChatboxSectionfromProjectEnvironmentsRouteand deleted the component and its test.useEnvironmentChatbox,usePublishEnvironmentChatbox,useUnpublishEnvironmentChatbox.chatboxes:publishEnvironmentChatbox,chatboxes:unpublishEnvironmentChatbox) for a future environment picker on the Chatbox tab.Written for commit 9c46fdd. Summary will update on new commits.