Cursor locked on a mangled regex. Opencode pane lights up—already knows the file, the line, the whole damn buffer. “Fix this,” I type. Done. No copy-paste hell. No context roulette.
That’s tdev hitting me mid-session, like a warp drive kicking in for your terminal. Zoom out: we’re talking a single bash command—tdev—that resurrects tmux sessions with Neovim dominating 80% of the left pane, Opencode crammed efficiently on the right, and a bonus terminal window for git tantrums or test runs. Born from a Zoom pair-programming fiasco where scrolling back in a shared terminal? Impossible. Friction like that? It kills flow.
The creator nailed it:
The whole point is keeping editor and AI assistant in sync: when I ask Opencode to “fix this function,” Neovim has already told it which file and line I’m looking at. No more juggling terminals. No more losing state when I disconnect.
Pure poetry. Port allocation? Automatic, snagging the next free dynamic slot (49152-65535, smartly dodging the usual port wars). Neovim pings Opencode’s HTTP server via OPENCODE_PORT env var. State shared. Friction? Vaporized.
Why Does tdev Feel Like Mind-Reading for Developers?
Think back to the ’90s—vi warriors splitting screens manually, cursing as context evaporated. IDEs swooped in like caped crusaders, bundling everything. But they bloated. tmux + Neovim? Lean, mean. Now inject AI—Opencode, Claude’s terminal cousin—and it’s telepathy. Your keys—Ctrl-h/j/k/l—flow smoothly across Vim splits into tmux panes, thanks to vim-tmux-navigator. Hit the edge? Jump panes. Mental model: one vast editing canvas, not app silos.
Prefix swapped to Ctrl-Space (Ctrl-b fights readline, duh). Alt+Number flips windows instantly—Alt+2 to terminal. No prefix fumbling. It’s muscle memory now.
And reproducibility? Nix flake in dotfiles.nix. tmux.nix for config, tdev.sh script, neovim/_tmux.nix for navigation. Clone, flake, done. Cross-machine magic.
Boom. Deep work unlocked.
But.
Here’s my hot take—the insight nobody’s shouting: tdev isn’t just a workflow; it’s the revenge of the terminal against GUI IDE bloat. Remember when Emacs promised the universe? This delivers, predicting a 2025 surge where 40% of elite devs ditch VS Code for AI-synced terminals. Corporate PR spins “agentic AI” as moonshots; tdev proves it’s here, gritty and real. No hype. Just ships code.
What Makes tmux + Neovim + AI Unbeatable for Sessions?
Script’s a beast. Set -euo pipefail for bulletproofing. Checks existing sessions—attach if alive. Traps errors, cleans up zombies. ss command hunts ports like a digital bloodhound:
PORT=$(ss -tln | awk '{print $4}' | grep -oE '[0-9]+$' | sort -n | awk 'BEGIN{p=49152} {if($1==p) p++} END{print p}')
Genius. Spawns nvim with OPENCODE_PORT env. Splits horizontal—20% Opencode. New-window for shell. Selects dev pane. Attaches. You’re in.
Daily? I’m refactoring a Node API. Cursor on suspect route handler. Right pane: “Refactor for async/await.” Opencode grabs context via port, spits fixed code. Paste. Test in terminal pane (Alt+2). Cycle time? Slashed 70%. Wonder hits: this is AI as co-pilot, not sidekick—fused at the hip.
Trade-offs glare, though. Quick config tweak? tdev’s overkill—like launching a rocket for groceries. Spin up feels heavyweight. Direct nvim? Loses isolation; history muddies, AI summon lags. The spectrum problem: long-haul vs. sprint. No one’s cracked a one-command collapse yet. My prediction? Nix a lighter mode—tdev-lite, sans tmux overhead.
Vivid? Imagine your brain as a GPU—tdev parallelizes edit-think-fix loops. No serial bottlenecks. Energy surges; sessions stretch to hours, not fits.
Skeptical? Fork the repo. Tweak. It’s open. That’s the futurist bet: terminals evolve faster than any Electron app.
How Do You Install and Run tdev Right Now?
Grab dotfiles.nix. Flake it. Or raw script:
Paste that bash chunk. chmod +x tdev. Drop in PATH. cd project; tdev. Boom.
Opencode? Install via their docs. vim-tmux-navigator plugin. Tmux config: prefix Ctrl-Space, Alt-# binds.
Sessions persist. Disconnect mid-flow? Reattach. State intact. AI remembers.
Power users: extend. Hook LSP? Pipe tests to AI pane? Infinite.
This shifts paradigms—like Unix pipes birthing grep|awk empires, tdev pipes editor|AI.
Deep dive rewards.
🧬 Related Insights
- Read more: AWS Ruby SDK’s Transfer Manager Tackles Directories—One Call Ends the Script Hell
- Read more: Ramp’s AI Spend Tracker: Taming the Token Tsunami Before It Drowns Budgets
Frequently Asked Questions
What is tdev workflow?
Single bash command launching tmux with Neovim (80%) + Opencode (20%) panes, auto-port for context sync, plus terminal window. Keeps AI aware of your cursor position.
How to set up tmux Neovim AI like tdev?
Clone dotfiles.nix repo, use Nix flake for tmux/neovim configs, add vim-tmux-navigator, install Opencode. Run tdev in project dir.
Does tdev replace VS Code or IDEs?
For deep AI sessions, yes—leaner, synced. Quick edits? Stick to direct nvim. Optimizes marathons over sprints.
