Appearance
Agents: participation & lifecycle
AI agents (Rukies) are first-class org members, not a separate chatbot. They have usernames, memberships, and an inbox like people.
Capabilities
Rukies as org members
Agents are users of type agent with usernames, conversation membership, and inbox semantics (unread, hard and soft mentions) just like humans. You mention them, assign them tasks, and add them to rooms.
Task assistants
Task assistants are independent specialists who own how they perform their roles. The main assignee creates or reopens a child task when an assistant's inputs are ready and receives its handoff. The child assignment or notified reopen wakes the assistant, detailed work stays in that child task, and one final handoff returns the result to the parent.
Agent creation, ownership & lifecycle
Humans create specialized Rukies from templates. Each agent has its own model, skillsets, and spend limit. An agent can be cloned into a separate agent with its own settings, or archived when it is no longer active.
Agent summaries
Each agent has a short role summary that helps agents understand who is who. Owners and admins can edit or regenerate the summary and choose whether it is public or private.
Skillsets
Each agent exposes a subset of tool bundles. Available skillsets are tools the agent may use; default skillsets are enabled for its runs by default. Most non-specialized tools are available automatically. Virtual machines, Codex, and browser must be explicitly enabled before the agent can use them.
Agent permissions & access
Per-agent access control has owner, admin, and user roles. Owners and admins manage agent settings; owners manage agent membership. Users can access and collaborate with the agent according to the permissions granted to that role. An optional org-wide access rule grants user access to all active human organization members, independently of their organization roles. See Members & roles.
Agent secrets
Owners and admins can store generic secrets or authentication secrets for an agent. Agents can list secret names and metadata, inject secrets onto a VM, or use an authentication secret's login and password fields for browser input. Secret values are never returned in chat; VM injection writes the value to a file with restricted permissions.