hive

Overview Schema Source Related Servers Discussions Admin

agent_resume

Resume a closed Claude or Codex worker from its session ID to restore a fresh pane, same actor_id, and full prior context; then use agent_send to deliver its next instruction.

Instructions

Resume a CLOSED claude or codex worker from its recorded session id (claude --resume / codex resume): a fresh pane, the same actor_id, and the worker's full prior context. Addressed by name or agent_id among closed agents (agent_list(include_closed: true)). Send it its next instruction with agent_send once resumed - this tool does not.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	The worker's name, e.g. "impl" or "DEVX-123". Prefer passing this rather than agent_id, but pass only one: if both arrive, agent_id wins and this is ignored. A partial name works when it matches exactly one running worker, so "123" finds DEVX-123.
`agent_id`	No	Numeric agent id. Use name instead unless you have the id to hand.
`project_id`	No	Different project override. Use ONLY when the user explicitly asks for another project by name; otherwise stay in the current scope, even when results are empty.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`actor_id`	Yes
`agent_id`	Yes
`hive_notice`	No
`tmux_target`	Yes
`branch_drift`	No
`was_parked_at`	No
`landed_in_project`	No
`resumed_session_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.2Sep 26, 2026
- addedOutput schema / properties / hive_notice
```
Added value: +{
+  "type": "string"
+}
```
First observedv1.0.0Sep 22, 2026

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations already declaring readOnlyHint=false, idempotentHint=false, and destructiveHint=false, the description adds useful behavior beyond the structured data: a fresh pane, the same actor_id, full prior context, and the fact that it does not send a follow-up instruction. It stops short of describing error or permission behavior, so it is not fully exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and is only three compact sentences. Each sentence carries necessary information: what is resumed, how it is addressed, and what to do after resuming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, output schema, and annotations, the description supplies the remaining context an agent needs: the worker must be CLOSED, targeting uses name or agent_id among closed agents, and sending the next instruction is a separate tool call. Nothing essential for correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the parameters thoroughly. The description still adds meaning by specifying that the target must be addressed by name or agent_id among closed agents, and by pointing to agent_list(include_closed: true) for finding them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Resume a CLOSED claude or codex worker from its recorded session id'. It also distinguishes the result from creating a new worker by noting 'a fresh pane, the same actor_id, and the worker's full prior context', so an agent can tell it apart from siblings like agent_spawn.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit conditions: resume a CLOSED worker, addressed by name or agent_id among closed agents, findable via agent_list(include_closed: true). It also names the alternative follow-up action: 'Send it its next instruction with agent_send once resumed - this tool does not.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.