Write something
Pinned
20h •
Context Compaction - A Lesson Learned/Question
So I was using Claude Code to create an n8n workflow for a routine/app over the weekend. Surprisingly, the workflow that I figured would be rather straightforward and simple needed multiple iterative updates and fixes. At one point, CC came back and stopped the work altogether for an hour because I had reached a limit. What limit? It turns out because I had been working on this workflow for hours in a single session, the length of context that CC was maintaining reached its limit, which it turns out is 200K tokens (https://support.claude.com/en/articles/8606394-how-large-is-the-context-window-on-paid-claude-plans). So it kicked me off the session (a well deserved break for me as well) and compacted the session summary so it can retain the key things about the work in progress. After that, I became aware of an indicator in the chat window that showed % context used (or something like that). So I asked CC to automatically compact the session, if it reached 80%, save this request to the CLAUDE.md file, and also in its memory, but do each compaction prior to starting any work that may exceed the limit and stop the work. It failed to do it automatically and proactively the few times, so I had to do it manually and remind CC. I asked CC to create and update a WIP summary pertaining to the project so I can come back to it to see the changes made, but it created something called STATUS file and kept it outside of the project file. I guess this lengthy post is so that I can share a lesson learned about context length that I never knew about before. But has anyone encountered a situation like this? How have you managed it? How can I manage WIP and STATUS without unnecessarily duplicating things? Cheers, Roger
Pinned
2d •
Official: Claude March 2026 usage promotion
Claude March 2026 usage promotion Updated today We're offering a limited-time promotion that doubles usage limits for Claude users outside 8 AM-2 PM ET/5-11 AM PT. This promotion is available for Free, Pro, Max, and Team plans. Enterprise plans are not included in this promotion. What is the promotion? From March 13, 2026 through March 27, 2026, your five-hour usage is doubled during off-peak hours (outside 8 AM-2 PM ET/5-11 AM PT). Usage remains unchanged from 8 AM-2 PM ET/5-11 AM PT. Eligibility No action is required to participate. If you’re on an eligible plan, the doubled usage is automatically applied. Where does this apply? The 2x usage increase applies across the following Claude surfaces: - Claude (web, desktop, and mobile) - Cowork - Claude Code - Claude for Excel - Claude for PowerPoint Frequently asked questions Do I need to do anything to get the extra usage? No. The promotion applies automatically. You’ll see higher limits reflected in your usage outside 8 AM-2 PM ET/5-11 AM PT without any changes to your account settings. Does bonus usage count against my weekly usage limit? No. The additional usage you get during off-peak hours doesn’t count toward any weekly usage limits on your plan. What happens when the promotion ends? After March 27, 2026, usage limits return to their standard levels at all hours. There’s no change to your plan or billing. Terms and conditions This offer is valid from March 13, 2026 through March 27, 2026 at 11:59 PM PT. It applies to Free, Pro, Max, and Team plans only and excludes Enterprise plans. This offer has no cash value and is not transferable. It may not be combined with other offers.
Pinned
27d •
New Here? Drop Your Intro. I Read Every One.
I started this community because I believe you can build a meaningfully better working life with AI — and I wanted a place to figure that out together, practically. I'm Matthew. I run ByteFlowAI, an AI automation consultancy. I'm building in public, and Claude Desktop is my primary tool — the foundation for everything in this course. I have more good questions than definitive answers. What I can promise: your time is respected, the lessons are honest, and this community is yours as much as it's mine. If you haven't started, Lesson 0 is in the Classroom. Then come back and introduce yourself — name, what you do, one thing you want AI to take off your plate. I read every single one.
7d •
Visual Code Studio / Cursor + Claude Code
I am not sure if this is a legit question. in case it's not please excuse me in advance and I will correct the aim for the future🥹 I'm doing my first experiments with Claude Code in combo with visual code studio. should I use instead Cursor+Claude Code? or maybe even directly just the interface of Claude Code? Sorry my AI fellows and mentors, but I'm already lost in the rabbit hole 🙏🏻🥹🙈
16h •
n8n 2.0 Just Dropped
n8n 2.0 Just Dropped. Here's What You Need to Know Before You Touch That Update Button. In8n 2.0 Just Dropped. Here's What You Need to Know Before You Touch That Update Button. If you're running n8n workflows (or planning to), pause before upgrading. n8n 2.0 landed back in December with breaking changes, and the team has been pushing bug-fix releases almost every other day through March. That's not a bad sign. It means they're actively fixing things. But it also means your workflows could behave differently after the upgrade. What's been getting patched in March alone: - Task runner stability (the sandboxed environment Code nodes now run in was hanging on connection failures) - Form Node rendering and security (custom CSS sanitization tightened up) - Kubernetes import issues and arm64 compatibility fixes - Credential modal and collaboration fixes They've shipped five patch releases in the first two weeks of March. The platform is stabilizing, but it's still moving fast. What to do: 1. Check your current version. If you're on 1.x and things are working, there's no rush. 1.x gets security patches for 3 more months. 2. If you're already on 2.x, make sure you're on the latest patch (2.11.4 as of March 13) 3. Before upgrading any production instance, read the breaking changes doc: https://docs.n8n.io/2-0-breaking-changes/ 4. Back up your workflows first. Export them. Every time. Non-negotiable. The short version: n8n 2.0 is a real upgrade with real improvements. But "real upgrade" also means "real changes that can break things." Don't upgrade blind. TLDR: n8n 2.0 broke ground in December. Three months later, the team is still patching (five releases in two weeks through March). Biggest recent fixes: task runner stability, Form Node security, and Kubernetes import handling. If you're on 1.x, you have 3 months of security support left. If you're on 2.x, update to 2.11.4. Either way, read the breaking changes doc and back up your workflows before touching anything.
1-30 of 42
powered by
skool.com/ai-for-life-3967
Claude Code lessons for Mac users. Operators share automation frameworks that work in production. Discover the highest-ROI automation opportunities.
Suggested communities
Powered by