Agents Are Teammates, Not Tools

The first year I used LLMs, I treated them like a smarter compiler: input in, artifact out. The results were fine. The leverage was small.

Everything changed when I started treating agents as teammates with a job description. A teammate has scope, memory, opinions about their craft, and a way to raise their hand when blocked. A tool has none of that.

What changes in practice

When an agent is a teammate, you stop writing prompts and start writing onboarding docs. My agent definitions now look like the first-week guide you would hand a new engineer: here is the codebase philosophy, here is what good looks like, here is when you must ask before acting.

The second shift is communication structure. Two agents passing free-form text to each other degrade fast. Two agents passing typed messages (proposal, review, handoff, block) stay coherent for hours. The orchestrator can supervise conversation state instead of guessing from prose.

The uncomfortable part

Managing a team is harder than using a tool. You inherit management problems: unclear requirements produce confident nonsense, silent failure is worse than loud failure, and a stalled worker costs money by the minute. The engineering that matters is supervision, budgets, and checkpoints, not clever prompting.

But the ceiling is completely different. A tool caps out at your own speed. A team compounds.