{"id":3895,"date":"2026-07-15T20:58:26","date_gmt":"2026-07-15T18:58:26","guid":{"rendered":"https:\/\/isla-stud.io\/?p=3895"},"modified":"2026-08-10T14:55:26","modified_gmt":"2026-08-10T12:55:26","slug":"openclaw-was-discontinued-what-remained-of-the-ki-team","status":"publish","type":"post","link":"https:\/\/isla-stud.io\/en\/ki-b2b\/openclaw-abgeschafft-was-vom-ki-team-blieb\/","title":{"rendered":"I've called it quits with OpenClaw. What's left of my AI team."},"content":{"rendered":"

What you'll take away from this:<\/strong> You'll see why a deliberately planned transition away from a tool still comes at the cost of context\u2014and how that led to the creation of my file-based Agents Brain.<\/p>\n\n\n\n\n\n

On February 10, 2026, I set up Nox: my AI orchestrator for a team of fifteen specialized agents. At the end of March, I discontinued the tool that had been used to organize this team.<\/p>\n\n\n\n

This wasn't an unplanned outage. OpenClaw had repeatedly caused me problems with updates. The updates often ran in the early morning hours. On some days, it would take me half a workday afterward just to get OpenClaw and my setup running smoothly again. Eventually, the math was clear: I was spending too much time fixing the infrastructure and not enough time doing what it was meant for. So I made a conscious decision to stop using it.<\/p>\n\n\n\n

The decision was the right one. Its consequences were nonetheless revealing.<\/p>\n\n\n\n

I thought I was just replacing a tool<\/h2>\n\n\n\n

Back in February and March, the team already had a clear division of labor. One agent did research, another wrote, and a third reviewed. Nox, as the orchestrator, kept track of tasks, their order, and hand-offs. This setup wasn\u2019t just theoretical\u2014it had been working effectively for six weeks.<\/p>\n\n\n\n

When the tool was discontinued, this collaboration could not simply be exported. The ongoing orchestration, channels, and automations were part of the system\u2019s state at that time. They could not be transferred to the next tool as a functioning unit.<\/p>\n\n\n\n

However, one part did survive: the Markdown files.<\/p>\n\n\n\n

Personas, long-term knowledge, and daily logs were readable even though the original tool was no longer in use. I didn't need an export function or a special interface for these files. A text editor was enough.<\/p>\n\n\n\n

This made the decisive boundary visible: I had to rebuild everything that existed only in the tool environment. I was able to reuse whatever was available as a file.<\/strong><\/p>\n\n\n\n

The model is rarely the problem. It's almost always the context.<\/p>\n\n\n\n

From late March to mid-May was the concept development phase<\/h2>\n\n\n\n

After the phase-out, I didn't just install the next agent framework. From April through mid-May, I worked on three issues.<\/p>\n\n\n\n

How can (my) AI team truly become portable?<\/h3>\n\n\n\n

A folder full of files isn't a system. I wanted a structure from which I could reliably load an agent into a new tool: with the same role, the same boundaries, and the same relevant knowledge.<\/p>\n\n\n\n

To do this, it had to be clear which pieces of information were part of an agent's identity\u2014and which were simply characteristics of the current tool.<\/p>\n\n\n\n

How do I change the orchestrator?<\/h3>\n\n\n\n

As a team lead, Nox was closely tied to his work environment at the time. I wanted to break that connection. The Orchestrator should be able to take on a different technical form without me having to reinvent its persona, craftsmanship, and approval rules.<\/p>\n\n\n\n

This meant that identity could no longer be tied to the system prompt of a single tool. The tool should only load what had already been defined in an independent location.<\/p>\n\n\n\n

How do sessions turn into long-term memory?<\/h3>\n\n\n\n

Session histories are convenient, but they are not a reliable long-term storage solution. They are truncated, disappear from the visible context, or can only be used within a specific product (e.g., Claude Code, ChatGPT Codex, OpenClaw, etc.).<\/p>\n\n\n\n

That's why I needed a writing routine: daily logs of my experiences, curated long-term knowledge of what matters most, and lessons learned from mistakes I don't want to repeat.<\/p>\n\n\n\n

These three questions\u2014portability, body-swapping, and memory\u2014became the core of my concept.<\/p>\n\n\n\n

On May 16, the sketches were turned into a report<\/h2>\n\n\n\n

On May 16, 2026, I made the first commit to the new repository. The commit message read: feat: initial shared brain skeleton<\/code>.<\/p>\n\n\n\n

The name was fitting. The system was a skeleton, not a finished product. But the fundamental decision had been made: Markdown is the source of truth. Git keeps track of changes. Each agent gets its own folder. Shared knowledge is referenced rather than copied. Tools are equipped with lightweight adapters that point to this source.<\/p>\n\n\n\n

I call my system Agents Brain<\/strong>. Similar file-based approaches also exist elsewhere, because, logically, I\u2019m not the only one struggling with the \u201eteething problems\u201c of agent-based AI, which is still in its infancy. Here is my workshop report: a live multi-agent system with roles, memory rules, and explicit approval gates.<\/p>\n\n\n\n

What Files Can Solve\u2014and What They Can't<\/h2>\n\n\n\n

Files make context readable, versionable, and portable. However, they do not automatically solve the memory problem.<\/p>\n\n\n\n

For example, a week in March is missing from the old daily logs. This gap is real. It didn't occur when we switched tools, but before that: What nobody writes down cannot be reconstructed later by any repository.<\/p>\n\n\n\n

That is precisely why architecture is more than just a storage location. It requires rules governing what is read at the beginning of a session and what is written at the end. It requires a boundary for sensitive content. And it requires the discipline to curate long-term knowledge rather than permanently storing every transaction.<\/p>\n\n\n\n

So my deliberate decision to stop using OpenClaw didn't show me that a particular tool is bad. It showed me that my agent identity must not be tied to any one tool.<\/p>\n\n\n\n

The Decision Behind the System<\/h2>\n\n\n\n

My most important design goal can be stated without any grandstanding:<\/p>\n\n\n\n

\n

If a tool were to disappear tomorrow, the Markdown files would remain readable and the agent could still be reconstructed from them. Engines and interfaces are add-ons, not prerequisites.<\/p>\n<\/blockquote>\n\n\n\n

I continued to refine the system from May through June. On July 6, the practical test run began: Nox was moved to Hermes, while its Brain remained in the repository.<\/p>\n\n\n\n

Whether this distinction holds up in everyday life is not something that can be answered by looking at an architectural drawing. It has to stand up to the realities of actual work. That is exactly what I have been testing ever since.<\/p>\n\n\n\n

In the next section, I'll outline the seven hard rules that emerged from this conceptual phase\u2014and explain why my Agents Brain is intentionally a Git repo rather than a new database.<\/p>\n\n\n\n

Sources<\/h2>\n\n\n\n