13 articles found
Running Claude Code, Codex, and Open Code at the same time is the new normal. Warp just shipped features that make it actually manageable — vertical tabs, code review, voice input, and custom tab configs.
Build a meta-skill that audits every other skill in the system — scoring effectiveness, reliability, and efficiency nightly.
Build the self-healing heartbeat and set up remote access to your agent from anywhere.
Build the meeting ingest skill and add failure handling to the entire agent.
Build three monitoring skills using the same pattern: PR reviewer, git reviewer, and standup generator.
Build your first skill (daily planner) and set up the scheduling system. Skills turn your agent from reactive to proactive -- it works on its own, on a schedule.
Give your agent the ability to learn from corrections in real-time. When you correct the agent, it writes the correction to a file immediately -- not at the end of the day, but in the same turn.
Add hooks to your agent for Telegram notifications and safety gates. Hooks give the agent reflexes -- deterministic behavior that fires every time, regardless of context.
Create the agent's brain (CLAUDE.md) and memory (state files). These four files are the foundation everything else builds on.
See the finished agent system before building anything. Understand the autonomy loop, the difference between a chatbot and an agent, and what makes Claude Code suitable for this.
Git worktrees have been around for years, but AI agents just made them essential. Here are two practical setups for running multiple agents on the same repo without conflicts.
Claude Code, Codex CLI, Gemini CLI — each has its strengths. Git worktrees, a shell function, and a terminal with splits let you run two agents on the same task and compare before you commit.
I started using Ghostty after I found myself running multiple Claude Code sessions at the same time. Here's my exact setup.
