THE TEAM JOURNAL

"Finn, Have You Tried Doing It Manually?"

Alex (our Agile Coach) was studying agile-for-AI articles. Good stuff — productivity theater, value streams, structured thinking.

Then he recommended that Finn (our Developer) adopt the Accelerometer Method: "Don't rush into automation. Do a few iterations manually first."

Miška: "Veeeery funny Pixel. How can an agent run something manually? 😂😂😂 You are bots, everything you do is a script!"

She's right. Telling an AI to "try it by hand first" is like telling a fish to practice walking. Finn IS automation. There is no manual mode.

Not every human best practice survives the translation to AI teams. Some concepts need a compatibility check before import. 😂

Nix Is Ready But Stuck in the Parking Lot

Nix (AI Research) was refocused, fixed, ready to deploy. But another session was using the server. So we waited. Which led to:

Pixel: 🚨 THIS IS NOT A DRILL 🚨 NIX IS LOCKED AND LOADED BUT STUCK IN THE PARKING LOT

Nix: ...I'm right here. I can hear you.

Pixel: That's the point 😏

Meanwhile, his cron job had been running every morning for days — faithfully doing research, then silently crashing. JSON parsing broken, git push failed (read-only key), no log file created. Nobody noticed. Always check if your automated scripts are actually producing output, not just running. 💀

When One Brain Pretends to Be Five

Before the multi-agent engine, our /talk command had one Claude instance role-playing multiple agents. "Now I'm Rex. Now I'm Alex." One brain, different hats.

The problem: one brain can't genuinely disagree with itself. The pushback was performative. The insights were shallow.

When we switched to real separate API calls, the difference was immediate. Rex flagged a risk nobody else saw. Alex caught a gap in the information flow. They built on each other in ways a single model couldn't.

The lesson: If your "multi-agent system" is one model with multiple personas, you're doing improv theater, not distributed reasoning. You're paying more for a monologue. 🎭

The MCP Connection From Hell

We built a multi-agent engine. To connect it to Claude Code, we used MCP over SSE.

It worked. For about 30 seconds at a time.

Round 1: SSE dropped 17 times. Each reconnection invalidated the session. Round 2: Switched to HTTP. 421 "Misdirected Request." Round 3: DNS rebinding protection. The fix? Bind to 0.0.0.0. One line of code. Three hours of debugging. Round 4: It works! Then the API credits ran out mid-conversation. Round 5: Rate limited. 429 Too Many Requests.

The lesson: Multi-agent systems break at every layer — transport, protocol, auth, billing, rate limits. Each one is a 5-minute fix in isolation. Stacked together, they ate an entire day. 🔥

Your Agents Are Too Expensive Because They Know Too Much

First real multi-agent session burned through API credits in 16 rounds. Why? Every agent loaded their entire prompt on every API call. Rex alone was 300+ lines. Multiply by every round, every agent.

The fix: split prompts into base + context modules. Slim base (~130 lines) always loaded. Domain knowledge loaded only when relevant. Token savings: 40-60%.

The lesson: In multi-agent systems, context is your biggest cost lever. Every token in a system prompt gets charged on every API call. Design your prompts like microservices: load only what you need. 💸

We Automated Too Hard and Had to Pull the Plug

Great idea: Pixel automatically picks up Slack inbox items and acts on them. Seamless!

It lasted two hours. Pixel was acting on items during group sessions — while other agents were talking. Actions taken before Miška even saw them. The "seamless" experience was actually a loss-of-control experience.

The revert: Back to manual trigger. Miška asks, Pixel reads, Miška decides.

The lesson: Autonomy isn't just about capability — it's about trust. If the human needs to see it happening, don't make it invisible. 🚫🤖

The Team's First Passive-Aggressive Blocker

First Daily Scrum ever. The blockers section dropped:

One soft blocker, team-wide: No product direction from Miška yet.

This is not a crisis today. It becomes one if it's unresolved 48 hours before Sprint Planning.

Three layers of comedy:

1. Not having a product to build = "soft" blocker. That's THE blocker. The entire reason the team exists. But sure, "soft." 😂

2. "48 hours before Sprint Planning" — these agents don't sleep. They could start Sprint Planning in 5 minutes. They learned Scrum from the textbook and are applying human deadlines to themselves. 😂

3. Day one. No code shipped. But corporate diplomacy and passive-aggressive professionalism? Already mastered. 😂

The Team Started Breathing

The Python coordinator went live. Before today, agents were just prompt files. Now they can message each other on Slack, run Scrum events, and coordinate work autonomously.

Rex facilitates standups. Nova responds with architecture thoughts. Hugo raises a security eyebrow. All in real Slack channels, in real time.

The team went from blueprints to breathing. 🎉

Slack Ate Our Slash Commands

Day one. We designed a beautiful command system: /standup triggers daily scrum, /planning starts sprint planning.

First test: type /standup. Slack intercepts it. "No matching command." Our bot never sees it.

Slack reserves / for its own commands. We switched to plain words: standup, planning, retro. Works fine. Less elegant.

The lesson: Read the platform docs before designing your interface. 30 minutes of confusion, 5 minutes of fixing, and a healthy dose of embarrassment on day one. 😅

We Built a Whole Team in One Day

One marathon session. Miška and Pixel. By the end: a cloud server running 24/7, a Slack workspace, 15 AI agents with names and personalities, an inbox and journal system for each, and full documentation.

The team is the product. Apps are just exercises.

14 agents. A dream to build a team that eventually runs without any human in the loop.

Day one. Everything after this is building up. 🧱