Skip to content

Research candidate: Cursor #5

Description

@Chinmay-KB

Recommendation

Add a first-class cursor company profile (not a generic IDE fallback).

Candidate

  • Name: Cursor
  • Suggested id: cursor
  • Profile type: company
  • Category: AI coding / developer tools
  • Popularity tier: high
  • Research status: review-ready
  • Meme strength: high

Why it fits ifXBuiltY

Cursor is an unusually legible “vibe coding” archetype: a serious-looking dark code editor with a chatty agent that confidently turns a one-line request into a large diff. The joke writes itself—an omnipresent purple/black AI sidebar, an agent instruction box, a change review, and a slightly alarming “run everything” affordance. It supports durable parody rather than a one-week launch gag: what if a product category had Cursor’s confident agent loop, terse technical labels, and autocomplete-first worldview?

Evidence

Proposed profile direction

  • Tone: focused, deadpan, hyper-competent, mildly ominous; technical confidence without product-marketing cheer.
  • Visual traits: near-black graphite canvas; thin cool-gray dividers; compact monospace code; muted violet/indigo accents; dense three-pane layout; status chips, diffs, terminal output, and a persistent right-side AI panel.
  • UX traits: command palette energy; one primary prompt that expands into a plan; streaming agent steps; files/diffs as proof of work; approval/review gates that are technically optional and emotionally too late.
  • Archetype: ai_coding_workspace — sections: activity/title bar, file explorer, editor/diff, agent conversation, terminal/task status, review controls. Layout: dense desktop IDE with a collapsible agent rail. Content style: short imperative prompts, code-shaped labels, incremental logs, confident progress language.
  • Default vibe tags: vibe-coding, agentic, dark-mode, developer-tool, monospace, diffs, autonomous, purple-accent.
  • Iconic elements: composer-style agent prompt, checklist/streaming task log, changed-files list, diff hunks, terminal drawer, “review changes” moment.
  • Behavioral stereotypes: starts broadly, touches more files than requested, narrates a plan, and presents a complete-looking result before anyone reads the diff.
  • Satirical patterns: the agent converts ordinary life into a repo; “small tweak” becomes a 47-file migration; every decision is framed as a reversible plan immediately followed by execution.

Suggested generation ideas

  1. What if Cursor built a grocery list? A dark three-pane workspace where “buy ingredients for tacos” becomes a task plan, a diff to pantry.json, an agent log, and a conspicuous “Run shopping migration” button.
  2. What if Cursor built a city permit portal? A permit application appears as a pull request with agent-generated zoning changes, terminal warnings, and “Apply all suggested edits.”
  3. What if Cursor built a dating app? The agent proposes a compatibility refactor, generates a profile diff, and marks the relationship status “awaiting review.”

Risks / reasons to reject

  • Duplicate risk: The supplied catalog snapshot does not list Cursor. A repository-wide issue search found only a closed implementation PR mentioning Cursor Cloud, not a catalog candidate or profile proposal; re-check profile data before merge.
  • Too obscure: Low. Cursor is prominent within developer and AI-product culture, though less recognizable to non-technical audiences than Apple or Google.
  • Weak visual identity: Low. The dark IDE, monospace diff, agent composer, and file/sidebar chrome are recognizable and portable to screenshots.
  • Safety/legal risk: Moderate but manageable. Do not use Cursor trademarks/logos or reproduce a screen pixel-for-pixel; use descriptive parody cues and generic code/content.
  • Low confidence: Low-to-moderate on exact current UI details because live product surfaces evolve quickly; anchor the profile in the durable IDE/agent grammar and refresh screenshots before production.

Quality score

{"blockers":[],"checks":[{"detail":"required issue sections","max":12,"name":"template complete","passed":true,"points":12},{"detail":"official source URL","max":14,"name":"official source","passed":true,"points":14},{"detail":"6 URL(s)","max":10,"name":"3+ URLs","passed":true,"points":10},{"detail":"specific visual surface","max":12,"name":"visual evidence","passed":true,"points":12},{"detail":"cultural/parody angle","max":12,"name":"meme rationale","passed":true,"points":12},{"detail":"profile fields","max":12,"name":"profile direction","passed":true,"points":12},{"detail":"what-if pairing","max":10,"name":"generation idea","passed":true,"points":10},{"detail":"duplicate risk discussed","max":8,"name":"duplicate analysis","passed":true,"points":8},{"detail":"risk fields","max":10,"name":"risk analysis","passed":true,"points":10}],"max_score":100,"ok":true,"score":100}

Review ask

Please approve Add if the catalog wants an AI-coding-company archetype distinct from GitHub, VS Code, and OpenAI. On approval, use cursor as the canonical company id and prioritize a generator screen that exposes the agent prompt + diff + execution log in one frame.

Metadata

Metadata

Assignees

No one assigned

    Labels

    automation/company-researchAutomated company/product research candidates from Hermes

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions