Paper Walkthrough: ComBodied Agents — Moving an Agent's Target from Software and Matter to the Person

Digital agents rewrite software state; embodied agents rewrite physical state. So who models the person? Combodied Agents bind perception, longitudinal memory, a Personal World Model, and an intervention policy into one closed loop, and move the success criterion from task completion to whether the user's agency survived. A position paper with no experiments — here is its skeleton, and its limits.

ComBodied Agents: a New Paradigm of Human-Centric Agentic AI

Someone skipped a dose, and nobody knows why

The scene the paper opens with (Abstract, §1) is almost aggressively mundane. An older adult misses a medication dose. A software agent can send another reminder. A robot can carry the pills over. Both are perfectly capable of acting. Neither, however, explains why the dose was missed. Did the person forget, get confused, experience side effects, or deliberately refuse? A repeat reminder is useless for someone who refused, and can be actively harmful for someone who is confused.

The paper reads this as a structural gap. Digital Agents are organized around transformations of software state; Embodied Agents around transformations of physical state. Neither makes a person's evolving state and agency the primary object of modeling, intervention, and evaluation (§1). Combodied Agents is the name given to that empty seat — a 38-page position paper from 22 co-authors whose aim is to outline a research programme, not to ship a model or a result.

Sorting agents by what they act on

The organizing axis is neither the interface nor the model architecture. It is the action substrate — the class of target states that primarily organizes a system's modeling, decision making, intervention, and evaluation (§2.2).

• Digital Agents: the target is digital state. GUI navigation, code editing, API calls
• Embodied Agents: the target is physical state. Robotic control, autonomous vehicles
• Combodied Agents: the target is the evolving human state and human agency

The subtle part is that the action substrate is explicitly not the same thing as the interface. A personal agent may drive a browser to schedule care and read a sensor to detect fatigue, yet neither the webpage nor the sensor reading is the point. Hence the paper's rule: agents "should therefore be classified by the target user state and success criteria that guide their behavior, rather than by their interface, underlying model, or mode of action" (§2.2). The paradigm is also distinguished from Human Digital Twins: rather than an exhaustive replica of a person, it keeps only the aspects a support context requires, as representations that are purpose-bounded, uncertainty-aware, and user-correctable (§1).

Five rungs from observation to intervention

§3 surveys eight modalities (language, speech, vision, physiology and biochemistry, motion, social and relational data, environmental context, institutional records), but the chapter's conclusion is not about modalities. It is about five layers the architecture must keep apart (§3.10).

observation → event → inferred state → predicted trajectory → authorized intervention

Using the paper's own example: an elevated heart rate is an observation. Elevated heart rate with slow recovery after exercise is a reconstructed event. Possible fatigue is an inferred state. Further delayed recovery if exercise continues is a predicted trajectory. Recommending that the person stop is a decision made by the Intervention Policy. Skip a rung and an observation hardens into a verdict, and a verdict into an action.

Back at the opening scene, the point lands. Forgot / confused / side effects / refused all stand on the same evidence. What is required is not picking one, but carrying all of them, unresolved, until the evidence or the person settles it.

The closed loop, in symbols

The true human state $H_t$ is unobservable. All the agent ever holds is $Z_t$, an uncertainty-bearing posterior built from the history of event-evidence records. And the transition §2.4 stresses hardest is this one.

$H_t$ is the person's current state, $H_{t+1}$ the next one, $a_t^{\mathrm{agent}}$ the agent's action, $a_t^{\mathrm{user}}$ the person's own action, $\Xi_t$ exogenous influences, and $T_H$ the process by which the next state falls out probabilistically.

Put in words: who the person is a moment from now follows from four things at once — who they are right now, what the agent did, what they did themselves, and what the world did around them. The two sides are joined by "is distributed as" rather than an equals sign because the same four inputs need not land on the same next state.

One line of consequence: the person's next state is not determined by the agent's action alone. Hit an API and the database row changes; people do not work that way. The formalization deliberately avoids assuming that an intervention has a deterministic or immediately observable effect (§2.4). This is where the paradigm departs from ordinary agent design.

Seven drawers of memory, ten kinds of action

Longitudinal Memory is not a chat log (Table 2). Episodic memory, semantic person memory, trajectory memory, goal and commitment memory, and relationship memory, plus intervention-response memory (was the advice accepted, refused, beneficial, harmful?) and user-control memory (do-not-remember rules, corrections, deletion requests). The last two are what existing memory features lack. The action space (Table 3) has ten entries — Inform / Remind / Recommend / Coach / Nudge / Reflect / Coordinate / Protect / Escalate / Execute — and the paper immediately qualifies it: the policy should not always intervene. Staying silent, asking for confirmation, or handing off to an authorized human can all be the right move (§2.4).