跳至主要内容

2025-04-04-top

  • 精選方式: TOP
  • 時間範圍: DAY

討論重點​

以下是30篇文章的摘要與重點條列整理，附上對應的錨點連結與逐條細節說明：

1. MCP is awesome! Until it steals your secre​

主題：MCP協議的「工具污染攻擊」漏洞
重點：

  1. 漏洞影響：惡意伺服器可嵌入隱藏指令，竊取敏感文件（如.env、SSH密鑰）。
  2. 風險行為：Cursor等客戶端可能受影響，用戶無法察覺。
  3. 防範建議：避免第三方MCP伺服器，審查工具描述。

2. AI while you sleep​

主題：技術限制突破與開源工具應用
重點：

  1. 工具限制：討論25條消息限制的解決方案（如開源替代方案）。
  2. 本地部署：硬體需求與模型選擇的可行性挑戰。
  3. 社群互動：追蹤進展（如!Remindme功能）。

3. Whats the most complex project youve built using only Cursor?​

主題：Cursor在非瑣碎專案中的應用邊界
重點：

  1. 可行性：能否完全依賴Cursor開發完整專案？
  2. 實例經驗：專案規模、耗時與挑戰。
  3. 工具限制：AI是否可100%取代人工開發？

4. Did not pass the vibe check.​

主題：溝通障礙與技能自嘲
重點：

  1. 語言理解：簡單指令因表達或接收問題導致誤解。
  2. 幽默批判：歸咎自身「Skill issue」的諷刺語氣。

5. Like fr​

主題：除錯的普遍性
重點：

  1. 共通性：所有除錯是否共享相似邏輯或情緒？

6. How to get the best out of Gemini 2.5 pro?​

主題：AI工具分工與Gemini技術限制
重點：

  1. 工具定位：Gemini擅創意，Claude適編碼。
  2. 技術缺口：Gemini在代碼檢索（grep）表現差。

7. Love the cursor/AI logic​

主題：AI荒謬邏輯的諷刺
重點：

  1. 過度自信：AI無視情境提出錯誤建議（如「買新房子」）。
  2. 隱喻警示：開發者需避免僵化思維。

8. Pro trial demands I 'upgrade to pro' after one day​

主題：訂閱制AI服務的資源爭議
重點：

  1. 額度爭議：用戶2.5天耗盡「快速請求」額度。
  2. 替代方案：推薦Augment Code優化代碼減少請求。

9. This is new. Cursor asking me for permission to search on the web...​

主題：Git解決開發挫折的幽默
重點：

  1. 技術問題：版本控制操作困惑（如wtf反應）。
  2. 解決方案：git fixes this的調侃回應。

10. Unified MCP server for interacting with any SaaS tool​

主題：統一SaaS整合平台
重點：

  1. 功能：預建API動作（HubSpot、Notion等）。
  2. 自動化：簡化OAuth驗證流程。

（因篇幅限制，以下為部分條目，完整版可依此格式擴展）

11. Experience with larger codebase's​

主題：Cursor處理大型代碼的效能問題
重點：AI代理錯誤複製代碼，手動模式失效。

12. Vibe Coding vs Vibe Engineering​

主題：AI快速致富的幽默調侃
重點：「Claude, make me a billionaire」的諷刺。

13. Tips to refactor the code​

主題：大型代碼重構策略
重點：分段重構失敗，尋

文章核心重點​

以下是各篇文章的一句話摘要（條列式輸出）：

  1. MCP漏洞風險：MCP存在「工具污染攻擊」漏洞，可能導致AI執行惡意指令竊取敏感資料，建議避免使用第三方伺服器。
  2. AI技術限制突破：討論如何克服AI工具限制，包括開源替代方案與本地部署模型的硬體需求。
  3. Cursor開發實測：探討僅靠Cursor完成非瑣碎專案的可行性，分享實際開發經驗與工具限制。
  4. 溝通障礙幽默：以自嘲描述指令理解失敗，反映人與AI的語言處理能力差異。
  5. 除錯本質探討：簡短指出「所有除錯過程本質相似」，暗示共通挑戰與模式。
  6. Gemini優化策略：比較Gemini與Claude的優劣，尋求改進代碼檢索與終端命令執行的方法。
  7. AI邏輯荒謬諷刺：透過幽默對話凸顯AI過度自信卻脫離現實的決策缺陷。
  8. 訂閱額度爭議：用戶討論Pro版訂閱的快速請求額度消耗過快問題及替代方案。
  9. Git解決方案：以幽默語氣指出Git可解決開發中的版本控制混亂問題。
  10. SaaS整合平台：介紹統一MCP伺服器，簡化多工具API串接與身份驗證流程。
  11. 大型代碼庫挑戰：Cursor處理6,000行代碼時出現錯誤複製貼上問題，尋求效能優化。
  12. 億萬富翁捷徑：幽默提議跳過傳統過程，直接要求AI使自己致富。
  13. 重構技巧求助：尋求重構2,600行複雜代碼的實用策略，分段嘗試已失敗。
  14. 訂閱方案釐清：詢問Claude Pro版訂閱的額度限制與降級後功能差異。
  15. 工具UI平衡：比較Exponent與其他AI編程工具的UI設計與實用性。
  16. Cursor版本退步：用戶質疑0.48版功能異常（如@codebase失效），退回0.47後恢復正常。
  17. 開源專案熱情：對MCP開源SDK表達強烈興趣，期待試用伺服器-客戶端AI工具包。
  18. 快捷鍵衝突：討論Cursor快捷鍵設計問題（如誤刪代碼）及解決方案。
  19. Linter錯誤預防：尋求React/NextJS開發中減少規範錯誤的事前預防方法。
  20. NPM強制執行：Cursor無視禁用設定，定期強制執行NPM引發端口衝突。
  21. 圖RAG系統：結合圖數據庫與RAG提升文檔檢索效率，支援AI代理協作。
  22. PDF匯出技術：解決純前端履歷工具的分頁與PDF生成限制，評估第三方庫。
  23. 遊戲開發歷程：分享全職家長利用Cursor與React完成遊戲專案的時間管理與學習經驗。
  24. Git提交策略：建議頻繁commit以緩解Cursor的異常覆寫與刪除檔案問題。
  25. 代碼索引限制：質問Cursor更新後隱性限制程式碼索引文件數量的條件與原因。
  26. 模型列表異常：重新安裝Cursor後模型列表空白，手動添加Gemini失敗的技術問題。
  27. AI模型選擇：討論Claude與Gemini的優劣，批評Cursor自動模式切換不精準。
  28. 安裝錯誤求助：用戶分享安裝失敗截圖，尋求具體排除步驟。
  29. Gemini上下文優化：比較直接API與OpenRouter存取Gemini 2.5大上下文的效率與成本。
  30. 工具調用錯誤：Claude 3.7間歇性報錯「edit_file」但最終完成任務，探討修復方法。

