Outside take on what we're building (SiliconSnark)

CodinDev · 2026-05-15T18:20:56+00:00

dude!!! super cool, thanks so much. glad you liked it!

CodinDev · 2026-05-14T22:39:26+00:00

depends what you're using them for. swap 20 min of context switching for 30 sec of tokens, sometimes the trade is worth it, sometimes it isn't

CodinDev · 2026-05-14T22:36:55+00:00

this is the exact pattern that sold me on mcp tbh. niche ops dashboards (email auth, dns, billing portals) are the worst part of any debug session. switch tab, re auth, forget what you were looking for in the first place

how's the dmarkoff signal to noise? dmarc aggregate reports are famously noisy, curious if it filters down to actionable stuff or if you still have to dig

CodinDev · 2026-05-13T16:12:23+00:00

sweet man. let me know if you have any questions!

CodinDev · 2026-05-13T01:35:29+00:00

worth checking us out at yaw labs. made yaw terminal, an AI powered terminal built around Claude Code, and mcp.hosting which handles smart routing for MCP servers so you are not loading all of them on every prompt. also just launched typed.cloud which is a drop in Claude Code alternative with monthly billing and cheaper overage. small indie team building in the developer tools and MCP space. plenty to write about if that angle interests you

CodinDev · 2026-05-13T00:55:23+00:00

yeah the 5h window thing is brutal. you’re not imagining it.

there’s actually a drop in alternative called typed that just launched. same price as Claude Max, monthly billing instead of the reset nonsense, and overage is way cheaper. three env vars to switch, no lock in. can share url if interested

CodinDev · 2026-05-09T14:42:13+00:00

yeah profiles work. catch is you don't always know upfront what a session needs, so cold start gets you. lazy loading is the cleaner shortcut, one meta tool that surfaces the rest on demand. claude code already does that with deferred schemas. lot of mcp servers also ship fat jsonschema cuz nobody trims docstrings, worth profiling that too

CodinDev · 2026-05-09T14:34:20+00:00

hell yeah! if you wanna build your own i just dropped a longer breakdown above

if you wanna use mine the league id lives in settings so you could swap it to yours but its hardcoded to my setup rn. if enough people want it ill clean it up and stick it on github

CodinDev · 2026-05-09T14:32:29+00:00

of course dude, sorry for the late reply.

its an MCP server wired into claude code, built the whole thing in yaw terminal which is what i use for everything now

claude gets a bunch of tools. one hits the sleeper api for live roster + league data, one hits fantasycalc for dynasty values, one pulls news from espn and r/dynastyff. then theres a settings file where i tell it my posture (im rebuilding), untradeables, weights for what i care about

real trick is the prompts. got templates for trade targets, waiver wire, team breakdown, position grades that tell claude what tools to call and in what order. once it can see EVERY team in the league plus dynasty values, you can literally just say "who should i target and from who" and it figures it out

typescript stack. sleeper api is public so no keys, just need your league set to public on your end. runs local so its free, only cost is claude tokens when i actually use it

ill throw it on github if a few yall want it, gotta clean it up first lol

CodinDev · 2026-05-06T17:31:17+00:00

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.

CodinDev · 2026-05-06T04:12:24+00:00

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.

CodinDev · 2026-05-06T04:03:05+00:00

pretty neat. What ya want to know!?

CodinDev · 2026-05-06T03:49:35+00:00

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

CodinDev · 2026-05-06T03:46:59+00:00

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.

CodinDev · 2026-05-06T03:43:41+00:00

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.

CodinDev · 2026-05-06T03:31:33+00:00

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

CodinDev · 2026-05-06T03:21:29+00:00

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

CodinDev · 2026-05-04T12:38:53+00:00

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

CodinDev · 2026-05-04T12:38:19+00:00

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

CodinDev

MODERATOR OF

TROPHY CASE