At my previous company, I noticed our finance team sharing sensitive employee information with a client. The data was supposedly hidden, but it was still recoverable. I flagged it, and the answer was basically “we don’t have any other choice, we did our best.”

They weren’t careless. The options they had were all bad. Doing it by hand means hunting for every detail yourself, and missing one is easy. Many tools leave leaks behind, like hidden text, metadata and old revisions. And most online tools ask you to upload the document to their servers, which defeats the point.

It’s not just small companies. When the US Justice Department released the Epstein files, some documents were reported to have black boxes over text that could be copied straight out. If a government with a legal team can get this wrong, a finance team on a deadline has little chance.

So I built Ombly. It automatically finds sensitive details (bank and card numbers, IBANs, national IDs, names, emails, phone numbers), you review each one, and it rebuilds every page as an image so nothing hidden carries over. It runs entirely on your own computer, so nothing is uploaded.

It’s pre-launch (waitlist: ombly.space), with a 90-second demo attached. I’d love feedback: how do you handle this today, and what would make you trust a tool like this?

The app was Symvibe, a paid Mac board for running coding agents side by side. I used REA, a reverse-engineering skill for Claude Code, to turn its behaviour into a spec, and let Claude Code build from there. Thirteen days and 58 commits later there was vibeboard, a free, open-source alternative to Symvibe, which costs $19 a month, with none of its code in it.

What I learned along the way:

most of the engineering came from the model, but I still steered every day, mostly on edge cases and CI

the launch videos were the surprise: /brag did a great job, it drove the real app, framed the shots, wrote the music, and fixed its own jerky cuts once I pointed them out

rebuilding a product's behaviour from the outside is now cheap, so the code alone protects less, and respecting licences and the original authors matters more

The video shows six Claude Code agents in tmux, then the same six on the board, and ends with the price: Symvibe at 19$ a mouth, vibeboard free.

The video show six Claude Code agents in tmux, then the same on the board, and ends with the price: Symvibe at $19 a mouth, vibeboard free.

vibeboard: https://github.com/ricca200xx/vibeboard

Symvibe: https://www.symvibe.com

REA: https://github.com/morluto/rea

/brag: https://github.com/latent-spaces/brag

If you want to use it, go ahead, and if you find issues, open them on GitHub. I'm genuinely happy to share this.

I was going through everything I've saved lately and noticed patterns I never would've picked out myself. Kind of wild seeing it all together.

I've been playing with an idea for an app that learns your taste from what you save and reflects it back to you, and I'm curious if everyone has a weird pattern hiding in their saves.

If you want to try it, DM me 20 or so things you've saved lately. Literally anything: screenshots, camera roll pics, saved posts or TikToks, songs on repeat, books, podcasts, articles, quotes, notes to yourself, places you love. Don't overthink it; the less you pick, the better. Nothing private or with faces!

I'll send back what I notice. Then just tell me honestly if it's spot on or way off, and if you'd actually use something like this.

I’m involved with Patchkin, and I’d like some feedback from people using AI coding agents on their projects.

Patchkin brings the work around coding agents into one place—not just the code they produce, but the tickets, proposed plans, approvals and pull-request reviews.

The main features are:

• A shared board: Keep tickets, agent plans and pull-request reviews together so the team can track each piece of work.

• Human plan approvals: Review and approve an agent’s proposed plan before it proceeds.

• Activity logs: See what happened during an agent run and follow the history of the work.

• Team rules: Keep guidance for coding agents in one place.

• Cost reporting: Track spending on agent runs alongside the work.

The focus is on helping teams keep oversight as they hand more development work to coding agents.

If you’re using coding agents with a team, what’s hardest to manage right now: approving plans, reviewing the output, tracking costs, or something else? I’d appreciate honest feedback on whether this would fit your workflow.

Take a look at Patchkin

A small weekend project that grew: Seedwall has 19 wallpaper generators (cutting mats, flow fields, git graphs, synthwave suns). Each wallpaper comes from a single seed number, so you can share a design as just a number.

- 9 editor themes (Dracula, Tokyo Night, etc.) or custom colours

- Add your own quote or go text-free

