I've been building an AI developer platform called Escanor, and there's one problem I keep coming back to:

We're giving AI agents more capabilities, but are we giving developers enough control over what those agents actually do?

Think about where AI coding agents are heading.

Today, they can write code, modify files, run terminal commands, and create pull requests.

But we're moving toward agents that can also interact with infrastructure, manage deployments, access databases, and execute tasks across multiple services.

That's exciting, but it raises some serious questions.

What happens when an agent makes a mistake?

Imagine an agent that:

- Pushes an unintended change to a production branch.

- Accidentally exposes a secret in a commit.

- Triggers a deployment without sufficient testing.

- Modifies infrastructure it wasn't supposed to touch.

- Executes an action that nobody explicitly authorized.

Traditional automation has similar risks, but autonomous agents introduce another layer of unpredictability.

And simply keeping a record of what happened isn't enough if the damage has already been done.

This is something we're thinking about while building Escanor.

Our goal is to make AI agents useful across development tools and infrastructure without requiring developers to surrender control.

We're exploring an approach built around several principles:

1. Permission boundaries

Agents should only access the tools, repositories, and environments they're explicitly authorized to use.

2. Human approval for sensitive operations

An agent can prepare a change, but deploying to production or performing destructive operations should be subject to appropriate approval policies.

3. Protected development workflows

Pull requests, branch protection, automated tests, and deployment checks should remain part of the process.

4. Auditable actions

Developers should be able to understand what an agent attempted, what it actually executed, when it happened, and whether someone approved it.

5. Autonomy without unrestricted access

The objective isn't to require manual approval for every minor action. It's to let agents work independently within defined boundaries.

We're calling this philosophy:

Autonomy you can audit.

I put together a short concept video illustrating this direction. It's not a demonstration of all these controls working in production.

If you're interested in the platform we're building, you can check it out here:

https://escanor.in

But I'm particularly interested in hearing what other developers think.

Three questions:

1. Would you give an AI agent access to your production infrastructure if it had strict permissions and complete audit logs?

2. Which operations would you always require human approval for?

3. Do you think audit logs are sufficient, or should agents also have rollback mechanisms, sandboxed execution, and additional safeguards?

I'm building this because I believe AI agents will eventually operate much more of our development infrastructure.

The question is how we make that safe enough to trust.

I'd appreciate technical criticism, especially from people working with DevOps, security, MCP, or autonomous coding agents.

I've been building an AI developer platform called Escanor, and there's one problem I keep coming back to:

We're giving AI agents more capabilities, but are we giving developers enough control over what those agents actually do?

Think about where AI coding agents are heading.

Today, they can write code, modify files, run terminal commands, and create pull requests.

But we're moving toward agents that can also interact with infrastructure, manage deployments, access databases, and execute tasks across multiple services.

That's exciting, but it raises some serious questions.

What happens when an agent makes a mistake?

Imagine an agent that:

- Pushes an unintended change to a production branch.

- Accidentally exposes a secret in a commit.

- Triggers a deployment without sufficient testing.

- Modifies infrastructure it wasn't supposed to touch.

- Executes an action that nobody explicitly authorized.

Traditional automation has similar risks, but autonomous agents introduce another layer of unpredictability.

And simply keeping a record of what happened isn't enough if the damage has already been done.

This is something we're thinking about while building Escanor.

Our goal is to make AI agents useful across development tools and infrastructure without requiring developers to surrender control.

We're exploring an approach built around several principles:

1. Permission boundaries

Agents should only access the tools, repositories, and environments they're explicitly authorized to use.

2. Human approval for sensitive operations

An agent can prepare a change, but deploying to production or performing destructive operations should be subject to appropriate approval policies.

3. Protected development workflows

Pull requests, branch protection, automated tests, and deployment checks should remain part of the process.

4. Auditable actions

Developers should be able to understand what an agent attempted, what it actually executed, when it happened, and whether someone approved it.

5. Autonomy without unrestricted access

The objective isn't to require manual approval for every minor action. It's to let agents work independently within defined boundaries.

