Inside an agentic engineering setup after 6,775 sessions

Step-by-Step Breakdown

1. Pick an interface that can hold more than one agent

   The setup runs several: an open-source multi-harness UI that puts Codex, Claude Code, Pi, Cursor CLI, OpenCode, Grok and Hermes behind a single interface so no subscription goes unused; a terminal-multiplexer-style workspace tool for split-pane work; and a lightweight terminal-native agent runtime. The stated failure mode of the workspace tool is scale — a left sidebar of workspaces stops being the right primitive once you have many agents.

2. Assemble subscriptions by budget rather than by brand

   The tiers described: ~$10 for a multi-model plan carrying Kimi K3, Grok 4.6, GLM 5.3 and DeepSeek V4 Pro but not the frontier models; add a $20 first-party plan (Codex or Claude) next; add a second $20 plan after that; move to the large plans once budget allows. The repeated instruction is to avoid API pricing entirely — the subsidy only exists inside subscriptions.

3. Provision a VPS and hand it to an agent

   Any VPS with a couple of vCPUs and ~8 GB RAM is enough to start. Rather than following install docs by hand, open a coding agent in one pane and an SSH session in the other, then tell the agent which pane to run commands in. Ondrej primes the session first — telling the agent what the session is for and to answer in plain English — before giving it any credentials.

4. Keep credentials out of prompts and skills

   This is the most transferable rule in the video. If you are repeating a credential often enough to want it saved, put it in a local env file and reference only the file's location in your skills. Never paste credentials or environment variables into a skill or a prompt — those get committed, shared, and fed to models.

5. Install the runtime and dependencies by description, not by command

   The agent is told what the environment needs — a persistent agent runtime, Node.js, Python 3, Git — and finds the current official installers itself. The point made is that this avoids the stale-install-command problem: an agent fetching the latest stable release beats a copy-pasted command from a blog post.

6. Compound: use the installed agent to install the next one

   Once one agent is running on the box, it installs the rest — locating an official installer, running the onboarding, and even finding an existing API key on the local machine to reuse. The framing: fight to set up the first agent, and everything after that is cheap.

7. Alias the long commands you run daily

   A global alias so one or two characters launches a coding agent in its permissive mode, rather than typing the full flag every time. Small, but the stated principle is the point: agentic engineering is about how much you get done in the same time, and re-typing a long flag dozens of times a day is pure loss.

8. Build review skills that fan out to multiple models

   His "total review" skill runs two other review skills — one per model family — against the same change set, so a review is a second and third opinion rather than one model checking its own work. Anything repeated often enough becomes a skill or a text-replacement shortcut.

Gotchas & Caveats

• This video contains an affiliate promotion for a specific VPS host. Nothing in the workflow depends on that host — any VPS with SSH works. We have summarised the method and left the promotion out.
• The subscription rankings are explicitly time-boxed. Ondrej says the best-value plan "could be completely different two months from now," and the claim that one provider's subscription will become the best deal is his prediction, not a current fact. Treat the tier structure as the durable part and the specific plan names as a snapshot — check current rates in our cost calculator.
• Running a coding agent in a permissive, skip-permissions mode — which the alias tip assumes — is a real risk on a machine holding credentials. It is more defensible on a disposable VPS than on your laptop, which is arguably an underrated argument for the VPS setup itself.
• Giving an agent your root SSH credentials means the agent can do anything on that box. That is the trade being made here, stated plainly rather than hidden — and it is another reason the box should be one you can destroy and rebuild.

Key Takeaways

• Do not pay API pricing for agent work. The argument is that subscriptions are subsidised and API rates are not, so the goal is to stack subscriptions by budget: an open-router-style plan at the low end for Kimi K3, Grok 4.6, GLM 5.3 and DeepSeek V4 Pro, then a $20 tier, then the large plans. Whether the specific plans hold, the principle — buy tokens where they are subsidised — is the reusable part.
• Agent state tracking is the interface problem. The reason he uses a runtime that shows which agent is running, idle, or blocked is that human attention is the bottleneck once you pass a handful of agents. A sidebar of workspaces stops working at scale; a state list does not.
• Priority ordering beats round-robin. His own fork ("coral") exists because most multi-agent UIs surface whichever agent finished most recently. He argues a P1 agent finishing should always jump ahead of a P4 — agents have different importance and the queue should reflect it.
• Own your cloud agents to avoid ecosystem lock-in. Hosted cloud-agent platforms require you to load secrets and environment config into them, which is both hours of setup and a switching cost you cannot undo. A VPS running a persistent agent runtime over SSH gets most of the benefit — persistent sessions, many concurrent agents, survives a closed laptop — without the lock-in.
• Use one agent to install the others. The whole VPS build is done by giving a coding agent the SSH session and describing the target in plain English. "You need one agent, and then you use that agent to compound and set up the others."
• Match the harness to the uncertainty of the task. For work where you already know the shape of the answer, use a conventional coding harness. For work where you do not, use a self-improving harness that writes skills as it goes — because that is where accumulated skills actually pay off.