A terminal IDE you can
use in five minutes.

No tutorial. No muscle-memory tax. If you come from VS Code, Zed, or JetBrains, everything works the way you expect: visible menus and tabs, a command palette, familiar shortcuts, real mouse support. And your coding agent gets a cockpit, not just a terminal tab.

$ brew install GurYN/tap/cove
Get started ★ Star on GitHub
sources
▾ cmd
▾ cove
main.go
▾ internal
▸ app
▾ git
diff.go
diff_test.go
git.go
▸ lsp
▸ syntax
▸ term
▸ scripts
go.mod
README.md
Files
Search
Git
Review
Terminal claude 1 +
~/Projects/cove-editor/sources ❯ on main at 12:40:26
❯

A scripted walkthrough: open a file, split the view, run a build, right-click to stage, commit — then hand the next change to Claude Code and review it. Click to skip ahead.

// WHAT'S INSIDE

GUI ergonomics, terminal speed

// AGENT COCKPIT

Your coding agent, with an editor behind it

Claude Code, aider, codex, opencode — anything that runs in a terminal. Flag it agent = true in the config and the panel it runs in becomes a cockpit: you feed it context, it queries your language servers, and every edit it makes lands in a review queue.

1

Send context, not screenshots

Select code and press Alt+A: it lands in the agent's prompt as a path:line-line reference plus a fenced block. Same for the file under the cursor or the diagnostic under it. Cove never presses Enter for you.

Alt+A · Send Selection
2

The agent asks the editor

Cove serves its warm language servers over MCP: diagnostics, definition, references, hover, symbols, rename, project search — straight from gopls, pyright, tsc, rust-analyzer or clangd, instead of the agent re-running builds and grepping.

cove mcp · one-time register
3

Review every hunk

Launching the agent takes a checkpoint. The Review panel lists what changed since, per prompt. r reverts, a accepts by staging, x pastes the hunk back to ask about it, d shows checkpoint │ now. Files that gained errors are flagged.

Alt+R · Review Changes

Two lines of TOML

One [apps.*] entry with agent = true. Register the MCP server once from the palette (Agent: Register Cove's MCP Server with Claude Code) and every agent started in the panel finds its editor through COVE_SOCKET. Outside Cove, the server simply has no tools.

[apps.claude] command = ["claude"] agent = true [mcp] enabled = true [agent] checkpoint_on_launch = true follow = false
// LANGUAGE SUPPORT

Syntax in the binary. Intelligence on your PATH.

Tree-sitter highlighting ships built in for fifteen languages — C/C++ is the newest — plus the config files around them: .env, .gitignore, go.mod, lockfiles, shell dotfiles, INI-style files. Language servers plug in from your PATH — seven come preconfigured, and any other registers with a few lines of TOML. The same servers answer your agent over MCP.

LANGUAGESERVERINSTALL

Still on TypeScript 5? Cove probes your tsc once and falls back to typescript-language-server automatically — no config needed. On a Mac, clangd already ships with the Xcode command line tools.

// GET STARTED

Two ways in

Homebrew

macOS / Linux. Builds from source (tree-sitter uses CGo); Homebrew pulls the Go toolchain for you.

$ brew install GurYN/tap/cove

From source

Go 1.26+ and a C compiler. Then open a file or a whole directory.

$ git clone https://github.com/GurYN/cove-editor $ cd cove-editor && go build -o cove ./cmd/cove $ cove .
Or download a release binary ↗

On Windows? Cove runs great in WSL — install with Homebrew inside it.

If it needs a manual, we failed.

Every keybinding, theme, server, agent, and AI endpoint lives in one TOML file. A Vim keymap is one setting away — opt-in, never default. Cove is pre-1.0 and in active development, MIT-licensed and open on GitHub.