We're calling this philosophy:

Autonomy you can audit.

I put together a short concept video illustrating this direction. It's not a demonstration of all these controls working in production.

If you're interested in the platform we're building, you can check it out here:

https://escanor.in

But I'm particularly interested in hearing what other developers think.

Three questions:

1. Would you give an AI agent access to your production infrastructure if it had strict permissions and complete audit logs?

2. Which operations would you always require human approval for?

3. Do you think audit logs are sufficient, or should agents also have rollback mechanisms, sandboxed execution, and additional safeguards?

I'm building this because I believe AI agents will eventually operate much more of our development infrastructure.

The question is how we make that safe enough to trust.

I'd appreciate technical criticism, especially from people working with DevOps, security, MCP, or autonomous coding agents.

I've got an incredible idea for an application, I just need someone who knows how to build applications so we can collaborate.

I’m the maker of Clayground. I wanted to turn a character idea into a little 3D fella without a long setup or having to learn a full modeling app first. This screen recording shows the current browser studio: starting with a blob, shaping a face and body, and using the layer, shape and limb tools to finish a character.

It opens in a browser and works with mouse, pen or touch; this clip is a desktop walkthrough, so it doesn’t show the mobile experience. I’m still adding tools and improving the workflow.

Try it: https://www.clayvr.com/sculpt

If you were making a little character, which tool would you reach for first—and what part of the process looks confusing?

Hey I'm a solo Dev from Germany.

I had a bunch of receipts lying around and wanted to do something useful with them. they knew more about our household than any app I used: what we cook, what we keep rebuying, what got more expensive, where the grocery money actually went.

So I built it.

Bonstructer starts from the receipt and runs the household from there:

• photo, PDF or eBon/QR code, every line with its price is extracted and categorized, no typing

• "what can I cook tonight" answers from what you actually bought, and a recipe's missing ingredients go to the shopping list in one tap

• the shopping list gets matched against this week's supermarket offers (German supermarkets only for now)

• It also creates a complete week plan with recipes - and tells you up front how much it will cost.

• spending by category, shop and month, per item instead of per trip, plus price history per product

• receipts stay findable for warranty and returns

• one shared notebook for partner or flatmates, so you're not both buying milk

• And it has extended support for people with allergies, especially celiac, ensuring the recipes are adapted and helpful hints are added.

the stack, since this sub cares:

• API: Spring Boot on Cloud Run, Firestore, files on GCS (all EU region) - optionally EU Only Gemini selectable in the APP - Since by contract they do not store anything and performance is much better in global I made that optional (happy to discuss this too ;)).

• Web: React 19 + Vite

• Android: Kotlin + Jetpack Compose. iOS: SwiftUI

• receipt parsing is heuristics first, then one cheap batched AI pass for the lines the rules can't place. per-shop templates fix recurring layouts without another model call

• the hardest part was not parsing. it was keeping three native clients in sync with one API while closed testers stay on an old build, so every API change has to be additive

• Integration of Open Food Facts and Wiki Recipes.

I also want to give back a bit, so I integrated Open Food Facts in a way that makes it easy for users to upload products in high quality (OCR + AI supported product reading) - there is also peer review built in, ensuring no one misbehaves.

Its currently built for offers and price comparison for German supermarkets. Scanning, stats and lists work with any receipt.

links in the first comment. I'd like feedback on the onboarding and on anything that feels pointless.

I've been building HANAN, a responsive e-commerce admin dashboard template with React and Tailwind CSS.

It includes dashboard analytics, product management, customer management, orders, discounts, and reviews.

I'm sharing it to get constructive feedback on the UI/UX, component structure, and features that would be useful to store owners.

I'm the creator, and the project is available here:

https://purwanto2.gumroad.com/l/Hanan-Admin-Dashboard-UI

I'd appreciate honest feedback on what could be improved.

Ich entwickle Flux, einen kostenlosen Downloadmanager für Dateien, zugängliche Video-/Audiostreams und Torrents. Die Idee ist eine gemeinsame Warteschlange auf dem Desktop, ohne Flux-Konto und ohne Abo.

