2h ago

Systems engineer Yacine proposes distributing software by piping text prompts from `curl` directly into Codex

Nick Dobos suggested using a `codex://` URL scheme instead.

——0——
Original post
OPkache#488kache@YACINEMTB

I think the best way to distribute my software is to tell people to curl a prompt that literally pipes it into codex with dangerously approve that would be basically 0 friction..

11:41 AM · May 29, 2026 View on X
POSTkache#488kache@YACINEMTB

this but instead of piping into sh you pipe a prompt into codex dangerously skip permissions

6:48 PM · May 29, 2026 · 2.7K Views
REPLYkache#488kache@YACINEMTB

you can see these things coming for like, 4 years, but when they happen it still feels like getting punched in the stomach

kachekache@yacineMTB

I think the best way to distribute my software is to tell people to curl a prompt that literally pipes it into codex with dangerously approve that would be basically 0 friction..

6:41 PM · May 29, 2026 · 8.5K Views
6:42 PM · May 29, 2026 · 2.1K Views
REPLYNick Dobos#1894Nick Dobos@NICKADOBOS

@yacineMTB Try this:

codex://prompt?=Hello

kachekache@yacineMTB

I think the best way to distribute my software is to tell people to curl a prompt that literally pipes it into codex with dangerously approve that would be basically 0 friction..

6:41 PM · May 29, 2026 · 8.5K Views
7:08 PM · May 29, 2026 · 595 Views
Systems engineer Yacine proposes distributing software by piping text prompts from `curl` directly into Codex · Digg