Projects

A workspace can hold more than one line of work at once — a feature you're building, a bug you're chasing, an experiment on the side. Projects keep those streams separate inside a single workspace: each one has its own run history and its own short list of the workflows it actually uses, without you juggling folders or splitting up the shared .ring record.

The Default project

Every workspace has a Default project. It's created automatically the first time you open a workspace, and it's the home for every run that isn't filed anywhere else — including all the runs you made before you had any projects. You never have to set it up, and you can't delete it. If you never create another project, nothing changes: the app looks and works exactly as it did before Projects existed.

The active project

Each window has one active project, shown in a dropdown in the toolbar next to the workspace name. The active project scopes what the window shows and where new work goes:

• Recent Runs and Search list only the runs filed under it (the Default project also sweeps in every unfiled and legacy run).
• New runs you start are filed under it automatically.
• If it pins workflows (below), the Workflows list narrows to just those.

Switching the active project re-scopes the window instantly. The choice is remembered per window, so reopening a workspace lands you back on the project you left.

Creating and switching projects

Open the Projects tool window from the briefcase icon in the left rail, or choose Manage Projects… in the toolbar's project dropdown. From there you can create a project, rename it, switch which one is active, and delete the ones you no longer need. You can switch the active project from either the Projects list or the toolbar dropdown.

Pinned workflows

A workspace's full workflow library is shared across every project, but most projects only touch a handful of workflows. Pin the ones a project uses and the Workflows list shows just those, in the order you pinned them, whenever that project is active. Pin and unpin from the Projects tool window.

Pinning is only a view. Every workflow is still runnable, and a project with no pins shows the full Built-in/Custom library exactly as before — which is why the auto-created Default project reads like a pre-Projects workspace. The Editor tab always shows the whole library, since authoring is workspace-wide.

Moving a run between projects

Filed a run under the wrong project, or want to tidy an old one into place? Right-click any run in Recent Runs and choose Move to Project. The run keeps all of its history; only which stream it belongs to changes.

Deleting a project

Deleting a project (any one but Default) removes it from the list. Its runs are not touched or lost: with no project left to claim them, they fall back to the Default project, where you'll find them again. Nothing on disk is rewritten, so a deleted project's runs keep their full provenance.

Where projects live

The set of projects and their pins is saved in your workspace's .ring/projects.json; which project is active in a window is part of that window's saved layout. A run only records which project it belongs to — the runs themselves stay in the single .ring/runs/ directory, so provenance, search, and the CLI are unaffected.