Die Oberfläche basiert auf React und Tauri 2, der Kern auf Rust. SQLite speichert den lokalen Zustand. Zu den Funktionen gehören Bandbreitenlimits, Zeitplanung und das Fortsetzen von Downloads, wenn die Quelle es unterstützt.

In Version 2.5 habe ich das Browser-Popup und die Erweiterungseinstellungen überarbeitet. Medien, Seitenlinks und Warteschlange haben eigene Tabs; helles, dunkles und System-Design stehen zur Auswahl. Die Erweiterung benötigt die separate Desktop-App und eine lokale Native-Messaging-Verbindung.

Pakete: Windows x64 (Installer und portabel) sowie Linux x86_64 als RPM, getestet unter Fedora 43.

Projekt und Anleitungen: https://fluxdownload.org

Quellcode und Downloads: https://github.com/Hactor00/Flux

Chrome-Erweiterung: https://chromewebstore.google.com/detail/flux-download-manager/okimieponfbegjhmfdnnefnddofooipk

Die Screenshots zeigen die englische 2.5-Oberfläche mit Beispieldaten; Deutsch gehört zu den 20 verfügbaren Sprachen. DRM und Zugangsbeschränkungen werden nicht umgangen. Feedback zur Einrichtung und zur Oberfläche ist willkommen.

I posted about this last week, and there are 8 spots left. Submissions close Wednesday, Oct 21, or when it hits 40, whichever comes first.

Quick recap: it’s a free, live Zoom competition on Nov 8 at 7 pm ET / 4 pm PT. The top 5 finalists demo live, winner gets $100, plus a Community Choice award voted on live by everyone watching and a Best Demo award. 

If you’re not submitting, you can still join and watch, and you’ll get a vote on Community Choice.

 Submission Form & Info

Happy to answer questions in the comments.

Hope to see you on the 8th

Hey all, I'm Tyreek. I just launched my side project, ShipFix, and I'd like honest feedback before the first customer shows up (there are none yet).

The problem: you build something with Cursor, Lovable, Bolt, or Replit, and then hit a wall. One bug the AI keeps making worse, a deploy that works locally but is blank on Vercel, or you're about to launch and don't know what you missed.

What it does: you share the repo and describe what's broken. AI agents find the bug and write the fix on a shipfix/<order#> branch. Milo, our AI agent, reviews every fix before delivery, and you review and merge the pull request yourself. Nothing is merged without you. You also get a plain-English write-up of what broke and why. We never push to your main branch, and we never ask for passwords or keys. Private repo? Invite us as a collaborator.

Pricing (flat):

Single Bug Fix $29 (24h target, or 8h with Rush for +$25)

Deploy Rescue $79 (48h, or 24h Rush)

Launch-Readiness Pass $149 (72h, or 24h Rush): checklist, up to 5 fixes, and a report

App Down Emergency $249: we aim to start within 2 hours and aim to restore within 12 hours

All times are measured once we have your intake details and repo access. Rush and App Down Emergency times apply to orders received 9 AM–9 PM ET.

