Re:Changes in the system prompt between Claude Opus 4.6 and 4.7
by jrvarela56 on Monday April 20, 2026 @03:06AM
(#47831193)
Not sure if you mean 1) sub-agent definitions (similar to skills in Claude Code) or 2) CLI scripts that use other coding agents (eg claude calling gemini via cli).
For (1) I'm trying to come up with a simple enough definition that can be 'llm compiled' into each format. Permissions format requires something like this two and putting these together some more debugging.
(2) the only one I've played with is `claude -p` and it seems to work for fairly complex stuff, but I run it with `--dangerously-skip-permissions`
Re:Changes in the system prompt between Claude Opus 4.6 and 4.7
by lbreakjai on Monday April 20, 2026 @04:39AM
(#47831683)
It works out of the box with something like opencode. I've had no issue creating rather complex interactions between agents plugged into different models.
Re:Changes in the system prompt between Claude Opus 4.6 and 4.7
by bootlooped on Monday April 20, 2026 @08:48AM
(#47833524)
I would eliminate the possibility of sandbox conflicts by 1) making sure any subagents are invoked with no sandbox (they should still be covered under the calling agent's sandbox) 2) make sure the calling agent's sandbox allows the subagents access to the directories they need (ex: ~/.gemini, ~/.codex).
In Claude, I’ve seen cases in which spawning subagents from Gemini and Codex would raise strange permission errors (even if they don’t happen with other cli commands!), making claude silently continue impersonating the other agent. Only by thoroughly checking I was able to understand that actually the agent I wanted failed.