Section header (Sidebar) doeas not expand / collapse anymore
since today’s update of the macOS desktop app, sections in my notes can no longer be opened or closed. Clicking the section header or its expand/collapse control has no effect.
Mac Version 1.76.2
Capacities v1.72.6; none none; Mac OS v10.15.7; Chrome v148.0.7778.280 (WebKit v537.36); Desktop (Electron); 29.10.2026, 15:36:01
10 Comments
Sign in to comment
·3 days agoYour request is completed, thanks for reporting!

·3 days agoThis is fixed on the latest version, apologies for the inconvenience!
Solved by today's update. Thanks.
Same issue just started happening afer updating this morning
Capacities v1.72.6; none none; Mac OS v10.15.7; Chrome v148.0.7778.280 (WebKit v537.36); Desktop (Electron); 10/29/2026, 8:41:14 AM; en (America/Phoenix, UTC-7); Memory: 170.37 MB / 4 GB; Storage: 1.23 GB / 192.43 GB; Portal: reachable; S3: reachable; Dead Workers: none
I am having the same issue after the update, on windows

Same here! Sections do not expand anymore.
This bug, only recently resolved after weeks, is now back again. This is unbelievable!
You guys should really focus on your quality control!
If I didn't still have data to migrate, I wouldn't even bother with this software anymore.
Capacities v1.72.6; none none; Mac OS v10.15.7; Chrome v148.0.7778.280 (WebKit v537.36); Desktop (Electron); 29.10.2026, 15:42:42; de (Europe/Vienna, UTC+1); Memory: 92,08 MB / 4 GB; Storage: 2,73 GB / 19,03 GB; Portal: reachable; S3: reachable; Dead Workers: none
Honestly dawg, I totally get you. I'm having the same issue. At the same time, I feel its not very productive to berate them.
Its not like either of us would know how to create an App like Capacities anyways, nevermind getting it to the level of evolution I've seen it take on these last four years of use.
They're a small team with nowhere near as much support or hands available as bigger firms like Notion, and the global vision/philosophy for the Capacities UI inevitably means that temporary problems are always bound to arise in the face of trying to balance complexity with ease-of-use. Its no small feat, and rest assured the team is running around trying to address all of our comments as fast as humanly possible. Last I checked, the board was up to something like >370 comments for bugs alone; can u imagine being in their position and trying to successfully — because they have been successful, lets not kid ourselves — manage all of that on top of getting out releases/updates for brand new features (OCR on PDFs/weblinks, whiteboards, global graph, etc.) in the span of 1-2 months? I certainly couldn't imagine the effort it would take lol.
All that being said, I get you, its frustrating and you have every right to be, but nothing good comes out of being backseat drivers and gratuitously rude to the team. And I know that if you're anything like me, frustration is what drove spur-of-the-moment commenting and you didn't actually mean it, so rest assured nobody is holding it against you either.

I appreciate your friendly attitude, but you may not realize that I was left completely on my own for weeks with exactly this bug and no one thought it particularly noteworthy that I couldn't use Capacities at all.
And now the same bug is happening again while I'm in the middle of exporting my data. Am I supposed to be particularly delighted about that?
The team is working on a fix!
Thanks for the update @Beth (Team) , and thank you team for getting on it so quickly! Have an awesome rest of your day!