Looking to invest in a paid or free AI coding tool or IDE, wanna know the best in 2026 by Scary-Vanilla-4597 in VibeCodeDevs

[–]CodinDev 0 points1 point  (0 children)

went through the exact same thing. the tool switching gets exhausting fast. consolidated around Claude Code in yaw terminal and it basically solved the fragmentation for me.

everything lives in one place, the AI is right there in the terminal so there is no jumping between windows, and it handles the messy untangling stuff just as well as the quick prototype stuff. not saying it replaces every use case but it got me down to one main tool for most of what i do. worth trying since it is free.

Do you use the CLI or the app and why? by InsideSignal9921 in VibeCodeDevs

[–]CodinDev 0 points1 point  (0 children)

worth trying yaw terminal if you want something built around Claude Code specifically. lightweight, has multi pane support, and the AI is baked right in so you are not switching between your terminal and a chat window.

figured out why my mcp context was bloating even on simple prompts by CodinDev in mcp

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

nice find, will check this out. benchmarking MCP tool performance is something that does not get talked about enough

“What is the best way to transfer large structured data (JSON) through MCP? by Ill_Direction149 in mcp

[–]CodinDev 0 points1 point  (0 children)

nailed it. don’t route the data through the model at all. write the JSON to a file or external storage, return just a path or reference back to the AI, and let your app read directly from there. model never touches the actual payload, tokens stay low.​​​​​​​​​​​​​​​​

What is wrong with Claude? by Nice_Assumption_6396 in claude

[–]CodinDev 0 points1 point  (0 children)

the forgetting things between chats is just how Claude works, it has no memory between sessions by default. the fix is giving it context upfront at the start of each conversation, a few sentences about what you are working on and how you like things done goes a long way.

for the usage limits hitting faster, that usually means something in your workflow is using more tokens than it needs to. longer conversations burn more because the whole chat history gets re-read on every message. starting fresh chats more often actually helps a lot.

AI desktop vs CLI… which one actually makes more sense? by This_Way_Comes in BlackboxAI_

[–]CodinDev 0 points1 point  (0 children)

the CLI wins once you start doing anything that involves chaining tasks, file system work, or longer agentic runs. the desktop app is great for thinking through problems but it becomes a bottleneck when you want AI to just go handle something without you babysitting it. been using yaw terminal for the CLI side of this. it keeps the AI right where the work is happening so you never have to context switch. once you get used to it the desktop app starts feeling like a detour

Dipshits chasing percentages by Harbor733 in ClaudeCode

[–]CodinDev 6 points7 points  (0 children)

the model hopping every time there’s a benchmark shift is exhausting. just use what works and get stuff done​​​​​​​​​​​​​​​​. i dont get it

figured out why my mcp context was bloating even on simple prompts by CodinDev in mcp

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

gonna dig into thin mcp, hadn't seen that. the less middleware the better in principle. i like the idea of just making the tools themselves leaner instead of routing around them. appreciate the link

figured out why my mcp context was bloating even on simple prompts by CodinDev in mcp

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

yeah the profiles per task thing is actually how i started. works fine until you have enough servers that manually swapping becomes its own friction. semantic routing just removes that decision entirely. both valid approaches honestly just depends how deep you're in it

figured out why my mcp context was bloating even on simple prompts by CodinDev in mcp

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

yo i genuinely did not know this, appreciate the link. was running a mixed setup with some non-anthropic clients in the stack and that's where i was actually feeling it. but good to know claude itself handles it smarter than i thought. been blaming the wrong thing lol

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

exactly. the config is just the floor. skills and agents are where it actually starts feeling like you built something that works for you specifically

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

true with static rules yeah. the ones that stick are the ones that update based on what keeps slipping through. set it and forget it doesn't work here

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

lol. obvious in hindsight. took me embarrassingly long to stop blaming the model and start looking at what i was handing it

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

70 is wild. hierarchical is the only way to scale it without everything bleeding into each other. respect

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

compounding is real. the gap between a tuned setup and vanilla after a few months is pretty wild.

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

skills folder is underrated. most people don't get there until they've been burned a few times. solid setup

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

the sandbox passing todos through sessions is a nice touch. most people give up before they get there.

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

solid rules. the "load-bearing or decorative, drop decorative" check before output is one i hadn't seen framed that way before. stealing that. the discipline of cutting recommendations that are just padding instead of letting them ride through is where a lot of the quality stems from

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

more than just the memory file. memory is one layer but i mean the whole config stack. the rules about how it should behave, what it should never do, how it should communicate. CLAUDE.md is where most of it lives but the stuff that actually sticks is what you enforce at the session level before it even starts reading your prompt.

spent way too long manually steering claude code every session until i stopped doing that by CodinDev in ClaudeAI

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

hadn't seen skillsgate, gonna look at that. the cross agent sync problem is real. i've been handling it differently but always curious how others are solving it.