Pagayo is built inside Cursor.

A single operator,
moving like a team.

Pagayo is built by one founder, in one editor, across twelve repositories and nineteen subagents. Cursor turns a single window into a development organisation — write, refactor, review, test, deploy, all in the same tab, all in parallel.

Visit cursor.com
12
Repos in one workspace
19
Subagents on call
1
Operator, end to end
Parallel tabs, no context switch

Twelve Cursor features. One workflow.

Tab, Agent, Composer, Chat, @-mentions, Cmd+K, codebase indexing — every Cursor feature is a piece of the daily Pagayo loop. Here is the full set.

  • Tab Autocomplete

    Multi-line predictive edits that learn your repo and finish your thought.

  • Agent Autonomous

    A coding agent that plans, edits, runs commands, fixes its own mistakes.

  • Composer Multi-file

    Refactors that span dozens of files in one reviewable diff.

  • Chat Q&A

    Ask anything about the codebase. Cursor answers with file citations.

  • @ mentions Context

    Pull files, folders, docs, git diffs and the web into any prompt.

  • Cmd+K Inline edit

    Select a block, describe a change, get a clean diff to accept or reject.

  • Codebase index Semantic

    Every repo is embedded once. Cursor finds the right file instantly.

  • Apply Patches

    A model-suggested patch lands as a precise diff, not a copy-paste.

  • Rules AGENTS.md

    Project rules become guardrails the agent reads on every turn.

  • Subagents Parallel

    Fan out independent tasks. The main thread stays focused.

  • MCP Tools

    Custom servers expose Cloudflare, D1, GitHub and Stripe to the agent.

  • BugBot Review

    AI review on every PR — catches the small things before they merge.

Six layers, one workflow.

Multi-repo, parallel agents, the full edit-to-deploy loop, project rules, deep context, and AI review. Here is what each layer of the Cursor workflow does for Pagayo.

01 Multi-root workspace

Twelve repos, one window

The whole platform, always in context.

Pagayo lives in twelve repositories — storefront, api-stack, edge, workflows, schema, config, design, marketing, proxy, maintenance, docs and vault. Cursor opens them as a single multi-root workspace. One @ symbol reaches any file. One Composer prompt refactors across packages. There is no "context switch" because everything is already in context.

  • Multi-root workspace = no jumping between editors
  • Cross-repo @-mentions for shared types and schemas
  • Codebase index spans every package, every branch
WORKSPACEstorefrontapi-stackedgeworkflowsschemaconfigdesignmarketingproxymaintenancedocsvaultorder.service.ts × 3 repos+ 3 files updatedstorefront · api-stack · edge
02 Subagent fan-out

Parallel agents, one operator

One prompt out. Many workstreams back.

Pagayo defines specialised subagents — BackendDev, FrontendDev, DatabaseReview, CloudflareOps, SecurityAudit, Tester, Explore — each with their own scope and rules. When a task fans out into independent pieces, the main agent dispatches them in parallel. A schema change, a UI update, a smoke test and a config bump can all run at the same time, in the same session.

  • 19 specialised agents, each with their own AGENTS.md
  • Read-only Explore agents for safe, fast research
  • TaskDispatcher routes work to the right specialist
prompt"ship this"BackendDevrunningDatabaseReviewdoneTesterrunningCloudflareOpsdoneSecurityAuditqueuedExploredone
03 The full loop

From idea to deploy, in one window

Write. Run. Test. Build. Ship. Same tab.

Cursor is not just an editor. It is the terminal, the test runner, the build, the wrangler deploy, the git status. The agent writes the code, runs the tests, reads the output, fixes the failure, builds the bundle and triggers the staging deploy — all without leaving the chat. The loop that used to take five tools takes one window.

  • Integrated terminal: agent reads its own command output
  • Inline test results, lint warnings and type errors
  • wrangler dev, build and deploy all live in-session
01writeTab + Composer02runwrangler dev03testvitest04buildnpm run build05reviewBugBot + CodeReview06shipwrangler deploy
04 AGENTS.md · Instructions

The platform writes its own rules

Every repo teaches the agent how to behave in it.

Every Pagayo repository ships an AGENTS.md and a .github/copilot-instructions.md. The agent reads them on every turn: deploy policy, branch naming, schema ownership, Order-First rules, design system contracts, security boundaries. The rules are version-controlled, reviewable in PRs, and apply automatically — Pagayo's standards are encoded once, enforced everywhere.

  • AGENTS.md per repo — scope, boundaries, verification
  • applyTo patterns target the right instructions
  • Workspace-wide PAGAYO-NIVEAU.md as the canon
AGENTS.md# Scopestorefront · tenant + admin# Deploy Policystaging-only firstnever push main directly# Order-Firstone Order modelsource + originator enums# DatabaseDrizzle on D1@pagayo/schema onlyAGENTreadsruleseveryturn
05 Indexing · @-mentions

Deep codebase context

Ask in English. Cursor finds the file.

Every repository is embedded into a semantic index. When a prompt mentions "the order status webhook" or "the bunq sync service", Cursor pulls the right files without you typing a path. @ symbols layer in more: a folder, a Git diff, a doc, a Notion page, a web result. The agent never starts a turn cold — it starts with the relevant code already loaded.

  • Semantic codebase index, recomputed on save
  • @file · @folder · @docs · @git · @web — one syntax
  • Memory files (/memories/) for cross-session knowledge
@fileorder.tsfolderadmin/docsAGENTS.mdgitHEAD~3webcf docsmemory/repo
06 BugBot · CodeReview

AI that reviews AI

Every PR gets a second pair of eyes — automatically.

Cursor's BugBot scans every pull request and leaves structured review comments — security risks, regressions, missing tests, accidental any-casts, broken contracts. The CodeReview subagent runs a deeper architectural pass. Pagayo merges what the bots confirm. The five-pillar standard (consistency, testability, fault handling, single source of truth, edge-first) gets enforced before code ever reaches main.

  • Automatic PR review on every open pull request
  • CodeReview subagent for architectural deep-dives
  • Catches ORM drift, schema mismatch, missing tests
#412 · feat(order): bunq syncopen++-+!BugBotMissing idempotency key on bunqwebhook handler — replay risk.CodeReviewSchema check passes · Order-Firstrespected · 100% coverage on diff.

A team of one, that ships like ten.

You will never see Cursor in the product. What you will feel is the cadence. New features land weekly. Bugs are fixed the day they are reported. The platform keeps moving — because the editor moves with it.

Cursor turns one operator into a development organisation: twelve repos, nineteen agents, one window, one head. It is how a single founder can build a real SaaS platform without losing weekends to context-switching.

That's the "Cursor inside" advantage.

Start selling today.
Grow with the platform.

Free to start. All features included. Yours to leave whenever you want — most never do.

Have an idea, a question, or a feature you wish existed? Get in touch — we listen.