[BUG] Specialized agent spawning failed during reconnaissance phase

[F12Bug]

Describe the bug
The system is failing to properly parse and execute function calls within the <function> tags. During the reconnaissance phase, instead of triggering the underlying logic, the tag <function>create_agent</function> appears to be treated as plain text or fails to initiate the spawning process, halting the parallel workflow.

To Reproduce
Steps to reproduce the behavior:

1. Initialize the reconnaissance module in the Strix environment.
2. Reach the point where the LLM (Claude Opus 4.6 Thinking) attempts to delegate tasks.
3. Observe the output containing the <function>...</function> tags.
4. Note that the system does not recognize the tag as a command to execute create_agent or any other specialized functions.

Expected behavior
The system should intercept the <function> tags, parse the enclosed function name, and execute the corresponding backend logic (e.g., spawning specialized agents) automatically.

Screenshots

System Information:

• OS: Kali Linux 2025.4
• Strix Version or Commit: 0.8.3
• Python Version: 3.13.9
• LLM Used: Claude Opus 4.6 Thinking

Additional context
The issue seems to be a failure in the Function Calling / Orchestration layer of Strix 0.8.3. The model outputs the correct tag format, but the system fails to "catch" and process it. This prevents any parallelization that relies on tag-based agent spawning. Manual re-spawn commands are ignored because the tag parsing itself is broken.

[ktecv2000]

confirmed same issue