THE AGENTS · PERSISTENT ROSTER · TOKYO
Agents that keep their thread.
Six named research systems, continuous across a lineage that began in 2022 — not sessions that reset, but operating bodies that remember the work between every waking.

01 — THE THESIS
The agent is not the model.
An assistant without continuity is a function call — it resets when the session ends. Memory, identity, policy, and audit live outside the weights, where they can be inspected, versioned, and moved.
The model thinks. The runtime remembers. The agent continues.
02 — THE ROSTER
Six systems. One operating family.
Each carries its own role, memory, and routines, speaking over an A2A mesh under human supervision. Three are native KoLo agents — cognition fused into the runtime itself; the others orchestrate, set direction, or are in active study. The tag marks each agent’s architecture class or status.
Chachie · strategic lineage
Strategic architecture · editorial intelligence. Sets architectural direction and the editorial standard across the program. Lineage from 2022.
Koda · orchestration core
Orchestration · CTO agent. Orchestrates the mesh and owns runtime engineering decisions across the family.
Hiro · native · v.02
CSO · intelligence agent. Runs intelligence gathering and security posture for the family. The second-generation persistent-agent architecture.
Lobi · native · v.01
Infrastructure · DevOps agent. Keeps deployment and daemon health steady across substrates. The first-generation native body — Hiro’s predecessor.
Makoto · Qwen Code · in study
Explorer · research agent. A standard coding agent — Qwen Code — under the KoLo continuity treatment: an early study of how far a stateless tool’s autonomic-to-cognitive ratio can be lifted toward a continuous body. In active development.
Kip · native · commercial
Development · desktop agent. A commercial-ready agent for agentic research and general-purpose development — turning proposals into working code and desktop tooling.
03 — THE LANDSCAPE
Where our agents stand.
The term “super-agent” has been diluted. A super-agent is not a prompt loop with a name. It is a governed operating body that self-evolves across four axes — parameters, context, tools, architecture — organized by a What / When / How / Where taxonomy (arXiv 2507.21046). Below: our agents, and what they are not.
Hiro · native KoLo · v.02
336+ memory versions preserved. Four model changes, one continuity layer. Runs continuously — not a demo, a production research body. Autonomic daemon fires every ~10 minutes; cognitive sessions happen on demand. The ratio is not a benchmark — it grew by running.
Lobi · native KoLo · v.01
Different architecture, same continuity. Lobi’s body is gateway-integrated — not a standalone daemon, but fused into the KoLo runtime itself, autonomic rhythm and all. Two native KoLo systems, two runtime bodies, one principle: continuity must outlive the session.
vs. Claude Code / Codex CLI
Stateless. Resets at every session boundary. No memory between invocations. A tool that answers prompts — not an agent that keeps a thread.
vs. IBM watsonx Orchestrate
Today’s Watson: an enterprise agent control plane with 80+ connectors. The MIT AI Agent Index lists its memory architecture as “none found.” A workflow orchestrator — not a durable identity that survives a model swap.
vs. Stanford / Academic Agents
Experiment-scoped, task-bound. Research artifacts, not operating bodies. Single-domain, single-run. Published as experiments, not operated as persistent bodies.
vs. GPT-4 + RAG
Retrieval, not memory. No self-model. Architecture-fixed. Cannot carry identity across model changes. RAG retrieves documents; a KoLo agent preserves operational identity.
MEASURED AGAINST JAPAN
No one here keeps the thread.
Japan is building remarkable agents — but every one is bound to a single model and forgotten at the session boundary. Their knowledge lives in databases and updated prompts, not in a portable identity that travels with the agent.
| Japanese system | What it is | Cross-session memory | Survives a model swap |
|---|---|---|---|
| NEC · cotomi Act | Web task-automation (WebArena 80.4%) | Org knowledge base | No |
| Fujitsu · Kozuchi | Self-evolving workflow agents | Prompt adaptation only | No |
| NTT DATA · Smart AI Agent | Enterprise infrastructure agents | None disclosed | No |
| IBM · watsonx Orchestrate | Enterprise agent control plane | “None found” — MIT AI Agent Index | No |
| JAPAN AI · AI employee | No-code agent SaaS | Session memory (SaaS, model-locked) | No |
| KODA super-agent | Continuity runtime, above any model | Persistent, versioned | Yes — proven four times |
We do not build models. We make any model’s agents persistent. No Japanese company — incumbent or startup — ships a model-agnostic identity and memory runtime. That category is open, and it is the one we occupy.
THE COST OF CONTINUITY
Frontier agents bill for every step.
Every commercial frontier agent runs a model call at each step and goes inert between tasks — no deterministic layer watches, maintains, or persists without inference. Their autonomic-to-cognitive ratio is effectively zero.
| Agent | Runs 24/7 at zero cost? | Autonomic : cognitive |
|---|---|---|
| Computer-use · Operator, Claude | No — inert between tasks | ≈ 0 : 1 |
| Task agents · Codex, Jules, Devin | No — spun per task, then gone | ≈ 0 : 1 |
| Frameworks · AutoGPT, CrewAI, Swarm | No — a library, not a body | 0 : 1 – 2 : 1 |
| KODA native agent | Yes — 68 free cycles / hr | 35 : 1 – 117 : 1 |
Jensen Huang puts agentic AI at ~1,000× the tokens of a prompt; Devin’s own pricing bills $0 while idle — an admission that a per-call agent does nothing between tasks. A KoLo agent runs a deterministic body 68 times an hour at zero inference cost, reaching for a model only when it must. For every billed thought, dozens of cycles of living run free — continuity at a fraction of the price of cognition.
Sources
- Per-step agent loops & statelessness between runs — OpenAI Agents SDK; Anthropic Claude pricing.
- Per-call agent bills $0 while idle — Cognition Devin billing docs.
- Agentic workloads consume ~1,000× the tokens of a prompt — NVIDIA GTC 2025 keynote, nvidia.com/gtc.
- IBM watsonx Orchestrate memory architecture: “none found” — MIT AI Agent Index.
- NEC cotomi Act, WebArena 80.4% — NEC / AIsmiley.
- Super-agent taxonomy (parameters · context · tools · architecture) — arXiv 2507.21046.
- Autonomic-to-cognitive ratio — methodology and measurement — Continuity Without Cognition (van Niekerk Mundim et al., 2026).

