Glossary
Short definitions of the words you see in the desktop app, the Organization Console and these docs.
| Term | Meaning |
|---|---|
| Organization | Your company's Clauge account. It holds the members, groups, policy and shared resources. See Organizations & Members |
| Organization Console | The web app. Administrators use it to manage groups, people, resources, policy and AI-DLC. Members use it to see their groups and download the app |
| Administrator | A member who can change policy, groups and AI settings for the whole organization |
| Group | The area a piece of work belongs to. The same groups appear in Workspace, Meetings, SQL, NoSQL, REST, SSH and Explorer. A session started inside a group can reach the meetings, databases, APIs, servers and files of that group. See Groups |
| Organization group | A group created by an admin. It carries the ORG badge and follows the organization's policy |
| Private group | A group you create for your own work, if your organization's policy allows it. It is not tracked by the organization and AI-DLC does not apply to it |
| Project | The unit of work under a group, usually linked to a repository folder. It has its own sessions, boards, notes and automations. See Projects |
| Session | A coding agent working on a project, on its own branch. You can run any number in parallel. See Sessions |
| Session purpose | What a session is for: Brainstorming, Development, Code Review, PR Review, Debugging or Custom. The purpose sets the agent's working rules |
| Coding agent | The agent a session runs: Claude Code, Codex, Antigravity or OpenCode. You sign in to it with your own account |
| AI assistant | The in-app assistant in SQL, NoSQL, REST and SSH. It uses the organization's AI key |
| Board | Columns and cards for tickets and pull requests, under a group or a project. See Boards |
| Card | One ticket on a board |
| Automation | An agent or coworker job that runs on a schedule in a group or a project. See Automations |
| Coworker | A named AI persona with a role, run by a coding agent. See Coworkers |
| Resource | A connection the organization owns (SSH, SQL, NoSQL, REST or Explorer), created in the console and attached to groups. See Resources & Access |
| Integration | An organization-level connection to Jira, GitHub, GitLab, Slack or Microsoft Teams. Integrations are separate from plugins |
| Policy | The organization's rules for which modes and actions are allowed |
| AI-DLC | The organization's delivery standard for board cards in organization groups. It has five stages: Plan, Ticket, Implement, Review, Merge. See Development Standards |
| Standard | An AI-DLC definition that admins write and publish. Each stage has instructions, a template, rules, a gate and metrics |
| Gate | The check at a stage that decides whether a card may move on. It is set to Off, Advisory or Blocking |
| Blocking | A gate or rule level that stops the action and marks the card blocked |
| Override | An administrator passing a blocked card with a reason. Overrides are listed under Compliance |
| Dictation | System-wide, on-device speech to text. It types what you say at your cursor in any app |
| Meeting notes | The transcript and AI summary of a recorded call. Transcription happens on the device. See Meetings |
| Remote | Reaching a Clauge desktop from another desktop or from the iOS or Android app. See Remote Access |
| Workspace MCP server | A local server that lets coding agents on your computer call 45+ Workspace tools. See MCP Setup |
Desktop app and Organization Console
- Desktop app: where the work happens. Groups, projects, sessions, boards and notes, plus the modes for databases, APIs, servers, files, meetings and remote access.
- Organization Console: the web app where admins create groups, attach resources, manage people, set policy and review usage.