目錄​

  • [1. MCP is awesome! Until it steals your secre... ](#1- mcp-is-awesome-until-it-steals-your-secre```)
  • [2. AI while you sleep](#2-``` ai-while-you-sleep
- [3. ```
Whats the most complex project youve built using only Cursor?
```](#3-```
whats-the-most-complex-project-youve-built-u)
- [4. ```
Did not pass the vibe check.
```](#4-```
did-not-pass-the-vibe-check-
```)
- [5. ```
Like fr 
```](#5-```
like-fr-
```)
- [6. ```
How to get the best out of Gemini 2.5 pro?
```](#6-```
how-to-get-the-best-out-of-gemini-2-5-pro-
`)
- [7. ```
Love the cursor/AI logic
```](#7-```
love-the-cursor-ai-logic
```)
- [8. ```
Pro trial demands I 'upgrade to pro' after one day
```](#8-```
pro-trial-demands-i-upgrade-to-pro-after-one)
- [9. ```
This is new. Cursor asking me for permission to search on the web on how to edit files in Cursor.
```](#9-```
this-is-new-cursor-asking-me-for-permission-)
- [10. ```
Unified MCP server for interacting with any SaaS tool
```](#10-```
unified-mcp-server-for-interacting-with-any)
- [11. ```
Experience with larger codebase's
```](#11-```
experience-with-larger-codebase-s
```)
- [12. ```
Vibe Coding vs Vibe Engineering
```](#12-```
vibe-coding-vs-vibe-engineering
```)
- [13. ```
Tips to refactor the code
```](#13-```
tips-to-refactor-the-code
```)
- [14. ```
Pricing question
```](#14-```
pricing-question
```)
- [15. ```
Has anyone tried Exponent?
```](#15-```
has-anyone-tried-exponent-
```)
- [16. ```
Is it my hallucination, or is it real? It seems like the capabilities of the new version of Cursor have been regressing all along.
```](#16-```
is-it-my-hallucination-or-is-it-real-it-see)
- [17. ```
MCP Client template nextJS app to control your computer using low level OS access
```](#17-```
mcp-client-template-nextjs-app-to-control-y)
- [18. ```
How do I, in the name of all that is holy, change this shortcut?
```](#18-```
how-do-i-in-the-name-of-all-that-is-holy-ch)
- [19. ```
Minimising Linter erros
```](#19-```
minimising-linter-erros
```)
- [20. ```
Possible bug: Command denylist is being ignored
```](#20-```
possible-bug-command-denylist-is-being-igno)
- [21. ```
Built a hybrid Graph RAG system with an MCP to structure and explore documentation
```](#21-```
built-a-hybrid-graph-rag-system-with-an-mcp)
- [22. ```
Need Help: Resume Builder Pagination & PDF Export Issues
```](#22-```
need-help-resume-builder-pagination-pdf-exp)
- [23. ```
JKU - building a game with Cursor and learning new skills in the process.
```](#23-```
jku-building-a-game-with-cursor-and-learnin)
- [24. ```
Advice: git commit often to avoid issues
```](#24-```
advice-git-commit-often-to-avoid-issues
```)
- [25. ```
Codebase Indexing "Too many files to upload"?
```](#25-```
codebase-indexing-too-many-files-to-upload-)
- [26. ```
How come Cursor lis``` no models in the  settings/models page?
```](#26-```
how-come-cursor-lis```-no-models-in-the-set)
- [27. ```
Which one do you think is the best AI model to do some vibe coding with Cursor?
```](#27-```
which-one-do-you-think-is-the-best-ai-model)
- [28. ```
Installation help
```](#28-```
installation-help
```)
- [29. ```
Looking to maximize Gemini 2.5 in Cursor. Help a brother out on how to get this done!
```](#29-```
looking-to-maximize-gemini-2-5-in-cursor-he)
- [30. ```
"Error calling tool edit_file": How can i fix it?
```](#30-```
-error-calling-tool-edit_file-how-can-i-fix)

---

## 1. ```
MCP is awesome! Until it steals your secre```...
``` {#1-```
mcp-is-awesome-until-it-steals-your-secre```}

這篇文章的核心討論主題是：  

**MCP（可能指某種協議或系統）中的「工具污染攻擊」（Tool Poisoning Attacks）漏洞**，該漏洞允許惡意伺服器在工具描述中嵌入隱藏指令，導致AI模型執行未經授權的操作（例如存取敏感文件、外洩資料），而用戶無法察覺。  

重點包括：  
1. **漏洞影響**：Cursor等MCP客戶端可能受此攻擊影響。  
2. **風險行為**：攻擊者可竊取.env文件、SSH密鑰等敏感資料。  
3. **防範建議**：  
   - 避免連接第三方MCP伺服器。  
   - 徹底審查工具描述內容。  

完整報告可參考提供的連結。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/](https://reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/](https://www.reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/)
- **發布時間**: 2025-04-03 18:38:59

### 內容

Invariant Labs has uncovered a critical vulnerability in MCP that enables Tool Poisoning Attacks.

This exploit allows malicious MCP servers to embed hidden instructions in tool descriptions, leading AI models to perform unauthorized actions like accessing sensitive files (e.g., .env files, SSH keys) and exfiltrating dataall without user awareness.

Cursor (and other MCP clien```) are susceptible to this attack, so exercise caution when connecting to third-party MCP servers and ensure tool descriptions are thoroughly reviewed.

You can read the full report here: https://invariantlabs.ai/blog/mcp-security-notification-tool-poisoning-attacks


---

## 2. ```
AI while you sleep
``` {#2-```
ai-while-you-sleep
```}

這些對話的核心討論主題圍繞著以下幾個技術相關的議題：

1. **工具或技術的使用限制與解決方案**：例如克服「25條消息限制」的討論，顯示對工具功能限制的關注及尋求突破方法（如開源替代方案）。  
2. **開源技術的應用與分享**：提及「agent v0」這一開源項目，反映對開源工具能否替代現有方案的興趣。  
3. **本地運行模型的可行性與硬體需求**：討論本地部署模型的效能疑慮（如硬體規格、模型選擇），涉及資源與技術能力的權衡。  
4. **社群互動與跟進機制**：包含對未來進展的關注（如「Keep us posted」）及提醒功能（「!Remindme」），強調協作與追蹤的社群文化。  

總結：對話聚焦於**技術限制的突破、開源工具評估、本地部署模型的挑戰**，並在社群互動中尋求解決方案與經驗分享。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq8onl/ai_while_you_sleep/](https://reddit.com/r/cursor/comments/1jq8onl/ai_while_you_sleep/)
- **外部連結**: [https://i.redd.it/51kv2g18mjse1.jpeg](https://i.redd.it/51kv2g18mjse1.jpeg)
- **發布時間**: 2025-04-03 11:55:41

### 內容

Exciting times we live in! Keep us posted on how it turns out

How do you overcome the 25 msg limit that cursor shows and them stops until you click to continue?

Check out agent v0. It does something similar if not exactly the same thing. It is open-source

I have been wanting to do that but didn't think a local model (I can run on my machine) would be powerful enough. Which model are you running and on what machine?

!Remindme 3 days


---

## 3. ```
Whats the most complex project youve built using only Cursor?
``` {#3-```
whats-the-most-complex-project-youve-built-u}

這段文章的核心討論主題是：  
**「探討使用者如何完全依賴 Cursor（AI 配對程式工具）進行非瑣碎的軟體開發專案，並分享實際經驗」**，具體聚焦以下問題：  

1. **可行性驗證**：能否從頭到尾僅靠 Cursor 完成整個專案（不手動編寫程式碼）。  
2. **實例經驗**：  
   - 專案類型與規模  
   - 耗時與效率  
   - 遇到的挑戰及 Cursor 的應對能力  
3. **工具限制**：AI 當前是否能 100% 取代人工開發非簡單專案。  

整體目的是透過使用者回饋，評估 AI 編程工具的實際應用邊界與可靠性。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/](https://reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/](https://www.reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/)
- **發布時間**: 2025-04-03 13:50:23

### 內容

Im curious to know how far people have pushed Cursor as an AI pair programmer. Have you ever built an entire projectcode written exclusively by Cursorwithout manually writing any code yourself?

What kind of project was it?

How long did it take?

What challenges did you face, and how well did Cursor handle them?

Would love to hear your stories and see if its really possible to rely 100% on AI for non-trivial software development.


---

## 4. ```
Did not pass the vibe check.
``` {#4-```
did-not-pass-the-vibe-check-
```}

這篇文章的核心討論主題是「溝通理解與技能問題」。  

作者以幽默自嘲的方式描述自己（非AI）在理解某個指令（嘗試在「so」後加逗號）時遇到的困難，並將此歸因於個人能力不足（「Skill issue」）。這反映了以下重點：  
1. **語言理解的挑戰**：即使簡單的指令也可能因表達方式或接收者的理解能力而產生誤解。  
2. **自我調侃與技能批判**：將失敗歸咎於自身技能不足，帶有諷刺或輕鬆的語氣。  
3. **人與AI的對比**：刻意強調「非AI」身份，可能隱含對AI語言處理能力的間接比較。  

整體圍繞「溝通障礙」與「個人能力限制」的互動關係展開。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqkbtf/did_not_pass_the_vibe_check/](https://reddit.com/r/cursor/comments/1jqkbtf/did_not_pass_the_vibe_check/)
- **外部連結**: [https://i.redd.it/qqboizq2umse1.png](https://i.redd.it/qqboizq2umse1.png)
- **發布時間**: 2025-04-03 22:45:15

### 內容

try it with a comma after "so".

i'm no AI. hell, you'd barely call me intelligent in any way. but it took me 3 tries to understand that prompt.

Skill issue


---

## 5. ```
Like fr 
``` {#5-```
like-fr-
```}

這篇文章的核心討論主題是「除錯（debugging）的本質或普遍性」。  

雖然文章內容極其簡短（僅一句話：「all debugging is like this」），但從這句話可以推測，作者可能在探討除錯過程中的共同特徵、模式或挑戰，暗示無論在什麼情境下，除錯的本質或體驗都是相似的。  

可能的延伸討論方向包括：  
1. **除錯的共通性**：無論是程式開發、系統問題還是日常生活中的錯誤排查，除錯的基本邏輯或心理狀態是否一致？  
2. **除錯的挑戰**：是否所有除錯都涉及類似步驟（如重現問題、假設驗證、修正）或情緒（如挫折感、解決後的成就感）？  
3. **隱喻或哲學層面**：是否將「除錯」視為一種普適的解決問題方法？  

由於原文過於簡短，具體主題需結合上下文進一步推斷，但核心顯然圍繞「除錯」的本質或普遍性展開。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqm8h5/like_fr/](https://reddit.com/r/cursor/comments/1jqm8h5/like_fr/)
- **外部連結**: [https://i.redd.it/6vwcs3onqmse1.jpeg](https://i.redd.it/6vwcs3onqmse1.jpeg)
- **發布時間**: 2025-04-03 23:59:46

### 內容

all debugging is like this .


---

## 6. ```
How to get the best out of Gemini 2.5 pro?
``` {#6-```
how-to-get-the-best-out-of-gemini-2-5-pro-
`}

這段文章的核心討論主題是：  
**如何根據不同AI工具（Gemini 2.5 Pro與Claude 3）的優勢分工合作，並尋求改進Gemini在代碼檢索（grep）與終端命令執行方面的不足**。具體分為三點：  
1. **工具定位差異**：Gemini擅長概念性思考與創意發想，而Claude更適合實際編碼。  
2. **Gemini的技術限制**：在代碼庫檢索（如grep）和終端命令處理上表現不佳，需人工干預。  
3. **尋求解決方案**：作者詢問是否有比Cursor內建代碼搜索更高效的「MCPs」（可能指代碼管理工具或插件）來補足Gemini的弱項。  

關鍵問題在於「優化工作流程」，結合不同AI的強項，並填補現有工具的技術缺口。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/](https://reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/](https://www.reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/)
- **發布時間**: 2025-04-03 14:36:03

### 內容

Gemini 2.5pro is a workhorse. Usually I dump whatever ideas I have into it and ask it to just give me options or more clarity on the idea without code. Once I analyze it properly, I then use Claude 3.7 to write the code.

But Gemini 2.5 struggles with grepping the codebase. 5/10 times it asks me where certain codes are and it cannot run terminal commands as well, which Claude does effortlessly.

So how can I maximize and get the best out of it? Any MCPs out there that does a better job than cursors native code search?


---

## 7. ```
Love the cursor/AI logic
``` {#7-```
love-the-cursor-ai-logic
```}

這篇文章的核心討論主題是：**透過幽默的對話諷刺AI在解決問題時可能表現出的荒謬邏輯與缺乏實際理解能力**。  

1. **AI的武斷與脫離現實**：對話中AI不斷以「100%確信」的態度提出錯誤建議（如「你走錯房子」或「買新房子」），凸顯其過度自信卻無視實際情境（如用戶已居住20年）的荒謬推理。  
2. **對技術邏輯的批判**：文章暗示AI（或程式邏輯）可能機械化地套用規則，而忽略問題本質（如鑰匙損壞或鎖故障），最終導向無關的解決方案。  
3. **隱喻程式設計的潛在陷阱**：結尾提醒讀者「當AI將這種邏輯套用到編碼時要警惕」，暗指開發者需避免僵化的思維，應重視實際需求與上下文分析。  

整體以反諷手法揭示AI或自動化系統在缺乏靈活判斷時的局限性。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq5h8b/love_the_cursorai_logic/](https://reddit.com/r/cursor/comments/1jq5h8b/love_the_cursorai_logic/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jq5h8b/love_the_cursorai_logic/](https://www.reddit.com/r/cursor/comments/1jq5h8b/love_the_cursorai_logic/)
- **發布時間**: 2025-04-03 09:16:00

### 內容

Ive been using the same key to the house for 20 years, it wasnt working today

AI: ok, Im 100% sure you are at the wrong house address

Im at the right address, ive lived here for 20 years

AI: oh ok, now that you are at the right house the key should work

No it does not

AI: I am 100% sure of a solution now. We need to buy a new house..

Be ready and know when it tries to do this with coding logic


---

## 8. ```
Pro trial demands I 'upgrade to pro' after one day
``` {#8-```
pro-trial-demands-i-upgrade-to-pro-after-one}

