Tag: claude-code

Run Claude Code, Codex CLI, or Aider in parallel with one git worktree per agent, one tmux window each, and a bell that tells you which agent is waiting.

Agent Skills package know-how, MCP servers package access. Here is how each one loads into context, what each one costs, and when your home lab needs which.

Blender MCP is great for building one model with an agent watching screenshots. Headless bpy scripts win for batches, parallel agents, and automated checks.

Prompt-level defenses against injection are probabilistic and lose to a patient attacker. Here's the capability-level design that holds, with working configs.

Coding agents write flawless code and leave hero.png blank. Compare self-hosted GPU image generation against subpixel, a ChatGPT-subscription CLI tool.

Run several Claude Code accounts on one Linux machine. CLAUDE_CONFIG_DIR plus symlinks share your skills, hooks and history while each login stays isolated.

Comparing context-mode, code-review-graph, token-savior, and claude-context, MCP tools that stop AI coding agents from reading your whole codebase blind.

RTK, snip, and lean-ctx filter your AI coding agent's output before it burns context tokens. I run RTK daily, here's the one I'd actually switch to.

Claude Code puts an agentic AI assistant in your terminal for real homelab work, compose files, bash, Ansible, systemd. The honest take on cost and data.

Self-host Gemma 4 or Qwen3-Coder via Ollama or llama.cpp in Docker, then let Claude delegate the grunt work to it. Free tokens, zero code leakage.

Stop burning expensive AI tokens on boring grunt work. The overseer/workhorse pattern routes mechanical tasks to a cheap model and saves more than you'd think.