Brightstack is a shared context layer for product work. Sessions handle conversational execution, and issues, projects, documents, skills, and connected apps are the durable records those sessions read and update. The line to understand is between conversation state, which lives in a session, and workspace state, which outlives any one conversation.

​
The four building blocks

Issues

The core unit of work. One task, one owner, one status.

Documents

Plans, specs, and decisions in a block editor. Every document has its own context chat.

Projects

Related issues grouped under a lead, dates, and a timeline.

Chat and agents

Describe an outcome. Bright plans it, routes it to specialists, and checks the results.

​
How the pieces connect

  • An issue describes an outcome and carries its planning properties: status, priority, effort, assignee, labels, project.
  • A project groups related issues under a lead, dates, and a timeline.
  • A document holds knowledge that outlives a task: plans, specs, decisions, notes.
  • A session makes the work happen. You describe an outcome, Bright plans it, hands pieces to specialist agents, and checks the results.
  • Skills make the repeatable parts reusable, and agents give recurring roles a name.
One pass through the loop: capture work as issues in a project, write the thinking down in a document, then ask Bright in chat to take an issue end to end. Loop engineering covers the build loop Brightstack is designed around, and why it changes how you write an issue. Forge is the route when the result needs an independent verdict.

​
Find your way around

The app has no top bar. Four icons at the head of the left rail are the sections:
  • Work is the organization’s home. Sessions live here, and New session starts one.
  • Plan holds issues, projects, and the roadmap.
  • Docs holds documents.
  • Capabilities holds skills, agents, tools, apps, and build defaults.
Settings is not a section. Open your name at the bottom of the left rail to reach it, next to Switch organization.

​
Conversation state and workspace state

A session holds conversation state: messages, tool calls, approvals, goals, tasks, and artifacts. Closing a tab does not delete the session. Archiving moves it out of the Active sessions list into Archived. Switch the rail filter to Archived or All to see it, and use Restore to bring it back. Session lifecycle follows a session from new conversation to archive. Workspace state persists independently of any one conversation: issues, projects, labels, documents, skills, agents, settings, and connected apps. A session reads and updates these resources when you provide context and approve the tools it asks for.

​
Tips

  • New to Brightstack? The Quickstart uses all four building blocks in about five minutes.

​
Good to know

  • A session holds messages, tool calls, approvals, goals, tasks, and artifacts.
  • Closing a tab does not delete a session. Archiving moves it from Active to Archived, and Restore brings it back.
  • The left rail has four sections: Work, Plan, Docs, and Capabilities. Settings lives under your name at the bottom of the rail.
  • Workspace state (issues, projects, labels, documents, skills, agents, settings, connected apps) persists independently of any conversation.
  • Every document has its own context chat.

​
Next step

Give Bright somewhere to work by linking your tools in Connect apps.