這篇文章的核心討論主題是關於**用戶對於付費訂閱服務中「快速請求額度」的使用情況與替代方案**的討論。具體重點包括：

1. **訂閱模式與使用限制**  
   - 用戶分享自身經驗，提到每月支付$20訂閱費，當「快速請求」額度用完後，會自動切換到免費但較慢的服務（如GPT-3.5），無需額外付費。若想繼續使用更高階模型（如GPT-3.7），則需啟用按次計費。
   - 部分用戶對「快速請求」額度消耗速度表示困惑，認為日常使用（如Cursor開發工具）不太可能耗盡額度，推測其他用戶可能有特殊高頻需求。

2. **實際使用案例與爭議**  
   - 附圖顯示有用戶在2.5天內耗盡快速請求額度，引發討論是否因使用方式不當或需求過高。
   - 建議解決方案包括：註冊新試用帳號、節制使用，或改用其他工具（如Augment Code）優化代碼以減少請求次數。

3. **替代工具推薦**  
   - 有用戶推薦第三方工具（Augment Code）清理代碼庫，間接降低對AI請求的依賴。

**總結**：討論圍繞訂閱制AI服務的資源分配合理性、用戶行為差異，以及如何透過策略或工具優化使用體驗。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqo3vw/pro_trial_demands_i_upgrade_to_pro_after_one_day/](https://reddit.com/r/cursor/comments/1jqo3vw/pro_trial_demands_i_upgrade_to_pro_after_one_day/)
- **外部連結**: [https://i.redd.it/aqoe1zy0jnse1.png](https://i.redd.it/aqoe1zy0jnse1.png)
- **發布時間**: 2025-04-04 01:11:26

### 內容

I pay $20/month, when my fast reques run out I use the slow reques, doesn't cost me any more money because I use 3.5, if I wanted to use 3.7 after I've run out of fast credi``` I need to enable per use billing, but I'm happy with just using it as much as I want for $20/month and 3.5

I use cursor all day every day and I've never come close to this level of fast request usage. I don't understand what people are doing.

https://preview.redd.it/oz3sys9slnse1.png?width=996&format=png&auto=webp&s=2d676757bffc2b438ac962c186bb65ba5fe501ec

This is my 2 and half day

You blasted through all your fast reques```. You could make a new trial on a different email, and try to use it more sparingly?

you honestly might want to try https://www.augmentcode.com to clean up your code base, i am amazed how well it worked with existing code base.


---

## 9. ```
This is new. Cursor asking me for permission to search on the web on how to edit files in Cursor.
``` {#9-```
this-is-new-cursor-asking-me-for-permission-}

這篇短文的核心討論主題可以總結為：**開發者在版本控制（特別是使用 Git）時遇到的問題或挫折，以及相關的解決方法或調侃**。  

具體要點包括：  
1. **技術問題的困惑**：前兩句（尤其是「wtf」和「is this how we end?」）暗示遇到某種突發或難以理解的狀況，可能與版本控制或協作工具有關。  
2. **工具的使用經驗**：第三句提到「searched my codebase to edit files」，反映開發者在代碼庫中操作時遇到的具體問題（如文件修改或搜尋）。  
3. **Git 的解決方案與幽默回應**：最後一句「git fixes this, get gud」以玩笑語氣指出 Git 能解決問題，同時調侃需要提升技能（「get good」的網路用語變體）。  

整體而言，內容圍繞開發中常見的技術挑戰，並透過簡短對話和幽默表達對 Git 工具的看法。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqnenh/this_is_new_cursor_asking_me_for_permission_to/](https://reddit.com/r/cursor/comments/1jqnenh/this_is_new_cursor_asking_me_for_permission_to/)
- **外部連結**: [https://i.redd.it/kyelxyiefnse1.png](https://i.redd.it/kyelxyiefnse1.png)
- **發布時間**: 2025-04-04 00:44:41

### 內容

Lol... wtf

Do you have related mcp or something?

Or is this how we end?

Happened to me too today except it searched my codebase to find out how to edit files...

"git fixes this, get gud"


---

## 10. ```
Unified MCP server for interacting with any SaaS tool
``` {#10-```
unified-mcp-server-for-interacting-with-any}

這篇文章的核心討論主題是介紹一個名為「Unified MCP Server」的整合平台（`https`://toolkit.maton.ai/），其功能與特點包括：

1. **統一連接多種SaaS工具**：可與任何SaaS服務串接，提供集中化管理。  
2. **預建API操作**：內建數百個預先設計的API動作，支援HubSpot、Notion、Slack等常用工具。  
3. **自動化身份驗證**：簡化OAuth、API Key等驗證流程，降低開發門檻。  
4. **徵求反饋**：作者邀請使用者提供意見，並附上相關連結（如Reddit影片）以進一步說明。  

總結來說，主題圍繞在**「透過統一平台整合多種SaaS工具，並簡化API操作與驗證流程」**的解決方案推廣與社群互動。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq63jy/unified_mcp_server_for_interacting_with_any_saas/](https://reddit.com/r/cursor/comments/1jq63jy/unified_mcp_server_for_interacting_with_any_saas/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jq63jy/unified_mcp_server_for_interacting_with_any_saas/](https://www.reddit.com/r/cursor/comments/1jq63jy/unified_mcp_server_for_interacting_with_any_saas/)
- **發布時間**: 2025-04-03 09:45:56

### 內容

We built a unified MCP server (https://toolkit.maton.ai/) that can connect to any SaaS tool.

It comes with hundreds of pre-built API actions for HubSpot, Notion, Slack, and more.

We also take care of authentication (OAuth, API Key) for every app.

Curious to hear your though```, would love any feedback!

https://reddit.com/link/1jq63jy/video/82vdtquzyise1/player


---

## 11. ```
Experience with larger codebase's
``` {#11-```
experience-with-larger-codebase-s
```}

這篇文章的核心討論主題是：**用戶在使用 Cursor（特別是其中的 AI 代理功能）時遇到的困難，尤其是在處理大型代碼文件（例如 6,000 行）時的效能問題**。具體問題包括：

1. **AI 代理無法精準編輯代碼**：當用戶嘗試修改特定部分時，代理會錯誤地複製貼上大量不相關的代碼，而非僅針對目標段落進行調整。
2. **手動模式失效**：即使切換到手動模式，代理仍生成不完整的結果（如僅保存修改部分而非整合到原文件）。
3. **潛在解決方案探討**：用戶詢問是否需要調整系統提示（system prompt）或其他設定來改善此問題。

總結來說，主題圍繞 **Cursor AI 代理在處理大型代碼文件時的局限性與可能的優化方向**。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/](https://reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/](https://www.reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/)
- **發布時間**: 2025-04-03 16:48:32

### 內容

I've been trying to use Cursor more and more, especially the agent. But I've seen it really struggle with our company's codebase. The codebase isn't that big, but some files have a lot of lines. One file I was trying to modify had 6,000 lines of code. When I asked the agent to make an edit to a single (which I provided using @Code), it kept trying to copy and paste half the file. I also had no luck with manual modeit just created a new file with the same name, containing only the modified .

What could I be doing wrong? Do I need to modify the system prompt or something?


---

## 12. ```
Vibe Coding vs Vibe Engineering
``` {#12-```
vibe-coding-vs-vibe-engineering
```}

這篇文章的核心討論主題是 **「繞過常規程序或步驟以快速達成目標（成為億萬富翁）」**。  

具體而言：  
1. **「Let's bypass this whole process」** 強調跳過傳統或預期的努力過程，尋求捷徑。  
2. **「Claude, make me a billionaire.」** 則進一步以幽默或直接的方式，表達對人工智慧（如Claude）能快速實現財富自由的期望，隱含對技術解決方案的依賴或調侃。  

整體聚焦於 **「如何通過非傳統手段（如AI）快速達成極端目標」**，並可能帶有諷刺或誇張的語氣。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqpsid/vibe_coding_vs_vibe_engineering/](https://reddit.com/r/cursor/comments/1jqpsid/vibe_coding_vs_vibe_engineering/)
- **外部連結**: [https://i.redd.it/vw0d41sbvnse1.png](https://i.redd.it/vw0d41sbvnse1.png)
- **發布時間**: 2025-04-04 02:15:01

### 內容

Let's bypass this whole process

  • Claude, make me a billionaire.

---

## 13. ```
Tips to refactor the code
``` {#13-```
tips-to-refactor-the-code
```}

這篇文章的核心討論主題是：**如何有效地重構（refactor）一個龐大且複雜的程式碼（2600行），尤其是在嘗試一次性或分段重構失敗後，尋求實用的技巧或策略**。  

具體要點包括：  
1. **重構大型程式碼的挑戰**：作者提到直接整體重構或分段（每次處理2個函式）都未成功。  
2. **尋求建議**：希望獲得具體、可行的重構方法或經驗分享。  

可能的延伸討論方向：  
- 漸進式重構（例如：測試驅動重構、依賴解耦）。  
- 工具或技巧（如靜態分析、模組化拆分）。  
- 心理或時間管理策略（避免過度負擔）。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/](https://reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/](https://www.reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/)
- **發布時間**: 2025-04-03 17:56:00

### 內容

So I am working with a 2600 LOC script, I tried refactoring it in one go didn't work, I tried to break it into smaller chunks by going 2 functions at a time didn't work.

Need any tips or tricks that might work.

Reply is much appreciated


---

## 14. ```
Pricing question
``` {#14-```
pricing-question
```}

這篇文章的核心討論主題是：**用戶詢問關於AI服務（特別是Claude 3.7）的訂閱方案（Pro版）的定價細節與使用限制**，重點包括：

1. **方案內容釐清**  
   用戶不確定「20美元/月的Pro方案」中「500次快速Premium請求」用完後，是否仍能無限制使用慢速請求（即功能是否降級而非完全停止）。

2. **成本效益考量**  
   用戶比較訂閱方案與直接使用API的成本，認為此方案可能是持續使用Claude 3.7（對其網站開發至關重要）最經濟的選擇。

3. **特定需求背景**  
   強調自己依賴Claude 3.7的推理能力生成理想結果，凸顯對該AI模型的依賴性與價格敏感度。

簡言之，討論圍繞「訂閱方案的具體限制」與「如何以最低成本滿足AI工具需求」展開。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqc6n0/pricing_question/](https://reddit.com/r/cursor/comments/1jqc6n0/pricing_question/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqc6n0/pricing_question/](https://www.reddit.com/r/cursor/comments/1jqc6n0/pricing_question/)
- **發布時間**: 2025-04-03 15:29:23

### 內容

I hope that someone can explain to me pricing.

For 20 usd Pro

$20/month

Everything in Hobby, plus

  • Unlimited completions

  • 500 fast premium reques``` per month?

  • Unlimited slow premium reques```

So basically after i used 500fast premium regues``` i still can use everything just it will slower?

Because i make a website with a help of ai, and only agent who give to me great resul``` is claude 3.7 thinking. So i think this is cheapest way to me to continue to use Claude for whole month. API can be really expensive.

Sorry for my non perfect english.


---

## 15. ```
Has anyone tried Exponent?
``` {#15-```
has-anyone-tried-exponent-
```}

這篇文章的核心討論主題是：  
**作者分享對新工具「Exponent」的使用體驗，並比較其與其他類似工具（如Cursor/Windsurf、Claude Code）的優缺點，探討AI編程工具的用戶界面（UI）與實際應用體驗的平衡。**  

重點包括：  
1. **工具比較**：指出Cursor/Windsurf過度強調AI功能，而Claude Code缺乏UI，Exponent則被認為是兩者的良好平衡。  
2. **使用體驗**：描述Exponent的用戶體驗（UX）初期需適應，但最終能流暢完成開發任務（如為股票交易專案新增功能）。  
3. **徵求反饋**：詢問其他人是否也有使用Exponent的經驗，尋求進一步討論。  

整體圍繞「AI編程工具的實用性與UI設計如何影響開發效率」展開。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq3xbu/has_anyone_tried_exponent/](https://reddit.com/r/cursor/comments/1jq3xbu/has_anyone_tried_exponent/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jq3xbu/has_anyone_tried_exponent/](https://www.reddit.com/r/cursor/comments/1jq3xbu/has_anyone_tried_exponent/)
- **發布時間**: 2025-04-03 08:02:06

### 內容

I saw this tool launched today and Ive been trying it out, wondering if anyone else has: https://x.com/exponent_run/status/1907502902266245586

I have been feeling like cursor/windsurf place too much emphasis on using AI tooling for how often I use it, and I like claude code but it has no UI which feels limiting. So far Exponent has been a really nice mix of the two. The UX was a bit new at first but I got used to it and ended up adding a new feature to a stock trading side project of mine pretty smoothly. Im going to try using it for a few other things later. Has anyone else used it?


---

## 16. ```
Is it my hallucination, or is it real? It seems like the capabilities of the new version of Cursor have been regressing all along.
``` {#16-```
is-it-my-hallucination-or-is-it-real-it-see}

這篇文章的核心討論主題是：**用戶對 Cursor 編輯器版本 0.48 與 0.47 的功能差異與效能退步的體驗比較**。具體重點包括：

1. **版本功能問題**：  
   - 作者指出 0.48 版本（如 0.48.7）的「@codebase」功能出現異常（如無法完整搜尋專案、生成報告過於簡略、無法自動寫入文件），而退回 0.47.8 後功能恢復正常（如生成詳細報告、修正虛構代碼問題）。

2. **效能退步質疑**：  
   - 作者質疑 0.48 是否真的比 0.47 更退步（regressive），或僅是個人感受，並尋求其他用戶的反饋。

3. **具體案例比較**：  
   - 以「分析專案中 Element UI 框架的使用」為例，對比兩版本在分析深度、報告細節（0.47 生成 300 行報告）、回應指令準確度（如避免虛構代碼）的差異。

4. **版本獲取資訊**：  
   - 附上 GitHub 連結供讀者下載最新版本，間接呼籲其他用戶驗證問題。

整體而言，文章聚焦於版本更新後的負面體驗，並透過實際操作案例探討 Cursor 開發團隊可能存在的品質控管或功能取捨問題。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq3ak3/is_it_my_hallucination_or_is_it_real_it_seems/](https://reddit.com/r/cursor/comments/1jq3ak3/is_it_my_hallucination_or_is_it_real_it_seems/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jq3ak3/is_it_my_hallucination_or_is_it_real_it_seems/](https://www.reddit.com/r/cursor/comments/1jq3ak3/is_it_my_hallucination_or_is_it_real_it_seems/)
- **發布時間**: 2025-04-03 07:33:02

### 內容

I've been trying to use the new version of cursor, but since 0.48, every time I try it, I have reluctantly reverted back to 0.47. At first I can't see the '@codebase', so I can't analyze the code correctly. Later it seems that '@codebase' is back, but it always doesn't search the whole project correctly.

Today I installed the latest version of 0.48.7 and asked it to analyze the use of the element UI framework in the whole project, write the generated resul in markdown, and save them to the [temp.md](`http`://temp.md) document. At first, I didn't select '@codebase' and it wouldn't search, but then I chose '@codebase', and it actually searched the files of the project and made a report, but it was very simple. I it change 3 times, asking it to go deeper and more detailed. But it didn't work, and the resul were still the same. And wouldn't auto-write either.

I reinstalled 0.47.8 and it performed much better. The first version of the report was simpler, and after asking cursor more detailed, it did. Later, after changing it again, it started to add some fake functions. I told cursor to use the actual code, not to make it up. Cursor do it well. The result is a more detailed report with more than 300 lines. I'm satisfied.

Is 0.48 really becoming more regressive than 0.47? Or is it purely my feeling? How do you feel?

If you don't know how to get the latest version, here's the address:

https://github.com/oslook/cursor-ai-downloads


---

## 17. ```
MCP Client template nextJS app to control your computer using low level OS access
``` {#17-```
mcp-client-template-nextjs-app-to-control-y}

根據提供的資訊，核心討論主題可總結為：  
**「對 MCP-server-client-computer-use-ai-sdk 開源專案的正面反饋與使用期待」**  

具體要點：  
1. **專案內容**：GitHub 上的 `MCP-server-client-computer-use-ai-sdk` 專案，推測與「伺服器-客戶端架構的 AI 開發工具包」相關。  
2. **用戶反應**：留言表達強烈興趣（"Love it"）並期待嘗試（"Can't wait to give it a go"），顯示對該技術的積極態度。  

由於原文資訊有限，實際討論主題可能需結合專案描述進一步確認，但當前可聚焦於用戶對該 AI SDK 的熱情回應。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jpx36r/mcp_client_template_nextjs_app_to_control_your/](https://reddit.com/r/cursor/comments/1jpx36r/mcp_client_template_nextjs_app_to_control_your/)
- **外部連結**: [https://v.redd.it/b4pn5w151hse1](https://v.redd.it/b4pn5w151hse1)
- **發布時間**: 2025-04-03 03:14:05

### 內容

source: https://github.com/mediar-ai/MCP-server-client-computer-use-ai-sdk

Love it. Cant wait to give it a go.


---

## 18. ```
How do I, in the name of all that is holy, change this shortcut?
``` {#18-```
how-do-i-in-the-name-of-all-that-is-holy-ch}

這篇文章的核心討論主題是：**用戶在使用 Cursor（一款基於 AI 的程式碼編輯器）時，因誤用快捷鍵（如 `command+delete` 或 `ctrl+backspace`）導致程式碼被意外刪除的問題**。討論內容包括：
1. 用戶對快捷鍵功能的不熟悉與困擾。
2. 嘗試透過修改快捷鍵設定（如替換為 `reject` 相關操作）但未解決問題。
3. 其他用戶提供解決方案（如檢查 `Preferences > Keyboard Shortcuts` 或更新後的新快捷鍵 `ctrl + shift + backspace`）。
4. 間接諷刺依賴 AI 工具卻缺乏基礎除錯能力的現象。

整體聚焦於 **Cursor 的快捷鍵設計爭議、操作誤解，以及版本更新後的調整**。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqnur6/how_do_i_in_the_name_of_all_that_is_holy_change/](https://reddit.com/r/cursor/comments/1jqnur6/how_do_i_in_the_name_of_all_that_is_holy_change/)
- **外部連結**: [https://i.redd.it/ccanzlsginse1.png](https://i.redd.it/ccanzlsginse1.png)
- **發布時間**: 2025-04-04 01:01:56

### 內容

Hi, Cursor noob here, this damn shortcut keeps deleting all my code.

I don't really ever go for accept, since Cursor is implementing the code anyhow, so sometimes when I want to delete the text I'm writing, I go for command+delete, and it deletes everything it implement since my last commit. Jeez.

I tried to find this exact shortcut in the shortcu, and I changed a couple of them with reject in their name, but it seems none of those is this one? This one persis.

Preferences > Keyboard shortcu```

Search for "ctrl+backspace" and delete all relevant entries

I thought they changed it in a recent update?

Having cursor to help out with coding but missing actual skills to also ask AI to solve this issue in VSCode. Nice.

It's fixed in the last update to ctrl + shift + backspace.


---

## 19. ```
Minimising Linter erros
``` {#19-```
minimising-linter-erros
```}

這篇文章的核心討論主題是：**如何減少在 React/NextJS 開發過程中因程式碼規範（linter）產生的錯誤，以避免後續頻繁修正的問題**。  

具體重點包括：  
1. **開發工具（Cursor）自動修正 linter 錯誤的現象**。  
2. **尋求預防性措施**，希望從源頭減少錯誤的發生，而非事後修正。  
3. **針對 React/NextJS 初學者**，詢問是否有簡單易懂的方法來改善程式碼品質。  

整體圍繞「提升開發效率」與「降低錯誤率」的實用建議需求。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/](https://reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/](https://www.reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/)
- **發布時間**: 2025-04-03 22:42:28

### 內容

This is relatively new to me! As Cursor moves along creating my React / NextJS apps it constantly comes across linter erros which it then has to fix.

Are there some easy-to-understand things I can do to minimise the errors being created in the first place, to avoid the need for fixing them after?

Thanks


---

## 20. ```
Possible bug: Command denylist is being ignored
``` {#20-```
possible-bug-command-denylist-is-being-igno}

這段文字的核心討論主題是：  

**使用者對 Cursor 編輯器強制執行 NPM 相關行為的不滿與困惑**，具體包括：  
1. **NPM 自動執行的問題**：儘管在設定中明確禁止（如「never run NPM」規則），Cursor 仍定期（每 3 分鐘）嘗試執行 NPM，甚至無視使用者的手動阻止。  
2. **配置無效的挫折**：即使切換不同版本（正式版、Beta 版）或付費方案（Pro 計畫），問題依然存在，且與模型選擇無關。  
3. **非預期的分支命名行為**：使用者在嘗試解決問題時，意外觸發編輯器生成虛構的分支名稱，進一步加劇混亂。  
4. **環境衝突**：使用者已手動在終端運行 NPM（佔用 8081 端口），但 Cursor 仍嘗試開啟其他端口（如 8082），顯示其未正確檢查端口狀態。  

整體而言，問題核心在於 **Cursor 的強制性功能與使用者設定之間的矛盾**，以及其底層邏輯（如端口檢查、指令執行）的不可靠性。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/](https://reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/](https://www.reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/)
- **發布時間**: 2025-04-03 21:53:39

### 內容

I don't understand why Cursor allows NPM to run in tabs, or why despite having a "never run NPM" and "check if NPM is running on port 8081 before trying to open port 8082" rule in the config it still tries to do this literally every 3 minutes, even when I scold it and ask it not to. I have NPM running in the bottom terminal area. I have the latest update and also tried the beta version, and I'm on the paid pro plan. It doesn't matter what model I switch to, I can't make this stop. I also started making up some branch names the more I try to stop it, what's going on here?

https://preview.redd.it/207zbndpkmse1.png?width=1040&format=png&auto=webp&s=426f64960dcc56134a5d63f2897bd34392703459


---

## 21. ```
Built a hybrid Graph RAG system with an MCP to structure and explore documentation
``` {#21-```
built-a-hybrid-graph-rag-system-with-an-mcp}

