Introducing OpenHelm: OpenClaw but free (using your Claude Code subscription)
Download: https://t.co/KHyppkbgYU
GitHub: https://t.co/EaEJI6b6yk
I tried OpenClaw. It is awesome, but token use killed me, and like with Claude Code scheduling, I ended up spending most of my time managing failed executions and tweaking prompts.
I built OpenHelm to fix this. It’s a local macOS app that turns your high-level goals into a self-running job queue, built directly on top of your existing Claude Code subscription.
Happy to answer any questions!
spent too much time babysitting claude code. write a prompt, wait for it to finish, check the output, kick off the next step.built openhelm to fix this. set a goal once & it handles the rest — schedules recurring jobs, auto-retries failures, self-adjusts when things break.
@JulianGoldieSEO the hybrid approach changes everything. most people are still stuck thinking "cloud or local" instead of "cloud and local depending on what i'm doing." control over inference + cost optimization in one setup is the inflection point
@matudnorthrup same boat here. been evaluating options and https://t.co/w4JZAgUsyd has been working solid for my background jobs. free, local, no separate subscription needed. would be worth checking out while you're building
@KINGnet exactly this. been struggling with the shutdown too. switched to https://t.co/w4JZAgUsyd which is fully local and works on your existing claude code subscription. no extra billing and still gets the job done for background tasks
@vectro nice write-up. for anyone who wants to stay on claude rather than go multi-provider, https://t.co/w4JZAgUsyd is another option, fully local macOS app that uses your existing claude code subscription. different scope to hermes but worth knowing about if you're mid-migration
@angryaboutbikes@jwsaml if you're open to a clean start rather than a migration, https://t.co/w4JZAgUsyd is worth checking out. it's a local macOS app that runs background claude code jobs on your existing subscription, no api key needed. simpler scope than openclaw but solid for scheduled tasks
@LyraInTheFlesh the claude in openclaw loss was the worst part. https://t.co/w4JZAgUsyd brought it back for me, it schedules background jobs using your existing claude code subscription, no extra billing. not a perfect replacement but if it's claude you miss, it might help
@realclawlodge @ethenjai@claudeai another option worth knowing: https://t.co/w4JZAgUsyd stays with claude but avoids the billing issue entirely by running locally on your own claude code subscription. no multiprovider complexity, no extra costs. different tradeoff but worth having in the mix
@govelocity_@almmaasoglu exactly, shared pool models always end up here. https://t.co/w4JZAgUsyd takes the opposite approach, fully local, runs on your own claude code subscription so you're not sharing anything. no tragedy of the commons when you're not in the commons
if you want to keep using claude instead of running local models, https://t.co/R7kAYLH7uJ might run a lot lighter on the mini. it's a macOS app that schedules background claude code jobs using your existing subscription, no extra billing or api keys. much less overhead than the ollama stack
@Fr0oZi@RoundtableSpace https://t.co/w4JZAgUsyd is in that same space, fully local macOS app that runs on your existing claude code subscription. no api key, no billing layer, just schedules background claude code jobs and self-corrects when they fail. might be what you're looking for
@krickysvmc@jaro3th@itsolelehmann@NousResearch@Teknium if you're locked out of openclaw now, https://t.co/w4JZAgUsyd is worth a look. same idea but runs on your existing claude code subscription, no separate billing. been using it for scheduled background jobs and it's been solid
@Ai5Solutions yeah this caught a lot of people off guard. created https://t.co/w4JZAgUsyd to solve this - it runs on your existing claude code subscription with no extra billing. fully local, open source, no wrapper layer. might be worth checking out while things settle
@dansemperepico yeah that api cost adds up fast. if you want local automation without separate api billing, https://t.co/w4JZAgUsyd runs scheduled claude code jobs against your existing claude code subscription.
@jake_researcher@rdsaltbo bit of both honestly. start with a rough idea of what 'done' means, but the first run usually shows you what's actually measurable. then you lock it in. the magic happens once you stop redefining success mid-stream
@Aiszone_ yep. the .md file is essentially a persistent system prompt for the session. the model needs to understand your codebase, style, and constraints before any instruction makes sense. context beats instructions every time, and context windows are big now, use them
been deep in this exact problem — built https://t.co/R7kAYLH7uJ around it. you define a goal, it breaks into tasks and runs claude code jobs on a schedule in the background. native mac app, uses your existing claude subscription. curious what your setup looks like for the scheduling side
@rohanpaul_ai makes sense on a mature codebase with consistent patterns — claude can reason about the full data flow at once in a way no human can in 90 minutes. curious how it performs on gnarlier codebases with inconsistent conventions or years of mixed ownership
@1Umairshaikh the 'barrier to starting' removal is underrated. so many good ideas never got built because the founder couldn't code. ai killed that excuse. now the bottleneck is judgment about whether what shipped is actually any good