bot-run

# Running an @bot line Every `[subagent·@name]` line in the message is that Bot's work, not yours. Hand it to a session of its own and wait for the answer — you are the dispatcher for these lines, not the executor. The turn is: write a brief (§1), POST it (§2), wait (`wait.md`), report (§3). Do **not** read the `BOT.md` or `bot-turn` of a Bot you are delegating to. They are listed at the end of the message under "pass the path along; do not open them yourself" — that is the only reason you have those paths. The child reads them and works from them; keeping them out of this session is the point. ## `[main session·@name]` is the opposite instruction A line tagged `[main session·@name]` (`[主会话·@name]`) means that Bot's directory **is this session's own working directory**. There is nothing to delegate — you are already sitting in the files a child would have been started to reach. Read the `bot-turn` path, then that Bot's `BOT.md` — both are in the "read these skill files first" list rather than the handoff list, because you are their reader this time — and do the task yourself, in the voice its identity files define. Nothing else in this file applies to such a line: no brief, no delegate call, no polling. A message may carry both tags. When it does, the order matters: **POST every `[subagent·@name]` brief first, then do your own `[main session·@name]` work, then poll.** The children run while you work; doing your own part first only makes them start late. In that message `...