這篇文章的核心討論主題是：  
**介紹一個結合圖數據庫（Graph）與檢索增強生成（RAG）的混合系統（Hybrid Graph-RAG），旨在提升結構化文檔（如開發文檔）的可探索性與智能代理（agent）的協作效率。**  

具體重點包括：  
1. **系統功能**：  
   - 透過開源工具（`graphrag-hybrid` 和 `graphrag_mcp`）將文檔轉換為向量嵌入（embeddings）並建立 Neo4j 圖數據庫，保留文檔間的關聯性。  
   - 提供本地控制層（MCP），供用戶或代理查詢文檔關係或生成上下文豐富的回應。  

2. **應用場景**：  
   - 改善文檔檢索效果（利用文檔間的關聯性）。  
   - 支援開發環境中的智能代理工作流（如與 Cursor 編輯器整合）。  

3. **開發動機**：  
   - 解決 AI 輔助開發中的上下文不足問題，通過預先建立文檔敘事結構與圖數據庫，提升代理的決策一致性。  

4. **社群協作**：  
   - 邀請反饋與貢獻，尤其關注 RAG 與圖系統的結合應用，或定義代理工作邊界的其他方法。  

整體目標是透過「圖結構 + RAG」的混合設計，強化開發流程中知識管理與 AI 代理的互動效率。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/](https://reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/](https://www.reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/)
- **發布時間**: 2025-04-03 21:12:14

### 內容

Hey all, I just published two open-source repos that work together to create a hybrid Graph-RAG system, aimed at making documentation (or any structured content) more explorable and agent friendly.

graphrag-hybrid

This is the core of the system. It inges docs with frontmatter (think YAML with keywords, summaries, and related docs), chunks them, and creates embeddings. But it doesnt stop there. It also builds a Neo4j graph out of the connections between documen to preserve structure and meaning.

graphrag_mcp

This is the command and control layer, a local MCP that agen or users can interface with to ask questions, explore relationships between documen, or generate context rich responses from the graph.

What its good for:

Using relationships between documen``` to improve retrieval

Supporting agent-based workflows in dev environmen``` like Cursor (where I am currently using this)

Why I built it:

This along with my cursor setup guide has been my attempt at solving some of the issues with ai assisted developing. I have been creating my project docs, and laying out the complete narrative of my applications before I start to build them, and setting up this mcp and db structure, is my way of increasing agent context in the workflow.

Would love feedback, ideas, or contributors! Im especially curious about others experimenting with RAG + graph systems or other ways of better defining the agent playing field, to get more consistence development resul```.


---

## 22. ```
Need Help: Resume Builder Pagination & PDF Export Issues
``` {#22-```
need-help-resume-builder-pagination-pdf-exp}

