Show HN: OpenWork – an open-source alternative to Claude Cowork https://ift.tt/iOAep6b

Show HN: OpenWork – an open-source alternative to Claude Cowork hi hn, i built openwork, an open-source, local-first system inspired by claude cowork. it’s a native desktop app that runs on top of opencode (opencode.ai). it’s basically an alternative gui for opencode, which (at least until now) has been more focused on technical folks. the original seed for openwork was simple: i have a home server, and i wanted my wife and i to be able to run privileged workflows. things like controlling home assistant, or deploying custom web apps (e.g. our customs recipe app recipes.benjaminshafii.com), legal torrents, without living in a terminal. our initial setup was running the opencode web server directly and sharing credentials to it. that worked, but i found the web ui unreliable and very unfriendly for non-technical users. the goal with openwork is to bring the kind of workflows i’m used to running in the cli into a gui, while keeping a very deep extensibility mindset. ideally this grows into something closer to an obsidian-style ecosystem, but for agentic work. some core principles i had in mind: - open by design: no black boxes, no hosted lock-in. everything runs locally or on your own servers. (models don’t run locally yet, but both opencode and openwork are built with that future in mind.) - hyper extensible: skills are installable modules via a skill/package manager, using the native opencode plugin ecosystem. - non-technical by default: plans, progress, permissions, and artifacts are surfaced in the ui, not buried in logs. you can already try it: - there’s an unsigned dmg - or you can clone the repo, install deps, and if you already have opencode running it should work right away it’s very alpha, lots of rough edges. i’d love feedback on what feels the roughest or most confusing. happy to answer questions. https://ift.tt/0MCoDBW January 14, 2026 at 10:25AM

Show HN: Webctl – Browser automation for agents based on CLI instead of MCP https://ift.tt/SsDzOcQ

Show HN: Webctl – Browser automation for agents based on CLI instead of MCP https://ift.tt/6WX54D3 January 14, 2026 at 08:04PM

Show HN: Repomance: A Tinder style app for GitHub repo discovery https://ift.tt/nOQSK7x

Show HN: Repomance: A Tinder style app for GitHub repo discovery Hi everyone, Repomance is an app for discovering curated and trending repositories. Swipe to star them directly using your GitHub account. It is currently available on iOS, iPadOS, and macOS. I plan to develop an Android version once the app reaches 100 users. Repomance is open source: https://ift.tt/w4PcdKo All feedback is welcome, hope you enjoy using it. https://ift.tt/rJIg23q January 15, 2026 at 12:24AM

Show HN: Sparrow-1 – Audio-native model for human-level turn-taking without ASR https://ift.tt/BzCUbXK

Show HN: Sparrow-1 – Audio-native model for human-level turn-taking without ASR For the past year I've been working to rethink how AI manages timing in conversation at Tavus. I've spent a lot of time listening to conversations. Today we're announcing the release of Sparrow-1, the most advanced conversational flow model in the world. Some technical details: - Predicts conversational floor ownership, not speech endpoints - Audio-native streaming model, no ASR dependency - Human-timed responses without silence-based delays - Zero interruptions at sub-100ms median latency - In benchmarks Sparrow-1 beats all existing models at real world turn-taking baselines I wrote more about the work here: https://ift.tt/ZPbis1G... https://ift.tt/wquciJY January 14, 2026 at 11:31PM

Closing Potrero Yard: How We’ll Keep Muni Moving with Feb. 14 Service Changes

Closing Potrero Yard: How We’ll Keep Muni Moving with Feb. 14 Service Changes
By Brian Haagsman

The 49 Van Ness-Mission is one of the busiest routes we maintain at Potrero Yard. On Feb. 14, we’re taking two major steps to keep Muni fast and reliable. First, we’ll be making several changes to bus stops and routes to: Improve reliability Provide better connections to regional transit Avoid delays And to improve Muni for years to come, we are working to replace Potrero Yard with a modern bus maintenance facility through the Potrero Yard Modernization Project. For crews to prepare for future construction, we need to close Potrero Yard in February 2026. We’ll move existing bus operations and...

Published January 13, 2026 at 05:30AM
https://ift.tt/VjweJch

Show HN: Self-host Reddit – 2.38B posts, works offline, yours forever https://ift.tt/HE6nygs

Show HN: Self-host Reddit – 2.38B posts, works offline, yours forever Reddit's API is effectively dead for archival. Third-party apps are gone. Reddit has threatened to cut off access to the Pushshift dataset multiple times. But 3.28TB of Reddit history exists as a torrent right now, and I built a tool to turn it into something you can browse on your own hardware. The key point: This doesn't touch Reddit's servers. Ever. Download the Pushshift dataset, run my tool locally, get a fully browsable archive. Works on an air-gapped machine. Works on a Raspberry Pi serving your LAN. Works on a USB drive you hand to someone. What it does: Takes compressed data dumps from Reddit (.zst), Voat (SQL), and Ruqqus (.7z) and generates static HTML. No JavaScript, no external requests, no tracking. Open index.html and browse. Want search? Run the optional Docker stack with PostgreSQL – still entirely on your machine. API & AI Integration: Full REST API with 30+ endpoints – posts, comments, users, subreddits, full-text search, aggregations. Also ships with an MCP server (29 tools) so you can query your archive directly from AI tools. Self-hosting options: - USB drive / local folder (just open the HTML files) - Home server on your LAN - Tor hidden service (2 commands, no port forwarding needed) - VPS with HTTPS - GitHub Pages for small archives Why this matters: Once you have the data, you own it. No API keys, no rate limits, no ToS changes can take it away. Scale: Tens of millions of posts per instance. PostgreSQL backend keeps memory constant regardless of dataset size. For the full 2.38B post dataset, run multiple instances by topic. How I built it: Python, PostgreSQL, Jinja2 templates, Docker. Used Claude Code throughout as an experiment in AI-assisted development. Learned that the workflow is "trust but verify" – it accelerates the boring parts but you still own the architecture. Live demo: https://online-archives.github.io/redd-archiver-example/ GitHub: https://ift.tt/UkorjtI (Public Domain) Pushshift torrent: https://ift.tt/vmz0acY... https://ift.tt/UkorjtI January 13, 2026 at 09:05PM

Show HN: AI video generator that outputs React instead of video files https://ift.tt/Kc47AHn

Show HN: AI video generator that outputs React instead of video files Hey HN! This is Mayank from Outscal with a new update. Our website is now live. Quick context: we built a tool that generates animated videos from text scripts. The twist: instead of rendering pixels, it outputs React/TSX components that render as the video. Try it: https://ai.outscal.com/ Sample video: https://ift.tt/csQAhfg... You pick a style (pencil sketch or neon), enter a script (up to 2000 chars), and it runs: scene direction → ElevenLabs audio → SVG assets → Scene Design → React components → deployed video. What we learned building this: We built the first version on Claude Code. Even with a human triggering commands, agents kept going off-script — they had file tools and would wander off reading random files, exploring tangents, producing inconsistent output. The fix was counterintuitive: fewer tools, not more guardrails. We stripped each agent to only what it needed and pre-fed context instead of letting agents fetch it themselves. Quality improved immediately. We wouldn't launch the web version until this was solid. Moved to Claude Agent SDK, kept the same constraints, now fully automated. Happy to discuss the agent architecture, why React-as-video, or anything else. https://ai.outscal.com/ January 13, 2026 at 12:33AM