feat(chat): hide the Chat module when NEXT_PUBLIC_CHAT_DISABLED is set

[TheodoreSpeaks]

Summary

• Gate the Chat module behind NEXT_PUBLIC_CHAT_DISABLED. It's an opt-out, so existing deployments are unaffected — nothing to set to keep Chat.
• One variable, no server/client twin: it isn't a secret, so getEnv resolves the same value from process.env on the server and window.__ENV in the browser.
• Presentation and capability are separate. The flag decides whether surfaces render; COPILOT_API_KEY decides whether the work can run, and gates the Sim Chat block, prompt-job claims, and Inbox — each failing on its own terms.
• With Chat off the workspace lands on your first workflow, and the chats list, scheduled tasks, editor Chat panel, and chat CTAs are gone. Routes are gated, not deleted: /home redirects because it's baked into delivered invite emails and the invitation-accept contract.
• The setup wizard writes the opt-out when you skip the chat key, in all three modes. k8s now prompts for the key too — it previously did neither.
• Compose forwards the flag to the app container; it was writing it to .env where nothing passed it through.

Fixes three bugs the gate exposed:

• A persisted activeTab: 'copilot' left the workflow panel blank from first paint, including pre-hydration via the blocking script.
• The panel's handoff listener claimed MOTHERSHIP_SEND_MESSAGE events outside its own gate, silently swallowing "Fix in Chat".
• Its auto-select effect read a deliberately-skipped query as "chat deleted elsewhere" and cleared the user's selection permanently.

Type of Change

• New feature

Testing

Tested manually. bun run lint:check, type-check, and the full audit suite (boundaries, api-validation:strict, utils, zustand-v5, react-query, client-boundary, bare-icons, icon-paths, realtime-prune, skills, agent-stream-docs) all pass. Full vitest suite green apart from two failures inherited from staging (executor/handlers/pi/* — one needs rg on PATH). No migrations authored here.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
35187658	Triggered	Username Password	bc14b58	apps/desktop/src/main/browser-credentials/vault.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Jul 31, 2026 11:13pm

[cursor]

PR Summary

Medium Risk
Wide routing and navigation changes (default landing, invites, sidebar) plus schedule and executor gating; behavior is env-driven and mostly UI, but misconfiguration could strand users or skip prompt jobs unexpectedly.

Overview
Adds an opt-out for the Chat module via NEXT_PUBLIC_CHAT_DISABLED and isChatEnabled (Chat stays on when unset). UI visibility is separate from mothership capability: the public flag hides surfaces; COPILOT_API_KEY still gates the Sim Chat block, prompt-job schedule claims, Inbox, and mothership SSE.

With Chat off, workspaces land on the first workflow (/w instead of /home), the sidebar drops chats and scheduled tasks, and chat CTAs and the editor Chat tab are hidden. /home and chat routes redirect or 404 so old invite links keep working.

The setup wizard writes the opt-out when the chat key is skipped (compose, dev, and k8s); Docker compose files pass the flag into the app container. Docs and .env.example document COPILOT_API_KEY and the new variable.

Fixes regressions from hiding Chat: persisted copilot panel tab no longer blanks the workflow panel (including pre-hydration script), the panel handoff listener only runs when Chat is available, and copilot auto-select no longer treats a skipped query as a deleted chat.

^{Reviewed by Cursor Bugbot for commit 0809195. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

Adds an opt-out deployment flag for the Chat module.

• Hides Chat routes, navigation, queries, editor surfaces, scheduled tasks, and related calls to action when NEXT_PUBLIC_CHAT_DISABLED=true.
• Redirects workspace landing routes to the workflow list and provides permission-aware handling for workspaces with no workflows.
• Gates Chat-dependent execution paths on COPILOT_API_KEY and propagates setup configuration through supported deployment modes.
• Corrects persisted panel state and Chat handoff behavior when the Chat tab is unavailable.

Confidence Score: 5/5

The PR appears safe to merge.

The previously reported read-only empty-workspace failure is fixed: workflow creation remains hidden until permissions resolve and is unavailable to read-only members, while editors retain the creation path.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/page.tsx	Adds a terminal empty-workspace state and correctly limits workflow creation to users with resolved edit permission.
apps/sim/lib/core/config/env-flags.ts	Defines the deployment-wide Chat feature gate used by server and client surfaces.
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/panel.tsx	Prevents unavailable Chat state from blanking the panel, clearing selections, or consuming handoff events.
apps/sim/app/api/schedules/execute/route.ts	Avoids claiming Chat-dependent prompt jobs when the required Copilot credential is absent.
scripts/setup/steps.ts	Integrates Chat configuration into setup so skipped credentials produce the corresponding opt-out setting.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  Flag[NEXT_PUBLIC_CHAT_DISABLED] --> Enabled{Chat enabled?}
  Enabled -->|Yes| Chat[Render Chat surfaces]
  Enabled -->|No| Workflows[Land on workflow list]
  Workflows --> Existing{Workflow exists?}
  Existing -->|Yes| Editor[Open first workflow]
  Existing -->|No| Permission{User can edit?}
  Permission -->|Yes| Create[Offer Create workflow]
  Permission -->|No| Admin[Ask workspace admin]
  Key[COPILOT_API_KEY] --> Capability{Chat capability available?}
  Capability -->|Yes| Jobs[Run prompt jobs and Inbox]
  Capability -->|No| Skip[Skip Chat-dependent work]

Loading

_{Reviews (3): Last reviewed commit: "fix(setup): name both variables in the c..." | Re-trigger Greptile}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 0809195. Configure here.}