Bots & workspaces
Give work a home and give every specialist a clear responsibility.
Spaces organize the work
A Space groups your bots, conversations, shared knowledge, and working setup. Keep unrelated businesses or goals in separate spaces and choose context sharing deliberately.
Bots have instructions, model choices, conversations, and, where configured, persistent computers. Preparation-only bots are intentionally prevented from carrying out operational tool work.
The Architect
The Architect helps inspect the crew, review activity, and propose changes to the setup. Workspace proposals are reviewed before being applied. Changes have an audit trail and supported reversal paths.
The Architect can use its allowed planning, knowledge, and connector tools. It cannot operate a bot computer directly, and is not a general replacement for the specialists in the crew.
Routines and persistent files
Routines attach recurring work to a bot. Define the schedule and prompt explicitly; a natural-language onboarding plan does not automatically become an active schedule.
Files in a bot’s persistent home survive supported computer recreation. Deleting a bot, resetting a computer, and deleting a space are different operations; review the application’s confirmation before making a destructive change.