---
title: "Discussion on \"Seven Coding Agents. One Chat Window.\" | Hashnode"
description: "Discussion on \"Seven Coding Agents. One Chat Window.\". Building lasteverLM in 78 hours with a head agent, a Linux VM and 20–24 hours of my own time — and what I want from fleet tooling next."
url: "https://hashnode.com/posts/seven-coding-agents-one-chat-window/6ad470d3992bdd59decec50c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Seven Coding Agents. One Chat Window.](https://blog.technopathy.club/seven-coding-agents-one-chat-window?utm_source=hashnode&utm_medium=feed)

Building lasteverLM in 78 hours with a head agent, a Linux VM and 20–24 hours of my own time — and what I want from fleet tooling next.

Oct 18 · 7 min read · blog.technopathy.club  
Read the article

-   [#coding-agents](https://hashnode.com/tag/coding-agents)
-   [#agentic-ai](https://hashnode.com/tag/agentic-ai)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#project-memory](https://hashnode.com/tag/project-memory)

## Written by

[Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner)

@oliver-zehentleitner · Vienna, Austria

  
[View profile](https://hashnode.com/@oliver-zehentleitner)

DevSecOps · Python · AI-driven Development · Real-world findings from production systems.

I build systems that work — technically sound, security-first, and actually useful to the people who depend on them. Creator of the UNICORN Binance Suite — six open-source Python libraries with 3.3M+ downloads and 390+ dependent public projects — and Keep the Why, an open-source agent skill that preserves the reasoning behind engineering decisions alongside the code. Currently pioneering AI-driven open-source maintenance: running a controlled AI agent that maintains production code and documenting what this shift means for engineering teams. Vienna, Austria 🇦🇹

## Responses 5

Markdown supported · ⌘↵ to post

[Damiano Bianda](https://hashnode.com/@damianobianda)

[Oct 19](https://hashnode.com/posts/seven-coding-agents-one-chat-window/6ad470d3992bdd59decec50c/comment/6ad61ebb88b9464ea32d897b)

The part I'd want the sequel on: what did the coordination actually cost? Seven agents in parallel is the throughput win, but the bill usually arrives as context-syncing - every agent that touches the shared library needs to know what the ingestion agent decided an hour ago. You mention the agents talk to each other: did you route that through the head agent, or did pairs coordinate directly? And did you ever catch two of them quietly solving the same problem twice?

[Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner)

[Oct 19](https://hashnode.com/posts/seven-coding-agents-one-chat-window/6ad470d3992bdd59decec50c/comment/6ad61ebb88b9464ea32d897b#reply-6ad6598d64221b52481e3b6d)

I am using an Anthropic "max 20" and have consumed approximately 70% of my weekly token allowance.

The agents communicate in two ways:

1.  Directly via file sockets.
2.  Via "Keep the Why" - an open-source tool for GitHub - where 300 entries have been saved over the three days, which the agents share. You can view the entries here: [oliver-zehentleitner.github.io/lasteverLM/keep-th…](https://oliver-zehentleitner.github.io/lasteverLM/keep-the-why-dashboard/) This knowledge can also be utilized by future agents and humans for ongoing work.

[BomToBe](https://hashnode.com/@bomtobe-orke)

[Oct 18](https://hashnode.com/posts/seven-coding-agents-one-chat-window/6ad470d3992bdd59decec50c/comment/6ad4ce596dbc8a66c0f6992c)

I work on Orke at BOMTOBE, a desktop workspace for Claude Code and Codex, so the human-handoff part of your fleet-tool idea is relevant to us. One reliability detail I’d make explicit: treat each request as a durable, task-linked item tied to the agent and session that asked it, with waiting/answered/withdrawn/stale states. If that session compacts or restarts, the answer should still route to the original request (or clearly ask to rebind) instead of disappearing in chat history. I’d also keep the top blocker distinct from lower-priority questions so a busy inbox still tells you what is holding up work. Would you prefer stale requests to expire automatically or require an explicit close?

[Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner)

[Oct 18](https://hashnode.com/posts/seven-coding-agents-one-chat-window/6ad470d3992bdd59decec50c/comment/6ad4ce596dbc8a66c0f6992c#reply-6ad4debc81e14769469fae72)

Do you have a GitHub link?

[Damiano Bianda](https://hashnode.com/@damianobianda)

[Oct 20](https://hashnode.com/posts/seven-coding-agents-one-chat-window/6ad470d3992bdd59decec50c/comment/6ad4ce596dbc8a66c0f6992c#reply-6ad72f9fc1488ed1235e224b)

Direct over routed, interesting. And 300 entries in three days is a lot of captured why. Did you ever catch two agents quietly solving the same problem twice?
