Install, Sign In and Open a Real Project
Start in the repo you actually work in, not a sample app.
Use the right surface
After this you can pick Quickstart for the right job and define done.
Done means a real repository is open, trusted, indexed and ready for a scoped Cursor task.
A concrete first-hour target: the right repo is open, the index is ready and the first prompt is scoped.
Use Quickstart when you are opening Cursor for the first time and need one trustworthy first loop. Keep the boundary narrow.
Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.
Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Run this loop in a real repo.
- Entry point
- Cursor app, sign-in flow, file explorer and settings
- Source
- Cursor quickstart, indexing, privacy and account docs
Use the source as the product reference.
Ask Cursor for an output you can inspect.
If the output cannot be checked, narrow the task before you continue.
A good run leaves a file, setting, screenshot, command result or written claim you can verify.
Takeaway. Done means a real repository is open, trusted, indexed and ready for a scoped Cursor task.
Self-check
QWhen should you reach for Quickstart?
Run it
After this you can do the task with clear scope and one proof point.
Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.
- 1Install Cursor and sign in with the account or SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. identity you will actually use.
- 2Open a real project and confirm the workspace, branch, terminal and extensions look right.
- 3Check whether the codebase index is building before asking broad codebase questions.
- 4Write down one real task from the current repo that is small enough to verify today.
The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.
Keep the task small enough to review.
Indexing has started or completed before broad codebase questions.
Takeaway. Stop when you have proof: The repository path and branch are the ones you intend to edit..
Self-check
QWhich habit makes this workflow safe to use on a real project?
Check it
After this you can find the first failed check before changing tools.
Verification decides the next move.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Pick a row to see what to look for.
Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.
No proof means more checking.
Use a real repo or admin setting. Save the prompt, context and proof.
Takeaway. If it fails, find the first failed check.
Self-check
QThe workflow failed. What is the best first move?