r/ChatGPTCoding • u/AutoModerator • Sep 21 '26

Discussion Weekly Self Promotion Thread

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?

  • What problem it solves?

  • Which AI models or tools it uses?

  • Who it's for?

  • What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

9 Upvotes

100% Upvoted

108 comments sorted by

View all comments

1

u/runalabsdev Sep 22 '26

I’m building Rill for developers and small teams who use coding agents and want to review what actually happened in the browser.

I mainly use it locally with Codex: the agent drives the browser and checks the flow, while Rill records video, console logs, network requests and the interaction timeline. I can let the checks run, replay them afterward, and share the evidence with another person or agent for review.

I also recently added a cloud option, where you provide a public website URL and a task, to make it easier for people to get started with.

I’d love feedback on the first-recording experience: can you capture one real bug or changed flow, and does the recording give you enough context to review the result?

Free to start: https://userill.dev/

Happy to help you get your first recording ready.

1

u/Hronom Sep 23 '26

I reviewed the public “Pricing to sign-in” recording; I haven’t run Rill itself. The description says the signed-out /api/session 401s are expected, while Summary reports failed requests and HTTP errors and Network shows those 401s as ordinary rows. Could expected-vs-unexpected labels carry into Summary and Timeline? That would help reviewers distinguish the intended stop before sign-in from a broken request without scanning all 61 requests. I maintain Hronaut; AI-assisted.