Tab show even if I have only 1 opened

[janblahout-cell]

What happened?

before , there was an option, that if you have only 1 tab open, you wouldnt see the tab on top of the window.
After last update (3rd of August), it is no longer there.

Even if i have single tab open, i see it on the top.

Steps to reproduce

1. Open opencode
2. Select a project
3. Create a single tab
4. You should see the tab on top, before there was an option to disable tabs if only 1 is open.

Supacode version and build

0.10.7

macOS version

Tahoe 26.5.2

System locale

cs_CZ

Mac hardware

M4 Pro

Relevant logs or screenshots

Are you planning to fix this yourself?

• I intend to open a pull request once this is confirmed and marked ready.

Before submitting

• I searched existing issues and this is not a duplicate.
• I am on the latest available version of Supacode.
• I understand pull requests are closed until the issue is marked ready.
• I agree to follow this project's Code of Conduct.

[github-actions]

Thank you for filing this. A maintainer will review it and follow up here.

Please do not start any work or open a pull request until this issue is labeled ready. That label is a maintainer's go-ahead: a pull request opened against an issue that is not yet ready is labeled invalid until then. You will get a comment here the moment it is marked ready.

See CONTRIBUTING.md for the full flow.

[sbertix]

Yeah, this is intentional. The feature is no longer supported 🥺 (at least for now).

To elaborate, it had a few issues that we’re trying to move away from:

1. More and more information is now displayed in the tab item, such as agent badges, progress, hibernation, and locked status. Hiding the tab completely removed access to this information in most cases, with no separate way to view it.
2. It hides the "wrong" information. With the sidebar open, it's the navigation item (with icon, branch name, repository, etc.) usually being redundant, not the actual tab. The end goal is to hide the navigation item instead, especially as part of the tab and split rework I’ve been postponing for too long.
3. It was originally introduced for tmux (and similar), so users could manage their own splits there. However, that causes all sorts of performance and compatibility issues with zmx, which we now use to provide persistence across terminals.

• some other quirks we could have fixed, so not counting those (e.g., animations, etc).

Would the solution outlined in point 2 work for your use case? Is there anything I haven’t covered above that we should evaluate? Open to anyone, btw, not just the author.

[JanBlahout]

Thanks for the quick reply. Aprreciate it