---
title: The Case for a Keyboard-Driven Workflow
description: The CLI tools and shortcuts behind a keyboard-driven workflow that cut my mouse use to almost nothing, and the two places the mouse still wins outright.
canonical: https://lukeocodes.dev/keyboard-driven-workflow
type: article
locale: en_GB
published: 2026-08-28T00:00:00.000Z
modified: 2026-08-28T00:00:00.000Z
authors:
  - Luke Oliff
section: Opinion
tags:
  - Opinion
  - Developer Experience
  - tmux
  - fzf
  - vim
  - tiling wm
  - terminal
  - productivity
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Engineer and developer relations leader. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Engineer and developer relations leader
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Engineer and developer relations leader. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Engineer and developer relations leader
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/keyboard-driven-workflow#article
        headline: The Case for a Keyboard-Driven Workflow
        alternativeHeadline: The Case for a Keyboard-Driven Workflow
        description: The CLI tools and shortcuts behind a keyboard-driven workflow that cut my mouse use to almost nothing, and the two places the mouse still wins outright.
        datePublished: 2026-08-28T00:00:00.000Z
        dateModified: 2026-08-28T00:00:00.000Z
        url: https://lukeocodes.dev/keyboard-driven-workflow
        mainEntityOfPage: https://lukeocodes.dev/keyboard-driven-workflow
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Opinion, Developer Experience, tmux, fzf, vim, tiling wm, terminal, productivity
        articleSection: Opinion
        about:
          - "@type": SoftwareApplication
            name: tmux
          - "@type": SoftwareApplication
            name: fzf
          - "@type": SoftwareApplication
            name: Vim
          - "@type": Thing
            name: Developer Experience
        abstract: A keyboard-driven workflow built on tmux, fzf, a tiling window manager and vim motions removes most of the reach-for-the-mouse tax. Here's what actually stuck, and where a pointer still beats a keystroke.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=The+Case+for+a+Keyboard-Driven+Workflow&d=The+CLI+tools+and+shortcuts+behind+a+keyboard-driven+workflow+that+cut+my+mouse+use+to+almost+nothing%2C+and+the+two+places+the+mouse+still+wins+outright.&e=Writing
        wordCount: 633
        timeRequired: PT4M
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: The Case for a Keyboard-Driven Workflow
            item: https://lukeocodes.dev/keyboard-driven-workflow
      - "@type": FAQPage
        "@id": https://lukeocodes.dev/keyboard-driven-workflow#faq
        mainEntity:
          - "@type": Question
            name: Do I need a tiling window manager for a keyboard-driven workflow?
            acceptedAnswer:
              "@type": Answer
              text: No. Start with fzf and shell history search, they pay off in a day. A tiling window manager is a bigger commitment and the last piece I'd add, not the first.
          - "@type": Question
            name: What's the single fastest win for keyboard-driven work?
            acceptedAnswer:
              "@type": Answer
              text: Binding fuzzy history search to Ctrl-R with fzf. It replaces most of your terminal reaching-and-clicking in one afternoon and works everywhere your shell does.
          - "@type": Question
            name: Where does the mouse still beat the keyboard?
            acceptedAnswer:
              "@type": Answer
              text: Design canvases like Figma, freeform diagramming, and any unfamiliar web app that never bothered with shortcuts. Dragging a shape into place is faster than describing it in keystrokes.
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# The Case for a Keyboard-Driven Workflow

Aug 2026 · [Opinion](/blog/category/opinion) · 4 min read · [Luke Oliff](/authors/luke)

**TL;DR:** A keyboard-driven workflow built on tmux, fzf, a tiling window manager and vim motions removes most of the reach-for-the-mouse tax. Here's what actually stuck, and where a pointer still beats a keystroke.

A keyboard-driven workflow is worth building because the constant reach to the mouse is a tax you pay hundreds of times a day and never notice. Move the common actions to the home row and you get the time back plus a chunk of focus, since your hands stop leaving the keyboard mid-thought. The tools that got me there: tmux, fzf, a tiling window manager, and vim motions everywhere they're allowed.

On 28 August 2026 a post titled ["GUIs should be fully keyboard-driven"](https://ckardaris.com/blog/2026/08/28/keyboard-driven-guis.html) went up on Charalampos Kardaris's blog and lit up Hacker News. The argument: there's nothing stopping a GUI being as keyboard-navigable as a terminal, and most just don't bother. I agree, but I'm not waiting for every app to fix it. I built around the ones that already work.

## The four tools doing the heavy lifting

`fzf` is the one I'd install first if I could only keep one. Wired into `Ctrl-R`, it turns shell history from a blind up-arrow scroll into fuzzy search. `Ctrl-T` fuzzy-finds files under the cwd. Type a few non-adjacent letters and the match surfaces. This single change removed more mouse trips than anything else I did.

`tmux` holds the session together. One prefix key, then a letter to split a pane, jump between windows, or detach and reattach later with the layout intact. I don't reach for the terminal app's own tabs anymore. I haven't opened them in months.

Vim motions are the part people resist and then can't give up. `hjkl` to move, `ciw` to change a word, `dd` to kill a line. I run them in Neovim, and through the vim keybinding modes in VS Code and the browser (Vimium), so the same muscle memory carries across the three places I read and edit text.

The tiling window manager is the last and biggest piece. On macOS I use AeroSpace, which lays windows out automatically and moves focus between them with a modifier plus a direction key. No dragging, no hunting for a half-hidden window, no clicking a dock icon and praying. Windows just go where the keyboard sends them.

## Building a keyboard-driven workflow that sticks

The mistake is installing all of this in one weekend and quitting by Wednesday. Add one tool, let it become invisible, then add the next. `fzf` first, because the payoff is same-day and the muscle memory is trivial. `tmux` second. Vim motions third, and give that one a fortnight before you judge it, because it feels slower for about ten days and then it doesn't. The window manager last, once the rest is automatic.

Remap Caps Lock to something useful while you're at it. It's the best-placed key on the board doing the least work. Mine sends Escape on tap and a modifier on hold, which feeds both the vim motions and the window manager.

## Where the mouse still wins, and I let it

I'm not a purist about this. A keyboard-driven workflow is a default, not a religion. Some work is genuinely spatial, and pretending otherwise is just posturing.

Figma and any design canvas: dragging a shape into position is faster and clearer than describing the move in keystrokes. Freeform diagramming, same. Reading a long article, I'll grab the mouse to scroll and skim rather than page through with the keyboard. And any unfamiliar web app that never implemented shortcuts, I'm clicking, because learning nonexistent bindings is a worse use of time than a few clicks.

The goal was never zero mouse. It was making the keyboard the fast path for the ninety-odd percent of the day that's text, navigation and repetition, and leaving the pointer for the genuinely spatial rest. That split has held for years now, and the reach for the mouse finally feels like a decision instead of a reflex.

[← Newer: AI Safety Became a Marketing Department](/ai-safety-marketing)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
