Ai-agent

A year after the first dotfiles post, my arch-config repository looks very different. This post traces the timeline of changes, compares the current setup against the 2025 snapshot, and explains why the AI-agent phase reshaped the whole configuration from a personal-app showcase into a minimal substrate for agent-supervised, browser-first work.

After nearly one year using Arch Linux, my workflow has shifted again: from terminal-first minimalism toward a browser-first system powered by web applications, Surfingkeys, and AI agents controlled through web interfaces.

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.

A practical breakdown of the two main paths for AI agent token access — pay-per-token API and subscription code plans — with real cost numbers and a concrete recommendation depending on whether you work solo or multi-agent.