[tombert]

It's not a terrible idea, but I'm not sure how that would work logistically.

When I use Codex to do vibe coding stuff, I don't usually have one big prompt, I usually have it do small things piecemeal and I iterate with it later. Maybe I'm using it wrong but it tends to be more "conversational" and I think that would be harder to share, especially considering I'll do things over dozens of sessions.

I suppose I could keep an archive of every session I've ever opened with Codex and share that, but thus far I haven't really done that.

Granted, I don't really share my stuff with "Show HN".

[PacificSpecific]

That's how I do it too. I haven't checked (and can't right now as I'm not at work) but does codex not have a feature that lets you download your codex chat logs? I would certainly hope so...

[dang]

I'm not sure how it would work. That would have to be figured out, so we would start with the simplest implementation that is not nothing.

The limitations you're describing seem mostly to have to do with tooling, rather than objections in principle.

[tombert]

I certainly don’t disagree with the idea; AI stuff can be so low-effort that requiring some how-to makes sense.

I am just not 100% sure how it will be implemented. Maybe even a high-level overview of roughly what the conversation looks like.