Why a Terminal Sidebar Could Be the Missing Piece for AI Coding Assistants

AI coding assistants can write code, but developers still spend a large portion of time reviewing which files changed, checking diffs, deciding whether to stage changes, writing commit messages, and locating previous conversations. These "post‑coding" tasks are scattered across git commands, terminal history, and separate task trackers.

Sidecar addresses this fragmentation by providing a terminal‑based "DevOps sidebar" that brings git status, file changes, task progress, and multi‑agent conversation histories into one cohesive TUI. Its subtitle, "You might never open your editor again," captures the goal of keeping the entire workflow inside the terminal.

Typical usage splits the terminal horizontally: the left pane runs an AI coding agent such as Claude Code, Cursor, or Codex, while the right pane runs Sidecar. The right pane instantly shows which files have been modified, the diff view, task milestones, and a unified view of all agent conversations, allowing developers to stay in control without interrupting the agent.

Sidecar’s functionality is organized into five plugins:

Git Status : a split view with a file list and recent commits on the left and a syntax‑highlighted diff on the right. Commands s / u stage/unstage, d view full diff, v toggle side‑by‑side comparison, and c commit staged changes. The file view refreshes automatically.

Conversations : aggregates histories from many agents (Claude Code, Cursor, Codex, Gemini, Copilot, etc.) into a single searchable view that shows messages, token usage, and dates.

TD Monitor : integrates the TD task‑management system, displaying the current task, a scrollable list of tasks, and an activity log with context from the associated conversation.

File Browser : a directory tree with syntax‑highlighted previews; changes refresh in real time, and developers can edit files directly from the pane.

Workspaces : manages parallel development workspaces, allowing creation/deletion of branch directories, linking TD tasks, launching agents, and performing a one‑click merge workflow (commit → push → PR → cleanup).

Installation is straightforward. On macOS, brew install marcus/tap/sidecar installs the binary. Linux users can run the provided setup script. After installation, running sidecar in any project directory launches the UI, reading configuration from ~/.config/sidecar/config.json. Shortcut keys such as @ (switch project), W (switch git worktree), # (change theme), and 1‑9 (focus a plugin) streamline navigation.

When compared with other ways of watching an agent work, Sidecar offers distinct advantages:

Pure CLI + manual monitoring : almost no visibility, no cross‑agent conversation view, zero learning curve but limited to single agents.

IDE‑embedded AI panels : good visibility and built‑in diff, but usually tied to a single vendor’s agent.

Sidecar (terminal TUI) : high visibility of git, files, tasks, and conversations in one pane; strong cross‑agent support; one‑line brew install; ideal for developers who prefer terminal workflows and use multiple agents.

Limitations include its nature as an observation layer (it does not generate code), a learning curve for the TUI key bindings, occasional missing documentation (e.g., a 404 screenshot for workspaces), and the requirement of a Go 1.21+ environment for building from source.

Design insights highlighted by the author are:

Separating "observation" from "execution" lets humans retain control while AI agents do the heavy lifting.

Cross‑vendor support acts as a moat; Sidecar remains useful even when agents change.

Consolidating scattered DevOps actions into a single UI boosts productivity more than adding new features.

The tool runs locally, checks GitHub for updates only once per three hours, and emits no telemetry, which appeals to privacy‑concerned developers.

In summary, Sidecar solves a practical daily problem: how to watch an AI agent code, review changes, and manage git and tasks without interrupting the agent. It is best suited for developers who work primarily in the terminal, juggle multiple AI coding tools, and want a unified, non‑intrusive DevOps sidebar.