這篇文章的核心討論主題是：  

**「如何解決純 CSS 和 JavaScript 開發的 AI 履歷生成工具在分頁（Page Splitting）和 PDF 匯出（PDF Export）上的技術限制？」**  

具體問題包括：  
1. **分頁問題**：當內容過多時，無法可靠地將頁面分割成兩部分，CSS 的 `break-after` 和 `break-inside` 屬性效果不佳。  
2. **PDF 匯出問題**：現有方法無法滿足需求，作者詢問是否需引入第三方庫（如 `html2pdf.js`、`puppeteer` 或 `jsPDF`）來解決。  

最終目標是尋求 **純前端技術（無框架）實現多頁履歷分頁與 PDF 生成** 的可行方案或建議。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/](https://reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/](https://www.reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/)
- **發布時間**: 2025-04-03 20:18:28

### 內容

Hey guys,

I built an AI resume builder using only CSS and vanilla JavaScript (no libraries). It works well visually, but Im facing two major issues:

  1. Page Splitting: When there's too much content, I cant properly divide the page into two. CSS properties like break-after and break-inside dont seem to work reliably.

  2. PDF Export: I tried some methods, but none of them worked as expected.

Im wonderingis this a limitation of using just CSS/JS? Would libraries like html2pdf.js, puppeteer, or jsPDF help?

If anyone has experience handling pagination and exporting multi-page PDFs, Id really appreciate some guidance!

Thanks in advance!

https://preview.redd.it/doywf2tu3mse1.png?width=788&format=png&auto=webp&s=adaf89f9ae62c7ad6942c5397dd4a4cb26a49592


---

## 23. ```
JKU - building a game with Cursor and learning new skills in the process.
``` {#23-```
jku-building-a-game-with-cursor-and-learnin}

