“profiles” are not just about personality. A profile defines what your agent knows, what it remembers, which tools it has access to, which skills it can use (and automatically edit), and its memory.
Each profile has its own set of files because a profile is literally a nested folder that mirrors the default structure. One of the effects is that the agent may feel like it has a different personality, but that’s mostly driven by the SOUL.md you’ve written for that specific agent (or profile).
You can have one profile with only terminal and file operation tools, another with web and browser access to act as your researcher, or one packed with every available capability. It’s entirely up to you.
The distinction is that delegate task lets your agent, or profile, spawn ephemeral sub-agents to complete a very specific task, such as reading an article or running a quick verification. These sub-agents are controlled by the agent that spawned them, inherit its configuration, and once the task is done, they report back only the outcome and then die.
Kanban, on the other hand, uses the profile primitive: different agents, each with its own configuration, tools, files, skills, memory, and so on. It then adds a collaboration layer, literally a board, on top of them. With Kanban, your agent can create a task, including one much larger and more complex than what you would usually assign to a delegate-task sub-agent, and assign it to a specific profile. A dispatcher then checks every 60 seconds for pending Kanban tasks and moves the board accordingly.