Yes all this has been known since the M4 came out. The memory bandwidth is too low.
Try using it with real tasks like cline or opencode and the context length is too long and slow to be practical
1,450 karma · joined August 4, 2012
Writing https://leanpub.com/aismarthome
Yes all this has been known since the M4 came out. The memory bandwidth is too low.
Try using it with real tasks like cline or opencode and the context length is too long and slow to be practical
I think they’re trying to compete with Gemini cli and now I’m glad I’m paying less
And you are never going to sit around waiting for anything larger than the 96+gb of ram that the RTX pro has.
If you’re using it for background tasks and not coding it’s a different story
Get the RTX Pro 6000 for 8.5k with double the bandwidth. It will be way better
It’s actually surprising just how powerful 1-5 tools can be if you document it well and the llm knows how to pass arguments from other tool responses you had higher up in the thread
You can ask the client to fill in a dropdown or input.
Example they give is a restaurants table booking tool.
Imagine saying book a table at 5pm. But 5pm is taken.
You can “elicit” the user and have them select from a list of available times
One weird thing I found a few weeks ago, when I added my remote MCP to Claude's integration tab on the website, I was getting OAuth errors.
Turns out they are requiring a special "claudeai" scope. Once I added that to my server, I was able to use it remotely in claude desktop!
I couldn't find any docs or reasons online for them requesting this scope.
Also, I have been using remote mcps in claude code for weeks with the awesome mcp-remote proxy tool. It's nice to not need that any longer!
Then as I'm writing a book currently on MCP Servers with OAuth, Elicitations come out! I'm rushing to update this book and be the best source for every part of the latest spec, as I can already see lots of gaps in documentation on all these things.
Huge shout out to VS Code for being the best MCP Client, they have support for Elicitations in Insiders already and it works great from my testing.
Essentially you can use stdio, without the hassle of a shared internal http server, and still have it auto update with changes your team makes.
I tried this idea with the new MCP prompt support in VS code and I’m pretty happy with it so far.
One time I simply made a post about how a page was simpler to code and understand in Remix.
You may not believe this but I had 3+ chat requests from multiple employees at vercel.
Across multiple social media accounts. All asking to take it down or meet and discuss with them.
Now if you convert the request / response types to native bun server, it can be finicky.
But it works fine using express under bun with the official protocol implementation for typescript.
Actually writing a book about this too and will be using bun for it https://leanpub.com/creatingmcpserverswithoauth
Rather ship oven/bun through docker and have a 90mb container vs using node.