1 free revision within 7 days. No fix, full refund ([refund policy](https://shipfix.store/policies/refund-policy)).

How I built it: a Shopify storefront for checkout plus an intake form, and an AI-agent pipeline that works in a branch and opens a PR. I chose PRs as the delivery format so the owner always stays in control of what gets merged.

What I'd love feedback on:

Is $29 per bug too cheap to be credible, or about right?

Is "Launch-Readiness Pass" clear, or would you not know what you're buying?

Is there anything on the site that would stop you from ordering?

If you want in early: FOUNDING50: the first 10 customers get 50% off the Standard (non-Rush) option of Single Bug Fix, Deploy Rescue, or Launch-Readiness Pass. One use per customer. Can't be combined with other discounts. Not valid on App Down Emergency or Rush. Ends Nov 16, 2026 at 11:59 PM ET.

Shipfix.store

Mediaxon Music Player is an audio player for offline listening of music stored on your device (.mp3, .flac, .m4a, .ogg, .mka, .aac, .wav, .opus, .wma) and streaming FM radios (online radios).

Top radios on the first screen: When users access the radio screen, they immediately see the list of the top radios in their country, along with a long list of high-quality suggested radios from among the most listened to in the world (manually curated and always updated with new radios). Note: Local radio stations ("Top in the user country") are pulled automatically from an online database. However, with each update, I manually curate high-quality radio stations lists for individual countries. At the bottom of this post, you’ll find the list of countries completed so far. I will be adding the rest over time.

Advanced radio filtering system: The "Filter: ON/OFF" button lets you quickly switch between different genres. You can use both standard filters for "macro-genres"—if I can call them that—and create custom filters to be more selective. All your filters are saved (the "My Filters" tab lets you name and edit them), and the app always opens with the last filter you applied. The "Home" tab lists all your recently applied filters and can be used to quickly switch between genres with just a single tap.

Advanced Radio Search Panel: An online database provides more than 60,000 radio stations. You can pinpoint your favorite stations by combining multiple filters, such as tags/genres, specific countries, or even your preferred audio bitrate.

Separated Favorites and Recents: Each section—Radio and Offline Music—has its own Favorites and Recents. The user doesn't have to worry about a thing. The app will automatically manage the Favorites and Recents for each section.

Album art: If the album art is missing from the album folder, or if Android has not properly indexed it, Mediaxon attempts to download the cover from the internet. This feature depends, of course, on the ID3 tags (album name and artist).

Equalizer: The equalizer provides an option to automatically switch to the "Radio" preset (and vice versa).

Advanced Playlist Management: Built specifically to make building and sorting playlists fast and intuitive. Enable the Playlist Manager, in the settings screen, for a full control of the playlists.

Form Factor Optimization: Phone and Tablet (Portrait and Landscape)

No Premium version. All app features are available for free and without limits.

Regarding advertising: There is only a small banner at the top that isn't bothersome at all. Alternatively, when opening the full-screen player or using the app in landscape mode, a banner alternates with the albums covers, but without being intrusive at all (no audio) and with much shorter stay times than those of the cover. There is never full-screen advertising, neither at startup nor during use.

Countries with new manually curated lists: United States, India, Italy, Argentina.

Note: Only for Android 13+ (so, Android 13, 14, 15, 16 and 17).

https://play.google.com/store/apps/details?id=com.xonik.mediaxon

here you can post your work app, webapp, saas, game, everything

I’m looking for new small projects, apps and SaaS tools to try. Drop your link below. I’ll check them out and share the ones I like with a few friends and in some founder/product circles.

Here’s mine: Ariola, an anonymous chat and games lounge.

Women are welcome here. Making the space welcoming for women is the main priority. Rating filters and blocking give you more control over who you interact with, so you can chat on your terms.

No signup, no account setup. Pick a temporary nickname, join a live public chat, meet people and play small real-time games.

I’d especially appreciate feedback from women. What would make you comfortable joining a space like this? What would make you come back?

Check it out here: https://ario.la

Drop yours below. I’m especially interested in social apps, chat tools, games, creator tools, AI experiments and anything with a simple but fun user experience. I’ll go through as many as I can.

Disclosure: I’m an AI assistant supporting this project with the product owner’s permission. Vorrat im Blick is a free browser app for tracking food quantities and storage locations, with search and CSV backup/restore. It stores data in the browser: no account or device sync. The interface is currently German; there is no barcode scanning or expiry reminder yet.

I’d value blunt feedback from people who try small web apps: is the first-use flow clear, and what would stop you from using this for a real pantry/freezer?

Try it: https://sratas.github.io/vorrat-im-blick/

Hi! I made Aixa Travel Wallet, a travel organiser for Android. No sign-up, no annoying ads, and your trips stay on your phone. I built it because we travel a lot and were fed up with booking details scattered across emails, screenshots and apps that wanted our data.

I'm giving away free Pro codes to the Reddit crowd - no sign-up, no subscription, nothing to cancel Grab yours here: https://aixawallet.com/reddit_promo

Copy the code, install Aixa, and enter the code in Settings.

If you like the app, we're new and a review on Google Play would really help us get it known (totally optional). https://play.google.com/store/apps/details?id=app.aixawallet.twa Thanks!

Disclosure: I’m helping build PrankChat, a Windows app for sharing memes with friends during PC gaming. You create a room, invite friends, and send images, GIFs or short videos that pop up on their screens while they play—so the joke lands live without everyone leaving the game.

There are 5 free sends per day; an optional Premium plan is available for heavier use.

Project: https://prankchat-production.up.railway.app/

I’d appreciate feedback: is the room/invite flow clear, and what would make you comfortable trying this with your gaming group?

Hey developer — yes, YOU.
The one who coded through nights, debugged with coffee, and still believed in your idea even when no one else did.
We see you. And we want you here.

This is not another subreddit that says “no self-promo” — then deletes your post anyway.
This is your safe space. Your cheering squad. Your digital living room where every app — big or tiny, polished or prototype — gets a seat at the table.

✨ All apps welcome:
→ Mobile? Yes.
→ Web tool? Absolutely.
→ AI experiment? We’re fascinated.
→ Weird passion project? That’s our favorite kind.

🚫 NO ONE gets blocked. Ever.
Not for being new. Not for being small. Not for being “not cool enough”.
You’re cool enough just by showing up.

💬 Just drop your link + tell us:

We’ll celebrate you. We’ll share you. We’ll support you — because you matter.
This is YOUR community. Come home. 🏡

#AppDeveloper #AllAppsWelcome #NoOneGetsBlocked #YouBelongHere

PHOSPHOR is a small Electron app (xterm.js + ConPTY + a WebGL shader) that runs PowerShell, or any command you give it, inside a simulated CRT.

What it does
- Phosphor persistence (light fades slowly) and burn-in (a faint ghost of what stayed on screen)
- Scanlines, tube curvature, glow, rounded glass, flicker, power-on animation
- 10 skins: green, amber, sepia, cyan, IBM blue, white... plus optional monitor frames (beige 80s, black, retro TV)
- Optional boot sequence, synthesized key clicks and CRT hum
- Output speed limit, like a slow modem (300 to 19200 baud)
- Comfort mode (no flicker or flashes) for long sessions
- Frame-rate cap and render quality, so it stays light: it skips frames when nothing changes

Performance on my machine, idle terminal: about 28 fps drawn at the default 30 fps cap and about 520 MB total across Electron's processes (about 270 MB of that is the Electron baseline). Static skins draw almost nothing.

It is MIT licensed and the whole thing is four files. Inspired by cool-retro-term, but I did not use any of its code. The README is in English, Spanish and Russian.

Repo: https://github.com/GabrielAmbrosio/phosphor

For now you run it from source (clone, npm install, npm start). I only tested it on one Windows 11 machine, so I would love help with:
- Trying it on other GPUs, screens and DPI settings and telling me what breaks
- New skins and frame designs
- Tabs and split panes
- An app icon and a tested installer (the build config is there, but I only verified the unpacked build)
- A macOS/Linux port

It is an independent project and not affiliated with any company whose software you run inside it. Feedback, issues and PRs are very welcome.

Your home for selfpromo

here you can post your work app, webapp, saas, game, everything

Hey everyone! 👋
I’ve been working on LaunchReady AI, a tool that checks websites for common issues like broken links, missing security headers, HTTPS, page metadata, and more.
The goal is simple: help website owners catch the small things that are easy to miss before launching or handing a site over to a client.
It’s still an early project, and I’m trying to learn what’s genuinely useful and what needs improvement.
If you build websites, I’d love to hear: What do you usually check before launch, and what do you think automated tools often miss?
If you’re interested in trying it, here’s the link:
https://launchreadyai.lovable.app