Custom Linux Workflow: i3wm + tmux + Emacs + AI-RAG + ORUI

Arun Jyothish — Tue, 10 Nov 2026 15:08:22 +0000

A practical profile of a fully tailored Linux development environment built around i3wm, tmux, Emacs, local AI-RAG, and a personal ORUI layer — plus the real benefits of owning your entire stack.

Most people accept the default desktop, the default terminal multiplexer, and a pile of browser tabs. I stopped doing that.

This is a profile of the custom workflow I actually use every day: a fully tailored Linux setup built around i3wm, tmux, Emacs, local AI-RAG, and a personal ORUI layer. It’s opinionated, dense, and extremely effective for the kind of deep technical work I do (embedded systems, FreeRTOS, Jetson edge AI, architecture, etc.).

The Stack

i3wm — The Spatial Foundation

I run a bare i3 window manager. No desktop environment, no panels I don’t control, no animations.

Workspaces are purpose-built:

Dev / Emacs
Terminals + tmux
Browser / docs
ORUI / system overview
Jetson / hardware architecture views

Windows are tiled exactly where I want them. Moving between contexts is a keystroke, not a hunt through a taskbar.

tmux — Persistent Sessions Everywhere

tmux is non-negotiable. Every long-running task lives in a named session:

Firmware builds and serial monitors
Jetson SSH sessions
Log watching
Multi-pane debugging setups

I can detach, reboot the machine, reattach, and everything is exactly where I left it. Combined with i3, I get persistent, tiled, keyboard-driven environments that survive restarts.

Emacs — The Actual Work Environment

Emacs is the center of gravity. Not just an editor — the place where most of the thinking and doing happens.

Org-mode for structured notes and task capture
Lazygit for git
LSP + tree-sitter for C/C++ (FreeRTOS, STM32, etc.)
Custom modes and keybindings tuned to my workflow
Direct integration points with the AI-RAG layer

If something can live in Emacs, it does.

ORUI — The Situational Awareness Layer

ORUI is a Chromium-based personal HUD that sits on top of everything else. It shows:

Live system telemetry (CPU, RAM, network, processes)
A living knowledge graph of FreeRTOS / STM32 concepts
Architecture diagrams (Jetson carrier board, acoustic localization pipeline, etc.)
Occasional focus elements (quotes, short meditations)

It’s not the primary workspace — it’s the always-visible instrument panel. I glance at it the same way a pilot glances at instruments.

Custom Tailored Linux

The base is a minimal Linux install that I’ve shaped over time:

Only the packages I actually use
Custom keybindings and scripts
Fast boot, low idle resource use
Everything reproducible via config files (dotfiles + a few bootstrap scripts)

No desktop environment bloat. No surprise updates. The machine behaves like a tool I own.

How a Typical Session Actually Looks

Boot into i3.
Attach to the main tmux session (or start the ones I need).
Emacs opens in its dedicated workspace with the current Org buffer and code.
AI-RAG is available in a pane or via Emacs for quick lookups
ORUI is on another workspace or a floating/always-visible layer so I can see system state and the knowledge graph without leaving the flow.
Everything is keyboard-driven. Mouse is optional.

Context switches are cheap because the spatial layout (i3), the session persistence (tmux), the thinking environment (Emacs), and the retrieval layer (AI-RAG) all stay consistent.

Benefits

Extremely low context-switching cost

i3 + tmux means the exact layout and state I want is one keystroke away and survives reboots. I don’t lose my place.

Deep, personal knowledge access

The AI-RAG layer is trained on my notes and the docs I actually use. It beats generic web search for domain-specific questions.

High situational awareness without noise

ORUI gives me live telemetry and a visual map of concepts without forcing me to open another monitoring tool or Notion page.

True ownership of the environment

Because the whole stack is mine (window manager, multiplexer, editor, RAG, HUD, base OS), I can change any part of it when it starts to get in the way. Nothing is locked behind a vendor’s defaults.

Scales to complex multi-domain work

Embedded firmware, edge AI, architecture diagrams, and knowledge management all live in the same coherent system instead of five different apps.

Focus and sustainability

The setup is quiet, fast, and keyboard-centric. It stays out of the way for long sessions.

Who This Is For

People who already live in the terminal and want the rest of the system to match
Developers working on complex, multi-layered technical problems (embedded + AI + systems)
Anyone who has felt the friction of modern desktop environments and browser-based tools
Solo builders who want maximum leverage from their tools

Honest Limitations

High upfront investment. You have to configure i3, tmux, Emacs, and the RAG pipeline yourself.
Steep learning curve if you’re not already comfortable with keyboard-driven tools.
It’s personal. My keybindings, Org structure, and knowledge graph won’t transfer cleanly to someone else.
ORUI and the RAG layer are custom — they require maintenance when the underlying tools change.

Closing

The point isn’t “everyone should use i3 and Emacs.” The point is that owning your entire workflow — from the window manager up through retrieval and awareness layers — removes a surprising amount of friction.

Once the pieces (i3wm, tmux, Emacs, AI-RAG, ORUI, tailored Linux) are all pointed in the same direction, the environment stops being something you fight and starts being something that compounds.

DEV Community: Arun Jyothish