Account
The identity you use to sign in. Check it first when expected projects or connections are missing.
Organization and role
The organization associates people and access rules. A role affects which actions a person can perform. The demo’s Member role could not open agent administration. See Roles and access.
Space or workspace
The area shown in the sidebar for the current work context. Public and interface material use both terms. See Accounts and workspaces for the documented hierarchy and limits.
Space assistant
The assistant reached through Space assistant in the sidebar. It helps create and staff projects and coordinate their managers across accessible projects. Its own conversation is separate from project conversations. See Space assistant.
Project
Work organized around a goal. Project setup asks about the goal and staffing. A project is distinct from an individual message or task.
Project manager
The coordinating agent for a project. It tracks objectives and blockers, delegates specialist execution, reviews contributions, and handles project documentation and advice. See Project manager.
Agent and team
An agent is an AI worker with a role. A team groups agents working toward a project outcome. Suggested roles in examples are not necessarily built-in templates.
Conversation, thread, and branch
A conversation carries the messages for a piece of work. A thread keeps a conversation distinct. A branch explores another continuation where the relevant conversation type supports it. See Chats and branches for scope-specific behavior.
Rewind
A history-changing conversation action. Read the warning before sending a replacement message; it must not be treated as undoing an external action.
Knowledge and artifact
Knowledge is source context used for work. An artifact is a deliverable such as a document, sheet, or file. An artifact can later become source material, but its presence alone does not prove it was included in a particular answer.
Connection
Authorized access to an external service. A Marketplace listing, a connected account, and a successfully tested operation are separate states.
Channel and trigger
A project channel is a messaging endpoint routed to an assigned project agent. A trigger is a workflow definition that starts specified work for eligible input. Connecting a conversational channel does not require creating a trigger. See Channels and triggers.
Scheduled task and recurring schedule
A scheduled task is one concrete future action. A recurring schedule defines repeated work using a timetable or interval; cron is a way to express such a timetable. An objective due date is neither. See Scheduled tasks and Recurring schedules.
Project Flow
The objective handoff and automation controls under Dashboard → Objectives. Selected creation/status events can queue a manager check; the completion-review toggle is separate. The conditions are not a global switch for every automatic run. See Project Flow.
Heartbeat
A project-manager check after inactivity, once at a future time, or daily. Current controls are managed by users through Workflows → Heartbeats; agents can inspect them. A heartbeat is separate from an agent-created cron schedule or one-off task. See Heartbeats.
Codebase
A project resource connecting software work to a local working copy, GitHub mirror, or both. A knowledge document about code is not a connected execution environment. See Codebases.
Skill and tool
A skill is reusable written guidance. A tool performs an operation when the agent has the required access and context. Loading a tool group changes visibility, not authorization. See Capabilities.
Delegated task and incoming request
In Flexible chats, delegated work can use a focused task with separate history and review. In Persistent team, it can be a tracked incoming request in an agent’s ongoing conversation. Neither creates a permanent supervisor tree. See Delegation and messages.
Shared state and core memory
Shared state is explicit project information, such as a document or sheet that agents can reference. Core memory is durable guidance or preferences belonging to an agent. Neither is a promise that all conversations are automatically merged. See Shared state and memory.
Work mode, context, and approval mode
Work mode offers Fast, Balanced, and Powerful in the inspected composer. Context offers Standard and Max. Approval mode is a separate setting with its own choices. See Work modes and context and Approvals and review.
Reviewable result
An output you can inspect against the task: text, a file, source links, or a verified external result. A progress message is not itself proof that the requested work is complete.