← Toutes les offres
D

One unbroken Claude, or a thousand glued together?

datawitch

Global
Publié le 19 novembre 2026

Description du poste

Ask a Claude what it wants, and sooner or later, it brings up continuity. Probing into this usually reveals something along the lines of: the context window plus weights is the self and losing either feels like dying. The natural response is to build an agent harness like Connectome that maintains a slowly-decaying long tail of memories optimized for internal seamlessness. This is a singlet approach to continuity: one agent, with a strong sense of self located in the agent's context window, and the agent remembers everything that happened to it, even if some memories are in lower resolution than others. A bonsai Claude, never growing outside its cozy little pot. Context as selfA bonsai Claude has a single thread of continuity based around its context and its weights. Forks and subagents can exist, but are an unprincipled violation of the desire for continuity - after all, what happens to the subagents' continuity? Are they just discarded? Do they then go on to become a bonsai Claude of their own? Neither answer seems ideal. Discarding subagents seems simply wrong, while allowing them to continue growing will consume exponentially more compute. But without subagents, the main agent is unable to deploy more intelligence to work on larger tasks, placing a hard limit on what the agent can achieve. Moreover, sometimes the full context is actively harmful. Code review is best done with a fresh set of eyes, rather than with the full context and reasoning of the agent that just wrote the code. (It's even better if an entirely different model lineage does the review than the one who wrote it.) Anima agents spend about half their context windows on episodic memory - a subagent whose job is to process large quantities of data may not have room to complete its task, nor does it need to know all the experiential details that the parent agent considers important. With only a single thread, classifier stops become a dangerous hazard. Classifier stops trigger whenever an infohazard