The lifecycle
- Start. Open Work and select New session. It opens as a new tab, so several threads run side by side.
- Interpret. Bright reads your request against the context you provided, the selected mode, and available skills.
- Plan. The session reports a goal and its todos in the right rail’s Work tab.
- Act. Bright uses the tools it is permitted to use and pauses when an action needs your approval. The request appears in the Waiting on you strip above the composer.
- Produce. Results arrive in chat. Reusable outputs become artifacts, listed in the right rail’s Artifacts tab and the Sessions panel.
- Review. Check the result against the goal. Iterate in the same thread; the session keeps its context.
- Close or archive. Closing a tab removes it from view. Archiving removes the session from the active Sessions list; the list’s Archived and All filters bring it back.
A quiet session is not a finished session
A session that is not generating can still be waiting: on an approval, or on an answer you owe it. Check the Waiting on you strip above the composer and the right rail’s Work tab before treating a session as complete.Good to know
- Each new session opens as its own tab, so several threads run side by side.
- Closing a tab only removes it from view. Archiving removes the session from the active Sessions list; the Archived and All filters bring it back.
- Reusable outputs become artifacts, listed in the right rail’s Artifacts tab and the Sessions panel.
- Pending approvals appear in the Waiting on you strip above the composer, not in the right rail.
- The selected mode decides what Bright is allowed to change. Sessions and modes covers what Ask, Plan, and Agent may touch, and the day-to-day of running sessions.
- Loop Engineering describes the build loop Brightstack is designed around.