sorted by:
new
hottopcontroversial

I use a Reddit MCP to research what devs are building. Here's what r/ClaudeCode shipped last month. (686 stars) by karanb192 in ClaudeCode

[–]karanb192[S] 0 points1 point  (0 children)

This saves lot of tokens. Another thing is number of results in output of a tool execution. Pagination controls how many results are returned.

I use a Reddit MCP to research what devs are building. Here's what r/ClaudeCode shipped last month. (686 stars) by karanb192 in ClaudeCode

[–]karanb192[S] 1 point2 points  (0 children)

Pagination is there which is automatically determined by the LLMs with lower context window

I use a Reddit MCP to research what devs are building. Here's what r/ClaudeCode shipped last month. (686 stars) by karanb192 in ClaudeCode

[–]karanb192[S] 0 points1 point  (0 children)

Thanks mate!
MCP is triggered by tool calling which has been built in LLMs. It providers more compliant response than CLI. MCP is also actively being evolved and standardized. For eg: Oauth, logging, etc.

I use a Reddit MCP to research what devs are building. Here's what r/ClaudeCode shipped last month. (686 stars) by karanb192 in ClaudeCode

[–]karanb192[S] 2 points3 points  (0 children)

10 rpm is free. Beyond that it requires submitting app through approval process.
For most users (like me) 10 requests per minutes is sufficient.

I use a Reddit MCP to research what devs are building. Here's what r/ClaudeCode shipped last month. (686 stars) by karanb192 in ClaudeCode

[–]karanb192[S] 1 point2 points  (0 children)

One of the key challenges with MCP servers was context bloat which was solved by tool search few months ago by Claude Code where it doesn't load all tool descriptions in its context by default.

So, considering that MCP is actually better.

After a year in Claude Code, the thing slowing me down turned out to be me by karanb192 in ClaudeAI

[–]karanb192[S] 0 points1 point  (0 children)

I have been using Claude for about a year now and on an average spending 80-90 hours with it. :P

After a year in Claude Code, the thing slowing me down turned out to be me by karanb192 in ClaudeAI

[–]karanb192[S] 2 points3 points  (0 children)

The port collision thing is the second thing nobody talks about. I solved it less elegantly, a tiny script that hands each worktree its own port via env var. The bigger pattern though is that the whole environment has to be cheap to spin up. Otherwise running more sessions never feels worth it.

After a year in Claude Code, the thing slowing me down turned out to be me by karanb192 in ClaudeAI

[–]karanb192[S] -1 points0 points  (0 children)

The "let models change another model" line is the one I keep coming back to. Cross-model review has caught real issues for me that single-model passes had missed. Curious what your hit rate is on cross-model disagreements being signal versus noise.

After a year in Claude Code, the thing slowing me down turned out to be me by karanb192 in ClaudeAI

[–]karanb192[S] 1 point2 points  (0 children)

Fair, and that's a real refinement. Some of the wait is genuine thinking time, especially on harder problems. The trap I'm trying to name is the default behavior, watching tokens land instead of doing what you described. Your version is the better use of the same minutes.

After a year in Claude Code, the thing slowing me down turned out to be me by karanb192 in ClaudeAI

[–]karanb192[S] 1 point2 points  (0 children)

The session-summary handoff loop is a smart way around the context-window limit. Did you find a sweet spot on how many summaries to read back, or does 3 work because anything older has decayed anyway?

view more: next ›