Scott Barden

@dkundel @CastAsHuman my wife installed codex in "everyday" work mode. too technical still: e.g. prompting to install git CLI, asking for permissions remove node_modules (after asking codex to produce a spreadsheet from photos of handwritten notes)

@CastAsHuman What can we do to make it even better?

I love Codex so, so much!

@thsottiaux With recent app updates I don't see running processes as easily Also can no longer get the option to open folder in an IDE if it's not a repo (mentioned the elsewhere just now). In my case the folder is a parent of multiple repo subfolders

It’s the little things that matter, what are some small papercuts you have noticed in Codex? We’ll fix as many as possible in the next week.

@dinkomarinac @remi_rousselet Same

@remi_rousselet Have always used it, just not with Riverpod. I do use it with Retrofit, freezed, json_serialozable, envied.

#Dart and #Flutter folks, what are we feeling about code-generation lately? Are you satisfied with the build_runner improvements? Do you want more? Do you still refuse to use codegen, or did you finally start using it?

@jxnlco @henrycunh Minor thing is that I can no longer open a non-repo folder in an IDE from the codex app (the folder is a parent of multiple related repo subfolders)

@henrycunh Let us know how we can do better.

codex app is trending to be the best software i've ever used ridiculous how fast it got so good

@Dimillian Allow me to see archived chats by project

I’m diligently working on enhancing all the features of the Codex app to make it even better for you. If you have any suggestions or ideas for improvement, please feel free to share them with us here!

@Dimillian Fix the bug with automations running on a (parent) folder that is not a git repo. Automation conversations get auto archived and sometimes no content.

@Shpigford Box?

what's the easiest way to layer AI/chat on top of a bunch of documents for a group of people to access? don't need anything fancy, but do need separate/unshared chat sessions. would be hundreds of docs. probably 1m+ words worth of text.

@Zubbyyke @Thedrivenman safety engineering is better

@Thedrivenman Oh my God, did he survive this?😳😳😳! Truly God is Good🙌🙌🙌

Just when everyone believed he was gone, he did the unthinkable

@nank1ro A little feedback. I'm open to a commercial model but it has to include access to the source. It's too risky otherwise.

I know — you haven’t heard much from me lately. I had some doubts about Flutter in 2026, but I’m still all in. I’m about to release something new that solves Flutter styling. It won’t be open source. It won’t be free. 🧵👇

@ah20im Reuse terminal across project threads for the same worktree

What would you like to see in Codex?

@dkundel We need rules for MCP too. I always get asked to approve the Dart MCP format tool.

💡 Codex tip: Rules You can have Codex analyze past conversations. This comes in especially handy if you want to create rules files to have your Codex automations run inside the sandbox without using "full access". Have Codex do the task inside the sandbox and approve requests, then have Codex analyze the past conversation to create a rules file.

@dkundel @raycast The same ability to grab and attach a screenshot as ChatGPT has would be really useful, e.g. iOS simulator

💡 Friday Codex tip: If you are using the Codex app and regularly find yourself copy and pasting text from error messages or plans from other apps into Codex to start a new task, you can use @raycast deeplinks to map it to a hotkey.

@luke_pighetti What's the issue with hot reload with agent using dart MCP? I've had success though only tried with iOS simulator

refusal to trigger flutter hot reload on file save looks pretty dumb now that hot reload is totally broken for agentic coding workflows

@_eseidel @shorebirddev ok, so we'd need to make sure that we don't use any newer features or update packages dependent on the newer features.

@scottbarden @shorebirddev When you build the patch, we'll build it with 3.38.10. If your code still compiles correctly with 3.38.10 it will patch, yes. But if it doesn't, then no it can't be. One would have to make a 3.38.10-ready branch of the code to send that code to the release in question.

Compounding is wild. More new paying customers for @shorebirddev this week than we used to see in a month. 📈

@_eseidel @shorebirddev Does that mean that an installed app that was built with say Flutter 3.38.10 can be patched by shorebird when the updated code is built with 3.41.4?

@scottbarden @shorebirddev The `shorebird patch` command will automatically pull down and use the exact version of Flutter that the `shorebird release` command used when building the initial store release of your app. It remembers and handles the "fvm-like" management for you.

@_eseidel @shorebirddev Could you expand on what you mean by you manage it for us? I guess my concern is that we seem to update versions of Flutter fairly often.

@scottbarden @shorebirddev Correct. We automatically manage that for you.

@0x_cim @dzhng @morganlinton @denisyarats That should be controlled by the scope that you grant the API credentials

@dzhng @morganlinton @denisyarats This works if your API is mostly GET requests or data queries. Imagine giving your agent full API access and it starts making delete requests. Or just drop some rows off your DB. MCP allows you to pick and choose what requests the agent makes without refactoring your backend.

The cofounder and CTO of Perplexity, @denisyarats just said internally at Perplexity they’re moving away from MCPs and instead using APIs and CLIs 👀

@Shpigford Great post. Gonna try it with codex.

here's my full system for hyper-personalizing AI! open.substack.com/pub/everydayis…

@ElmbridgeBC And why do the 3 different car parks have to have different names anyway when they're all charged the same

@ElmbridgeBC can you explain why the car park immediately next to the Weybridge train station isn't the one called the Weybridge Station car park, and why the actual name doesn't show up nearby on the RingGo app? It's like you're setting us up to fail when we try to do it right.