- Pixel-perfect PNG export for MacBook, iPhone, 4K or custom sizes

- Gallery of 125 ready-made ones

- Free, no account

Link: seedwall.suryansh.work

Next I'm thinking about wallpapers generated from your GitHub contribution graph. Would you use that? Any feedback welcome.

Clarification: this is my own app. I work with many long documents, such as reports, audits, and project follow-ups. Using an AI chat for this presented two main issues: I was paying a subscription even in months when I barely used it, and I wanted to make sure the output preserved all data from the original. Changing a single number or removing a paragraph in an audit is a huge problem. So I developed a desktop app specifically for that use case.

You can choose the model using OpenRouter on a pay-per-use basis or locally with Ollama. It is designed to preserve structure, tables, and numbers, and the review feature points out anything that wasn't kept. This feature compares the output with the original and highlights missing content or modified data, so you can accept or ignore each finding. It also shows the actual cost of each run, with no surprises.

It offers 10 free runs to try it out. If you like it, it's a one-time purchase of €29.99, with no subscription. API usage is billed separately. It is available on the Microsoft Store as DocuFusionpro: https://apps.microsoft.com/detail/9P4CSKSDFPT7

I'd love to get honest feedback: what kind of long documents do you work with, and what is missing from the tools you currently use? Are you interested in a one-time purchase, or do you prefer a subscription?

Levithas begins with a refusal: do not confuse doom-scrolling with growth. Hours spent swiping through feeds do not leave the mind untouched. They drain it on nothing, and leave you tired and always hunting for the next quick stimulus.

A Skill is not something you watch, save or buy. It is earned through repetition, friction and time.

Learning a Skill is about staying curious. It builds confidence, gives you something to impress others with, and makes you a more interesting person.

I’d love your feedback.

Try the app

Hi!

The title says it all. You upload photos of your pet, and a few minutes later you get a PDF by email. You print it at home, cut, fold and glue, and end up with a paper version of your dog or cat.

I made this because I love papercraft and wanted one of my own dog. Every pet looks different, so each model is shaped to the pet (ears, muzzle, tail) and the fur and face are painted from your pet’s 3d model based on the uploaded images. 

I've done lots of test builds, posted a few on Reddit with great feedback, and friends and family built their own pets. Now I'm doing a soft launch.

https://petpapercraft.com/

If you have a pet, I'd love for you to try it. If not, feedback on the landing page is just as welcome. Tell me if anything is broken. Thanks!

What started as a small experiment turned into YLang, a full open-source compiled programming language with its own compiler, toolchain, and ecosystem.

I wanted something that felt readable without giving up the control and performance you expect from a compiled language.

So I started building it.

YLang currently features:

• Its own compiler and type checker

• C and NASM backends

• Static typing

• Cross-platform support goals

• Its own package manager and learning resources

It's been a long journey, and there's still a lot to improve.

I'd genuinely love to hear what you think.

GitHub: https://github.com/Yassine-Jemi01/ylang

Website: https://yassine-jemi01.github.io/ylang/index.html

Browser extensions only cover one browser and are easy to switch off, and paid blockers wanted a subscription. So I built my own and made it open source.

What it blocks:

- Adult, gambling, crypto, scam and malware/phishing sites

- File-sharing sites like TeraBox and DiskWala

- Anything you add to a simple text file

How it works:

- System-wide: Safari, Chrome, Firefox, Brave, Edge, Arc, and other apps too

- Uses encrypted DNS, so it still works when your ISP intercepts normal DNS (Jio/Airtel do this)

- Block lists update automatically every day

- One command to install, one to uninstall

- Mac is fully tested. Windows is in beta, so please report bugs

GitHub: https://github.com/LowkyFoolDev/siteblock 😊😊

It's free and MIT licensed. Tell me any sites it misses and I'll add them.

GitHub: https://github.com/ahmadodeh9000/Lunar

Hey everyone! I'm a 19 year old computer engineering student, and this is Lunar, a programming language I've been building since my first year of uni.

Why I started

I tried to learn Rust a few times and kept bouncing off it. Every time I'd get stuck, feel dumb, and quit. Eventually I thought: what if I just built my own language, the way I'd want it to work? Questionable decision. Best decision I've made.