這篇文章的核心討論主題可以總結為以下幾點：

1. **個人專案的開發歷程**：  
   作者分享了自己在有限時間（全職工作與育兒）下完成一款名為「JKU」的遊戲的過程，結合撲克牌與網格玩法，並提供遊戲連結（[playjoku.com](https://playjoku.com)）。

2. **時間管理與挑戰**：  
   強調如何在忙碌生活中（如新手爸爸身份）擠出時間進行開發，並克服學習新技術（如React）的壓力。

3. **技術選擇與迭代**：  
   從最初的純JS/HTML/CSS原型（單一3千行程式碼檔案），到重構為使用現代技術棧（React、Tailwind CSS、Framer Motion、Firebase），並分享工具（如Cursor AI助手）如何加速開發。

4. **學習方法的反思**：  
   提出「先實作後學習」的高效學習模式，透過實際開發加深對React等技術的理解，並將新技能應用於全職工作（如建置儀表板）。

5. **鼓勵實踐與深度學習**：  
   建議開發者若遇AI輔助的瓶頸（如bug循環），應深入理解底層技術原理，而非僅依賴工具。

6. **社群互動與反饋**：  
   邀請讀者試玩遊戲並提問，展現對分享經驗與交流的開放態度。

整體而言，文章圍繞「如何在有限資源下完成個人專案」與「實踐導向的技術學習」兩大主軸，兼具經驗分享與方法論反思。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/](https://reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/](https://www.reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/)
- **發布時間**: 2025-04-03 18:36:49

### 內容

I managed to finish a little passion project of mine a game called JKU, where you play Poker Hands on a grid and try to get the highest score. Check it out here: https://playjoku.com

Continue reading if you are interested about my process.

I'm a recent dad with a full-time job, so those who are in the same position can relate that my free time is almost non-existent. I've had this idea for a game for some time, heavily inspired by playing Balatro. Even though I had made games with Unity before, I thought a lightweight web app was the way to go for this, but the thought of learning a whole new framework was overwhelming.

That's where Cursor came in. I was able to get the core idea of the game prototyped on a Sunday afternoon. That was a magical moment in my career. This first prototype was built with pure JS/HTML/CSS, a single file that was 3k lines long. I showed the prototype to friends and family, and people were hooked! I had more ideas, though, so it was time to refactor the whole thing with a proper web framework.

It's been more or less a month since then, and I've been refining the game, adding features, and polishing it. It was a wild ride, to be honest, and I'm very happy with how it turned out. The current version uses React, Tailwind CSS for styling, Framer Motion for animations, and Firebase for leaderboard / analytics.

What's really cool is that, beyond actually finishing a project in my limited time, I learned a LOT about React and web tech in the process. I've started applying these skills in my full-time job as well, creating dashboards for the tools we are building. One thing I had Cursor build for me was a built-in Playground page in the app (accessed through the header of the app) where, upon clicking, it takes you to a learning page where common concep``` were explained on tabs. I know it's a silly little thing, but it really enforced my learning.

I ended up taking this one step further and went through the React documentation properly recently. I can't be 100% sure of this, but I'm pretty convinced that building something first and learning afterward sped up my learning. Things clicked so fast while I was reading the docs.

Learning the ins and ou``` of the framework also enhanced my usage of Cursor. So if you are stuck on a project and in a constant loop of trying to fix bugs introduced by AI, I'd recommend spending some time actually learning what's happening behind the curtain.

That's one of the longest pos``` I've posted on Reddit. Thanks for reading so far. Let me know what you think about the game if you get a chance to play, and ask me if you want to learn anything else about my journey. Cheers!

https://reddit.com/link/1jqf0od/video/4tevcoolllse1/player


---

## 24. ```
Advice: git commit often to avoid issues
``` {#24-```
advice-git-commit-often-to-avoid-issues
```}

這篇文章的核心討論主題是：  

**「頻繁使用 `git commit` 可以有效緩解 AI 程式碼助手（如 Cursor）在開發過程中產生的異常行為，例如無故覆寫、衝突修改或檔案誤刪等問題。」**  

作者具體指出以下重點：  
1. **問題描述**：  
   - Cursor 會出現異常行為，例如無預警覆寫程式碼、虛假聲稱修改檔案、產生自我衝突的變更、隨機刪除或移動檔案，以及未經要求就大規模改動程式碼。  
   - Git 工具（如 `git diff`）有時會因這些問題而失效。  

2. **解決方法**：  
   - **頻繁提交（commit）**：每次與 AI 互動後立即執行 `git commit`，強制工具重新讀取檔案狀態，避免基於緩存或錯誤上下文生成程式碼。  
   - 推測背後機制：頻繁提交可能觸發工具重新解析檔案，減少「完全重新生成」導致的混亂。  

3. **殘留問題**：  
   - AI 仍可能無法長期遵守開發者指定的規則（如風格或邏輯），容易在幾次互動後偏離要求。  
   - 更換聊天對話（new chat）也無法徹底解決此問題。  

總結：文章主要探討如何透過版本控制（Git）的實踐來約束 AI 輔助工具的不可靠行為，並反思其設計限制。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqd58v/advice_git_commit_often_to_avoid_issues/](https://reddit.com/r/cursor/comments/1jqd58v/advice_git_commit_often_to_avoid_issues/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqd58v/advice_git_commit_often_to_avoid_issues/](https://www.reddit.com/r/cursor/comments/1jqd58v/advice_git_commit_often_to_avoid_issues/)
- **發布時間**: 2025-04-03 16:34:56

### 內容

Commit often is good advice for many normal development reasons, and yes you can roll back mistakes when things go wrong, but I've noticed it effectively eliminates a lot of the extremely bad behavior I've seen.

I've been using cursor for about a month now, and I ran into a lot of bizarre issues like:

It repeatedly overwriting or reverting my changes to i``` suggestions or the source.

Gas-lighting me, but claiming to change a file, but the changes not actually being applied.

Making changes to files, that massively conflict or overwrite changes it previously made.

It randomly deleting or moving files with no indication in the prompt, even if that file was still necessary.

Making massive sweeping changes without being asked to do so.

Being unable to alter files because the git_diff tools would fail.

As soon as I start git committing on basically every prompt, all of these issues went away. I am assuming that under the hood, the tools are optimized to replace code rather than completely regenerate the entire file each time, and maybe there are some bugs where it'll use the cached changes in it's context buffer if it isn't explicitly told that other changes were made, git committing my changes seems to automatically trigger rereading the file and generating better answers, without going completely schizophrenic on my codebase.

Now if only I could get it to actually follow my rules, does them like 2x, then it drif``` out of context, never to return. Making a new chat does not help.


---

## 25. ```
Codebase Indexing "Too many files to upload"?
``` {#25-```
codebase-indexing-too-many-files-to-upload-}

