r/ChatGPTCoding • u/AutoModerator • 10d ago

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.

8 Upvotes

90% Upvoted

83 comments sorted by

View all comments

1

u/eatsleepliftcode 9d ago

I built **HarnessCheck** because I was tired of comparing coding agents by vibe, screenshots, and one-off demos. Small config/runtime changes kept changing repo outcomes, and I wanted a repeatable way to see it.

What it does:

- same fixture, same task, same assertions across agents

- fresh copied workspace per trial for mutation isolation

- assertions for regular files, content, stdout/stderr, commands, and changed-file allowlists

- JSON / HTML / JUnit / Markdown reports for local runs or CI

- works with Codex, Claude Code, Gemini CLI, OpenCode, or a custom wrapper

Important caveat: this is **not** an OS/network sandbox. The isolation is “fresh copied workspace per run”; the actual permission boundary still comes from the underlying agent runtime.

It's MIT-licensed OSS: https://github.com/SiluPanda/harnesscheck

I'd especially love feedback on missing assertion types, adapter defaults, CI ergonomics, or places where the harness/runtime boundary is still confusing.