Teams and sync

Cue can work as a local Windows cockpit or connect projects and procedures through the Gapfy platform. Its workspace model gives shared work an owner, while offline guest mode keeps the local workflow available without an account.

Organize work by ownership

Connected work follows an Organization, Team and Project hierarchy. The people directory represents the people in the organization, and memberships connect them to the teams and projects where they work.

Use the hierarchy to keep a project with the team responsible for it. Shared blueprints and procedures then have a clear workspace context instead of becoming unowned templates. Memberships should reflect real working responsibility so developers see the projects and reusable setup relevant to them.

Sync across machines

When signed in, Cue syncs through the Gapfy platform. Project definitions, procedures and workspace material can follow a developer between machines, so the cockpit does not need to be rebuilt from memory on every computer.

The machine itself still has local state. Use workspace readiness after moving to another computer to see which dependencies are missing there. Then run the relevant environment setup and verify the saved launch profiles on that machine.

Cue is local first, so temporary loss of connectivity does not have to stop local work. Once the connection is available again, connected work can continue syncing through the platform.

Work in offline guest mode

Full offline guest mode works without a Gapfy account. It is appropriate when the cockpit and procedures need to remain on one machine or when no connection is available. Guest mode preserves the local-first workflow, including project actions and local procedures, without depending on platform access.

Workspace sharing and cross-machine sync require connected work. Decide which mode fits the task, especially before expecting another person or machine to receive a project or blueprint.

Protect sensitive values

Secrets stored in Cue variables are encrypted at rest on the local machine and on the server. Azure DevOps tokens used to trigger pipelines are also stored encrypted. Keep secrets in protected variables rather than copying them into procedure text, project notes or scripts.

Production-sensitive steps require explicit confirmation. Cue's activity ledger records who ran what, providing a history for connected operational work and making important executions easier to review.

Adapt the desktop experience

Cue is localized in multiple languages and supports light and dark themes with selectable accent colors. These preferences let each developer adjust the desktop experience without changing the shared project and procedure definitions.

For the first connected project, continue with the projects and onboarding guide. For reusable workspace templates, see the environment setup guide. For recorded execution and pipeline hand-offs, see the procedures and runbooks guide.