Project
cortex
Description
The CreateAgent tool reports success and writes a file under .cortex/agents/, but it writes <name>.toml. The standard custom-agent loader only discovers Markdown agent files, so the created agent is immediately invisible to normal agent discovery and cannot be delegated to through the standard loader path.
Error Message
No explicit error. The tool returns success, but the created agent does not appear in the standard loader results.
Debug Logs
Focused test:
test_create_agent_project_output_is_not_discoverable_by_standard_loader
Observed file created by CreateAgent:
.cortex/agents/process-and-transform-data-files.toml
Observed loader search paths:
- .agents
- .agent
- .cortex/agents
- ~/.cortex/agents
- ~/Library/Application Support/cortex/agents
Observed loader result:
loaded_names=[]
System Information
cortex source tree v0.0.7
macOS arm64
Screenshots
https://raw.githubusercontent.com/DDDDDGCSM/solid-carnival/master/evidence/cortex-create-agent-toml-proof.png
Steps to Reproduce
- Invoke the
CreateAgent tool with a valid project-scoped description.
- Let it create the agent under
.cortex/agents/.
- Run the standard custom-agent loader over the same project root.
- Observe that the loader returns no agent with that name.
Expected Behavior
A newly created custom agent should be written in the same file format that the standard loader understands, so the created agent is immediately discoverable and usable.
Actual Behavior
CreateAgent writes a TOML file into .cortex/agents/, but the standard loader only discovers Markdown agent files, so the created agent is effectively orphaned.
Additional Context
Code evidence in v0.0.7:
src/cortex-engine/src/tools/handlers/create_agent.rs writes agents_dir.join(format!("{}.toml", agent_name))
src/cortex-agents/src/custom/loader.rs loads standard agent directories and reads Markdown agent files (*.md)
This is independent from the app-server .factory/agents path mismatch: here the directory is nominally correct, but the file format is incompatible with the loader.
Project
cortex
Description
The
CreateAgenttool reports success and writes a file under.cortex/agents/, but it writes<name>.toml. The standard custom-agent loader only discovers Markdown agent files, so the created agent is immediately invisible to normal agent discovery and cannot be delegated to through the standard loader path.Error Message
No explicit error. The tool returns success, but the created agent does not appear in the standard loader results.Debug Logs
System Information
cortex source tree v0.0.7 macOS arm64Screenshots
https://raw.githubusercontent.com/DDDDDGCSM/solid-carnival/master/evidence/cortex-create-agent-toml-proof.png
Steps to Reproduce
CreateAgenttool with a valid project-scoped description..cortex/agents/.Expected Behavior
A newly created custom agent should be written in the same file format that the standard loader understands, so the created agent is immediately discoverable and usable.
Actual Behavior
CreateAgentwrites a TOML file into.cortex/agents/, but the standard loader only discovers Markdown agent files, so the created agent is effectively orphaned.Additional Context
Code evidence in v0.0.7:
src/cortex-engine/src/tools/handlers/create_agent.rswritesagents_dir.join(format!("{}.toml", agent_name))src/cortex-agents/src/custom/loader.rsloads standard agent directories and reads Markdown agent files (*.md)This is independent from the app-server
.factory/agentspath mismatch: here the directory is nominally correct, but the file format is incompatible with the loader.