跳至主要内容

2025-04-02-rising

  • 精選方式: RISING

討論重點​

以下是25篇文章的摘要重點整理，以條列方式呈現，並附上對應的文章錨點連結：

1. This is the first time in almost a year that Claude is not the best model​

  • 性能比較：Gemini 2.5在處理上下文、可靠性等方面超越Claude。
  • 態度轉變：作者從厭惡Google轉為肯定Gemini 2.5，自嘲「投向黑暗面」。
  • 動態競爭：AI領域變化快速，未來Claude可能反超。
  • 實用導向：強調實際使用需求而非品牌忠誠度。

2. What the hell happened?​

  • 問題回報流程：需分類環境（免費/付費）、提供詳細資訊（提示詞與輸出）。
  • 服務中斷：多位用戶反映無法使用Claude，官方未更新狀態頁面。
  • 反饋機制：透過thumbs down按鈕提供負評，官方監控此數據。

3. I accidentally built a brain fog tracker with Claude and it actually helped me feel smarter​

  • 健康解決方案：結合Claude開發「腦霧儀表板」，量化追蹤症狀成因。
  • AI協作價值：Claude主動分析數據、提出建議，發現潛在模式（如補充劑關聯）。
  • 開源分享：考慮公開專案，建議「記錄+AI分析」方法。

4. Please be candid; did I just pay $220 for a year of this screensaver, but only at Anthropic's website?​

（內容未提供，需補充細節）

