Загрузка видео...

Не удалось загрузить видео

На главную

“Codex from the Shitter” 🚽 That's the core idea of my latest side project. It syncs Codex sessions between CLI and phone, so I can pick up where I left off anywhere. Built on Codex App Server. Runs entirely locally, no servers involved. Remote access via Tailscale.

42,271 просмотров • 3 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Higgsfield MCP + Codex is f*cking wild 🤯 Here's how you can generate 17 on-brand Amazon listing images by uploading one product photo. One plain-English prompt, zero manual generation. All inside the Codex app. Perfect for DTC brands and agencies who need production-quality product shots without booking a shoot or briefing a designer. If you're prompting image generators one shot at a time: Tweaking the lighting, adjusting the angle, re-running generations until something usable comes out. This combination eliminates the entire loop: → Install the Higgsfield CLI and add the skills to Codex in 5 minutes → Drop one product photo into your project folder → Type one prompt: "make me Amazon listing images — hero, lifestyle, detail, angles" → Codex interprets it, Higgsfield skills fire automatically → Finished images land in an organized folder on your machine No manual prompt tweaking. No re-running generations. No briefing a designer. What you get: → Production-quality listing images from a single product photo → Lighting, angles, and reflections handled automatically → Everything organized into folders locally on your machine → A pipeline that runs in minutes, not days Setup takes five minutes. I put together a full guide showing the exact install, the skills setup, and the prompt to run it yourself. Want it for free? > Like this post > Comment "CODEX" And I'll send it over (must be following so I can DM)

Mike Futia

12,833 просмотров • 2 месяцев назад

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 просмотров • 1 месяц назад