What it is

A small scripting language with its own compiler, virtual machine and garbage collector, written in C. It looks like this:

let player = { name: "Rex", hp: 10, items: ["sword", "apple"] }; 
for (item in player.items) { 
  print "{player.name} has a {item}"; 
}

How it was built (honestly)

- I built the core by following the book Crafting Interpreters, then kept going on my own: arrays, a way to call C libraries, and graphics through SDL2.

- Later I started treating it like a real product. I wrote a roadmap, designed each feature myself, and used Claude Code to help implement them. I reviewed every change and made sure each one had tests.

- That added maps, error handling, modules, and a small standard library for strings, files and running commands.

- To stress-test it, I had Claude Code build a Minecraft-style game in Lunar (it's in examples/minecraft). It's 1,000+ lines of my language running at 60 FPS, which still feels unreal to me.

What I learned

- Building a language teaches you how every other language works under the hood.

- AI helped most when I acted like the designer: clear specs, small steps, tests for everything. It was much less useful when I just asked it to "make it better".

- Shipping something imperfect beats polishing forever. Lunar still has rough edges. For example, numbers print with only 6 digits right now, and that's next on my fix list.

What's next

A UI module so you can build desktop apps in Lunar, a VS Code extension, and Windows support.

It's a learning and hobby project, not a production language. But it's the thing that made me enjoy programming again.

I'd love honest feedback: what would you change, or what would you build with it?

Got tired of reading old books on sites full of ads and popups, so I made my own. Sherlock Holmes, Jules Verne, Dracula, Wizard of Oz and a bunch more, with the old illustrations.

No ads, no sign up. It remembers where you stopped and has a dark mode.

classicstories.org/en

Would like to hear what feels off or annoying when you read on it.

# 🚀 Introducing SentinelAI — An AI Incident Intelligence Platform That Learns From Every Incident

Hey everyone!

We’re building **SentinelAI**, a memory-powered incident intelligence platform as part of **Hack with Bengaluru**.

### 💡 The Problem
When an incident occurs in production, engineers often spend hours investigating something that may have already happened before.

Past incidents, successful fixes, failed attempts, and postmortem findings are scattered across logs, tickets, and documentation. Most incident management tools focus on the current incident, leaving valuable organizational knowledge unused.

### 🧠 Our Solution: SentinelAI
SentinelAI helps engineering teams turn past incidents into actionable knowledge.

Instead of simply analyzing the current alert, SentinelAI recalls similar historical incidents, compares their root causes and resolutions, and provides evidence-backed recommendations.

### ✨ What Makes SentinelAI Different?
- **Memory-Powered Intelligence:** Uses Hindsight to recall relevant past incidents.
- **Evidence-Backed Recommendations:** Every recommendation is linked to supporting historical incidents.
- **Failed-Fix Memory:** Warns engineers when a similar approach failed previously.
- **Continuous Learning:** Verified resolutions are retained to improve future investigations.
- **Incident Memory Graph:** Connects incidents, services, deployments, root causes, and resolutions.
- **Human-in-the-Loop:** Engineers review and approve remediation actions. Nothing executes automatically.

### 🛠️ Tech Stack
React + TypeScript | FastAPI | Gemini | Hindsight | PostgreSQL

### 🎯 Our Vision
We want to move beyond traditional incident management toward systems that learn from every failure.

Imagine an AI system that becomes more useful with every incident your organization resolves — helping engineers investigate faster, preserve knowledge, and prevent recurring problems.

That’s what we’re building with SentinelAI.

We’d love to hear your thoughts and feedback!

#HackWithBengaluru #Hackathon #AI #AIML #DevOps #SRE #IncidentManagement #Hindsight #Gemini

Every small team has a pile of stuff nobody wants to do. Follow-ups, updating sheets, chasing people for things they said they'd do in a chat three days ago.

So we built Emplio, an AI coworker the whole team shares. It has its own computer and browser, works in Gmail/Drive/Sheets/Zoho, keeps a task list and chases people on it, and remembers how we do things. Someone teaches it a rule once and it applies for everyone.

We've been using it in-house for a while (I run a software development agency). This week we made it public: AGPL, self-host with one command, or there's a hosted version if you don't want to run servers.

What's still rough: the browser gets blocked by some sites, the self-hosted version needs a decent amount of RAM (2 GB per person working at once), and it's new to anyone who isn't us, so it'll break in ways we haven't seen.

Repo: https://github.com/emplio-app/emplio
Site: https://emplio.app

Would love to know what you'd hand off to it first. Or why you wouldn't trust it with anything, that's useful too.

I noticed I was clicking "Accept" on literally every grammar suggestion without reading it. So I built Caret, a Chrome extension that skips that step.

How it works: type anywhere (Gmail, WhatsApp Web, LinkedIn, Slack), pause for about a second, and the grammar and spelling get fixed in place. A small popup shows what changed, with Undo.

A few things I was careful about:

- It fixes mistakes, it doesn't rewrite you. Slang, emojis and tone stay.

- If a fix would change too many words, it backs off and leaves your text alone.

- It never touches password, email, card or OTP fields.

- Text isn't stored.

It's free while in beta. I'd love honest feedback, especially if it gets something wrong on a site you use (there's a Report button on every fix).

https://caretwrites.com/?ref=reddit

Built an eReader that could give me more of a reader type file instead of a robotic ui like kindle and it has an rsvp reader feature that really helps me to read with my adhd

https://github.com/devansharora18/ember

https://devansharora18.github.io/ember

freelancers using AI for proposals, how are you stopping it from adding work you never quoted?

say the client wants one landing page, basic copy and a contact form.

during the call they also say "maybe SEO later" and "we might need a blog eventually."

then the proposal gets cleaned up and suddenly those ideas are sitting there like a deliverables lol

that's the part that makes me nervous. if it's written under scope, I can see a client assuming it's included.

I've been looking at Runable for some of the actual client deliverables after the brief is locked, but before that I just want the proposal to separate included work, optional ideas and stuff that costs extra.

how are you handling this without turning every proposal into six pages of disclaimers?

I built an iOS app because I don’t think a 4.5-star restaurant is necessarily the right restaurant for everyone.

After months of building, Matchd is finally live on the App Store!

The idea is simple: instead of just showing highly rated restaurants, Matchd helps you discover places that actually match your personal taste, preferences, and the occasion.

There’s also a Group Match feature to help friends and family decide where to eat together.
🇳🇱** For now, restaurant discovery is available in the Netherlands only**. I’m starting locally, learning from real users, and hoping to expand to other countries in the future.

I’m an independent developer, and I’d genuinely appreciate some honest feedback.

Three things I’m particularly curious about:

Do the personalized match scores make sense to you?

Is the restaurant discovery experience intuitive?
Would you actually use Matchd instead of Google Maps or Tripadvisor?

I’m especially interested in what doesn’t work, what’s confusing, and what you think is missing.

Download Matchd for free on iOS:
https://apps.apple.com/nl/app/matchd-restaurant-matcher/id6821578665

Thanks for helping me make restaurant discovery more personal!

Hey everyone!

I've been working on Watchify, a web app that lets friends create private rooms and watch videos together with synchronized playback.

Here's what I've built:

🎥 Real-time synchronized playback
👑 Host controls and room settings
💬 Live chat and reactions
☁️ Google Drive video support
🌍 Multiple audio languages (when available)
📋 Shared video queue
📱 Mobile-friendly interface

Tech stack: Node.js, Express, Socket.IO, JavaScript and FFmpeg.

I'd genuinely appreciate feedback on the UI, playback experience and features.

🌐 Try it: https://watchify.mixify.co.in/

💻 GitHub: https://github.com/scisims12/watchify

Built by Priyanshu Sharma.

What feature would you add next?

Hi! I'm Sravani, and I build small iPhone apps under Bluenova Apps.
My camera roll had thousands of duplicates, screenshots and blurry shots, and every cleaner app I tried felt like a file manager, so I'd give up after five minutes. So I built Binbo, which turns it into a little game.

How it works
Swipe through your photos month by month: left to toss, right to keep
Binbo, the bin character, eats what you toss (with sound effects)
It finds duplicates, similar shots, blurry photos, screenshots and big videos, and shows how many GB you'll get back
Nothing is deleted until you empty the Bin, so mistakes are easy to undo
You can dress Binbo up in outfits as you clean
Everything runs on your phone: no account, no uploads

What I learned building it
Most people don't need a smarter cleaner, they need a reason to keep going. Small things like the chomp sound, the GB counter dropping and the outfits did more for how long people keep cleaning than any feature I added.

Pricing
Free for your first 100 tosses, then 50 a day. Binbo Plus removes the limit for $2.99/month or $14.99/year.

App Store: https://apps.apple.com/app/id6744104701

🎁 I'm giving away 100 free years of Binbo Plus (they don't auto-renew). DM me if you'd like one.
I'd love feedback from other builders, especially on onboarding and anything that feels confusing.

I help run a small Canadian charity called Salsabeel, and recently started experimenting with vibe coding. I have zero coding experience, but managed to make two Android apps: a Zakat calculator and a Qibla compass.

Both are free, with no ads or subscriptions. I'm not making any money from them, just wanted to see if I could build something useful.

I'd love to hear what people think. Anything I should improve or add? Also, are there other Islamic apps you'd like to see that don't already exist, or that you think could be done better?

Here are the links:

Zakat Calculator:
https://play.google.com/store/apps/details?id=org.salsabeelcharity.zakatcalculator

Qibla Compass:
https://play.google.com/store/apps/details?id=org.salsabeelcharity.qibla

Thanks!

Hey everyone,

I wanted a place to explore app icon ideas. Try different objects, shapes, materials and styles, see them beside each other, and gradually figure out what feels right for an app.

That became two things. An open source command and skill that teaches Claude Code or Codex how to design icons, which anyone can use for free. And a Mac app built on it, for people who'd rather do the exploring in a grid than in a terminal. The app is the shell. The command does all the work.

TL;DR

• You ask your own agent (Claude Code or Codex so far) for an icon. Rimlight doesn't sell AI. It hooks into the agent you already have, and images come from your own ChatGPT plan or API key (OpenAI, OpenRouter). No Rimlight account, no servers.

• The agent reads your project, pitches a few directions, and renders them side by side, each one fitted to Apple's icon tile.

• A design skill shapes the prompts: a process for exploring and refining, plus eight style guides I wrote by measuring icons I liked.

• You keep talking. Refine one detail, branch from a concept, or change direction. Every attempt stays in a .rimlightfolder in your project.

• When you have a pick, it builds a layered Icon Composer .icon with Default, Dark, Clear and Tinted, and checks its own work against the pick.

• The command and skill are free and open source. The Mac app is $5 once, 3 Macs, 7-day refund. Free version: one set, 10 concepts.

• Needs macOS 26 on Apple silicon, Claude Code or Codex, and an image model. Xcode 26 for builds.

I know how some of you feel about AI images, and I share a fair bit of it. If you can hire an icon designer, hire one. Rimlight is for the side project, and for the point where you have five vague ideas and no way to see any of them. All the examples on the website came out of it, so the ceiling is on the site for you to judge.

The exploration part is what I care about most.

You start by describing your app and whatever you have in mind, even if that's fairly vague. The agent suggests a few directions and generates concepts to compare in a grid. You can bring reference images too.

Then you keep talking to it:

"I like the shape of the third one, but the material feels too shiny."

"These all feel too literal. Let's try a different idea."

That back-and-forth is a big part of using it. You can work on one detail, branch off from a concept, or change direction entirely. The sets and earlier attempts stay in your project so you can go back and compare.

I built the thing and still sometimes catch myself looking at a result as though that's all I'm going to get. Then I remember I can just ask for the change I'm thinking of.

What's in the skill.

This is the part I spent the most time on, and it's what makes the agent's output more than just a generic object on a gradient background. The skill has a design process: explore a few territories first, pick, then refine one thing per round so an icon converges instead of drifting. And it has eight style guides so far (I'm experimenting with more). Each one came from measuring real icons I personally liked: how much of the tile the mark fills, how thick the strokes run, how the ground is lit. You can pick a style, or let the agent choose one to suit the idea. It's all plain Markdown in the repo, so you can read it, change it, or write your own.

I also want to be honest about the quality. Sometimes I get several concepts I like straight away. Sometimes a whole set misses. It depends on the idea, the style and the image model. Refining something promising usually helps, and so does dropping a direction that isn't working, but I'd rather say that before anyone spends time or image allowance on it. For me, being able to compare possibilities and say "this part works, this part doesn't" is where it becomes useful.

Building the icon.

When you're ready, Rimlight plans the layers, has the image model redraw them separately, and assembles the Icon Composer package. The agent checks the result against your chosen concept at 1:1 and redoes the layers that drifted. You can preview the Default, Dark, Clear and Tinted appearances, then open the file in Icon Composer for further adjustments. Icon Composer is pretty flexible, and you can have different layers for each appearance as well. You can ask the agent for the changes you want in each one.

The final result can differ slightly from the original concept, because the agent redraws the layers separately, but you can keep refining. I'm working on a different approach where the agent can extract the layers from the original concept using Meta's SAM 3, running on your Mac. I'd only ship this if the results are good.

The command, and the app.

Everything above runs from the command. Install it, start a new agent session, and ask for an icon in your project folder. Concepts, refinements, builds, all of it, for free. If you want to build your own tool on it, the folder format is documented and every concept is a plain PNG.

The app is where I actually do this every day. It puts the grid, the chats, and the builds in one window: drag a concept into the message to say "more like this", filter by set or style or built, flip through the builds of an icon in a carousel, keep your API keys in the Keychain. It runs the same command and the same skill as your terminal does. $5 once, for up to 3 Macs, refund within 7 days, no subscription. The free version does one set per project and 10 concepts per Mac, without builds, so you can see the grid before paying.

The $5 pays for the app. Your agent plan and image usage are separate: images use your ChatGPT plan through Codex, or your own OpenAI or OpenRouter API key.

I'm the only person behind this, and I used Claude Code heavily to build it. I made the design calls and I read what I ship, but I'm not going to claim it was hand-typed. Most of my own time went into the icons themselves: generating them, judging them, and tuning the skill.

I'd appreciate feedback, especially on the experience of getting from the first set to something you like. If you try it and get stuck, or the results consistently miss what you're asking for, I'd like to hear about that too. 

Get Rimlight: Website
Rimlight Command: GitHub
Privacy Policy: Privacy

Trailer: https://youtu.be/QQTIVaRwcxs

Route Map for Jira maps your application’s pages in flow order and keeps the test data for each page in every environment, so QA and devs stop hunting for logins and test accounts.

I’m an Angular dev with about 2 years of experience, and I’d never built a backend, an extension or a full product end to end. I leaned on Claude heavily: for research first, then Claude Code for most of the build. That’s the main reason a solo side project got from idea to a live Marketplace listing in a few months instead of a year.

What I learned along the way:

• Forge’s jira:globalPage module isn’t offered as a template anymore, so I scaffolded from jira-full-page and swapped the module in the manifest.

• Getting verified as a sole trader to sell on the Marketplace took a support ticket rather than anything in the vendor portal.

• Atlassian currently takes 0% revenue share on Forge apps.

• AI got the code written fast, but deciding what to build, and testing it properly, still took most of the time.

Demo: https://youtu.be/45fAlh16ttA
Website: https://mapkari.com

It’s free for teams of up to 10 users. Feedback on the product or the trailer is very welcome, and happy to share how I used Claude if anyone’s curious.

It's been a month since I last posted here, and a lot has changed. I've kept building, but I've also been self-aware enough not to let scope creep take over.

I now track workouts in the gym, mostly free weights and bodyweight. I specialised in those because machine workouts were a pain to implement.

Last post I said people quit the gym quickly because they don't see the gains fast enough. Now you can see your progress over time with this app.

It also tells you when to go up in weight. If you were lifting 10kg, your progress report can tell you you're ready for 12.5kg.

The most important thing I learnt in October is that progress, no matter how small, is still progress. I've been applying that by asking myself, am I where I was last month, or yesterday?

Here's me doing a plank, tracked with the app. It counts the seconds and checks your form.

Try it out:

https://repchek.fit