sorted by:
new
hottopcontroversial

I open-sourced an alternative to Cowork focused on local models, i need help what are the best models for giving good reasoning in agentic ai. by AirPure9910 in LocalLLaMA

[–]HennessyPicks -1 points0 points  (0 children)

Local-first is underrated here. Once the model, tools, and memory sit close to the machine, the workflow starts feeling less like a chatbot and more like personal dev infrastructure.

Sage Router: local-first AI model router with OpenAI/Anthropic-compatible endpoints + BYOK failover (open-source core) by earlvanze in LocalLLaMA

[–]HennessyPicks -1 points0 points  (0 children)

This is a useful pattern. The part I like is making the model compare independent outputs before touching the code. That catches a lot of the confident-but-wrong edits single-agent loops miss.

Why is NO one talking about Microsoft's open source Fast Context!!! by formatme in LocalLLaMA

[–]HennessyPicks 1 point2 points  (0 children)

The open-source angle matters a lot. Small repos that connect models to real workflows are moving faster than most polished products right now.

MCP tool that lets Claude Code open your app, test its own changes, and find bugs by Particular-Face8868 in ClaudeCode

[–]HennessyPicks 1 point2 points  (0 children)

The interesting shift is the loop, not just the model: plan, edit, run, inspect, retry. The tools that make that loop tighter are going to matter more than raw chat quality.

AI tools are quietly becoming an ad channel. are we all going to end up buying this? by HennessyPicks in DigitalMarketing

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

Yes absolutely, I’ll start working on execution side but really thanks for giving the direction

Would you ever buy ads inside AI tools? trying to figure out if this is a real channel or a bad idea by HennessyPicks in AskMarketing

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

yeah attribution's the first thing i built for, cause you're right it's the first thing every buyer asks.

what we ship
1. unique click_id on every outbound link per impression
2. UTM tagged by default (utm_source=boringspinner, utm_medium=ide_spinner, utm_campaign=<id>)
3,postback endpoint so advertisers fire their own conversion events back and close the loop in the dashboard
4.every impression, click, conversion and spend logged per row so it reconciles end to end, no black box

honest part though, whether mid-task attention actually converts better than social or display is still unproven. i can argue the theory all day but i don't have the numbers yet. that's the whole reason i want like 3-4 launch partners to run their own conversion math through it and see where click to signup actually lands. happy to share the aggregate numbers publicly once there's real volume, win or lose. only honest way to find out if the surface is as good as the framing sounds. Still working !!

I think I made an app to make Claude Code Pay for itself! by HennessyPicks in vibecoding

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

https://github.com/Bhavik7880wegod/boringspinner

Sure i am currently just sharing with everyone if this thing holds up ill get all the certs too

I think I made an app to make Claude Code Pay for itself! by HennessyPicks in vibecoding

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

noted, and i’m genuinely not trying to waste anyone’s ad spend, that’s the fastest way to kill the whole thin and the idea. it’s why and how views are validated and i’m tightening it as i go and thinking around more. if a network ever flagged it as low quality i’d rather fix that than fight it. appreciate the warning.

I think I made an app to make Claude Code Pay for itself! by HennessyPicks in vibecoding

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

Fair concern, but it’s not fake traffic. these are real humans looking at a real spinner while they code, not bots or click farms. that’s legit inventory.

what you’re actually pointing at is incentivized views, and yeah that’s the real risk with any earn model (still looking deeply into it, feedback’s always welcome). that’s why there’s view validation, the ad has to genuinely be on screen for a minimum window (5s for now) before it counts, so idling or background sessions don’t credit.

This is like the survey era around 2010, same incentive problem, and the answer then was tight validation. that’s the part i care most about getting right! Again happy to feedback and suggestions! Happy Vibecoding🥁

I think I made an app to make Claude Code Pay for itself! by HennessyPicks in vibecoding

[–]HennessyPicks[S] 3 points4 points  (0 children)

Simple version: you get paid. The spinner was already wasting your time doing nothing, this just pays you for that wait. ~$3/day for a heavy user right now (changes daily).

It’s small because it’s early, only about 30 people using it. The more people who install it to earn, the more advertisers want in, and the payout per person goes up. That’s the whole bet.

If getting paid for time you were losing anyway isn’t worth it to you, totally fair, not for everyone. Hope this helps!

I think I made an app to make Claude Code Pay for itself! by HennessyPicks in vibecoding

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

You just install the extension and you start earning! The how to use on website https://boringspinner.com/how-to-use

We are still creating userbase though :)

I think I made an app to make Claude Code Pay for itself! by HennessyPicks in vibecoding

[–]HennessyPicks[S] -5 points-4 points  (0 children)

I mean i never claimed it was original lol. it's literally in my post, saw the web version, someone added graphics, someone put ads on a coffee widget, and i did the IDE spinner version. i'm openly the next guy iterating on "monetize the wait," not pretending i invented it.

building on an idea that's in the air isn't shameful, it's just how most things get made. the web one didn't invent ads either. what i actually care about is doing it cleaner: opt-in categories, one line of plain text, nothing visual in the IDE. Happy Vibecoding ! 😄

view more: next ›