Title: So I stopped using Ghostty... | BestBlogs.dev
URL Source: https://www.bestblogs.dev/video/5ae9df9
Published Time: 2026-03-12 20:21:31
Markdown Content: Skip to main content Toggle navigation menu Toggle navigation menuArticlesPodcastsVideosTweetsSourcesNewsletters
⌘K
Change language Switch ThemeSign In
Narrow Mode
So I stopped using Ghostty... =============================
!Image 2: Theo - t3․gg Theo - t3․gg @Theo - t3․gg
One Sentence Summary
Theo explains his transition from Ghostty to Semox, highlighting how modern 'agentic programming' with AI requires a more hierarchical and project-centric terminal workflow.
Summary
In this analysis, developer Theo discusses his move from the high-performance Ghostty terminal to Semox. He argues that traditional terminal multiplexers like T-Mux and standard macOS window management are no longer sufficient for the 'agentic' era of development, where AI agents (like Claude Code) perform parallel tasks. Semox, built on the libghosty core, introduces a project-based sidebar and nested tab layouts that better map to a developer's mental model. While acknowledging early-stage bugs and a weak internal browser, Theo emphasizes that Semox's ability to manage complex task flows and provide AI notifications represents the future of developer environments, moving away from chaotic window management toward structured order.
Main Points
* 1. Traditional terminal multiplexers like T-Mux struggle with the high-density parallel tasks of modern AI-assisted development.As developers move toward 'agentic programming,' the number of concurrent branches and AI-driven tasks increases, making flat window structures or simple tab management in tools like T-Mux cognitively overwhelming and inefficient. * 2. Semox utilizes a hierarchical project-based sidebar to organize complex development environments and reduce context-switching friction.By grouping terminal instances by project and allowing nested layouts, Semox enables developers to jump between different codebases while maintaining local task states, such as keeping an AI agent and a dev server in the same view. * 3. The integration of AI notifications within the terminal UI is a critical feature for managing asynchronous AI tasks.Semox's ability to alert users when an AI agent like Claude Code requires input allows developers to focus on other tasks without constantly polling the terminal, effectively managing the 'agentic' workflow. * 4. Future developer tools should adopt 'paper-like' window management philosophies rather than traditional tiling or OS-level spaces.Inspired by the Niri window manager, the author advocates for fluid, fixed-size panels that users scroll through, preventing the UI from becoming unreadable when multiple windows are opened simultaneously.
Metadata
AI Score
86
Website youtube.com
Published At Yesterday
Length 2174 words (about 9 min)
Sign in to bookmark videos and track your viewing history. Sign in now
!Image 3: So I stopped using Ghostty...
So I stopped using Ghostty...
内容概要 ----
在这段视频中，资深开发者 Theo 分享了他为何放弃备受好评的终端工具 Ghostty，转而投入新兴终端 Semox 怀抱的原因。他深入探讨了现代开发模式（尤其是引入 AI 代理后的「代理化编程」）对多任务并行处理的极高要求，分析了传统终端复用器（如 T-Mux）和 macOS 自带窗口管理系统的局限性。通过演示 Semox 如何通过分层管理、项目隔离以及与 Claude Code 的集成来重塑其工作流，Theo 勾勒出了下一代开发者工具的蓝图，并表达了对基于 libghosty 生态的未来充满期待。
目录 --
* 终端之选的变迁 * 传统工具的局限与并行工作的挑战 * 深度体验 Semox：效率的质变 * 仍待解决的问题与槽点 * Niri 带来的灵感：纸质窗口管理 * 开发者工具的未来：从混乱到秩序
终端之选的变迁 -------
我知道大家都在看我的笑话，觉得我一直在频繁更换软件。但这一次真的不同。我在近十年的时间里一直使用同一款终端，直到 Ghostty 出现。我之所以从 Mac 自带终端迁移到 Ghostty，是因为它非常出色。Ghostty 让我意识到原生的 Mac 终端在遵循标准方面做得有多差，给终端 UI 的维护者带来了多少麻烦。
Ghostty 确实令人惊叹。它不仅速度极快、性能可靠，而且高度可定制、开源且维护良好。这也是为什么我当初会如此兴奋。然而，尽管我的 Ghostty 配置已经非常完美，但我最近还是决定弃它而去。
传统工具的局限与并行工作的挑战 ---------------
我是一个深度 T-Mux 用户，从 15 岁使用 GNU Screen 开始，我就一直依赖终端复用器。现在我快 31 岁了，这意味着我生命中的大部分时间都在与这些工具打交道。但最近，我发现自己打开的标签页越来越多，思维逻辑开始出现偏差。
我意识到，目前我所从事的工作层级，无法很好地映射到 T-Mux 这类工具上。我的工作分支变得更多，上下层级的跳转更频繁，并行处理任务的方式也变得越来越奇怪。尝试在不同的窗口、标签和面板中管理所有工作，简直让人抓狂。我甚至做过一个实验，强迫自己停止使用 T-Mux，结果几乎让我发疯。直到我发现了 Semox，它彻底重连了我的大脑。
深度体验 Semox：效率的质变 ----------------
Semox 是基于 libghosty 构建的。libghosty 是 Ghostty 的核心库，而 Semox 则是在此基础上进行的创新。它完全改变了我与终端的关系。虽然它远非完美，但它在处理并行任务方面的表现极其出色。
在 Semox 中，我可以根据项目来划分侧边栏。比如，我有 T3 code 相关的项目，有我的 Sandbox（沙盒目录，用于存放各种临时的奇思妙想），还有其他的代码库。我可以非常轻松地在这些项目之间跳转，并且每个项目内部都有自己独立的窗口排版。
[演示界面操作]
举个例子，在同一个分割面板中，我可以开启多个标签页。我可以在一个面板里运行 Claude Code 进行 AI 辅助编程，而它背后的标签页则运行着开发服务器。这种层级结构非常符合直觉：顶级是项目目录，面板内是具体的任务流，比如一边是 Git 管理，一边是代码生成。它还集成了 Claude Code 的通知功能，当 AI 完成任务需要我输入时，侧边栏会弹出提示，这极大地缓解了多任务并行时的上下文切换压力。
仍待解决的问题与槽点 ----------
当然，Semox 目前还处于早期阶段，存在一些让人恼火的问题。最明显的是一个状态栏重复显示的 Bug，每次我按下回车或清屏，状态栏就会多叠一层，这非常影响心情。
此外，它内置的浏览器功能目前比较糟糕。这似乎是一个基于 Safari 的 Web 视图，但它不包含我的登录信息、Cookie，也不支持插件。这意味着我无法使用 1Password 自动登录。最让我生气的是，最初它会默认在应用内打开终端里的链接。我习惯每天几十次地通过 LazyGit 快速打开 GitHub 的拉取请求页面，结果它全在 Semox 内部那个简陋的浏览器里打开了。幸好我后来在设置里找到了关闭它的选项。不过，这些问题都不足以阻止我使用它，因为它带来的效率提升远超这些小瑕疵。
Niri 带来的灵感：纸质窗口管理 -----------------
为了解释我追求的理想工作流，我必须提到 Niri。Niri 并不是传统的平铺式窗口管理器。在传统的平铺模式下，如果你在现有窗口旁打开一个新窗口，它会挤占原有空间，导致内容变得太小而无法阅读。
而 Niri 采用的是「纸质窗口管理器」的概念。每一个面板都有自己的固定大小，就像一张张摆在桌面上的纸。你不是在缩放它们，而是在这些纸张之间滑动视口。
[演示 Niri 的滑动效果]
你可以横向滚动，也可以纵向布局。这种流动的体验让我着迷。我一直在尝试在单个应用中复现这种快感。想象一下，如果 Semox 的每一个项目部分都能像这样无限嵌套、无限滚动，那将是多么强大。你可以通过三指滑动在不同的终端任务之间无缝切换，同时保持侧边栏的项目级管理。
开发者工具的未来：从混乱到秩序 ---------------
很多人会问，macOS 的「调度中心」或多空间功能不是能做到这一点吗？坦白说，Mac 的空间管理非常糟糕。它的切换动画极其缓慢且无法关闭，应用间的跳转逻辑经常出错。它在不需要隔离的地方强行隔离，而在需要清晰界定边界的地方又模糊不清。
Semox 让我看到了一条新路径：我们不需要在操作系统层面去折腾窗口管理，而是可以在一个专门的开发应用内部实现这种高效的层级结构。未来的开发者工具不应该只是一个简单的终端或编辑器，而是一个能承载我们并行思维的完整环境。
现在的 Semox 就像是下一代技术的「胶带修补版」，虽然粗糙，但充满了未来感。AI 改变了我们构建软件的方式，我们的工具也必须随之进化。虽然我不知道几个月后我会用什么，或者我是否会自己动手写一个更好的工具，但目前，Semox 是最能帮我理清工作混沌的利器。
我强烈建议每一位在 Mac 上进行重度 AI 代理协作开发的开发者都去尝试一下。未来的工具正在今天被孕育，我迫不及待想看到这个领域还会演化出什么。
!Image 4: Theo - t3․gg Theo - t3․gg @Theo - t3․gg
One Sentence Summary
Theo explains his transition from Ghostty to Semox, highlighting how modern 'agentic programming' with AI requires a more hierarchical and project-centric terminal workflow.
Summary
In this analysis, developer Theo discusses his move from the high-performance Ghostty terminal to Semox. He argues that traditional terminal multiplexers like T-Mux and standard macOS window management are no longer sufficient for the 'agentic' era of development, where AI agents (like Claude Code) perform parallel tasks. Semox, built on the libghosty core, introduces a project-based sidebar and nested tab layouts that better map to a developer's mental model. While acknowledging early-stage bugs and a weak internal browser, Theo emphasizes that Semox's ability to manage complex task flows and provide AI notifications represents the future of developer environments, moving away from chaotic window management toward structured order.
Main Points
* 1. Traditional terminal multiplexers like T-Mux struggle with the high-density parallel tasks of modern AI-assisted development.
As developers move toward 'agentic programming,' the number of concurrent branches and AI-driven tasks increases, making flat window structures or simple tab management in tools like T-Mux cognitively overwhelming and inefficient.
* 2. Semox utilizes a hierarchical project-based sidebar to organize complex development environments and reduce context-switching friction.
By grouping terminal instances by project and allowing nested layouts, Semox enables developers to jump between different codebases while maintaining local task states, such as keeping an AI agent and a dev server in the same view.
* 3. The integration of AI notifications within the terminal UI is a critical feature for managing asynchronous AI tasks.
Semox's ability to alert users when an AI agent like Claude Code requires input allows developers to focus on other tasks without constantly polling the terminal, effectively managing the 'agentic' workflow.
* 4. Future developer tools should adopt 'paper-like' window management philosophies rather than traditional tiling or OS-level spaces.
Inspired by the Niri window manager, the author advocates for fluid, fixed-size panels that users scroll through, preventing the UI from becoming unreadable when multiple windows are opened simultaneously.
Key Quotes
* I realized that the level I'm working at right now doesn't map well to tools like T-Mux... my work branches more, my jumps between layers are more frequent. * Semox is built on libghosty... it completely changed my relationship with the terminal. * The way Mac handles spaces is terrible... it isolates where it shouldn't and blurs boundaries where they should be clear. * AI has changed how we build software, and our tools must evolve accordingly. * Semox feels like a 'duct-tape' version of next-gen tech—rough around the edges but full of the future.
AI Score
86
Website youtube.com
Published At Yesterday
Length 2174 words (about 9 min)
Tags
Terminal Emulators
Ghostty
Semox
AI Coding
Workflow Optimization
Related Articles
* Design-First Collaboration * Cursor, Claude Code, and Codex All Have a BIG Problem * They cut Node.js Memory in half 👀 * I can't believe nobody's done this before... * gpt-5.4 is really， really good * Software engineering is dead now * Conversation: LLMs and the what/how loop * Build Hour: API & Codex * Introducing GPT-5.2-Codex: Advanced Agentic Coding Model * Boris Cherny: How We Built Claude Code HomeArticlesPodcastsVideosTweets
So I stopped using Ghostty... | BestBlogs.dev ===============