The bar for shipping is about to get absurd. Local-first multi-service stacks, terminal agents that actually finish work, and zero-friction hot reload are becoming table stakes. Here’s the short list:
- Claude Code / OpenCode / Codex CLI — terminal agents that read the repo, edit across files, run tests, and keep going.
-
TDK CLI — turn a simple
service.jsoninto a full local Docker + Tilt stack.tdk upand you’re running multi-service apps with hot reload, no Kubernetes, no hand-maintained Compose files. Production stays on Helm. - Cursor (or Zed) — the AI-native editor that doesn’t fight you.
- Bun — JS/TS runtime that makes everything else feel slow.
- ripgrep + fzf — instant search and navigation. Still undefeated.
- lazygit — Git without leaving the terminal or losing flow.
- Ollama — local models for when you don’t want (or can’t) hit the cloud.
- gh — GitHub from the shell. PRs, issues, reviews, releases.
- Docker + Tilt — the actual runtime TDK (and everyone else) sits on. Learn them once.
- uv (or mise) — one tool that handles language versions and packages without the usual pain.
TDK CLI is the one most people still haven’t tried. Define the service once, run tdk doctor then tdk up, and the local stack (Dockerfiles with golden layers, Tilt live updates, Traefik, health checks, etc.) just appears. Perfect for the “agents generate services, you need them running and reachable in seconds” world we’re already in.
Install:
curl -fsSL https://tdk-landscape.github.io/install.sh | sh
or npm install -g @tdk-landscape/tdk-cli-core
If your 2027 stack is still “manually wire Compose + hope the wiki isn’t lying,” you’re going to feel it.
Top comments (0)