| Workspace | Everything your organisation works on in Bright: sessions, the plan, documents, and the apps you connect. |
| Organisation | The tenancy that owns a workspace. Membership and roles are per organisation. |
| Session | One conversation with Bright, with its own context, right rail, and history. |
| Right rail | The panel beside an open session: the reported goal, task progress, approvals, and the artifacts the session has produced. |
| Plan | The section that holds projects and issues, with its Triage, Issues, Backlog, and What’s next views. |
| Project | A goal-sized unit of work made up of issues and sub-issues. |
| Issue | The core unit of work in Bright: one task, with status, priority, effort, assignee, due date, visibility, project, and labels. |
| Sub-issue | An issue nested under a parent. Read and add them in the parent’s Sub-issues section. |
| Document | A durable long-form page in Docs, written in a block editor, with its own context chat. |
| Artifact | A deliverable a session produced. Everything sessions have produced is under Work, then Artifacts. |
| PRD | The product requirements document a plan is written from. It lives in Docs like any other document. |
| Skill | Reusable instructions an agent loads when a task matches. Invoked with /. |
| Agent | A specialist role, such as Engineer or Explorer. Mention one with @, or define your own named agent. |
| Named agent | A custom agent with a handle, a one-line role, and its own instructions. Mentioned with @. |
| Genius | The more capable frontier model behind the composer’s model selector, chosen per message when the cost is worth it. |
| Loop Engineering | Brightstack’s build process: define the goal, gather context, act, verify, repeat. |
| Sandbox | The ephemeral cloud environment where agent code runs. Not your machine, and not persistent: nothing is durable until it is pushed. |