An Agent Workspace for people who live in Vim

Drive every coding agent the way you edit.

Adroit puts your Claude Code, Codex, Pi and OpenCode sessions side by side in one window, each in the interface its agent ships. You write to them in a real Neovim and move between them with Vim's motions, by hand.

Free and open source · macOS on Apple silicon, Windows from source, headless hosts for Linux · Early, expect rough edges

Adroit's window: on the left the tree of sessions by repository, with its terminals, pull requests, issues and worktrees, and the session waiting on you listed again at the bottom; in the middle a tab holding a Claude Code session and a Codex session side by side, each in its own interface, with a prompt written in Neovim; on the right the details of the focused session, the timeline its agent records of its work, and its usage.

The hand on the work

Many tools run agents for you. Adroit is for working with them yourself, at the pace of your attention and your review, and for that to feel like editing rather than operating a dashboard.

  1. Any agent, as it is

    Claude Code, Codex, Pi and OpenCode run in the terminal interfaces they ship, unchanged, side by side. Pick the agent for the work, not the tool for the agent.

    Ctrl+gp
    next profile on a new session
  2. Writing in Neovim

    The prompt is a real Neovim, with your motions, operators, registers, mappings and plugins. Not an input line that imitates a few of them.

    i
    write to the session
    Ctrl+Enter
    send
  3. Moving in Vim's grammar

    Panes, the tree of sessions and what is selected are reached with motions and acted on with commands, as text is in Vim. Nothing needs the mouse.

    Ctrl+qhjkl
    move between windows
    Mod+j
    next session waiting on you

And the ground under it

What any place for agent sessions has to do well, done so it never gets in the way.

Start by choosing where. Nothing else.

Press Mod+p, pick a directory from those already in use, from your ghq repositories or from a file tree, and write the first prompt. The session lands in the tree under its repository, and its agent names it once it knows what the work is.

No project to set up, no task to declare. What the work turns out to be shows as you go. With no directory at all, a scratch session talks it through and hands the work to a session in the project once it turns into one.

Not cloned yet? Type github.com/owner/repo, or github: to look through GitHub, and the picker clones it with ghq.

Adroit's picker, titled Go to a session, or start one, with github.com/acme/web typed: two ghq repositories offered to start in, and a row to clone github.com/acme/web with ghq.Adroit's picker, titled Go to a session, or start one, with github.com/acme/web typed: two ghq repositories offered to start in, and a row to clone github.com/acme/web with ghq.

A shell where the work is.

Press Mod+s and a shell opens in the current worktree, listed under its Terminals beside that worktree's sessions and files. Run the build or the tests there, and read them in the same window.

Like a session, a shell keeps running when the window closes. Sessions can start one too, so a dev server or a probe an agent runs is in the tree where you can see it, not hidden in the background.

Shells and terminals

Adroit's window with the api repository's terminals in the tree, a cargo run terminal serving requests split above a shell showing git status and log, and the details panel on its Overview tab with the machine's meters.Adroit's window with the api repository's terminals in the tree, a cargo run terminal serving requests split above a shell showing git status and log, and the details panel on its Overview tab with the machine's meters.

Read what the work wrote.

A Markdown document opens in a viewer drawn in Adroit's theme, as GitHub would draw it: tables, highlighted code, alerts, formulas and Mermaid diagrams included. It follows the file as the agent changes it, at the place you were reading.

Press e and the same window switches to Neovim on the document, and back. Images a session draws open in a lightbox, one key from the next.

Viewers

The api repository's README.md opened from the tree's Files in Adroit's Markdown viewer, showing code blocks, a table of endpoints and a flowchart drawn from Mermaid, beside the tree with changed files marked.The api repository's README.md opened from the tree's Files in Adroit's Markdown viewer, showing code blocks, a table of endpoints and a flowchart drawn from Mermaid, beside the tree with changed files marked.

The details, arranged your way.

The details panel tells about what you are looking at: the session and its change, the timeline its agent records, its prompts and messages, the files and links it brought up, the account's limits and the machine's load.

Each of these is a component. Drag them onto tabs of your own, or onto the foot shown under every tab, on a picture of the panel in Settings.

The details panel

Adroit's Settings window on Details panel: a picture of the panel's Overview tab with a sample session and a foot of context, limits, CPU and memory, beside the tab's name and icon and the list of components to drag onto it.Adroit's Settings window on Details panel: a picture of the panel's Overview tab with a sample session and a foot of context, limits, CPU and memory, beside the tab's name and icon and the list of components to drag onto it.

What Adroit is not

The concept behind it

Install

Adroit needs git and at least one supported agent on your PATH. jj, ghq and the GitHub CLI are used when installed.

Homebrew

The released app, for Apple silicon Macs.

brew install --cask adroit-app/tap/adroit

Nix

The same build from the flake, prebuilt in Cachix.

nix profile install github:adroit-app/Adroit