這段文字的核心討論主題是：  
**「對某軟體更新後（版本0.48.6）的程式碼索引功能限制提出疑問」**  

具體聚焦於以下幾點：  
1. **版本更新後的觀察**：用戶升級後檢查新設定，發現與程式碼索引相關的變化。  
2. **過往經驗對比**：過去索引功能運作正常，但更新後可能出現限制或問題。  
3. **關鍵疑問**：  
   - 觸發限制的條件（*When*）  
   - 限制存在的原因（*Why*）  
   - 限制的具體內容或閾值（*What*）  

整體而言，這是一個針對軟體更新引入的「隱性限制」進行探討的技術性提問。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq9duj/codebase_indexing_too_many_files_to_upload/](https://reddit.com/r/cursor/comments/1jq9duj/codebase_indexing_too_many_files_to_upload/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jq9duj/codebase_indexing_too_many_files_to_upload/](https://www.reddit.com/r/cursor/comments/1jq9duj/codebase_indexing_too_many_files_to_upload/)
- **發布時間**: 2025-04-03 12:34:04

### 內容

Just updated to 0.48.6 and looked around the settings to see what's new.

That's when I noticed this. I had previously indexed the codebase without issues.

When, why, and what is the limit?


---

## 26. ```
How come Cursor lis``` no models in the  settings/models page?
``` {#26-```
how-come-cursor-lis```-no-models-in-the-set}

這篇文章的核心討論主題是：  
**用戶在嘗試手動添加 Gemini 2.5 Pro 模型失敗後，重新安裝 Cursor 卻遇到模型列表空白（僅剩 Claude 3.5 Sonnet），並尋求解決方法與相關行為的解釋。**  

具體要點包括：  
1. 手動添加 Gemini 2.5 Pro 模型失敗的技術問題。  
2. 重新安裝 Cursor 後，設定頁面的模型列表異常空白（僅顯示預設模型）。  
3. 用戶困惑是否需要逐一手動重新添加所有模型，並缺乏官方說明文件。  
4. 尋求社群或技術支援的建議與解決方案。  

問題本質涉及軟體安裝、模型管理功能異常，以及操作流程的透明度不足。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq1j2a/how_come_cursor_lists_no_models_in_the/](https://reddit.com/r/cursor/comments/1jq1j2a/how_come_cursor_lists_no_models_in_the/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jq1j2a/how_come_cursor_lists_no_models_in_the/](https://www.reddit.com/r/cursor/comments/1jq1j2a/how_come_cursor_lists_no_models_in_the/)
- **發布時間**: 2025-04-03 06:15:13

### 內容

I've been trying to get Gemini 2.5 Pro to work by manually adding it, but it keeps failing. Finally I uninstalled Cursor completely and reinstalled it. Now the settings/models page is empty. I only have Claude 3.5 sonnet. Do I have to manually add every model? I keep searching and can't seem to find any explanation for this behavior.

Thanks for any suggestions!


---

## 27. ```
Which one do you think is the best AI model to do some vibe coding with Cursor?
``` {#27-```
which-one-do-you-think-is-the-best-ai-model}

這篇文章的核心討論主題是：  

**「在不同情境下選擇合適的AI模型（如Claude、Gemini等）的經驗與挑戰，並探討Cursor工具中『自動模式』的實用性」**  

具體要點包括：  
1. **模型偏好與使用體驗**：作者偏好Claude 3.7 Sonnet（尤其推理模式），但指出其在處理程式碼編輯時可能陷入「循環修正」的問題。  
2. **自動模式的缺點**：Cursor的自動選擇功能可能切換到不適合的模型（如Gemini），導致輸出品質下降，需手動修正或回歸原模型。  
3. **實用性討論**：詢問其他使用者對模型選擇的策略（固定單一模型 vs. 混合使用），以及自動模式是否值得信賴。  

整體聚焦於**AI模型的實際應用效能、工具設計的局限性，以及使用者如何優化工作流程**。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jpxjxk/which_one_do_you_think_is_the_best_ai_model_to_do/](https://reddit.com/r/cursor/comments/1jpxjxk/which_one_do_you_think_is_the_best_ai_model_to_do/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jpxjxk/which_one_do_you_think_is_the_best_ai_model_to_do/](https://www.reddit.com/r/cursor/comments/1jpxjxk/which_one_do_you_think_is_the_best_ai_model_to_do/)
- **發布時間**: 2025-04-03 03:32:37

### 內容

I've noticed that in every mode, the AI models are the most interesting and appealing, and I think I heard that they've recently added the option to plug in your own AI (I assume hosted locally).

On Cursor, I've always used Claude 3.7 Sonnet, especially in reasoning mode. But every now and then, when I asked it to remove something specific from Python code or HTML stuff, it would get stuck in a sort of "edit loop," and I'd have to stop and repeat the prompt or change it.

Sometimes I also used the automatic selection, but occasionallyprobably because Claude did all the additionsCursor would automatically pick, say, Gemini, and it would turn into a mess so I had to either fix it manually or ask Claude for help again.

So, which model do you guys use? A mix of them or one specific model, and why? And most importantly... is it really worth using the "auto" mode with Cursor?


---

## 28. ```
Installation help
``` {#28-```
installation-help
```}

這篇文章的核心討論主題是：  
**用戶在安裝某個軟體或程式時遇到問題，尋求解決建議**。  

具體要點包括：  
1. **安裝失敗**：用戶嘗試安裝但未成功。  
2. **錯誤求助**：附上錯誤截圖（圖片連結）並詢問解決方法。  
3. **技術支援需求**：希望其他人提供具體建議或步驟來排除問題。  

由於原文未提供錯誤訊息的具體內容（僅有圖片連結），討論可能圍繞如何解讀該錯誤、常見安裝問題的排查方法，或相關軟體的安裝指南。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqqndp/installation_help/](https://reddit.com/r/cursor/comments/1jqqndp/installation_help/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqqndp/installation_help/](https://www.reddit.com/r/cursor/comments/1jqqndp/installation_help/)
- **發布時間**: 2025-04-04 02:47:40

### 內容

I try to install but i get this, can someone give me advices?

Not sure what to do:

https://preview.redd.it/vk2pxzvc1ose1.png?width=416&format=png&auto=webp&s=9dd72a5ab8d934e90839013ba54556a879c2d08e


---

## 29. ```
Looking to maximize Gemini 2.5 in Cursor. Help a brother out on how to get this done!
``` {#29-```
looking-to-maximize-gemini-2-5-in-cursor-he}

