Follow a term's link for examples and instructions.
#Workspace and collaborators
| Term | Meaning |
|---|---|
| Clay Studio | The application and server that provide your workspace |
| Clay | Your built-in lead Mate, who helps coordinate work and operates supported workspace controls |
| Mate | A private AI collaborator with a continuing role, instructions, and conversations |
| Project | A folder on the server, with conversations and records for the work there |
| Session | A conversation you can return to across visits |
| Provider runtime | The coding-agent application Clay Studio uses, such as Claude Code or Codex |
| Model | The AI model selected through that coding agent |
| Driver | The project agent responsible for the task and reviewing its result |
| Split Worker | A linked agent session assigned part of the Driver's work |
| Background task | A task started within a provider's execution, with provider-dependent inspection controls |
#Layout and files
| Term | Meaning |
|---|---|
| View | A saved project arrangement of conversations and tool panes |
| Folder | Organization for session-list entries; it does not move repository files |
| Worktree | A separate Git working directory for parallel changes |
| Overlay / Dock | A tool floating over the conversation / space reserved beside it |
| Follow / Pin | A file pane following your selection / keeping one file visible |
| GUI / TUI | A graphical conversation / a coding agent's terminal interface |
| CLI | A program you operate through typed terminal commands |
#Lasting context
Knowledge holds documents and databases in Mate workspaces. A database schema defines its fields; a saved table view chooses columns, filters, and ordering without copying its records.
Project Logs preserve task outcomes and decisions. Issues track actionable work. Notes keep reminders visible while they need attention.
Me holds private knowledge about you across projects and Mates. Clay reviews reported observations before saving them. Mate Memory refers to that Mate's recorded conversation material and is separate from Me.
#Messages and automation
A draft is unsent text. A queued message is waiting for delivery. Delivery or acknowledgement means it reached the receiving system; completion means the requested work finished.
A delayed message sends once after a delay. A Mate schedule sends a private recurring prompt. A Scheduled Task runs a project Driver/Worker pair. Loop/Ralph supports repeated attempts toward a defined outcome.
Skip omits an overlapping start; coalescing combines overlapping starts into one queued follow-up. Pause changes future scheduling. Stop interrupts execution without undoing actions already completed.
#Access
A public project is available under authenticated workspace rules, not anonymously published. Exact access grants access to one worktree; inherited access comes from its parent project. A session has its own visibility in addition to project access.
Permission mode controls how the agent handles tool actions. It does not grant access to another person's private content.