Problem
botnexus agent add <id> only creates the config entry — no workspace directory, no bootstrap files (SOUL.md, AGENTS.md, IDENTITY.md, USER.md, TOOLS.md, memory/). The agent wizard may do more, but the result should be identical regardless of how the agent was created.
Expected Behaviour
Every agent creation path should produce the same result:
botnexus agent add <id>
botnexus agent wizard
- Web UI
- Agent-driven (e.g. one agent creating another)
- API/programmatic
After creation, the agent should have:
- Config entry in platform config ✅ (already works)
- Workspace directory (
~/.botnexus/agents/<id>/workspace/)
- Scaffold files:
SOUL.md — with sensible defaults/placeholders
AGENTS.md — operational guidelines template
IDENTITY.md — agent identity (name, emoji, role)
USER.md — user context template
TOOLS.md — available tools reference
memory/ directory
- Any other bootstrap the platform expects
Approach
Extract workspace scaffolding into a shared method (e.g. AgentScaffolder or similar) that all creation paths call. This ensures consistency and means new bootstrap files only need adding in one place.
The wizard can still ask extra questions to customise the content, but the baseline scaffold should be identical.
Current State
agent add — config only, no workspace ❌
agent wizard — unclear if it scaffolds fully
- Web UI — not checked
- Agent-driven — not checked
Labels
area: platform, priority: medium
Problem
botnexus agent add <id>only creates the config entry — no workspace directory, no bootstrap files (SOUL.md,AGENTS.md,IDENTITY.md,USER.md,TOOLS.md,memory/). The agent wizard may do more, but the result should be identical regardless of how the agent was created.Expected Behaviour
Every agent creation path should produce the same result:
botnexus agent add <id>botnexus agent wizardAfter creation, the agent should have:
~/.botnexus/agents/<id>/workspace/)SOUL.md— with sensible defaults/placeholdersAGENTS.md— operational guidelines templateIDENTITY.md— agent identity (name, emoji, role)USER.md— user context templateTOOLS.md— available tools referencememory/directoryApproach
Extract workspace scaffolding into a shared method (e.g.
AgentScaffolderor similar) that all creation paths call. This ensures consistency and means new bootstrap files only need adding in one place.The wizard can still ask extra questions to customise the content, but the baseline scaffold should be identical.
Current State
agent add— config only, no workspace ❌agent wizard— unclear if it scaffolds fullyLabels
area: platform, priority: medium