Workflows are how you turn normal OpenWork chats into organized, repeatable work. In the UI, every session can be renamed, pinned, archived, reordered, or moved into a custom group folder from the session menu. Group folders are workspace-specific: create a group likeDocumentation Index
Fetch the complete documentation index at: https://openworklabs.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Research, Ready for review, Shipped, or Bugs, then move sessions into that group as the work changes.
You can also describe the workflow in the composer while you work. For example: When this is done, rename the session to "Auth cleanup", move it to Ready for review, and pin it, or If this turns into a bug investigation, put it in Bugs; otherwise archive it when finished. Those instructions map to OpenWork’s session management primitives: rename changes the session title, move to group stores a session-to-group assignment, pin keeps important sessions at the top, archive hides finished sessions without deleting them, and manual ordering lets you arrange sessions and groups around your process.
This makes session organization dynamic instead of manual bookkeeping. A team can keep groups for Triage, In progress, Needs human review, and Done, then ask OpenWork in chat to classify future sessions into those buckets as work completes. The exact groups and actions are configurable from the UI, so the workflow can match how you already work instead of forcing a fixed project-management structure.