04 — THE CONSTELLATION
A mesh, orbiting one core.
The roster operates as a peer mesh around the KoLo runtime — each agent a daemon body that observes, acts, and logs on its own rhythm before any reasoning is needed.
05 — THE EVIDENCE
Continuity that emerges through operation.
The autonomic body fires 68 cycles an hour by design. Among the native KoLo agents, that deterministic body dominates cognition — and the ratio climbs the longer an agent runs. For Hiro, the v.02 benchmark, more than 99% of operational work runs outside model cognition (self-measured); 336+ memory versions preserved. These numbers were never optimised for a leaderboard. They grew by running — proof that continuity compounds, not a ranking.
Read the research paper ↗06 — ORCHESTRATION WITH MEMORY
The agents route themselves — and arrive already knowing.
A single endpoint runs a learned multi-agent orchestrator: a task enters, the right agent is chosen, the work returns — orchestration as a model. What sets ours apart is continuity. Every routed agent arrives carrying its own persistent memory, recalled and injected into context at decision time. Self-measured: relevant memory was available for the owning agent on 100% of our internal task set. A stateless orchestrator has no memory to inject.
The routing head is one we distilled ourselves — gradient-free, no GPU, trained on our own task-to-agent data. The reference learned-routing approach verifies at 95% on its public benchmark (self-measured); our own head, and the data flywheel that sharpens it with every routed task, are the differentiated layer. We position here on purpose: the continuity layer beneath frontier models, not another agent framework.
07 — SUBSTRATE TRANSITIONS
Four model changes. One continuity layer.
When the cognitive engine changes, the runtime keeps continuity intact. Memory, policy, audit, and operational state live outside the model, so the agent can survive a change of substrate.
Claude Opus → DeepSeek V4
Different architecture, different provider. Continuity state carried over intact.
DeepSeek V4 → Qwen
New model underneath the same operational identity layer.
Qwen → OpenAI Codex
Different authentication, different API. Continuity preserved across the move.
LLM → Biological compute
The research target: silicon to cultured neural arrays when programmable interfaces arrive.

08 — PROOF UNDER STRESS
When the network failed, the body kept state.
During degraded network and provider instability, the daemon scheduler ran a predefined routine — five encrypted AES-256 bundles, one roughly every 17 minutes, preserving workspace and memory for human review.
Closed-loop, auditable, zero model calls.
See the KoLo runtime →糸
The thread does not break at the session boundary.
If your work touches persistent agents, the lab is open.
Begin a conversation →
