Gemini CLI Makes a “Generalist” Sub-Agent the Default Delegate

Gemini CLI has landed a new default behavior: a built-in generalist sub-agent is now enabled out of the box. The change arrives via the commit titled feat(core): Enable generalist agent (#19665), and it means users effectively have an always-available delegate ready to take on tasks without requiring explicit setup.

Under the hood, the generalist agent is defined as a tool-rich worker: it is granted access to all tools via the tool registry. It also runs using the core system prompt, with an important twist for operational behavior—its interactive override is set to false, putting it in non-interactive mode.

What changed in practice

Previously, using sub-agents could feel like a deliberate “turn it on when needed” pattern. With this update, the generalist agent is present by default, and the project’s own registry tests now assert that the agent is registered automatically. In other words: the default installation and runtime now expect this delegate to exist.

The result is a subtle but meaningful workflow shift: the main session can remain lean and focused, while long-running, tool-heavy, or “noisy” work can be offloaded to the generalist agent—without a user having to preconfigure an agent profile.

Why it matters

• Delegation becomes baseline: Making a generalist sub-agent default moves multi-agent work from “advanced usage” to standard behavior.
• Tool access is comprehensive: By granting access to all tools via the registry, the delegate is positioned as a practical catch-all worker.
• Cleaner primary sessions: Non-interactive mode helps keep the main interaction streamlined while background or verbose operations run elsewhere.
• More predictable availability: With tests asserting default registration, downstream users and contributors can rely on the agent being present.

Sources

• Commit: feat(core): Enable generalist agent (#19665)