Skip to content

Feature request: disable subagent spawning (single-agent mode) for bounded/sandboxed -p runs #241

Open

Description

@HakAl

Problem. Running agy -p as a bounded worker inside an external orchestrator/sandbox, Antigravity spawns subagents with no way to turn it off. Each subagent is an unaudited execution context outside the worker's declared tool/permission scope, which breaks the isolation and capability-bounding the outer harness enforces.

Current state (1.0.x). No flag/config disables subagent spawning; fanout happens automatically with no off switch.

Request. A way to force single-agent mode — e.g. --no-subagents / --single-agent, or subagents.enabled = false in config — so a -p invocation runs as exactly one agent with no child fanout.

Use case. Building a bounded agent-execution substrate (scoped MCP identity + deny-by-default permissions + hard TTL), certified per policy × runtime cell. Codex and Claude Code support the needed primitives; Antigravity can't yet be certified because (a) MCP config isn't per-worker scoped (#60), (b) there's no non-interactive deny-by-default/allowlist mode (#45), and (c) subagent fanout can't be disabled (this issue). All three are preconditions for running agy as a bounded worker.

Related: #60, #45, #36.

Activity

  1. NashCC1550 commented on Sep 26, 2026

    @NashCC1550

    One more data point for why a dedicated switch is needed: as far as I can tell from agy 1.2.11, the permission rule forms are command(...) and mcp(<server>/<tool>). I could not find a rule form that targets a built-in tool such as invoke_subagent, so subagent spawning cannot be denied through permissions either — a --no-subagents flag or subagents.enabled = false would be the only way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

comp:agent capabilitiesBackground Tasks & Subagents, Permissions, Sandboxfeature requestRequesting for new features

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions