SDK Quickstart in TypeScript and Python
Programmatic agents start as ordinary code with explicit credentials.
Use the right surface
After this you can pick Cursor SDK for the right job and define done.
Done means you can create the first SDK run and explain the credential boundary.
The same agent loop can run in a terminal, script, CI job or SDK-backed internal tool.
Use Cursor SDK when you want to build an internal tool or bot backed by Cursor agents. 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/sdk or Python SDK with service credentials
- Source
- TypeScript SDK and Python SDK 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 you can create the first SDK run and explain the credential boundary.
Self-check
QWhen should you reach for Cursor SDK?
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.
- 1Choose TypeScript or Python based on the host system.
- 2Create the first local run with a small prompt.
- 3Stream or wait for output in a reviewable way.
- 4Record request IDs and usage ownership.
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.
The run target and working directory are explicit.
Takeaway. Stop when you have proof: Credentials are loaded securely..
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?