Getting started
Gapfy Cue is a Windows desktop app for launching development projects and running guided procedures. This guide assumes Cue is already available on your machine and walks through the first useful setup without requiring a particular project type or development stack.
Choose how you work
Cue supports a full offline guest mode that works without an account. Guest mode is useful when you want a local-first cockpit on one machine or need to work without a connection.
Signing in connects Cue to the Gapfy platform. Connected work can sync across machines and use the workspace structure, shared blueprints, people directory and memberships. You can still keep working locally when the network is unavailable.
Register your first project
Start with a development project you use regularly. Register it in Cue, then associate the launch points that matter to the project: its IDE, terminal, folders and URLs. These become one-click actions in the projects cockpit, so the same starting tools stay close together.
Add a saved run or debug profile when the project needs a repeatable launch sequence. Profiles can orchestrate multiple steps and can attach to Visual Studio. Use the readiness view before launching to see whether a dependency is missing on this machine.
The complete project workflow is covered in the projects and onboarding guide.
Run a procedure
Open an existing procedure or create a small runbook for a task you know well. A procedure is made from typed steps, including local actions, checks, validations and scripts. Follow the numbered steps and review the result of each check before moving on.
Scripts wait for explicit confirmation. Production-sensitive steps do the same and leave a record in the activity ledger. If the procedure contains a Decision step, answer its question and Cue will follow the configured route: continue, jump to a later step, or end the run. If work is interrupted, safe resume provides a controlled return to the run.
For the full procedure model, see the procedures and runbooks guide.
Prepare another machine
When a machine needs the complete project setup, use the eight-step Create Local Environment wizard. The wizard turns tasks such as getting the code, restoring it and configuring it into an executable setup run. Check workspace readiness first so missing dependencies are visible, then follow the compiled run.
If the same setup should be reused, place the project or procedure definition in a workspace blueprint. Blueprints help another developer start from the same known structure instead of rebuilding it by hand. See the environment setup guide.