- Published on
The next step after vibe coding is not removing humans entirely, but removing them from every inner development loop. When agents can verify more of their own work, multi-agent systems stop being blocked by one human reviewer.
Workflow
All Posts
- workflow (14)
- linux (12)
- ai (12)
- opencode (12)
- tools (10)
- multi-agent (10)
- arch-linux (9)
- productivity (9)
- ai-agent (9)
- ai-coding (9)
- claude-code (8)
- ide (7)
- neovim (6)
- wayland (5)
- ikanban (5)
- window-manager (4)
- tiling (4)
- sway (4)
- coding (4)
- plugins (4)
- subagents (4)
- codex (4)
- vibe-coding (3)
- mcp (3)
- cli (3)
- journey (3)
- vim (3)
- dotfiles (3)
- reflection (3)
- configuration (3)
- development (3)
- surfingkeys (3)
- budget (3)
- deepseek (3)
- dynamic-workflows (3)
- rust (3)
- i3 (2)
- river (2)
- skills (2)
- vscode (2)
- editor (2)
- copilot (2)
- setup (2)
- guide (2)
- agent (2)
- introduction (2)
- chat (2)
- automation (2)
- misc (2)
- hyprland (2)
- browser (2)
- blog (2)
- research (2)
- verification (2)
- pricing (2)
- kimi (2)
- video-generation (2)
- superpowers (2)
- ai-workflow (2)
- development-tools (2)
- deepseek-harness (2)
- vibe-kanban (2)
- parallel-workflow (2)
- task-scheduling (2)
- qwen (2)
- 2025 (1)
- niri (1)
- scrollable-tiling (1)
- screen-sharing (1)
- webrtc (1)
- desktop-environment (1)
- x11 (1)
- keyboard-first (1)
- jetbrains (1)
- autohotkey (1)
- windows (1)
- docker-compose (1)
- experience (1)
- daily-use (1)
- security (1)
- openness (1)
- life (1)
- summary (1)
- philosophy (1)
- claude (1)
- specialized-agents (1)
- development-workflow (1)
- github (1)
- godot (1)
- game (1)
- dev (1)
- laptop (1)
- i3wm (1)
- nvidia (1)
- wlroots (1)
- nixos (1)
- declarative (1)
- reproducible (1)
- deploy (1)
- oss (1)
- bot (1)
- js (1)
- typst (1)
- typesetting (1)
- document (1)
- template (1)
- academic (1)
- keymaps (1)
- autonomy-levels (1)
- human-in-the-loop (1)
- chrome-devtools-mcp (1)
- token (1)
- openrouter (1)
- tts (1)
- python (1)
- manim (1)
- cache-hit (1)
- tmux (1)
- academic-research (1)
- cordis (1)
- multi-session (1)
- agent-runtime (1)
- ultracode (1)
- orchestrator (1)
- fzf (1)
- fuzzy-finding (1)
- ade (1)
- ai4paper (1)
- human-ability (1)
- danmu (1)
- streaming (1)
- real-time (1)
- bilibili (1)
- md2video (1)
- agent-first (1)
- markdown (1)
- cui (1)
- harness (1)
- tool-use (1)
- gesture-recognition (1)
- magic-mouse (1)
- multi-touch (1)
- multi-provider (1)
- glm (1)
- keyboard-navigation (1)
- gui (1)
- evdev (1)
- Published on
In the agent coding era, the key OS question is no longer desktop polish for humans, but safe and scriptable execution for agents. For serious AI coding workflows, Linux stands out through its permission model, CLI-first ecosystem, and open customization.- Published on
An introduction to our latest multi-agent workflow for readers new to agent coding: cheaper model access, OpenCode runtime, Superpowers automation, and iKanban review in one four-layer stack.- Published on
A three-part review of the shift from vibe coding to agent coding between January 2025 and March 2026: how software work became more structured, more modular, and more explicitly engineered through agents, MCP, skills, and parallel execution.- Published on
After years of IDE evolution—from JetBrains to VSCode to Neovim—we discovered that the AI era demands a fundamentally different interface. Software should serve AI first, then humans. This insight led us to build iKanban: a two-pane, keyboard-driven AI IDE where less is more.