heterogeneous-agent

Debug heterogeneous agent pipelines for tool persistence and step boundaries.

Updated May 11, 2026
One-click install
npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill heterogeneous-agent-zmh13928433602-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: heterogeneous-agent
Source: https://github.com/zmh13928433602-sys/lobe-chat/tree/main/.agents/skills/heterogeneous-agent
Command: npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill heterogeneous-agent-zmh13928433602-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debugging and stabilizing heterogeneous agent integrations (Claude Code, Codex, and other external CLI agents) and their adapters to fix issues in event mapping, transport, and tool orchestration across desktop and library boundaries.

Core Features & Use Cases

  • Debug adapter event flows, IPC transport, and tool-call chaining for heterogeneous agents
  • Reproduce, diagnose, and fix bugs like mixed tool messages, orphan tool messages, and step boundary problems
  • Inspect driver and adapter code across apps/desktop and packages to validate end-to-end behavior

Quick Start

Set up the local debugging environment and reproduce an issue in the heterogeneous agent pipeline using the referenced files and adapters.

Frequently Asked Questions about heterogeneous-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug orphan tool messages in heterogeneous agent adapters?

To debug orphan tool messages in heterogeneous agent adapters, inspect the driver code and adapter event mappings under packages/heterogeneous-agents/src/adapters to validate tool persistence and correct step boundaries across the pipeline.

Why does my Electron IPC transport drop tool-call chaining for Claude Code?

Electron IPC transport may drop tool-call chaining for Claude Code due to incorrect event mapping or threading issues across desktop and package layers, requiring inspection of apps/desktop/src/main/modules/heterogeneousAgent to ensure trace accuracy.

What causes mixed multi-tool messages in external CLI agent pipelines?

Mixed multi-tool messages in external CLI agent pipelines are caused by incorrect adapter event flows and step boundary problems, which can be reproduced and diagnosed by inspecting the heterogeneous agent driver code and validating end-to-end behavior.

How do I trace subagent threading issues across desktop and package layers?

Trace subagent threading issues across desktop and package layers by inspecting the heterogeneous agent modules and adapter mappings to validate tool persistence, step boundaries, and IPC transport accuracy for external CLI agents like Codex.

Does this debugging approach work for both Claude Code and Codex adapters?

Yes, this debugging approach works for both Claude Code and Codex adapters by inspecting the shared driver code and adapter mappings under packages/heterogeneous-agents/src/adapters to resolve event mapping and tool orchestration issues.