Skip to content

Introduction

Adroit is an Agent Workspace for people who live in Vim: one window to drive any coding agent, in its own terminal interface, by hand and the way you edit.

People who live in Vim and work with several coding agent sessions at the same time, often across repositories and often with more than one agent, and who want that work to feel like editing rather than like operating a dashboard.

  • A session is a conversation with an agent. Claude Code, Codex, Pi and OpenCode sessions stand side by side, each in the terminal interface its agent ships, unchanged. See Agents and profiles.
  • You start one by choosing where. Pick a directory, or a repository to clone, and write the first prompt. Nothing has to be set up or declared first, and the session’s agent names it once it knows what the work is. See Getting started.
  • The tree follows git. Sessions are listed under the repository they run in, with each worktree’s files and shells, and the repository’s open pull requests and issues beside them. The sessions waiting on you are listed again at the bottom, across every repository. See The window and Pull requests and issues.
  • You write in Neovim. The prompt under each session is a real Neovim, configured for Adroit with the mappings and plugins you choose. See The prompt.
  • You move with Vim’s grammar. Window motions move between the tree, the windows, the prompt and the details; the tree is browsed like a file explorer. See Keys.
  • You see where the work stands. The details panel shows the session, its changes, the plan its agent records as a timeline, the prompts and messages of its conversation and what it brought up, arranged as you like. See The details panel.
  • Sessions outlive the window. Every session and shell runs in a host of its own. Closing Adroit leaves them running; opening it again finds them as they were, and any number of windows can show the same work. When the host itself goes, Adroit offers to bring them back.
  • Sessions can open sessions. A session can open another for a line of work you will want to steer yourself, and talk with the others as a peer. Each one still answers to you. See Sessions that open sessions.
  • The work can run elsewhere. Pair with a work machine and its sessions appear in the same tree, from any computer that joins it. See Environments and work machines.
  • Rebuild an agent’s interface or replace its console with a chat view.
  • Orchestrate. No session runs others as its workers, and Adroit keeps no plan, task or verdict of its own: the timeline is the agent’s own record of its work.
  • Edit. Files, logs and diffs are there to be read; real editing happens in your usual editor, which Adroit can open beside your sessions.
  • An Apple silicon Mac for the released app. Adroit also builds from source on Windows, and its hosts and session commands build without the window for a Linux or macOS work machine.
  • git, and at least one of Claude Code, Codex CLI, Pi or OpenCode on your PATH.
  • Optionally jj, to read jj repositories and make jj workspaces; ghq, whose repositories the picker offers and clones; and the GitHub CLI gh, to list pull requests and issues and to look through GitHub for a repository.
  1. Install Adroit.
  2. Start your first session.
  3. Learn the window and the keys.