Reply to a Subagent
A composer under the subagent log sends your message on to that child — Enter to send, Shift+Enter for a newline — and the log follows from the tail so the reply lands where you are already reading. Correct a child mid-task instead of killing the run and starting over.
More Screenshots
Click any image to zoom in
Why You Need This
How this feature boosts your daily productivity
Reading a child agent's log only helps if you can act on what you read. A native child has no input of its own — the parent CLI owns it — so **Send to subagent** delivers your message to the parent conversation, which relays it addressed to that exact child id with an instruction to resume it rather than spawn a new one. The panel says as much under the composer, and you can watch the relay land in the parent's transcript. **Copy follow-up for parent** is still there for when you would rather paste the hand-off yourself, and if the parent terminal is gone, has moved to another session, or has exited, Send keeps your draft and tells you which of those happened rather than dropping it.
How It Works
Get started in 4 simple steps
Open the child’s log
Click the subagent count on the terminal, then pick a child from the searchable list to read its conversation, tool calls and results.
Type under the log
The composer sits beneath the transcript — `Ask for an update or suggest a change…`. Enter sends, Shift+Enter keeps the newline.
Send to subagent
A native child has no input of its own, so the message goes to the parent conversation, addressed to that exact child id with an instruction to resume it rather than spawn a new one.
Watch the relay land
The parent’s transcript shows the hand-off arriving and the child picking the work back up on the same session.
Or carry it across yourself
Copy follow-up for parent gives you the composed text to paste. If the parent terminal is gone, has moved session or has exited, Send keeps your draft and says which.
Without 1DevTool
The manual way vs. the 1DevTool way
The Hard Way
The 1DevTool Way
Key Capabilities
Everything included with Reply to a Subagent
Why It Matters
The productivity impact of having ai productivity built into your workspace
Correcting Costs One Sentence
Spotting a child heading the wrong way no longer means killing the run and rewriting the prompt — you answer it where you are reading it.
The Message Reaches The Right Child
The relay is addressed to that exact child id with a resume instruction, so the parent continues the agent instead of spawning a fresh one.
Nothing Is Lost On A Bad Send
A gone, moved or exited parent gets you your draft back and a reason, rather than a silent failure you notice much later.
The Manual Route Still Works
Copy follow-up for parent keeps the paste-it-yourself path for the times you want to see the hand-off before it goes.
More in AI Productivity
Other features in this category you might find useful
Prompt History
Search prompts and sticky notes from Remote Control while away from the desktop. Switch between This project and All projects, filter prompts by agent or notes by source, copy entries, delete with Operator access, and sync local prompt history.
Resume UI
Browse, search, and resume past AI sessions from Claude Code, Codex, and Gemini CLI — or combine multiple sessions into one.
Combine Sessions
Select sessions from Claude Code, Codex, and Gemini CLI and merge them into a single conversation — giving your next agent the full cross-agent context.
AI Diff Review Panel
Track every file modification any AI agent makes — Claude Code, Codex, Gemini, Amp, custom — and review, accept, or revert their work per file from a dedicated panel with inline diff overlays in the editor.
Ready to boost your workflow?
Download 1DevTool for free and experience Reply to a Subagent along with 298 other features — all in one app.