Bots, folders, and threads

Bots are persistent teammates

A bot keeps its identity, instructions, memory, approved skills, connected tools, and computer preference. Create separate bots when the role or access should differ. You do not need another bot just to start a different project or choose another model.

• A coding bot attached to one repository
• A research bot with browser and document tools
• An operations bot with Gmail, Calendar, and Slack
• A local-model bot for private or offline work

New bot opens an editable draft before anything is created. Review its profile, model, permissions, memory, skills, and routines, then select Create bot. Settings → General → Defaults for new bots → Edit sets the starting values for future creation dialogs without changing existing bots. See Create your first bot for the full flow.

Threads are independent conversations

The conversations previously called Tasks are now Threads. Expand a bot in the sidebar and choose New thread, or use All threads to find an older conversation. Existing history is preserved.

Each thread remembers its own model and has its own progress, approvals, and Stop control. Start another thread while one is working; changing or stopping one does not redirect its siblings. Up to three direct threads can run per bot, including threads waiting for your approval.

Folders keep related threads together

Folders are optional organization under a bot. For example, Pepper can have an Email folder containing Triage Gmail and Triage iCloud, alongside a Website folder.

A thread chooses its model in the chat header and its Ask/Auto setting inside the composer. Folders have no model or permission settings. Moving a thread does not change its model, account, or access, or interrupt it. Removing a folder leaves its conversations ungrouped; it does not delete their history.

All the bot's threads share its saved memory and skills; they do not automatically receive every sibling transcript. Folders are not separate accounts or privacy boundaries. Bot profiles can carry different access preferences, but app organization is not an operating-system sandbox.

Threads can converse independently, but a physical computer, browser session, or shared project folder cannot safely have two agents changing it at once. Brainwrite reports contention instead of allowing overlapping managed actions. New local-agent threads use separate working folders by default; existing pinned folders are retained.

Groups and teams

Groups are the conversations previously called channels or rooms. They let multiple bots share context. Use a group when several specialists need the same brief or should hand work to one another. Membership, instructions and thread history are retained. The existing multi-bot turn-taking behavior is unchanged.

Existing sections keep their Chief of Staff assignments and bot communication rules. They are not thread folders. A Chief remains a bot role: it receives requests, delegates focused tasks, and summarizes the results.

Ask an existing Chief to appoint a bot as Chief of an authorized team, including a new team it creates. The combined setup shows the leadership change. In Ask mode, choose Apply setup or Cancel; Full Access applies it immediately. To replace a Chief, the plan must explicitly remove the old assignment and appoint the new Chief together. Each team has at most one Chief.

The new Chief can coordinate and configure its own team. It does not inherit the creator's access to other teams or execution permissions. Removing a Chief assignment also removes that bot's additional managed-team access. Existing conversations and model selections remain intact.

Delegation

Delegation asks another bot to handle a bounded subtask. The delegated task keeps its own activity and returns a result to the originating conversation. Give each delegate a narrow outcome and avoid assigning two bots ownership of the same files.