@Joel Hebert Yes, you're not alone dear Joel — several people in the community (and on forums) have reported similar display flickering on MacBook Pro right after running Claude Cowork for a while. 😊 Claude Cowork (the desktop feature in the Claude Mac app) gives Claude the ability to take over parts of your screen, mouse, and keyboard to perform tasks autonomously. This "Computer Use" style control can sometimes interfere with macOS display rendering, especially during long sessions with heavy UI updates, thinking phases, or when it's rapidly interacting with the desktop. 🫣 Why this happens - Claude Cowork runs in the background with elevated screen access. - Rapid redraws or partial screen captures during agentic tasks can cause visual glitches (flickering, flashing, horizontal lines). - It can interact badly with macOS graphics switching, True Tone, or certain display settings on M-series MacBooks. - Similar (though usually milder) flickering issues have been common with Claude Code's terminal renderer in the past, and Cowork builds on related tech. The fact that it started exactly after running Cowork for a few hours strongly points to this as the trigger. Quick fixes to try right now (in order) 🥸 1. Force quit Claude completely Use Cmd + Option + Esc → find Claude → Force Quit. Also quit any related background processes if visible in Activity Monitor (search for "Claude"). 2. Restart your MacBook This resolves most Cowork-induced display glitches. Many users report the flickering stops after a full reboot. 3. Check and reset display settings Go to System Settings > Displays. Turn off True Tone (if on). Turn off Automatic graphics switching (if you see it under Battery or Displays). Try changing the refresh rate or resolution temporarily and switch back. 4. Update the Claude app Make sure you're on the latest version of the Claude desktop app — Anthropic has pushed several rendering and stability fixes over time. 5. Re-launch Cowork carefully After restarting, open Claude → go to the Cowork tab. Start with a short, simple task instead of long-running ones. Monitor if flickering returns only when Cowork is actively "working".

@John Geluch very welcome dear John 😊

@John Geluch Yes, both issues are very common and almost always related to backend processing delays. I'll break it down clearly for each one (I'm assuming you're in one of the AI automation communities that uses Claude + n8n workflows and provides private GitHub repos + a custom platform called NextWave). 😊 1. GitHub Repository Access (using the same signup email) This does take time on the backend — it’s not instant in most communities. Here’s what usually happens: - When you sign up to the community, the system adds your email to a list. - An admin/script then sends a GitHub organization invitation (or repo access) to that exact email. - GitHub has to process the invite, send you the email, and you have to accept it while logged into the correct GitHub account. Typical delays: - 5–30 minutes in most cases (if everything is automated) - Up to 2–4 hours if there’s any manual approval or batch processing - Occasionally overnight if the community runs invites in batches Quick things to check/fix right now: - Make sure you are logged into GitHub with the exact same email you used to sign up for the community. - Check your email (including spam/promotions folders) for a subject like “Invitation to join [CommunityName] on GitHub”. - If you don’t see the invite after ~1 hour, try logging out of GitHub completely, clearing cache, and logging back in. - Some communities require you to go to a specific link in the community dashboard to “claim” your GitHub access first. If it’s still not working after 4–6 hours, it’s safe to ping the community support (they usually have a #github-access or #tech-support channel). 2. NextWave login (“page not working” – can’t even reach the login page) This one is also almost certainly a backend/setup delay. NextWave is the community’s custom dashboard/platform (built on top of the same infrastructure as the GitHub stuff). When they roll it out to new members:

@Wolfgang Klaus good luck with this GHL stuff Wolfgang😃