tabsh

Product Introduction

1. Definition: tabsh is a lightweight, open-source Rust daemon and web application that functions as a browser-native integrated development environment (IDE) and terminal session manager. It consolidates shell sessions, AI coding agents, and project contexts into a unified Kanban-style interface accessible directly within a web browser tab.
2. Core Value Proposition: It exists to eliminate disruptive context switching between the browser (where modern development work occurs) and separate terminal windows. Its core value is providing a calmer, more focused developer workflow by centralizing all active coding sessions, AI agent interactions, and project statuses into a single, persistent, and browser-accessible view, thereby reducing cognitive load and improving productivity.

Main Features

1. Unified Session Kanban Board/List: The daemon (tabshd) manages all shell and agent processes, presenting them as "cards" on a web-based board or list. Each card is tied to a specific project directory. The interface groups cards by status (Backlog, In Progress, Needs Input, Completed) and allows drag-and-drop management. The technology stack uses Rust for the backend daemon and a modern web frontend communicating via HTTP and WebSockets for real-time updates.
2. Multi-Agent Integration with Dual Interfaces: tabsh supports popular AI coding assistants like Claude Code, Cursor CLI, and OpenCode as first-class "providers." It uniquely offers two interaction modes per card: a real terminal (TUI) for direct CLI interaction or a chat-style interface (UI). Providers are configured as shell commands with templated prompts ({prompt}, {session}), giving users full control over the agent invocation.
3. Browser-First, Persistent Architecture: The daemon runs independently, so all shells and agent sessions outlive the browser tab. Sessions persist across browser reloads, restarts, and even system reboots, with tabs, working directories, and scrollback restored. The frontend is a static web app that connects locally to the daemon on 127.0.0.1:7681, ensuring all keystrokes and data remain on the local machine.

Problems Solved

1. Pain Point: Context Switching Fatigue and Fragmented Workflows. Developers constantly alt-tab between browser-based tools (GitHub, docs, cloud consoles) and isolated terminal/IDE windows, breaking concentration. tabsh directly addresses this by bringing the terminal/agent session into the browser tab adjacent to the relevant work.
2. Target Audience: Full-stack and web developers who work heavily in browsers; engineers frequently using AI coding assistants who want a unified interface; developers managing multiple concurrent projects or features who need a high-level overview of work-in-progress.
3. Use Cases: Monitoring long-running processes (e.g., builds, tests) while browsing documentation in another tab; Switching context between multiple feature branches or bug fixes quickly using the card list; Interacting with an AI agent for a specific task while keeping the PR/issue it relates to open side-by-side.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):

   • Pros: Drastically reduces context switching by being browser-native. Offers exceptional session persistence and recovery. Provides flexible, user-configurable integration with multiple AI agents. Lightweight, local-first architecture ensures privacy and speed (no cloud relay). Open-source and free (MIT license).
   • Cons: No built-in isolation or worktree management – agents operate directly on your local checkout, which can lead to conflicts if not managed carefully. Currently no Windows support, limiting its audience. Requires a persistent daemon, adding a background process to manage. Advanced multi-device access requires manual Tailscale/SSH tunnel setup.

2. Key Alternatives & Differentiation:

   • Warp, Tabby, WezTerm: These are feature-rich, standalone terminal emulators. tabsh differentiates by not being a terminal emulator itself but a session manager and orchestrator that runs inside your existing browser, leveraging it as the UI layer.
   • Cursor, Zed, VS Code with Terminal Panels: These are full IDEs with integrated terminals. tabsh differentiates by being project-agnostic and lightweight, avoiding the overhead of a full IDE. It manages sessions across multiple projects and IDEs from one place.
   • tmux, screen: These are terminal multiplexers run within a single terminal. tabsh offers a more visual, card-based UI accessible from any browser tab on the machine, with native integration for AI agents, which pure terminal multiplexers lack.

Frequently Asked Questions (FAQ)

1. Is tabsh secure and where is my data stored? Yes, tabsh is designed with a security-first, local-only architecture. The tabshd daemon listens exclusively on the local loopback interface (127.0.0.1). All keystrokes, shell data, and AI interactions are contained within your machine and never transmitted to an external server. The web app connects via a secure token passed in the URL fragment.
2. How does tabsh compare to using a terminal multiplexer like tmux? While both manage persistent sessions, tabsh provides a graphical, web-based Kanban interface for organizing sessions by project and status, which tmux does not. It also offers built-in, configurable integrations for AI coding agents (Claude Code, etc.) as first-class citizens, a feature absent in traditional multiplexers.
3. Can I access my tabsh sessions from another computer or my phone? By default, no, as the daemon is locked to localhost for security. However, you can optionally expose it securely to other personal devices using Tailscale (in Serve mode) or an SSH tunnel. The documentation provides guides for setting this up using the Tailscale IP address.
4. What happens if my browser or computer crashes? The tabsh daemon (tabshd) is designed for resilience. If the browser tab crashes or is closed, you can simply reopen the app URL (http://127.0.0.1:7681), and it will reattach to all running shell and agent sessions, restoring their state, working directory, and scrollback.
5. Is tabsh free to use and is it open source? Yes, tabsh is completely free and open-source software (FOSS) released under the permissive MIT license. The full source code is available on GitHub, allowing for inspection, modification, and community contributions.