by RoversX
A modern terminal with a built-in multiplexer: close it and your sessions keep running. Run shells and tons of AI agents across your machines, then pick them up from desktop, browser, TUI and more. Written in Rust with no UI framework: interface drawn straight on the GPU. No Electron, GPUI or webview.
# Add to your Claude Code skills
git clone https://github.com/RoversX/ThinkTermSee how ThinkTerm compares with popular alternatives.
ThinkTerm is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by RoversX. A modern terminal with a built-in multiplexer: close it and your sessions keep running. Run shells and tons of AI agents across your machines, then pick them up from desktop, browser, TUI and more. Written in Rust with no UI framework: interface drawn straight on the GPU. No Electron, GPUI or webview. It has 58 GitHub stars.
ThinkTerm's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/RoversX/ThinkTerm" and add it to your Claude Code skills directory (see the Installation section above).
ThinkTerm is primarily written in Rust. It is open-source under RoversX on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh ThinkTerm against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
English · 简体中文 · 日本語 · Français · Deutsch
Download here - Get the latest release
🍺 Homebrew (macOS):
brew install --cask roversx/tap/thinkterm
🌐 Website: closex.org/thinkterm
📚 Documentation: docs.closex.org/thinkterm
⭐ Consider starring ThinkTerm!
Your machines fuse into one.
ThinkTerm is an open-source terminal with a built-in multiplexer, written in Rust, built on WezTerm. Its mux server runs your shells, tools, and coding agents; desktop, TUI, and browser clients connect to those sessions. Bring local and remote work into one workspace, and return to it from another device.
Platforms: macOS · Linux · Windows · Web · TUI — iOS and Android in development.
A terminal multiplexer manages multiple terminal sessions and lets clients attach to them. In ThinkTerm, the mux server owns the sessions, tabs, and split panes. The client displays them and sends your input.
thinkterm tui, or the browser to connect to the server. Multiple clients can be attached at once; each offers its own interface to the shared sessions.Session persistence depends on the mux server and its host remaining available; it does not restore running processes after a server restart or host reboot.
Running several agents across different projects quickly turns a tab bar into a guessing game: which session is working, which needs input, and where did that build finish? ThinkTerm puts the project structure and work status beside the terminal, with local and remote work visible together.
Rust powers ThinkTerm's terminal core, mux server, desktop client, and TUI. The desktop renders through the GPU without Electron or an embedded web view. Built on WezTerm, this native foundation supports workspace organization, persistent remote sessions, and tools for working alongside agents.
| Layer | Purpose |
|---|---|
| Space | A working context for local work, a remote mux connection, or a notes Vault. |
| Project | A project directory within that context. |
| Thread | A session with tabs and split panes; pin it or mark it unread. |
Local and remote workspaces share the sidebar. Thread status helps distinguish running work, work needing attention, completed work, and idle sessions. The overview displays live terminal previews grouped by Space, so you can find a session without opening every tab.
thinkterm-plugin. See the plugin guide for setup and development.The CLI also exposes panes to automation: thinkterm cli send-text sends input and thinkterm cli get-text reads terminal output. Agents can use these commands to interact through their terminals. The collaboration notes describe the demonstrated workflow and the limits of terminal input as a messaging mechanism.
| Client | Current scope |
|---|---|
| Desktop | Native application for macOS, Linux, and Windows. |
| TUI | Workspace navigation and terminal control inside an existing terminal, through thinkterm tui. |
| Browser | A client served by your own mux server; requires WebGPU and a secure browser context. Browser access must be enabled explicitly. |
| iOS and Android | Native clients in development, with a shared Rust core, GPU rendering, and SSH transport. Mobile release readiness and device coverage are still being established. |
The clients connect to server-held sessions; their interfaces and feature coverage differ.
thinkterm tui
thinkterm tui --help
The TUI supports workspace navigation, tabs, splits, resizing, copy mode, and mouse input. Exiting detaches from the server without closing its sessions. Run it from a separate terminal; launching it inside ThinkTerm's own session can trigger the nested-session guard.
Enable a listener in Settings → Web, then create an access token for the browser. The mux server serves the client and its assets. Connections away from loopback require HTTPS by default; the browser also needs a secure context to expose WebGPU.
See Browser access for listener setup, tokens, SSH forwarding, and certificate handling.
The iOS and Android apps use native interfaces and the shared mobile core. They connect over SSH to sessions on another machine. They are under active development and are not presented here as released mobile products.
For a desktop build on macOS or Linux, install Rust and your platform's build tools, then:
git clone --recursive https://github.com/RoversX/ThinkTerm.git
cd ThinkTerm
./get-deps
cargo build --release -p wezterm -p wezterm-gui -p wezterm-mux-server -p thinkterm-plugin-server
The binaries are written to target/release. See Contributing for the source layout and development workflow. The browser build script builds the separate Web assets; mobile build entry points are ios/build.sh and android/build.sh.
Once the binaries are on your PATH:
thinkterm start # Open the desktop application
thinkterm tui # Open the terminal interface
thinkterm connect <name> # Attach to a configured mux domain
thinkterm cli --help # Inspect and control mux sessions
thinkterm plugin list # List available plugins
thinkterm --help # Show all commands