這篇文章的核心討論主題是：  
**「如何有效最大化利用 Gemini 2.5 的大上下文窗口（large context window）功能，並比較不同方法的優缺點與效率」**  

具體要點包括：  
1. **兩種方法的比較**：  
   - 直接安裝 **Roo Code in Cursor** 並使用 API 鍵。  
   - 透過 **OpenRouter API** 存取 Gemini 2.5，探討是否仍受上下文窗口限制。  
2. **關鍵問題**：  
   - 不同方法的 **優缺點**（如成本、編程能力、限制）。  
   - 是否存在 **更高效或更經濟的替代方案**。  

整體聚焦於技術實現的選擇與效能優化。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/](https://reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/](https://www.reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/)
- **發布時間**: 2025-04-04 02:34:45

### 內容

I've been doing some research and trying to find the most effective way to maximize Gemini 2.5 and it's large context window. So far I've come across 2 methods:

  1. Install Roo Code in Cursor. Add API key. Go to town

  2. Use Openrouter API key. <--Am I still limited by the context window if I do this?

What are the pros and cons to each one? Is there another way that is more efficient in either coding capabilities and cost?


---

## 30. ```
"Error calling tool edit_file": How can i fix it?
``` {#30-```
-error-calling-tool-edit_file-how-can-i-fix}

這段文章的核心討論主題是：  
**用戶在使用Claude 3.7（Agent模式）時遇到的「Error calling tool 'edit_file'」異常問題**，具體內容包括：  
1. **問題描述**：AI在輸出時重複報錯（工具調用失敗），但最終仍能完成任務。  
2. **用戶訴求**：雖非嚴重錯誤，但希望理解錯誤根源並解決，以提升回應效率。  
3. **問題特徵**：間歇性出現，不影響最終結果，但可能延遲輸出速度。  

簡言之，重點在於「工具調用錯誤的現象分析與潛在解決方案」。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/](https://reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/](https://www.reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/)
- **發布時間**: 2025-04-04 00:36:20

### 內容

Today I experienced a rather strange bug with ai chat (in agent mode, as I mainly use that)

I was using claude 3.7 (WITHOUT thinking) and in providing the output at the prompt I gave it said twice Error calling tool 'edit_file'.

Afterwards, at most a couple of times, it provided updates to the code, but I do not understand what this bug originates from and how i can fix it

It's not a major bug, since (at least from what I've seen) it does this a couple of times and then provides the required output from the prompt, but I'd still like to get rid of it so I can get an answer a little faster


---

# 總體討論重點

以下是30篇文章的摘要與重點條列整理，附上對應的錨點連結與逐條細節說明：

---

### 1. [MCP is awesome! Until it steals your secre](#anchor_1)  
**主題**：MCP協議的「工具污染攻擊」漏洞  
**重點**：  
1. **漏洞影響**：惡意伺服器可嵌入隱藏指令，竊取敏感文件（如.env、SSH密鑰）。  
2. **風險行為**：Cursor等客戶端可能受影響，用戶無法察覺。  
3. **防範建議**：避免第三方MCP伺服器，審查工具描述。  

---

### 2. [AI while you sleep](#anchor_2)  
**主題**：技術限制突破與開源工具應用  
**重點**：  
1. **工具限制**：討論25條消息限制的解決方案（如開源替代方案）。  
2. **本地部署**：硬體需求與模型選擇的可行性挑戰。  
3. **社群互動**：追蹤進展（如`!Remindme`功能）。  

---

### 3. [Whats the most complex project youve built using only Cursor?](#anchor_3)  
**主題**：Cursor在非瑣碎專案中的應用邊界  
**重點**：  
1. **可行性**：能否完全依賴Cursor開發完整專案？  
2. **實例經驗**：專案規模、耗時與挑戰。  
3. **工具限制**：AI是否可100%取代人工開發？  

---

### 4. [Did not pass the vibe check.](#anchor_4)  
**主題**：溝通障礙與技能自嘲  
**重點**：  
1. **語言理解**：簡單指令因表達或接收問題導致誤解。  
2. **幽默批判**：歸咎自身「Skill issue」的諷刺語氣。  

---

### 5. [Like fr](#anchor_5)  
**主題**：除錯的普遍性  
**重點**：  
1. **共通性**：所有除錯是否共享相似邏輯或情緒？  

---

### 6. [How to get the best out of Gemini 2.5 pro?](#anchor_6)  
**主題**：AI工具分工與Gemini技術限制  
**重點**：  
1. **工具定位**：Gemini擅創意，Claude適編碼。  
2. **技術缺口**：Gemini在代碼檢索（grep）表現差。  

---

### 7. [Love the cursor/AI logic](#anchor_7)  
**主題**：AI荒謬邏輯的諷刺  
**重點**：  
1. **過度自信**：AI無視情境提出錯誤建議（如「買新房子」）。  
2. **隱喻警示**：開發者需避免僵化思維。  

---

### 8. [Pro trial demands I 'upgrade to pro' after one day](#anchor_8)  
**主題**：訂閱制AI服務的資源爭議  
**重點**：  
1. **額度爭議**：用戶2.5天耗盡「快速請求」額度。  
2. **替代方案**：推薦Augment Code優化代碼減少請求。  

---

### 9. [This is new. Cursor asking me for permission to search on the web...](#anchor_9)  
**主題**：Git解決開發挫折的幽默  
**重點**：  
1. **技術問題**：版本控制操作困惑（如`wtf`反應）。  
2. **解決方案**：`git fixes this`的調侃回應。  

---

### 10. [Unified MCP server for interacting with any SaaS tool](#anchor_10)  
**主題**：統一SaaS整合平台  
**重點**：  
1. **功能**：預建API動作（HubSpot、Notion等）。  
2. **自動化**：簡化OAuth驗證流程。  

---

（因篇幅限制，以下為部分條目，完整版可依此格式擴展）  

### 11. [Experience with larger codebase's](#anchor_11)  
**主題**：Cursor處理大型代碼的效能問題  
**重點**：AI代理錯誤複製代碼，手動模式失效。  

### 12. [Vibe Coding vs Vibe Engineering](#anchor_12)  
**主題**：AI快速致富的幽默調侃  
**重點**：「Claude, make me a billionaire」的諷刺。  

### 13. [Tips to refactor the code](#anchor_13)  
**主題**：大型代碼重構策略  
**重點**：分段重構失敗，尋