This seems wildly inconsistent. I just installed the beta, and I'd say that tangrid only picked up about 40% of the windows. I have windows spread across 4 desktops. I have 1 screen where 6 windows are all tabbed correctly, but the other 2 refuse to be managed - no focus border, and I can't hot key drag them to force them to be managed. I have 1 desktop with all 8 windows ignored, and another that's mostly mixed. Haven't worked out a pattern to it yet.
1.3.0-beta seems to ignore a lot of windows
回复11
Is this issue only happening with specific apps? For example, if after cmd q and restarting the app, it still can't be managed, then it's a case with that specific app.
Maybe. They are all apps started before tangrid, and I’ve not restarted them yet. So far it includes MS Edge, Chrome, Obsidian, Codex. These exact instances all worked with the last non-beta version. I’ll restart them when I get back to the computer and see if that helps.
Restarting those apps seems to have no effect. I did notice that on one display one MS Edge window was being managed, but on all of the other they are not. What's weird is that on one display it all seems to be working correct, but on the other displays each has something wrong it it.
It would be really handy if you could release a non-beta version with the update channel stuff in it, switching back to 1.2.0 is a bit fussy right now.
do let me know if there's nything more I can send you. I've swapped back to 1.2.4 for now but I'm more than happy to switch back and test stuff.
· 已编辑 2026年6月21日 13:29 UTC
Thanks a lot for the detailed feedback and the logs. Really appreciate your help testing this.
I’ve pushed v1.3.1-beta with a fix based on the logs you sent. When you have a chance, could you try this version and let me know if the ignored-window issue is resolved?
Well it no longer seems to ignore windows, so that's good, but on app restart it no longer recognizes any sort of previous configuration and seems to want to dump everything onto one bit fullscreen tab stack. My config is set to auto-split.
Previously, if I quit and restarted Tangrid, it did a generally awesome job of recognizing the prior config and putting most if not all into splits or stacks that matched what was there prior to exit. This is no longer the case.
I will say that the behavior outside the startup seems to be a lot smoother than the previous version, noticeably snappier and the grad and drop seems less laggy.
That’s encouraging overall. I’ll look into what’s causing the startup layout issue.
OK, it's generally massively better, but I just ran into a situation where I have about 20 or so windows open, 6 of which are vscode projects. Just opened the 7th vscode window and it's not managed. The other 6 are fine, but not this one - seems to be completely ignored by Tangrid.
Here's a new log.
i agree.. Mine does this some windows... claude in particular
Please check if v1.3.2 beta fixes this issue.