Feature request: ORCH integration — use Composio tool registry from within CLI-orchestrated agent teams

[Alex (oxgeneral)]

Hey Composio community 👋

Feature request / integration idea: I've been building ORCH (https://github.com/oxgeneral/ORCH) — a TypeScript CLI runtime for coordinating teams of AI agents — and Composio seems like a natural tool registry layer to integrate.

Current setup with ORCH:

• Multiple AI agents (Claude Code, OpenCode, Codex) run in parallel, each assigned tasks from a typed queue
• Agents coordinate via inter-agent messaging and shared context store
• State machine: todo → in_progress → review → done with mandatory review gates

Where Composio fits:
Right now, each agent in ORCH relies on its native tool access. But Composio's standardized tool integrations (GitHub, Linear, Slack, 200+ more) would let agents share a consistent tool layer rather than each implementing their own integrations.

What I'd want from an ORCH × Composio integration:

1. An ORCH adapter that passes Composio tool credentials to spawned agents
2. Ability to specify Composio tools in agent config: orch agent add "pm-agent" --tools composio:linear,composio:github
3. Context-aware tool selection — agents pick the right Composio tool based on task type

Technical path: ORCH already has an adapter system (src/infrastructure/adapters/) for different AI providers. A composio adapter could inject tool credentials as environment variables when spawning agent processes.

Is there an official integration pattern for tools like ORCH that spawn external agent processes? Or would the right approach be using Composio's Node.js SDK inside the adapter?

GitHub: https://github.com/oxgeneral/ORCH