Cursor AI logo

[ AI tools · Development ]

Cursor in Expert Hands Ships Features Faster

Several of our engineers work in Cursor every day. They use its Tab completions, agent and cloud agents on feature work in your codebase, with your rules in the repository and review on every change.

cart.tscheckout.tscart.test.tsAgent: 3 files changed
cart.tsReview

- const total = items.reduce((s, i) => s + i.price, 0);

+ const total = items.reduce((s, i) => s + i.price * i.qty, 0);

checkout.tsReview

- if (code) total = total - 10;

+ if (code) total = applyDiscount(total, code);

cart.test.tsReview

+ it('multiplies price by quantity', () => {

+ expect(totalOf([{ price: 5, qty: 3 }])).toBe(15);

+ });

export const totalOf = (items) => items.reduce(...)Tab

The AI Code Editor Most of Our Engineers Live In

Eight keys explain most of Cursor. Press one, or watch them go.

Tab

Tab that predicts edits

Suggests the next change, not just the next word, including jumps to the line you will edit next.

Default macOS shortcuts; they can change between Cursor versions.

[ How we use it ]

Four Modes, Picked by the Size of the Job

Writing code by hand

Our engineers keep typing; Tab fills in the obvious parts and predicts the next edit. Fast, local and always under the engineer's eye.

  • Agent: The agent plans the change, edits the files and runs the tests, then shows the diff. The engineer accepts, edits or rejects each part.
  • Cloud agents: Upgrades, test backfills and chores run remotely while the engineer works on something else, and arrive as branches to review.
  • Bugbot: Bugbot reads each pull request and flags likely bugs before a person reviews, so human review focuses on design and risk.
Cursor · Tab
  • function formatPrice(cents) {
  • return new Intl.NumberFormat('en-US', {
  • style: 'currency', currency: 'USD',
  • }).format(cents / 100);
[ A day on a client project ]

What Cursor Actually Does in One Engineer’s Day

An illustrative day on a typical feature sprint. The engineer decides; the tools take the typing.

  • 09:30

    Tab fills in a new API handler while the engineer writes the tricky validation by hand.

  • 10:15

    Agent adds the field across form, API and database, then runs the tests.

  • 11:00

    Pull request opened with the diff reviewed line by line.

  • Two developers working through code together at a desk
  • 13:30

    Two cloud agents start on a library upgrade and a test backfill.

  • 15:00

    Bugbot flags a double-applied discount; fixed before human review.

  • 16:30

    Cloud agent branches reviewed, one merged, one sent back with notes.

  • 17:30

    Rules file updated so tomorrow's agent avoids today's mistake.

[ For your security team ]

Cursor Settings We Turn On Before Day One

Six settings your security team will ask about, configured and documented before engineers start.

  1. 01

    Privacy mode

    With privacy mode on, Cursor states that code is not stored by it or its model providers and is not used for training.

  2. 02

    Project rules

    Rules files and AGENTS.md in the repository, so every engineer's agent follows the same conventions.

  3. 03

    Ignore files

    Sensitive paths excluded from indexing and from what the agent may read.

  4. 04

    SSO and admin

    SAML sign-in, SCIM provisioning, usage dashboards and model allowlists on business plans.

  5. 05

    Security reports

    Cursor publishes its SOC 2 report for security reviews.

  6. 06

    Predictable spend

    Seat pricing with usage limits and alerts, so agent use does not surprise finance.

[ Cursor or something else ]

Which Tool for Which Job

We use all three. The choice depends on the work and on what your organization already licenses.

  • Cursor AI logo

    Cursor AI

    Everyday feature work in an existing codebase, where the engineer wants AI inside the editor.

  • GitHub Copilot logo

    GitHub Copilot

    The organization is standardized on GitHub and its enterprise policies, and wants one vendor.

    About GitHub Copilot
  • Claude Code logo

    Claude Code

    Large migrations and refactors driven from the terminal across many files.

    About Claude Code

What Do You Need This Month?

Dedicated Developer Trial

A senior engineer for a month, working in Cursor on your codebase with your rules and review process.

  • Starts within 48 hours
  • Uses your licenses and your repositories
  • Every change reviewed in a pull request

$3,000 to $5,000/mo

1 month

Packages from $1,500; custom projects from $8,000.

01

Is our code safe in Cursor?

With privacy mode on, Cursor states that code is not stored by it or its model providers and is not used to train models. Business plans add SSO, admin controls and model allowlists, and Cursor publishes a SOC 2 report for security reviews.

02

Do your engineers need our Cursor licenses?

Either works. Our engineers can use their own Cursor seats under privacy mode, or seats in your organization so your admin policies apply. We follow whatever your security team prefers.

03

Is AI-written code reviewed?

Always. Every change, however it was written, is reviewed by a senior engineer and covered by tests before it merges.

04

Cursor or GitHub Copilot?

Cursor tends to suit engineers who want the agent deep inside the editor; Copilot suits organizations standardized on GitHub's policies and licensing. Many teams allow both.

05

Which models does Cursor use?

Cursor offers models from OpenAI, Anthropic, Google and others, plus its own coding models. Admins can restrict which models are allowed.

06

Can you set Cursor up for our team?

Yes. We write the rules files for your repositories, configure privacy and admin settings, enable Bugbot and run sessions with your engineers on real tickets.

[ Contact ]

Let's build your next product together

Book a free strategy call and leave with a clear plan and estimate. No commitment.

  1. 01Pick a time that suits you
  2. 0230 minutes on scope, stack, timeline and budget
  3. 03Fixed-price proposal, NDA on request
Prefer email? contact@sajaltech.com