Won the Vibe Code Camp challenge ๐
The challenge: do something cool with an 8-hour transcript.
So I built an app to grab speaker workflows, search insights, copy agent skills, and quiz yourself
Appreciate the free year @danshipper ๐ค
Link: https://t.co/orvhjBQAra
We got over 50 submissions for the Vibe Code Camp challenge. Wild range of projects.
The winner: @RisonSimon turned our 8-hour livestream into a full interactive learning app.
Searchable insights. Speaker workflows. Copy-paste agent skills. Even a quiz.
All vibe coded. Free year of @every is yours ๐
I avoided worktrees for months because they seemed unnecessarily complex.
Turns out I was wrong.
Now I can test 3 different product flows at once without touching my main codebase.
Here's how I got worktrees working with @convex in codex. (works with claude code too)
I started by asking codex to research the setup. Told it to check both codex and convex docs and come up with a plan.
Codex created a script for setting up the worktree, and copying over the relevant env vars.
First hiccup: codex was using outdated convex cli commands. I had to manually copy the new commands from convex's changelog and ask codex to use that.
Without this, it created overly complicated scripts.
Second hiccup: I didn't realize I had to manually select the new environment for each worktree. Once I figured that out, the setup script ran automatically.
For convex specifically, I needed to set a specific node version for it to run locally. But that was it.
I also set up portless by @ctatedev and Vercel Labs so that each worktree has its own website.
It works beautifully. Just need to create a branch in the worktree, and portless will create a URL with that branch name.
Another reason worktrees worked for me is using @better_auth .
Because each worktree can run fully isolated, each one keeping its own login state in the local convex. Itโs beautiful.
Now I can test different product concepts without touching my main deployment.
Everything runs locally. No extra costs.
Worth the setup time.
@embirico Will try it out.
One more thing, in the archived chats view in codex mac app, it doesn't show the title of the chat, making it harder to find it. also need search & folder level grouping for archived chats.
Just had a holy shit moment with codex computer use.
I asked it to archive all newsletters from my Missive inbox. Took some time but got through everything without errors.
I've tried multiple AI inbox tools before. None come close.
This uses the actual app on my mac. Way more powerful than I expected.
Just had a holy shit moment with codex computer use.
I asked it to archive all newsletters from my Missive inbox. Took some time but got through everything without errors.
I've tried multiple AI inbox tools before. None come close.
This uses the actual app on my mac. Way more powerful than I expected.
I don't get the Opus 4.7 hate.
Ya, it's more expensive with the new tokenizer. But performance wise? It's solid.
I've only used it in @cursor_ai till now and it's been fine.
Maybe it's just a claude code issue.