Brightstack is a shared context layer for product work. It combines conversational execution in sessions with durable records: issues, projects, documents, skills, and connected apps.

​
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 removes it from the active Recent list. 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.

​
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 roadmap.

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 roadmap.
  • 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.

​
Where to go next

  • Session lifecycle: a session from new conversation to archive.
  • Loop Engineering: the build loop Brightstack is designed around, and why it changes how you write an issue.
New to Brightstack? The Quickstart uses all four building blocks in about five minutes.