Workspace and sessions
| Term | What it means |
|---|---|
| Brightstack | The company and the platform as a whole. You sign up at app.brightstack.ai, and Loop Engineering is Brightstack’s build process. |
| Bright | The app itself, and the manager agent you talk to in a session, which routes work to the specialist agents. |
| Workspace | Everything your organization works on in Bright: sessions, the plan, documents, and the apps you connect. |
| Organization | The tenancy that owns a workspace. Membership and roles are per organization. |
| Work | The first section in the org navigation, where sessions live. Also the name of the right rail’s first tab. |
| Session | One conversation with Bright, with its own context, right rail, and history. |
| Mode | The composer’s permission setting for a session: Ask, Plan, or Agent. It decides how much Bright may change in the workspace. |
| Tool approval | The checkpoint before a protected action runs. It appears in the Waiting on you strip above the composer with Allow once, Always allow, Always deny, and Deny. |
| Right rail | The panel beside an open session, with tabs for Work (goal, todos, delegated agents), Artifacts, Side Session, and Changes. Approvals are not here; they appear in the Waiting on you strip above the composer. |
Plan and issues
| Term | What it means |
|---|---|
| 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, estimate, 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. |
Documents and artifacts
| Term | What it means |
|---|---|
| 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. |
Agents, skills, and models
| Term | What it means |
|---|---|
| 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 @. |
| Capabilities | The section in the org navigation with five tabs: Skills, Agents, Tools, Apps, and Build. Skills, named agents, and app connections are set up here. |
| Genius | The more capable frontier model behind the composer’s model selector, chosen per message when the cost is worth it. |
How work runs
| Term | What it means |
|---|---|
| Loop Engineering | Brightstack’s build process: define the goal, gather context, act, verify, repeat. |
| Forge | Bright’s delivery route: Spec, Plan, Build, Acceptance, and Ship, invoked with /forge. Each phase stops at its own boundary. |
| Phase | One of Forge’s five named stages. Naming a phase names where the work stops. |
| Candidate | The exact integrated change a review or acceptance run judges. |
| Acceptance | Exercising the real outcome of a review-passed candidate. A review PASS is not acceptance. |
| Independent review | A verdict from an engineer who did not write the change, produced inside Build. |
| Personal sandbox | The cloud machine your sessions, agents, and the built-in editor share. One per person per organization. |
| Built-in editor | Bright’s file tree, code editor, and Changes view, opened from the Work tab strip. |
| Sandbox | The ephemeral cloud environment where agent code runs. Not your machine, and not persistent: nothing is durable until it is pushed. |