termco_
Download

The complete workspace

Tools change. The project stays put.

Termco treats the project—not a terminal tab, AI conversation, or remote host—as the unit of work. Each capability appears around that shared context.

release/1.4 · local previewReady
Termco showing local Preview next to Git changes
One active projectSource → runtime → review
01

Workspace

Terminal sessions, panes, files, editor, LSP, search, command palette, and shortcuts.

02

Review

Git status, staged changes, diff review, commit graph, and local Preview in the same project.

03

AI

Provider-backed chat, tool approvals, workflows, managed agents, and external MCP access.

04

Environments

Local projects, SSH rigs, remote files, containers, ports, logs, and forwarded Preview.

05

Composition

Official, team, and user plugins with versioned contracts and independent releases.

06

Profiles

Share team-level plugins and commands while keeping user control over the active composition.

Workspace

Move through the work, not between apps.

Start a shell, edit a file, inspect diagnostics, search the project, review the diff, then run the result in Preview. The working directory and project state are already there.

  • Persistent shell sessions and pane layouts
  • Editor, LSP, syntax, search, and file navigation
  • Git changes, history, staging, commit, and diff surfaces
The Termco workspace moving through its built-in project surfaces.
Starting and following a managed coding agent against the current project.

AI and agents

Choose how assistance enters the project.

Use a model provider in built-in chat, author repeatable workflows, launch a managed agent locally or over SSH, or expose scoped tools to an external MCP client.

  • Provider configuration before chat is offered
  • Visible tool and file-change approvals
  • Current project directory prefilled for managed agents

Remote systems

Carry the workspace across the connection.

SSH is a first-class rig, not a detached terminal session. Browse remote files, inspect containers, forward ports, open services, and run agents where the project lives.

Set up a remote rig
Remote files and containers inside an SSH rig.

Plugin platform

Change the feature, not the whole application.

Plugins carry product capabilities behind explicit contracts. Official plugins update independently. Developers can create a new plugin, fork an existing one, replace its contribution, verify it, and roll back.

Read the plugin model
A plugin fork replacing an official contribution inside Termco.