cursor

Bilingual

Cancelling Cursor
2 months ago
- Cursor is based on outdated VSCode builds (7–10 months old), causing extension installation issues.
- The default 'Agent' view keeps reappearing after restart, and related settings are moved/renamed with each update.
- Reported bugs (e.g., misaligned checkbox in settings) remain unfixed for months, with minimal response from support.
- Community feedback, such as a Reddit post with 177 upvotes, was deleted by moderators, indicating poor responsiveness.
- Support is inadequate: forum threads go unanswered, and the support mailbox sends AI-generated generic replies.
- Cursor is shifting focus from a code-first IDE to an enterprise agent platform, diverging from user expectations.
- The user cancelled their subscription and returned to VSCode, citing the above issues and a desire for a proper IDE.
Cursor removed cost information from the usage page and CSV export
2 months ago
- Cursor replaced dollar amounts with token amounts on the usage page for non-enterprise plans, frustrating users who tracked spending.
- Enterprise plans still show dollar amounts; individual and self-serve Teams plans show tokens, with on-demand costs only in the Cost column.
- Users can find dollar totals on Dashboard > Spending and per-user on-demand on Dashboard > Members, but per-model breakdown is unavailable.
- The change is intentional: dollar values were removed from usage endpoints and CSV exports to avoid confusion about included vs. billed usage.
- Users criticize the lack of transparency, asking for a toggle to switch between tokens and dollars for better budget tracking.
- The API no longer returns per-request cost fields for self-serve plans, even historically, breaking independent cost tracking tools.
- Users request restoration of dollar-based usage analysis or improved visualization to distinguish included usage from actual charges.
How I created an Ethereum Proof-of-Stake demo
2 months ago
- The author created an Ethereum Proof-of-Stake demo using two LLMs: ChatGPT as a project manager and Cursor as a coder.
- ChatGPT handled UI design, technical requirements, and high-level planning, while Cursor implemented the code using its Composer mode.
- Key advice includes always committing changes, debugging code with Cursor and design with ChatGPT, and using a localStorage mockup file to track data structures.
- The author emphasizes the importance of clear, certain instructions to avoid confusion and bugs, and suggests re-sending source information to maintain context.
- Mistakes included not planning text storage format early, not creating reusable templates for multiple pages, and overcomplicating charts when simple SVGs worked better.

cursor

Cancelling Cursor

Cursor removed cost information from the usage page and CSV export

How I created an Ethereum Proof-of-Stake demo