jeffyaw

m5 max with UD-Q4_K_XL and 260k context is what i'm working with. and using compaction push it past 260k context just fine. i found when limiting the context that was one of the bigger debilitators. although, your setup sounds obviously better.

disagree, it’s absolutely comparable. but an m5 max is where it shines. and there are 50 flags to finetune with llama server before you get it right. i do prefer llama server over mlx currently on mac as well.

if you want to try a new runtime oam.js is focused on TypeScript & MCP servers.

i've been using a snapdragon x elite and loving it, albeit on Windows. 32GB ram

this sounds like you're stuck in 2010.

it's not that they can't afford to buy one. it's that they're not available. and now a lot of other tlds have gained traction so it's now reasonable to consider others.

thanks for clarifying.

so who/what countered Linus on this and where is the discussion or final conclusion?

once you have built up a trust in a model/harness/setup/workflow and you’ve been hitting enter for months straight then Auto Mode is appealing.

i found initially it would hang on some commands (moreso on subagents and moreso when first rolled out) and then roll past the hung command sometimes forgetting about it entirely. which wasn’t cool.

but after dialing in subagent permissions and probably some updates from anthropic Auto Mode is great. i still don’t always do it. but after reading this article just switched my current 12 panes to Auto.

appreciate the reply!

could you help me understand the appeal of running everything in tmux? i use tmux if i have long running scraping/db backup or restore, or something similar.

it seems like an awesome thing to geek out on.

but i keep claude code sessions running for days that sometimes get interrupted that are easily resumed. without the tmux latency or giving up aspects of rendering.

why even take funding at all?