{"version":"2.1.318","anchor":"subagent-time-cap-now-depends-on-the-parent-message-repl-mo","canonical_anchor":"subagent-time-cap-now-depends-on-the-parent-message-repl-mo","heading":"Subagent time limits now depend on the message that started them","tier":"internal","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/subagent-time-cap-now-depends-on-the-parent-message-repl-mo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Subagent time limits now depend on the message that started them\n\nThe time limit for a subagent now takes the triggering message into account, and REPL mode is now kept per session\n\n**What**\n\nA subagent is a separate helper agent that Claude Code starts to handle part of a task. Claude Code limits how long one may run. Before, that limit was worked out from the session alone. Now it is worked out from the session and the message that started the subagent.\n\nSeparately, when a session's state is restored, Claude Code now also restores whether REPL mode was on for that session, read from a record kept for each session.\n\n**Why**\n\nTwo subagents in the same session can now get different time limits depending on what asked for them. REPL mode is now remembered as part of a session's saved state.\n\n- Area: Agents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}