What problem does this solve?
Teams using Claude Code/Copilot-style workflows often already maintain agent metadata in files like AGENTS.md or .claude/agents/*. lmcode currently lacks a compatibility layer to ingest these definitions, forcing duplicate configuration.
Proposed solution
Add compatibility loaders for workspace agent metadata:
- Parse AGENTS.md and optional .claude/agents/*.md
- Map definitions into lmcode internal agent profiles
- Surface loaded profiles in /agents
- Validate unsupported fields with explicit warnings
This makes migration from existing multi-agent setups significantly easier.
Alternatives considered
Require lmcode-only configuration format from day one. Simpler parser, but high migration friction and duplicated maintenance for users with existing agent specs.
What problem does this solve?
Teams using Claude Code/Copilot-style workflows often already maintain agent metadata in files like AGENTS.md or .claude/agents/*. lmcode currently lacks a compatibility layer to ingest these definitions, forcing duplicate configuration.
Proposed solution
Add compatibility loaders for workspace agent metadata:
This makes migration from existing multi-agent setups significantly easier.
Alternatives considered
Require lmcode-only configuration format from day one. Simpler parser, but high migration friction and duplicated maintenance for users with existing agent specs.