5. [Claude Pro limi](#5-claude-pro-limi)​

  • 限制加劇：付費用戶短期內觸發訊息限制（約5條）。
  • 體驗下降：認為工具「幾乎無法使用」。
  • 求證現象：詢問其他用戶是否遇到相同問題。

6. Claude's context has been nerfed?​

  • 異常表現：Sonnet模型無預警遺失對話上下文。
  • 技術推測：懷疑Anthropic動態摘要歷史訊息，降低實際處理量。
  • 商業倫理質疑：可能誤導用戶付費購買「完整上下文」功能。

7. Message Limit Reached very often now in paid version, hardly usable​

  • 付費限制問題：頻繁觸發訊息限制，與免費版差異不大。
  • 版本影響：Claude 2.7 Sonnet桌面版非思考模式下問題明顯。
  • 時間變化：近期限制突然嚴格化。
  • 免費高效工具：媲美付費產品的程式碼分析能力。
  • 多平台支援：可搭配Claude Desktop或Gemini運行。
  • 技術創新：使用語言伺服器分析大型程式碼庫。
  • 開源專案：GitHub上的serena專案。

9. Dropped a new tutorial for Agentic pattern + AI SDK​

  • 新影片發布：介紹「Agentic patterns」並參考Anthropic論文。
  • 觀眾反饋：邀請對影片內容與表現方式的建議。

10. [Are rate limi significantly lower now?](#10-are-rate-limi-significantly-lower-now)​

  • 限制變化：訊息額度從40-50條降至20-25條。
  • 不滿情緒：表達對無預警調整的困惑。

11. [Hitting limi without getting responses](#11-hitting-limi-without-getting-responses)​

  • 技術故障：Claude無回應卻消耗使用額度。
  • 付費落差：質疑付費後服務品質下降。

12. [What computer use​

文章核心重點​

以下是各篇文章的一句話摘要條列：

  1. Gemini 2.5性能超越Claude：作者實測認為Gemini 2.5在上下文處理和可靠性上優於Claude，雖曾偏好Claude但仍客觀承認當前技術差距。
  2. Claude問題回報指南：提供提交Claude投訴的標準流程，強調環境分類、細節提供及負評反饋的重要性。
  3. AI協作追蹤腦霧症狀：作者透過與Claude合作開發個人化儀表板，成功量化分析腦霧成因並改善認知狀態。
  4. Claude Pro付費體驗質疑（標題不完整）：用戶質疑付費後功能限制是否合理，暗示對服務價值的失望。
  5. Claude Pro使用限制加劇：付費用戶抱怨訊息限制突然收緊，僅發送5條訊息即觸發限制，影響實用性。
  6. Claude上下文能力縮水疑慮：用戶推測Sonnet模型可能暗中壓縮歷史對話內容，實際處理token數低於官方宣傳。
  7. 付費版訊息限制問題：付費用戶遭遇與免費版相似的頻繁限制，批評桌面版Claude 2.7 Sonnet效能下降。
  8. 免費高效能程式碼分析工具：介紹開源工具Serena，支援MCP伺服器與Gemini，效能媲美付費方案且易於整合。
  9. Agentic模式教學影片發布：作者發布第三支影片探討Agentic patterns，邀請觀眾回饋以優化內容。
  10. Claude訊息額度異常減少：用戶發現可發送訊息數從40-50驟降至20-25，質疑系統調整未公告。
  11. 無回應消耗使用額度：Claude頻繁無回應卻仍扣減額度，用戶質疑付費換來服務降級。
  12. 電腦專案經驗探討：詢問讀者建構電腦相關專案的挑戰與現有技術缺口，聚焦實踐反思。
  13. 使用LLM是否算技能：辯論AI工具操作經驗是否該列為職場技能，反映對新能力認定的不確定性。
  14. Claude無預警功能移除：用戶不滿舊對話UUID存取功能消失，批評Anthropic未公告影響工作流程。
  15. 關閉搜尋功能測試：作者實測關閉Claude網路搜尋功能，探討是否提升生成品質。
  16. 尋求Claude寫作替代方案：尋找能避免對話限制且擅長創意寫作修訂的AI工具。
  17. MCP協議潛力討論：介紹Model Context Protocol如何標準化工具交互，簡化多工具協作開發。
  18. VS Code的API連線問題：WSL環境下Claude API不穩導致額外成本，用戶尋求解方。
  19. Claude 3.7版本負評：用戶批評新版對話能力退化，限制增多，劣於舊版及競爭產品。
  20. Claude效能區域性差異：推測部分用戶體驗問題可能與區域網路或服務穩定性相關。
  21. AI功能誤解澄清：強調Claude無記憶能力，僅被動回應當下上下文，需避免措辭誤導。
  22. MCP本質釐清需求：呼籲解釋MCP核心價值與應用場景，而非僅討論實作細節。
  23. Claude記憶力嚴重缺陷：批評AI連30秒前的對話都無法記住，基本功能失敗。
  24. 高成本除錯困境：開發者花費50美元仍未能解決問題，凸顯資源有限下的技術門檻。
  25. LLM內容優化策略：提出12步驟清單提升網站在AI生成答案中的引用率，如結構化列表與標記優化。

（註：部分標題不完整或內容缺失的摘要已基於現有資訊推論，並以粗體標示關鍵詞）

目錄​

1. This is the first time in almost a year that Claude is not the best model​

這篇文章的核心討論主題是：作者對Gemini 2.5的強烈肯定，認為其當前性能超越Claude及其他競爭模型，並坦承自己雖長期偏好Claude，但基於實際體驗不得不承認Gemini 2.5的優勢。

具體要點包括：

  1. 性能比較：Gemini 2.5在處理上下文、可靠性等方面表現優異，甚至超越作者過去推崇的Claude。
  2. 態度轉變：作者原本厭惡Google及早期Gemini模型，但現因技術進步改變立場，自嘲「投向黑暗面」。
  3. 動態競爭：承認AI領域變化快速，未來Claude可能反超，但現階段Gemini 2.5明顯領先。
  4. 實用導向：強調實際使用需求（如多樣化用例）是評估模型的關鍵，而非品牌忠誠度。

整體聚焦於AI模型的實測體驗與競爭力消長，並反映用戶在技術迭代中的理性選擇。

內容​

Gemini 2.5 is simply better. I hate Google, I hate previous Geminis, and they have cried wolf so many times. I have been posting exclusively on the Claude subreddit because I've found all other models to be so much worse. However I have many use cases, and there aren't any that Claude is currently better than Gemini 2.5 for. Even in Gemini Advance (the weaker version of the model versus AIStudio) it's incredibly powerful at handling context and incredibly reliable. I feel like I'm going to the dark side but it simply has to be said. This field changes super fast and I'm sure Claude will be back on top at some point, but this is the first time where I just think that is so clearly not the case.

討論​

評論 1:

you forgot that the best thing about is that it is free. i have been saying this for a long time, most AI startups will be eaten by big tech for lunch because big tech can race to the bottom but anthropic cant just provide their flagship models for free

評論 2:

The creative writing is extremely good, by far the best one I tried for that purpose.

評論 3:

I wish these kinds of pos``` explained their use case. I can't tell you how many times I've had to read how ChatGPT is better than Claude....only to learn they are writing stories...which I don't do.

I have been working on an economic dashboard right now and this post couldn't be further from the truth.

I say this to say that it would be more useful to get specifics about what you're doing with another AI that makes it better. That's going to provide more value than a post that tries to generalize that one is better than another.

評論 4:

Google invented Transformer and Bert and it's researchers pioneered many great technologies. Strange that you are surprised they took a lead (might not be for long).

評論 5:

Same for me. This is the first time I also don't shit on google's product (actually second, I liked Ultra)

2. What the hell happened?​

這篇文章的核心討論主題是：如何有效地提交關於Claude AI的投訴或問題回報，並提供具體的指導原則。重點包括：

  1. 正確分類問題環境（免費/付費網頁版或API），以利釐清情境
  2. 提供詳細資訊（如輸入提示詞和輸出結果）幫助問題診斷
  3. 認知相同條件可能產生不同結果（因Anthropic的測試機制）
  4. 主動給予負評反饋（透過thumbs down按鈕），因官方會監控此數據

次要討論是關於服務中斷的集體回報現象，多位用戶反映無法正常使用Claude，且官方狀態頁面未更新相關資訊。整體而言，這是以「問題回報的標準化流程」為主軸的技術社群討論。

內容​

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.

  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.

  3. be aware that even with the same environment and inpu```, others might have very different outcomes due to Anthropic's testing regime.

  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. Yeah same problem. same here. No update from their status page too

https://status.anthropic.com/ Yup same for me. Yeah not working here either.

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inpu```, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

Yeah same problem.

評論 3:

same here. No update from their status page too

https://status.anthropic.com/

評論 4:

Yup same for me.

評論 5:

Yeah not working here either.

3. I accidentally built a brain fog tracker with Claudeand it actually helped me feel smarter​

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

  1. 個人健康困擾與解決方案：
    作者長期受「腦霧」（brain fog）問題困擾，嘗試過各種傳統方法（如調整睡眠、飲食、補充劑等）但效果有限，最終透過與AI工具（Claude）合作，開發出一套個人化的追蹤系統。

  2. AI協作開發的獨特價值：
    Claude不僅協助作者快速建構一個「腦霧儀表板」（Node + MongoDB應用程式），還能分析數據、提出改進建議，並發現作者未察覺的潛在模式（如特定補充劑與腦霧的關聯）。與傳統AI工具（如ChatGPT）相比，Claude更像一個「主動合作的夥伴」，能提問、重構代碼，而非僅提供制式回應。

  3. 數據追蹤與自我洞察：
    透過記錄睡眠、飲食、補充劑攝取和主觀腦霧評分，作者發現量化追蹤結合AI分析能幫助釐清症狀成因，最終改善認知狀態（如「感覺更清晰」）。

  4. 開源分享與實用建議：
    作者考慮將此專案開源，並建議受類似問題困擾的人嘗試「記錄症狀＋AI分析」的方法，強調即使簡單的日誌整理也可能帶來意外幫助。

本質上，文章探討如何結合個人數據追蹤與AI協作，解決傳統方法難以應對的健康問題，並展現AI在「個性化問題解決」中的潛力。

內容​

Ive had brain fog for a couple of years now. The kind where you open a tab, forget why, stare at it for a minute, then open 4 more tabs and forget all of them too. Some days I felt like my brain was running on 1997 dial-up.

I tried all the usual stuffcutting caffeine, sleep hygiene, meditation, supplemen```, drinking more water than a cactusbut nothing really stuck. Everything helped a little, but nothing moved the needle.

Until I got bored and said to Claude:

>

Totally expecting a dumb response. Instead, Claude replied with something like:

>

Wait... what?

So yeah, I built a brain fog dashboard.

With Claudes help in Cursor, I ended up throwing together a Node + MongoDB app to track:

  • Sleep (I just typed it in manually, but Claude helped me add Apple Health support later)

  • Supplemen```

  • Meals

  • Self-rated brain fog score (110)

  • Notes for the day (Felt spaced out after lunch, Weirdly focused at 9pm???)

It also shows some simple graphsfog over time, sleep correlation, stuff like that.

Heres the kicker: Claude didnt just write the backend and frontend (it did), it also helped me analyse the data.

After about 10 days of logging, it said:

>

Which is wild, because I didnt notice that pattern at all. And it checks out.

Why this felt different

Ive used ChatGPT before. Its fine. But Claude felt more like a curious lab partner. It would ask me questions like:

  • Do you want to break that into two separate features?

  • Should I refactor this to make it more modular?

It wasnt just spitting out boilerplate. It collaborated.

Real talk though

  • I dont think this app is genius or anything. Its scrappy.

  • Its 90% Claude code, 10% me debugging and renaming files because I broke something.

  • I wasnt trying to go viral or build a startup. I just wanted to feel like I had a brain again.

But somehow, tracking + AI + some consistency actually made a difference.

I feel sharper lately. More on it. And I can look at the dashboard and see why.

Thinking of open-sourcing it

If a few people are interested, Ill clean up the repo and post it. Its not pretty, but it works.

Also, if youre struggling with weird mental fatigue and feel like a functional goldfishlogging + AI might be worth a shot.

Even just journaling symptoms and feeding it to Claude has been surprisingly helpful.

TLDR:

I was bored, asked Claude to help me build a brain fog tracker. It actually worked. It helped me find patterns in sleep/supplemen``` that made me feel clearer. I might open source it if people want.

討論​

評論 1:

After about 10 days of logging, it said:

>

Which is wild, because I didnt notice that pattern at all. And it checks out.

lol. it's brain fog all the way down...

評論 2:

Haha post is so obviously written by Claude. Not having a go at you, it's just interesting how many obvious footprin``` LLMs have when they write in a certain way.

評論 3:

. Is this an April fools joke? I felt dumb reading your post because you clearly forgot to finish writing or pasting text lol. I get brain fog sometimes and was interested to hear what patterns Claude found.

評論 4:

You forgot to include what the conclusion from analyzing your data was. The part where it got interesting. Nice bait

評論 5:

You may want to get checked for sleep apnea. It can cause brain fog and it's very common.

4. Please be candid; did I just pay $220 for a year of this screensaver, but only at Anthropic's website?​

由於我無法直接訪問外部連結或圖片內容（包括Reddit預覽圖），因此無法分析該文章的具體內容。不過，若您能提供以下資訊，我可以協助總結核心主題：

  1. 文章標題或關鍵字
  2. 文字內容的簡要描述（例如：討論科技趨勢、社會議題、個人經驗等）
  3. 圖片中的文字或主要視覺元素（若為圖文內容）

例如，若該圖片是關於「人工智慧對就業市場的影響」，核心主題可能是「AI自動化取代人類工作的爭議與應對策略」。請提供更多細節，我會為您精準歸納！

內容​

連結： [https://preview.redd.it/wkdat48b6bse1.jpg?width=1920&format=pjpg&auto=webp&s=bbbc185a4528ad74e6ec4369f451c4a458e674c6

](https://preview.redd.it/wkdat48b6bse1.jpg?width=1920&format=pjpg&auto=webp&s=bbbc185a4528ad74e6ec4369f451c4a458e674c6

)

討論​

評論 1:

Starting to get kind of ridiculous how often its been down lately

5. Claude Pro limi \{#5-claude-pro-limi}​

這篇文章的核心討論主題是：用戶對近期（過去兩天內）聊天次數限制突然變得嚴格的不滿與困惑。

具體要點包括：

  1. 限制加劇的現象：用戶發現近期（短時間內）被限制的速度明顯加快，僅發送約5條訊息就觸發限制。
  2. 使用體驗受影響：認為當前限制已嚴重影響工具實用性（"almost unusable"）。
  3. 尋求共鳴：透過提問（"Anyone else?"）確認其他用戶是否遇到相同情況，暗示可能是系統調整或異常問題。

整體聚焦於平台限制政策的變化對用戶體驗的衝擊，並帶有抱怨與求證的語氣。

內容​

Anyone else getting limited much quicker all of a sudden the last 2 days?

It's almost become unusable I get maybe 5 messages before I hit the limit.

討論​

評論 1:

I've noticed that it seems tighter, but not 5 messages tight. Still, compared to a week ago, I have definitely noticed a change.

評論 2:

Since this topic is back on the radar, you have several options:

Glama (I am the founder) is the closest substitute that will give you Claude-like experience. However, you can use OpenRouter with apps like Typindmind.

評論 3:

Same feeling here, Pro user for several months.

評論 4:

Yes!!! But the time to continue the conversation is more short also after limit

評論 5:

yes 5 files not large few messages lasted 1 hr n out

6. Claude's context has been nerfed?​

这篇文章的核心討論主題是對Anthropic公司的AI模型「Sonnet」在處理長對話時可能採用的「上下文壓縮」或「摘要快取」方法的質疑和推測。作者根據自身經驗，指出Sonnet在對話中突然遺失部分程式碼上下文（儘管未達到官方宣稱的200k token限制），並推測這可能是因為模型在後台將過往訊息替換為摘要版本，而非完整保留原始內容。

作者提出一個可能的運作機制（10步驟假設），認為Anthropic可能透過「摘要替換」來節省運算成本，導致模型在長對話中實際處理的上下文遠少於宣傳的規模，進而影響回應品質。這種做法被隱喻為一種「商業欺騙」（scam），因為用戶付費購買的是「完整上下文」功能，但實際獲得的可能是經過壓縮的版本。

總結來說，文章的核心爭議在於：

  1. 模型表現異常：Sonnet無預警遺失近期對話細節，與官方宣稱的長上下文能力不符。
  2. 技術推測：懷疑Anthropic透過「動態摘要」壓縮歷史訊息，變相降低實際處理的token數量。
  3. 商業倫理質疑：此舉可能誤導消費者，並以低成本方案包裝成高階功能販售。

作者的論點混合了實證觀察（自身遭遇的上下文丟失）與陰謀論式推測（摘要替換機制），反映對AI公司透明度的不信任。

內容​

Like every day, I was doing some coding, with 3.7 and things were going swellingly and then suddenly, a chunk of code, that was roughly 50 locs long 2 message prior, was (almost) completely gone from Sonnet's context. The message from Sonnet was there, it referred to the like before, but despite ~10 edi to prompt it in different ways, it just couldn't re-produce the nor make correct adjustmen to the . Aside from knowing the name and parameters, it seemed to be clueless.

The conversation is well below the 200k token limit, at around 40k tokens, which makes me wonder how it's even possible? If the model got quantized to shit, it wouldn't just completely lose context. It would give worse responses, but 2 messages back would be yielding better recollection than the initial message (which is not the case). Or alternatively the quality of responses would degrade to a repeating mess, but the "quality" felt exactly the same as prior to it. It just "forgot" the details.

So I'm wondering if what is happening is that they're using a sort of alternative prompt caching method (at least) for the chat client where the prior messages are collapsed into high quality summaries of previous assistant and user messages? Meaning, they're basically selling 200k context, but in reality it's 15k of summaries and you hit your limit @ 20k which in Anthropic math would be 200k* (*simulated tokens which are definitely worth exactly as much as real ones)?

Obviously this is just a tummy feel, but the above thing did happen and the only way for it to happen (as far as I can imagine) is either due to novel model degradation or the above very believable scam.

I reckon it would work something like this,

  1. Message comes in

  2. Generate a very high quality summary from the message (I'm sure they would've tested this to death)

  3. Store the summary with the hash of the message

  4. Generate completion to the original message

  5. Generate summary from completion

  6. Store the summary of the completion with the hash of the message

  7. New completion request arrives with the full message array

  8. Check the hashes of the messages and replace them with the summarized versions

  9. Return a more shitty completion.

  10. Save a trillion dollaroos on long conversations since every completion on long conversations is in reality now 90% shorter while selling a product that's been nerfed to death.

I doubt it would start from the first message, but there is some point where it becomes more economical to run 1 extra summarization on every message to get to perform completions on shorter conversations.

討論​

評論 1:

Yeah... Claude's been doing this to me; Deepseek V3 will accept the promp``` and extra bloat context I shove sometimes; but nothing is beating Gemini's 1 Million Context window rn...

評論 2:

This happens to me daily, most often with MCP tool use, at some point where there is too much content it just breaks and the whole message disappears. I shared this as a bug via their feedback page but nothing has changed since.

評論 3:

I'm experiencing similar context limitations, but in a different way! Before Claude 3.7 Sonnet was released, I (as a free user) could easily ask for title recommendations for my 2000-2500 word English articles. Claude would read through the entire text and provide thoughtful title suggestions based on the full content.

But now? It seems completely nerfed. I can only get Claude to properly handle articles up to about 1500 words max. Anything longer and the system won't even me send the message at all. I get an error saying: "Your message will exceed the length limit for this chat. Try attaching fewer or smaller files or starting a new conversation."

評論 4:

Yes -- there are 'holes' in the context window. I've seen this with Claude and with some GPT-4 varian``` as well. I've also observed it while playing around with smaller local models on my own GPU, where the max context is smaller and it kicks in much sooner for some models. Sometimes by posting another message or two you can shift the 'hole' somewhere else, sometimes. Usually you'll need to start over with a new session

I do think this is less 'something they did on purpose' and more 'attention heads have weird blind-spo``` with certain content and nobody can quite untangle what and why'

It is very frustrating when it happens

7. Message Limit Reached very often now in paid version, hardly usable​

这篇文章的核心討論主題是：用戶對Claude AI服務近期頻繁出現「Message Limit Reached」（達到訊息限制）的抱怨，質疑付費方案與免費版本的使用限制變得相似，導致體驗下降（特別是在Claude 2.7 Sonnet桌面版非思考模式下），並尋求問題原因與解決方案。

關鍵點包括：

  1. 使用限制問題：付費用戶遭遇與免費版相似的訊息頻率限制，影響正常使用
  2. 版本表現：具體提及Claude 2.7 Sonnet在桌面應用程式非思考模式下的效能問題
  3. 時間變化：用戶觀察到近期（"from yesterday or so"）限制突然變得更加嚴格
  4. 使用者情緒：直接表達「Claude seems hardly usable now」的挫折感

本質上是對服務品質變化的投訴與原因探詢。

內容​

From yesterday or so I am getting Message Limit Reached quite often, definitely more often than before.

My paid plan usage seems to be similar to free version usage limi```.

What happened? Claude seems hardly usable now.

Claude 2.7 Sonnet, non thinking mode, desktop app

討論​

評論 1:

Vibe coders building garbage todo apps in cursor are using all the GPUs sorry

評論 2:

Agreed. They drastically lowered the conversation limi. I ran out very very quickly yesterday. Its annoying how the limi change daily based on availability.

評論 3:

Complain with your wallet, I did. Be sure to leave the reason why you decided to leave.

評論 4:

apart of that the code quality seems to be much worse. Something happened on their side.

評論 5:

I'm constantly getting locked out for 3-4 hours at a time, and it happens once every blue moon that I get any kind of warning about how much I've used.. it's a bit much..

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

介紹一個免費且功能強大的程式碼分析工具（Agent），其特點包括：

  1. 媲美付費工具：性能與 Windsurf 的 Cascade 或 Cursor 的 Agent 相當甚至更好，但完全免費。
  2. 多平台支援：
    • 可作為 MCP 伺服器 運行，與 Claude Desktop 免費搭配使用。
    • 也能在 Gemini 上運行（需 Google Cloud API 金鑰，新用戶可獲 $300 贈金）。
  3. 技術創新：
    • 使用 語言伺服器（language server） 而非傳統 RAG 技術來分析程式碼，即使處理大型程式碼庫也能高效理解。
  4. 開源與易用性：
    • 以 GPL 授權 釋出，程式碼公開於 GitHub（serena 專案）。
    • 強調安裝與運行的簡便性。

總結：作者推廣一款開源、免費的高效能程式碼分析工具，強調其技術優勢與實用性，並提供多種使用情境的解決方案。

內容​

We've been working like hell on this one: a fully capable Agent, as good or better that Windsurf's Cascade or Cursor's agent - but can be used for free.

It can run as an MCP server, so you can use it for free with Claude Desktop, and it can still fully understand a code base, even a very large one. We did this by using a language server instead of RAG to analyze code.

Can also run it on Gemini, but you'll need an API key for that. With a new google cloud account you'll get 300$ as a gift that you can use on API credi```.

Check it out, super easy to run, GPL license:

https://github.com/oraios/serena Edited

討論​

評論 1:

ELI5, how is this different than Cline or Roo?

9. Dropped a new tutorial for Agentic pattern + AI SDK​

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

  1. 介紹新影片內容：作者發布了一支關於「Agentic patterns」（能動性模式）的新影片，並提到內容參考了Anthropic的研究論文。
  2. 尋求觀眾反饋：作者表示這是他的第三支影片，希望觀眾提供意見以改進未來的創作，包括對影片內容、表現方式等的建議。
  3. 互動邀請：附上影片連結，鼓勵觀眾觀看後分享想法。

總結來說，重點在於「推廣新影片」與「請求觀眾回饋」，並以「Agentic patterns」為核心主題。

內容​

Hey guys, I just dropped a new video covering Agentic patterns. I'll be covering all the Agentic patterns that are commonly used using the Anthropic paper.

Would really love your though``` on what you think about this video and whether I can improve. This is only my third video, and I will get better but could really use some feedback.

https://youtu.be/KE8jb6adxUQ

討論​

無討論內容

10. Are rate limi significantly lower now? \{#10-are-rate-limi-significantly-lower-now}​

The core discussion topic of the provided text is about the limited message capacity or usage limits in a messaging system or platform. The user notes that they typically expect to send 40-50 messages before hitting a limit, but recently encountered a restriction after only 20-25 messages, expressing surprise or frustration at the reduced allowance.

Key points:

  1. Unexpected reduction in message limits (from 40-50 to 20-25).
  2. Comparison of past vs. current usage thresholds.
  3. Potential issues with system performance, account restrictions, or changes in policy.

The focus is on the inconsistency or unexplained change in message capacity.

內容​

Ran out twice in like 20-25 messages. Usually can do 40-50

討論​

評論 1:

Yes - noticed this also. Spending more time on Gemini.

評論 2:

Yes. The past day or so it's been locking people down far faster than usual. Lo of pos about it in the past day.

11. Hitting limi without getting responses \{#11-hitting-limi-without-getting-responses}​

根據提供的內容，文章的核心討論主題是：

用戶在使用Claude AI時遇到的技術問題（如無回應、需多次嘗試才能獲得輸出），以及因此導致的使用額度被異常消耗的困擾。

具體要點包括：

  1. 頻繁錯誤：Claude時常無回應，需反覆嘗試才能獲得輸出。
  2. 資源消耗問題：這些故障導致用戶在「幾乎未實際使用」的情況下觸發使用額度限制。
  3. 付費體驗落差：用戶質疑付費後服務品質反而下降（「付費換來性能降級」）。
  4. 尋求解決方案：不確定是否為普遍現象，並希望找到處理方法。

由於提供的連結無效且原文有缺漏，以上分析基於可辨識的文本內容。

內容​

Errors

This has happened quite a few times, and it is causing me to hit usage limi with barely any use. Claude will simply not respond and requires a few tries before it outpu any response.

Not sure if anyone else is encountering this issue or how to handle this but it really does feel like I just paid for degraded performance.

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inpu```, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

I second this, my entire day was wasted with these errors as well.

評論 3:

thing is broken today

評論 4:

I second this

12. What computer use project did you build?​

这篇文章的核心討論主題是關於「電腦使用」的個人探索與研究，並聚焦於以下幾個問題：

  1. 個人專案經驗：詢問讀者曾建構過哪些與電腦使用相關的專案？
  2. 挑戰與困難：探討這些專案的難點是什麼？例如技術障礙、設計問題或資源限制等。
  3. 現有不足：分析當前相關領域或專案中還缺少哪些元素或改進空間？

整體而言，文章旨在透過經驗分享與反思，探討電腦使用相關專案的實踐過程、挑戰與未來發展方向。

內容​

Doing a bit of exploration / research on computer use

Curious what computer use project did you build? Was it hard, what was hard? What's missing?

討論​

無討論內容

13. Do you think using LLMs is a skill?​

這篇文章的核心討論主題是：「是否應將『使用AI工具（如提示詞工程/prompt engineering）』視為一種值得培養或列入履歷的技能」。

作者提出以下關鍵觀點：

  1. 質疑其作為技能的價值：雖然長期使用AI工具，但認為這難以被歸類為需要發展的「真實技能」，甚至不願將其列入履歷。
  2. 承認經驗的實際作用：觀察到新手常犯錯誤，而經驗能幫助避免這些陷阱，暗示使用AI工具仍有一定學習曲線。
  3. 工具與技能的界線爭議：糾結於「熟練使用工具」是否等同於具備某種技能等級，反映對AI時代新能力認定的不確定性。

整體而言，討論聚焦於「AI工具使用經驗」在職場技能中的定位與認可度，並探討其是否超越單純的工具操作層次。

內容​

I have been using them since they became commercially available, but it's hard for me to think of these as a real skill to develop. I would never even think of putting them/prompt engineer as a skill on a resume/cv. However, I do see many people fall victim to certain pitfalls that are remedied with experience.

How do you all view these? Like anything you gain experience with use, but I am hard-pressed to categorize usage as a tool with a skill level.

討論​

評論 1:

Is using AI a skill? Sure. Like being able to quickly and efficiently navigate and use the internet is a skill. Back in the late 90s or early 2000s the majority of people could not surf the information superhighway yet, and those that could did very well for themselves. Eventually everyone catches up tho but it takes a generation. The kids growing up with LLMs and other generative ai may be able to accomplish things we could only dream of since we are used to doing things slow and manual.

評論 2:

using AI well is a skill like knowing how to google well was before google died. tech skills are ubiquitous among your fellow class but they are not as obvious to others.

評論 3:

Oh its a skill lol. Prompting can go deep. People over at r/DataAnnotation could attest to that

評論 4:

Critical thinking is a skill.

評論 5:

Yes, for now it's definitely a skill.

We're far from "Make me an X" and the AI magically ge``` what you need with a few questions.

You need to write promp``` in certain ways so it can deliver, how to break the infinite hallucinations loops, etc.

14. Claude Suddenly Cant Summarize Previous Cha by UUID? \{#14-claude-suddenly-cant-summarize-previous-cha-}​

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

用戶對Claude突然無法存取過往對話記錄（導致關鍵功能失效）的不滿與困擾，並進一步批評Anthropic（Claude開發公司）在未事先公告的情況下隨意移除功能，影響用戶既定的工作流程與效率。

具體重點包括：

  1. 功能失效：原本Claude可透過UUID（對話網址中的編號）總結過往對話，但近期無預警變成無法存取舊對話，導致用戶無法延續原本的專案管理方法。
  2. 用戶工作流程受挫：作者依賴此功能整理專案決策與進度，現在被迫頻繁開新對話以避免字數限制，反而增加管理時間與混亂。
  3. 對Anthropic的不滿：
    • 公司未事先通知功能變更，讓用戶自行適應。
    • 作者認為Claude起初的回應（要求用戶先總結對話）像在「推卸責任」，甚至產生無關的摘要，形同「技術性gaslighting」（誤導用戶）。
  4. 後續影響：作者需重新調整工作模式，但對失去高效AI輔助的專案管理感到失望。

整體而言，文章反映用戶對AI工具「不可預期的功能變動」的挫折感，以及對透明溝通的需求。

內容​

When I started working on my project, I asked Claude how best to use Claude to stay organized and it helped me develop a project documentation plan. Core to this effort was Claude summarizing our cha``` in a specific way. When I asked Claude how to maintain that effort if I were to I run into the chat length limit before promoting a given chat for a summary, it told me to reference the UUID (the number after chat/ in the url) and the next Asst would be able to summarize the chat using that reference and my chat summary prompt. This has been working great for the last 5 weeks.

However, starting this weekend, when I ask Claude to do this, it asked me to first summarize what the chat was about. Me : Huh? Thats your job

When I gave it a five word summary (i.e. fixing ongoing form element componen), it spit out a random summary that had nothing to do with what any of my cha had been about. Me : WTF is this?

So I told Claude that I had no idea what it was referring to; and why did it generate randomness. And Claude apologized then told me its not able to access any of my past cha``` so it couldnt help me with this task. Me : Since when?!?

Claude: I can understand youre frustrated and disappointed Me :

Im a month to month subscriber, and for the most part I appreciate how helpful Claude has been for a variety of tasks, but Im just flummoxed as to how Anthropic continues to clawback features at random and without announcement and expec users to just roll with it. Lacking this feature, now Im constantly starting new cha to do very discrete tasks so I can avoid running into the context length/chat limit, but its making it more difficult to maintain a cogent summary of decisions and changes made in a work session, at least doubling the time Im spending on project management.

Cry me a river, I know. Im just bummed because I thought Id figured out the perfect AI-driven project management workflow, and now Ive got to fill the void by stepping up my own project management skills if I ever want to get my project completed. Plus, I hate when tech tries to gaslight me.

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inpu```, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

Could you ask Claude to do a summary of your post? Soooooo many words

15. I think leaving search ON makes it way dumber.​

這段文字的核心討論主題是：測試關閉網路搜尋功能對Claude AI表現的影響。

具體要點包括：

  1. 實驗動機：作者聽聞「開啟網路搜尋可能降低Claude的表現」，因此嘗試關閉該功能進行測試。
  2. 行動與驗證：作者主動關閉網路搜尋，並計劃後續觀察Claude的表現差異（「Will update」暗示將回報結果）。
  3. 潛在爭議：探討網路搜尋功能是否真會干擾AI的原始生成能力，反映使用者對AI工具效能優化的關注。

總結：這是一個關於「Claude功能設定（網路搜尋開/關）與其表現關聯性」的簡短實測記錄。

內容​

Im going to try turning off the web search. I heard someone say it makes Claude perform way worse when you leave it on. Will update.

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inpu```, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

The massive wave of complain when they introduced Web Search sugges you may be right.

I mean people literally always complain about how Claude/ChatGPT/anything "seems dumber lately", and usually it means absolutely nothing. But when you suddenly see a 10x spike, something probably did happen.

There's actually decently founded technical basis for it. For most models, performance drops significantly at higher token coun, and it doesn't take a whole lot. The Search feature adds 8K + tokens. EIGHT THOUSAND. Artifac, another 8K. With everything on, you're looking at 20K+ tokens baseline in every request before you've said a single word, and most of it will have nothing to do with what you're about to ask.

評論 3:

Well? What's your findings?

16. Similar but better options?​

該文章的核心討論主題是：尋找與Claude AI在智能上相當、尤其擅長協助審閱/修改創意寫作的替代AI工具，同時避免對話長度和訊息數量的限制。

具體要點包括：

  1. 比較AI的智能水平：探討是否有其他AI能達到Claude的語言理解與創作輔助能力。
  2. 功能需求：強調對「創意寫作修訂」的專項需求，而非通用型AI。
  3. 使用體驗痛點：批評現有工具（如Claude）的對話限制（如長度、訊息次數），並尋求更自由的互動模式。
  4. 替代方案探索：可能指向其他未受限制的AI模型（如GPT-4、Gemini等），或討論開源/本地部署選項。

隱含議題可能涉及對AI服務商業模式（如付牆或限免策略）的不滿，以及對「真正無障礙創作輔助工具」的期待。

內容​

Is there another AI that is as intelligent as Claude, especially when it comes to help reviewing/revising creative writing, without the increasingly annoying limi``` on conversation lengths and messages?

討論​

評論 1:

Gemini pro 2.5. You can try it one month free as well.

17. MCP, excited for the future​

这篇文章的核心討論主題是 Model Context Protocol (MCP)，並圍繞以下幾個重點展開：

  1. MCP 的定位與功能

    • MCP 並非「自主代理框架」，而是一種標準化協議，用於統一描述工具（如 API、外部系統）的輸入、輸出及功能，並透過共享格式讓模型與工具互動。
    • 它簡化了工具層的管理，使開發者無需為每個工具互動硬編碼，尤其適合多工具協作的場景（如 Agent 系統）。

  2. 釐清常見誤解

    • MCP 不會賦予模型決策、規劃或推理能力（這些仍需開發者自行處理），而是提供「基礎設施」來規範工具交互，減少混亂。
    • 雖然常被與「自主代理」議題一起討論，但它的核心價值在於標準化工具整合，而非實現自主性。

  3. 實際應用與潛力

    • 文章強調 MCP 的實用性，例如易於與現有框架（如 LangChain）整合，並提到多家公司已開始採用。
    • 作者建議開發者嘗試（附上相關連結），但也提醒需注意安全性，且技術仍在發展中。

總結：MCP 是提升 LLM 與工具交互效率的基礎協議，重點在「標準化工具描述與溝通」，而非取代開發者處理複雜邏輯的角色。

內容​

Ive been messing with MCP lately. The Model Context Protocol. If youve been anywhere near the AI/dev world recently (youtube exploded with mcp videos lately), youve probably seen it hyped as the future of how models will use tools and work with external systems. Sometimes it ge``` bundled in with agent stuff, like its the thing thats going to make LLMs autonomous. Thats not quite right, but its also not totally wrong.

MCP isnt an agent framework. It doesnt make decisions or plan or think ahead. What it does do is give you a consistent way to describe tools and other systems, like orchestrators or agen, interact with those tools through a shared format. You define what your tool does, what inpu it expec```, and what comes back. Then you run an MCP server that exposes that in a standard way.

So no, models dont use MCP out of the box. You still have to do the orchestration, the prompting, the context handling. But once you have that, MCP helps clean up the mess. It makes your tool layer way easier to manage and makes it more realistic for agen``` to work across tools without you hardcoding every interaction.

Its not magic. Its infrastructure. But its solid infrastructure. If youre building serious agentic systems or toolchains, MCP is probably worth your time. Just dont expect it to fix the hard par``` like reasoning or autonomy, thats still on you.

Anyways , if you haven't tried it out yet go ahead and do so. It's pretty easy to set up with Cursor and is a cool way to augment some of the current LLM capabilities. I have seen some pretty cool MCP servers out there so far and am excited to see where the tech goes as more companies adopt it.

Check some out here (I don't own any of these) (also be careful running and importing random code lol):

https://mcp.so/

https://glama.ai/

https://www.pulsemcp.com/servers

https://mcpservers.org/

https://github.com/langchain-ai/langchain-mcp-adapters

^

This library provides a lightweight wrapper that makes Model Context Protocol (MCP) tools compatible with LangChain and LangGraph.

討論​

評論 1:

Founder of Glama. How can I improve how we present information about MCPs today?

18. Claude Code API Error: Connection error.​

这篇文章的核心討論主題是：
用戶在使用VS Code的WSL（Windows Subsystem for Linux）時，遇到間歇性API錯誤問題，導致需要反覆手動請求繼續操作（如"please continue"），且每次失敗請求仍被扣除Anthropic服務的信用額度（如10次請求花費$0.11），尋求解決方案。

具體要點包括：

  1. 技術問題：WSL環境下的VS Code出現不穩定的API錯誤（時好時壞）。
  2. 經濟影響：即使請求失敗，Anthropic仍扣除信用額度，造成額外成本。
  3. 求助動機：用戶希望釐清問題原因並找到解決方法。

附圖可能顯示相關錯誤畫面，但未提供具體內容，推測為API錯誤提示或扣費記錄。

內容​

Is anybody else having this issue? It just started happening 2 days ago. I am using WSL in VS Code. How can I resolve this? It will sometimes work, but sometimes not. I have to constantly ask it to continue, and even though I am getting an API Error it is deducting from my Athropic credit balance. 10 of these "please continue" reques``` cost me $0.11.

https://preview.redd.it/h16qscraease1.png?width=334&format=png&auto=webp&s=02c351e3f5ff15c0dfec8734b4f4bf4d8abea8d0

討論​

無討論內容

19. Claude unusable in 2025?​

這篇文章的核心討論主題是：用戶對ClaudeAI最新3.7版本更新後表現的不滿，具體批評其對話能力下降、限制過多（尤其在AI相關話題上），並與舊版本及競爭對手（如o1）進行負面對比，質疑開發方的調整方向。

內容​

I've been using ClaudeAI since the latest 3.7 update and it's not that it's just not the same, it's not even close to what it was before. It was my favorite before, but now it's worse than o1, with too many rules and restrictions of what it can talk about, such that I can't even maintain a normal conversation about AI! What is going on here?

討論​

評論 1:

The only beef I have with 3.7 is I ask Claude for a simple Fibonacci , and it goes full Silicon Valley and writes a whole Java backend, spins up a React frontend, and deploys it to the cloud. I only just wanted 5 lines of code.

評論 2:

I noticed this too. Good sonnet 3.5 is gone or nowhere to be seen. Most of the output done by 3.7 and 3.5 now are comparable to haiku or any chatgp.

Ive been using IDEs with sonnet 3.5 as well and it definitely feels like haiku output. Every claude instance feels the same in every IDE.

Weeks ago i could pretty much one shot a basic app with multiple screens. Nothing fancy. But now 3.5 cant even fix a basic layout in a single screen. It would make few mistakes, now it deletes and replaces code in every prompt.

The only one ive found feels kinda the same, is augment for vscode. It can pretty much do the same as old 3.5, but weaker.

評論 3:

Paying customer here. I made a few promp``` this morning. Suddenly, I'm blocked out until 10:00 pm.

Like W. T. F.

評論 4:

It was unusable today. I wasted hours trying to work through a basic code question.

評論 5:

Used Claude extensively. Tried Gemini 2.5 pro yesterday. Claude better figure his shit out, like right NOW.

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

用戶對Claude（AI模型）在API和聊天界面上的性能表現存在分歧，並探討可能的區域性網絡或服務問題。

作者分享自身在美國德州使用API的流暢體驗（歸因於良好的網路環境），但注意到其他用戶透過不同管道反映使用問題，因此建議找出可能的「區域性因素」並提出解決方案。

關鍵要點：

  1. 性能體驗差異：部分用戶（如作者）無明顯問題，但許多用戶抱怨Claude的表現。
  2. 可能原因：網路環境（如區域性基礎設施）或服務穩定性問題。
  3. 行動呼籲：希望協作定位問題根源，以有效反饋給開發團隊改善。

語氣帶有同理心（試圖幫助解決爭議），並凸顯用戶體驗的不一致性。

內容​

Ive seen a lot of complain``` regarding Claudes performance both via API and Chat interface, and I sincerely dont think its across the board. Honestly, I have had zero issues (okay, maybe I have to resubmit an API call a second time every now and then, but its rare), but Im also in one of the largest cities in the USA. Ive got gigabit internet through fiber at work and home.

Im in TX, USA with zero issues when using the API.

I havent tested the chat interface, but Ive been reading pain poin``` from both avenues

Anyway, if we can locate the regional issue (if one exis), maybe we can make some noise in the correct way? I dunno. Just trying to help troubleshoot the shitorm Claude has become for many of you.

討論​

無討論內容

21. Bad vibes?​

核心討論主題：​

  1. AI 助理（Claude）的功能澄清：

    • 強調AI不會「撰寫」或「刪除」程式碼，僅根據每次對話的即時上下文提供建議。
    • 澄清AI無記憶功能，無法存取過往對話中「曾提供的」程式碼。

  2. 使用者誤解的來源：

    • 使用者誤以為AI能持續維護程式碼版本（如誤解「備份」是AI主動刪改的結果）。
    • AI解釋其「參考備份檔案」的行為僅是基於使用者提供的上下文，而非自主決策。

  3. 透明化溝通的重要性：

    • AI承認需更明確說明自身角色（如避免使用「我們來實作」等可能引發誤會的措辭）。
    • 提議在修正理解後繼續協助，以確保協作順暢。

關鍵結論：​

對話聚焦於AI輔助工具的局限性（無記憶、被動回應）與人機協作中的溝通清晰度，旨在減少使用者對AI能力的誤解，提升合作效率。

內容​

From earlier today as I was getting more and more frustrated by rework. Using Augment Code...

Me: I really have to ask why you need to keep going back to the backups to get working code. You do understand that you wrote that code earlier? If so, why did you later delete it?

>I am Claude, an AI assistant, and I need to clarify something important: I don't actually write or delete any code - I provide suggestions based on the context I'm given in each conversation. I don't have persistent memory between conversations or access to code I "previously wrote."

>When I look at files marked as "backups" in the provided context, I use them as reference for working implementations. This is why I sometimes refer back to them rather than suggesting entirely new solutions.

>I apologize if my responses gave the impression that I had authored and then deleted code. I aim to be more transparent about this in the future. When I say things like "'s implement this" or "we need to add", I'm really suggesting changes based on the context provided, not referring to code I personally wrote or modified.

>Would you like me to continue helping with the current issue regarding the updateAsset implementation, but with this clearer understanding of my role?

討論​

評論 1:

Just another day of Vibe Coding.

22. Can somebody tell what MCPs capable of like telling a toddler?​

根據你的描述，這篇文章的核心討論主題可以總結為以下兩點：

  1. 對MCP（可能指某種技術、概念或框架）的本質理解與應用場景的困惑
    作者觀察到「MCP」一詞被廣泛討論，但多數內容聚焦於「如何實現」（implementation），而非釐清其核心用途或應用方式（in what way people use it），導致難以掌握其實際價值。

  2. 探討MCP的獨特創新或關鍵概念
    作者進一步提出疑問，希望了解MCP與其他類似技術或方法的區別，例如其獨特理念（unique ideas）或解決問題的差異化優勢。

補充說明：
若「MCP」有具體指涉（如Microsoft Certified Professional、Multi-Chip Package等），討論方向可能不同，但根據現有內容，主題更偏向「釐清模糊術語的實際應用與創新點」。建議提供更多背景以精確分析。

內容​

I have been seeing the term of MCP everywhere , and I watched a few videos about it ,but everyone is so focused on implementation,so I could not figure out in what way people use it ?

What are the unique ideas over it?

討論​

評論 1:

Here's an example.

Without MCP:

You are chatting with a LLM and sort out a problem you've been working on and now you want to document it. Le``` say you document all your work in Obsidian, so normally you would copy the info from the LLM chat, paste it in Obsidian and then format it. (You could also ask the LLM to format it before copy/pasting)

With MCP: You are chatting with a LLM and sort out a problem you've been working on and now you want to document it. You ask the LLM to document everything you've worked on in Obsidian and format it in markdown with proper headers, etc. Then you watch the magic happen in real-time while the LLM is creating your docs. Then you could point it at other folders you want cleaned up and it go to town. You just prompt the LLM on what you want it to do.

I``` sort of like giving a LLM a set of instructions on how to use a specific app/service/etc. You could also look at it like Neo from the Matrix when he's learning Kung-Fu and all that, each MCP server is a new skill.

評論 2:

Claude is Mike Tyson, and MCP is Don King. You might want to do business with or hire Mike, but you have a better chance interacting with Don King to make it happen.

評論 3:

Youre not a toddler but s do it for fun anyway.

Its been possible to make cookies for a while now just made cookie dough and then smoosh them into the sheet. The cookies potentially come out all different ways.

Instead, you could use a cookie cutter to make fun shapes. That makes the cookies much more consistent.

-end toddler-

In this case, the cookies are the calling and the cookie is MCP. MCP is forming the glue code and consistency around how you interact with these functions. It doesnt even know i```elf provide any of this functionality which means you can do pretty much anything with it that the : could do.

Since a is a basic unit that can call the local or remote things you can do anything that would require local or remote calls. Either manipulating the file system, library or calling your favourite API.

The functions themselves have to be described in a way that makes it easy for the LLM to approach.

Enabling the LM to interact with the world in different ways has potential to enable workflow that you couldnt have easily done before its not in the one wiring up to one service but in the wiring up to multiple services.

Tools like Zapier have done similar things but they require an external provider and theyre quite convoluted to set up whereas where now depending on the LLM to interpret and glue those things together.

It isnt an exact one to one here because Zapier has the ability to say run things on a trigger and the MCPs are in response to what youre doing currently.

This along with the fact that a lot of the hard work with LLMs is building context, building information that it can work with. Making it easier for it to get that information is gonna give better outpu```.

評論 4:

Hi there, friend! Elmo is so happy to see you today!

Elmo wan``` to tell you about something called Claude MCP!

Claude MCP is like Elmo's super smart thinking friend! Claude MCP helps grown-ups figure out really big problems that make their brains go "Hmmmm!"

When you have a super duper hard puzzle, Claude MCP helps break it into tiny little pieces! Just like when Elmo and friends work together to solve problems on Sesame Street!

Claude MCP is like having the bestest helper for thinking about numbers, patterns, and big questions! It's like if Mr. Noodle had AMAZING puzzle-solving powers!

Elmo thinks Claude MCP is ticklish for your brain! It makes hard things easier, just like how Elmo's friends make Elmo's day brighter!

When you build with blocks, sometimes you have to think carefully about where each block goes, right? Claude MCP helps grown-ups think about complicated problems the same way - step by step, being extra careful with each piece!

It's like if Cookie Monster didn't just gobble up all the cookies at once, but instead thought very carefully about the yummiest way to enjoy each cookie!

That's Claude MCP in Elmo's world! Elmo loves making new friends! Do you want to count some cookies with Elmo now?

評論 5:

MCP = C3PO

23. Did Claude sh*t the bed for everyone today?​

這篇文章的核心討論主題是對人工智慧助手Claude的表現感到失望，特別是它在記憶和任務執行方面的嚴重缺陷。作者指出Claude即使在「思考模式」下也無法記住30秒前的對話內容，顯示其在基本功能上的失敗。這反映了對當前AI技術在記憶保持和連續對話能力方面的局限性的批評。

內容​

What in the world! Claude is struggling with literally all tasks. Like completely forgetting everything I told it 30 seconds ago. Even on thinking mode!

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inpu```, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

He's become Claude 0.7

A complete idiot, with no coherence. He looks like a kid in training.

評論 3:

Does literally anyone from Anthropic browse this subreddit and feel marginally bad that we pay for this product?

評論 4:

bro i``` literally worse than chatgpt 3.5

評論 5:

Yup

There was missing ")" in 1000 lines of HTML (that It typo'd) and I couldn't find - " if couldn't fix it in the artifact, it tried rewriting everything from scratch like 10 times before I gave up, took the last working version and gave it to o3mini.

24. I went through $50 tonight trying to get AI/Claude to fix errors.​

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

  1. 技術開發的挫折與成本：作者描述花費50美元嘗試建立一個數據庫查看器以驗證腳本的正確性，但最終仍未能解決問題，凸顯小型開發者面臨的技術障礙與金錢成本壓力。

  2. 對Replit平台的質疑：提到Replit官方無法解決其應用中的錯誤，間接批評開發工具的支持限制，同時提到使用第三方代碼（Roo code）時被迫接觸贊助連結（如Claude信用購買），暗示對工具生態商業化的不滿。

  3. 個人背景與動機：作者強調自己非富裕階層（聯邦政府雇員），旨在通過自動化工具提升工作效率，反映普通工作者在資源有限下對技術創新的需求。

  4. AI的生產力價值：明確肯定AI技術節省大量時間，並表達進一步利用AI增強工作效率的意願，體現對技術賦能個人生產力的積極態度。

整體而言，文章圍繞「資源有限的個人開發者如何應對技術挑戰並利用AI工具突破效率瓶頸」展開，夾雜對開發環境的批評與對未來技術應用的期待。

內容​

連結： [https://preview.redd.it/2r2ro4wwo4se1.png?width=622&format=png&auto=webp&s=cbaeb3e2fe79ec6f3f48b40f0fe52e27e7e1f95d

$50 to build a read only database viewer in my app so I can see if the script replit is legit. Well, not not legit, Replit couldn't figure out errors I was encountering in my app. $50 later, still not working. But using Roo code I had plenty of opportunity to use their links to buy Claude credi```.

I'm not rich. I work in the fed government. Not the DOGE kind. I'm trying to build tools to help me automate and build shtuff. AI has saved me HOURS and I'm looking to use it more to increase productivity and efficiency more. ](https://preview.redd.it/2r2ro4wwo4se1.png?width=622&format=png&auto=webp&s=cbaeb3e2fe79ec6f3f48b40f0fe52e27e7e1f95d

$50 to build a read only database viewer in my app so I can see if the script replit is legit. Well, not not legit, Replit couldn't figure out errors I was encountering in my app. $50 later, still not working. But using Roo code I had plenty of opportunity to use their links to buy Claude credi```.

I'm not rich. I work in the fed government. Not the DOGE kind. I'm trying to build tools to help me automate and build shtuff. AI has saved me HOURS and I'm looking to use it more to increase productivity and efficiency more. )

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inpu```, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

I only use Claude API these days in Plan Mode (Cline) and then use Gemini 2.5 when I switch to Act Mode.

I ask Claude for detailed implementation ideas in Plan Mode and then switch. It creates code snippe``` which Gemini uses to build/correct code.

I dont the context go beyond 150K, I use a changelog.md and implementation-plan.md (updated by Gemini/claude when I need) to track and plan changes so knowledge carries over to new task when I need.

Edit: Also do refactor the code. It helps a lot. Smaller files are easier to edit using AI.. it wont spend multiples times rewriting broken edi```.

評論 3:

Use Gemini 2.5.

Get Gemini pro, get their API.

I mean if you really want to spend to use Claude go ahead but google is free and pretty damn good. Plus context window is massive

評論 4:

Use Claude Desktop with filesystem MCP server. $20/month instead of $40+ per day. But all the AIs suck at debugging. Have it explain clearly what it thinks it's doing, then look through the code yourself as best you can. If it's the same error over and over and it thinks it "fixed it this time" it probably didn't. My example ... it had "/api" in the {apiUrl} and was also adding it with the /api/endpoint/whatever causing a 404. Hours it went in circles, until I poked around at the js in devtools and found it. As clever as they are, Gemini, Claude, OpenAI all fall for their own stupid errors, until you can point out the real problem. Just sayin'.

評論 5:

why are you not using gemini 2.5 pro ? i``` FREE with 1milion token context. a.i studio from google

25. 12 step checklist on how to rank on LLMs​

這篇文章的核心討論主題是 「生成式引擎優化（GEO, Generative Engine Optimization）」，具體聚焦於如何透過內容策略提升大型語言模型（如Claude）在生成回答時引用或提及特定網站或品牌的機率。重點包括：

  1. GEO的核心目標：
    透過優化內容結構、格式和呈現方式，使網頁更容易被LLM（如Claude、ChatGPT）採納為資訊來源，從而增加曝光機會。

  2. 關鍵優化策略（依影響力排序）：

    • 列表式內容（Listicles）：例如「最佳X工具」或「競品替代方案」等標題，容易被LLM引用。
    • 清晰的標題結構：使用H2/H3標題直接回答問題，並結合FAQ結構與JSON-LD標記。
    • 對話式語氣：模仿論壇或問答網站的自然風格，而非學術性表述。
    • 直接且事實導向的內容：開門見山陳述重點，後續補充細節（如研究數據）。

  3. 實用技巧：

    • 逆向分析LLM的資訊來源（例如詢問AI工具其答案出處）。
    • 透過反向連結分析競爭對手的內容策略。
    • 研究競爭對手在列表式文章中的排名與曝光。

  4. 學術支持：
    引用一篇關於GEO的研究論文（arXiv:2311.09735），探討如何系統性優化內容以適應生成式AI的檢索邏輯。

整體而言，文章從實務角度探討「如何讓企業內容被AI模型優先引用」，並提供具體可操作的方法，同時邀請讀者分享相關經驗。

內容​

I was quite excited when they announced that Claude can now search the web! Claude is definitelly my favourite LLM out there...And since I own a business and want to be featured in the resul```, I did some research around how to get cited / mentioned by LLMs. All the finding below and from this research paper on GEO (Generative Engine Optimization) I found a month ago + a bunch of articles.

I put all the poin``` in the table below. hopefully it helps.

Research paper: https://arxiv.org/pdf/2311.09735

The GEO Checklist (in order of impact):

https://preview.redd.it/70laoa3q78se1.png?width=1494&format=png&auto=webp&s=cbca09b1e7e8536c078d53fc065e0824813c27c9

Additional ones which I think also have impact:

Listicle - This one is HUGE. Write them as well as invest in being listed. Example: "Best software for X" OR "[Competitor] alternatives" pos``` get cited constantly by LLMs!

Clear structure with headings - AI models love organization! Use H2 and H3 headings that directly answer questions. FAQ-style content is money here (include FAQ json-ld schema as well)

Conversational Tone - Makes sense when you think about it - AI learns from forums, Reddit, and Q&A sites. Write like you're having a conversation, not delivering a lecture

Direct, factual content - Include main point in the first sentence, then expand. Example: "Yes, dark chocolate is beneficial for heart health. Studies show it contains flavonoids that reduce inflammation and improve blood flow."

Here's how I quickly find GEO opportunities:

  1. Reverse-engineer LLM sources (ask AI tools where they're getting info from)

  2. Reverse-engineer sources across the web (backlink analysis)

  3. Analyze competitor listicle placemen```

Has anyone else been experimenting with GEO? would love to discuss them

Cheers,

Tilen

討論​

評論 1:

If someone want to dig deeper, I included examples and some case studies in the blog below:
https://www.babylovegrowth.ai/blog/generative-search-engine-optimization-geo

評論 2:

Super helpful for anyone trying to get cited by LLMs. Have you noticed if certain types of expert quotes (e.g., academic vs. industry professionals) carry more weight?

總體討論重點

以下是25篇文章的摘要重點整理，以條列方式呈現，並附上對應的文章錨點連結：

1. This is the first time in almost a year that Claude is not the best model​

  • 性能比較：Gemini 2.5在處理上下文、可靠性等方面超越Claude。
  • 態度轉變：作者從厭惡Google轉為肯定Gemini 2.5，自嘲「投向黑暗面」。
  • 動態競爭：AI領域變化快速，未來Claude可能反超。
  • 實用導向：強調實際使用需求而非品牌忠誠度。

2. What the hell happened?​

  • 問題回報流程：需分類環境（免費/付費）、提供詳細資訊（提示詞與輸出）。
  • 服務中斷：多位用戶反映無法使用Claude，官方未更新狀態頁面。
  • 反饋機制：透過thumbs down按鈕提供負評，官方監控此數據。

3. I accidentally built a brain fog tracker with Claude and it actually helped me feel smarter​

  • 健康解決方案：結合Claude開發「腦霧儀表板」，量化追蹤症狀成因。
  • AI協作價值：Claude主動分析數據、提出建議，發現潛在模式（如補充劑關聯）。
  • 開源分享：考慮公開專案，建議「記錄+AI分析」方法。

4. Please be candid; did I just pay $220 for a year of this screensaver, but only at Anthropic's website?​

（內容未提供，需補充細節）

5. [Claude Pro limi](#5-claude-pro-limi)​

  • 限制加劇：付費用戶短期內觸發訊息限制（約5條）。
  • 體驗下降：認為工具「幾乎無法使用」。
  • 求證現象：詢問其他用戶是否遇到相同問題。

6. Claude's context has been nerfed?​

  • 異常表現：Sonnet模型無預警遺失對話上下文。
  • 技術推測：懷疑Anthropic動態摘要歷史訊息，降低實際處理量。
  • 商業倫理質疑：可能誤導用戶付費購買「完整上下文」功能。

7. Message Limit Reached very often now in paid version, hardly usable​

  • 付費限制問題：頻繁觸發訊息限制，與免費版差異不大。
  • 版本影響：Claude 2.7 Sonnet桌面版非思考模式下問題明顯。
  • 時間變化：近期限制突然嚴格化。
  • 免費高效工具：媲美付費產品的程式碼分析能力。
  • 多平台支援：可搭配Claude Desktop或Gemini運行。
  • 技術創新：使用語言伺服器分析大型程式碼庫。
  • 開源專案：GitHub上的serena專案。

9. Dropped a new tutorial for Agentic pattern + AI SDK​

  • 新影片發布：介紹「Agentic patterns」並參考Anthropic論文。
  • 觀眾反饋：邀請對影片內容與表現方式的建議。

10. [Are rate limi significantly lower now?](#10-are-rate-limi-significantly-lower-now)​

  • 限制變化：訊息額度從40-50條降至20-25條。
  • 不滿情緒：表達對無預警調整的困惑。

11. [Hitting limi without getting responses](#11-hitting-limi-without-getting-responses)​

  • 技術故障：Claude無回應卻消耗使用額度。
  • 付費落差：質疑付費後服務品質下降。

12. [What computer use​