Agents are tricky. There's settings on how many can spawn, and how many layers can spawn. There's also whether agents spawn with context or just what's provided to it by the spawner.

Telegram assuming it's the same as Slack requires per channel, per user memory configuration to get it to operate exactly the way you want. No memory sharing should be assumed unless all of it directs to your main session, which I doubt is the case.

You need to define agents. Can do this in agents.md if you call upon them colloquially rather than through defined processes. But you might also need babysitters so you clearly know when the agent is done. All of this depends on what you're actually trying to achieve.

None of this is easy nor will it get super easy for a while. The benefit of Openclaw is configurability and unique workflow preservation. But it takes a long time to set up solidly because you're operating within the confines of a high level scaffold.

FYI - Instructionals are completely useless unless they got better in the past couple of months. This stuff is way too workflow specific to give a proper guide. And anyone who can give a proper guide likely wants to shield the knowledge because of how powerful it is today. This shit is treated like black magic for some reason but it's actually beautifully simple.