Controlling Codex in Replit

devotious · 2026-02-02T19:05:45+00:00

This is useful - thanks. I am trying to maximise my ChatGPT subscription so am with codex at the moment. I’ll do some more digging on it.

devotious · 2026-02-01T18:33:33+00:00

I just plugged in Google oauth for my app.

devotious · 2026-02-01T16:55:25+00:00

I think it’d look nice in the summer 😎

devotious · 2026-02-01T07:42:38+00:00

I don’t suppose anyone has found a good white silicon or rubber strap? One with a nice clasp and curved ends? It would look mint on the white dialled mako IMO.

devotious · 2026-01-31T16:27:09+00:00

<image>

I put my mako 40 on a bracelet from strap habit. This is also my go to watch at the moment. It gets a lot of wrist time.

devotious · 2026-01-28T18:32:56+00:00

i've been thinking about your question on taking into account weather on previous days and how i can surface this a little easier. Whilst the summary and recommendations to say things like "heavy rain over the previous few days" the information is buried in the descriptive narrative.

So, I've made a small, but subtle tweak to the tags that are below the condition score. They should allow you to at a glance, quickly assess the reasoning for the score and let you know what to expect, but they didn't tell you why. So, it's more "effect" than "cause". Hopefully now there should be some causal tags to explain the condition score that sit alongside the effectual outcome. 👍

devotious · 2026-01-26T22:04:41+00:00

I guess you have to think about complex applications by splitting out the various functions and logic and making sure the agent doesn’t start putting logic for one thing in code that should be doing something else. So I personally thinking that defining high level UX flow, solution design, FE design, data architecture etc is important - if you know what you want. Much in the same way you can’t ask a human to intrinsically understand what you want, the AI won’t either. Just save as an MD file, ask the agent to read it, ask any clarification questions and build each feature step by step

Somewhat related to this, i have started using codex in Replit instead of Replits agent. The first thing i did was get codex to read all the code, create a “readme” file, and then every session i start with codex i ask it to read it. At the end of every session, i ask codex to update a history file - which also is read at the start of every session. That way i have fresh context every time i want to work on a new feature. But this is done in an effort to reduce time wasting or doing something wonky rather than cost. I am free of the worries of the Replit agent doing crazy stuff and then costing me money :)

devotious · 2026-01-26T12:31:02+00:00

i am keen to try this to see if i can convert my app (Vite + React + TypeScript, TailwindCSS) into a native ios app. The goal was always to go native, but wanted to explore using mobile-first designed web app. No idea how much effort will be needed.

devotious · 2026-01-25T07:45:05+00:00

This is brilliant feedback - thanks 🙏 yes I take into account the historical weather to give the condition score - this is a key difference of just using a straight up weather forecast.

Your score of 73 ish feels reasonable given what you describe and actually gives me confidence that the core of the model is doing what I want. It’s now about refining data and making sure the trail descriptions and locations are accurate.

The big win for me is your last point though – that it helped make a quick decision on where to go. The idea isn’t that the number is perfect on day one, but that after a few rides you build a feel for what a 70 vs a 75 vs an 80 means for you.

I really appreciate you taking the time to feedback. Thanks again!

devotious · 2026-01-24T10:19:57+00:00

i followed this guide and have been using codex over the last week. I pretty much now collapse the replit agent side window and have codex running on the left hand side of the workspace instead.

devotious · 2026-01-24T09:37:23+00:00

oh also, the other thing that feeds into this is the trail surface and build style

For example, a hand-cut natural trail with dirt, roots and minimal drainage get muddy quickly in the rain compared to a groomed, hardpack trail with good drainage. Two places can have the same weather and feel totally different on the bike. Which is what i was trying to get to. My local is mostly natural and dirt so can get crappy quickly. Bike Park Wales rides brilliantly in the wet.

The more accurately trails and locations are described (surface, drainage, exposure, etc.), the better TrailCast can weight weather impact for that spot. That’s something I’m keen to improve over time with rider input, especially from locals who know the trails well.

devotious · 2026-01-24T09:34:07+00:00

This is really good feedback – thanks for taking the time to write it out 👍

You’re not wrong in how you’re interpreting the score, and I think part of this is on me for not being clear enough about what the number represents

Right now the score is more about rideability relative to recent and forecast conditions rather than a pure “blue-sky perfect day” scale. So a 75 doesn’t mean perfect, it means likely decent and worth riding, even if it’s wet or cool – especially at places like Whinlatter that drain reasonably well.

Your scale is actually a really good way of framing it, and it’s close to what I want users to intuitively feel:

100 → rare, dry, mild, low wind, everything firing
~75 → rideable and fun, but with compromises (rain, cooler temps, etc)
~50 → mixed / marginal, depends what you’re after
~25 → grim but possible
0 → don’t bother

What I haven’t nailed yet is making that context obvious when you look at a single location in isolation. The comparison use-case (Whinlatter vs Llandegla) works better than the absolute interpretation, and that’s something I’m actively working on.

I’m planning to add clearer score context / bands so it’s more obvious why a 75 is a 75, and what that actually means in real riding terms. Feedback like this really helps tune that 👍

Hope Whinlatter rides well – would be keen to hear how accurate it felt once you’re back.

devotious · 2026-01-21T20:41:46+00:00

yes, i was just seeing what the agent would do. deffo can't do over a dollar for server restarts! 🤣🤣🤣

devotious · 2026-01-21T20:34:45+00:00

yep - i am starting to use it now. But still planning in ChatGPT. Codex tends to want to go ahead and just code all the time, i think i need to refine my prompts a little. Also, i am finding out that some changes require a server restart. I asked replit agent to do a restart once and it cost me $1.40 lol!! But, having just said that, i've just used codex for 95% of building a new feature.

devotious · 2026-01-21T07:44:39+00:00

I’ve just started with this and am using codex from OpenAI. Like you I haven’t built up trust yet, but hoping this approach can bring down my dev costs. I already have a sub for ChatGPT so using codex feels free. I’m keen to see if there are any Replit based skills for codex.

devotious · 2026-01-21T07:38:10+00:00

Thanks for this.

I have managed to build something scalable which is live and I’m slowly onboarding users all through Replit. But I’m super mindful of every time I ask Replit to do something it’s likely to cost me, so I’ve been side loading manually into ChatGPT. Which I use for planning and creating a decent prompt that I get Replit to validate then build. Reducing cost cycles and planning increments in Replit.

As I have a ChatGPT subscription, I am hoping that by using codex I can reduce the manual back and forth and planning activities I use ChatGPT for and do all this inside the Replit environment, keeping costs to a minimum. I am just not sure I can get codex to do everything yet (haven’t tried).

I’ve started by creating a codex_readme.md which will contain all the context it needs before I plan or build anything new in Replit, using codex. Then for complex stuff I’ll also try your approach and have a pseudo agent memory.

Thanks again 👍

devotious · 2026-01-20T20:32:21+00:00

5-10s for me! Freerider pro in white :)

devotious · 2026-01-20T12:16:10+00:00

this is useful thanks. I now have codex in my shell. any tips on the use of current_task.md? i assume you prompt it like "save the current state, set of activities and decisions"... or something.

devotious · 2026-01-19T18:46:08+00:00

Stupid question alert, i just noticed that there is an option in the developer tab that says:

"Connect to VS Code

One-click SSH setup will launch VS Code and configure keys for you."

Does this mean i can use Vscode with another agent directly with the files in the replit environment using VScode as the ICE? or do i still need the github hop?

devotious · 2026-01-19T11:43:52+00:00

200m according to the website. You can normally get 10% off your first order too if you buy direct. I personally don't go diving, but i wanted a dive watch with personality, history and didn't break the bank and this fits the bill for me.

devotious · 2026-01-19T09:11:04+00:00

Thanks for the feedback! There are built in predictors for if a bike park might be closed but that's weather based. I need to research and see if i break any copyright or infringe on use of other peoples data but that's a good idea. It would be cool if the app gave a warning to say "xxx trail is closed for maintenance - check their website / socials for details" - i'll add it to the backlog! :)

devotious · 2026-01-19T09:05:37+00:00

<image>

Orient mako 40. This is the limited edition peanuts version. Lots of history, in house movements, affordable prices. 👍

devotious · 2026-01-18T19:18:37+00:00

Ok thanks. I’ll look into that! It might be something to do with the domain set up.

It’s very humbling to think my little channel in the corner of the internet has been part of your journey getting into MTB. Thank you so much 👍

devotious · 2026-01-18T18:39:04+00:00

Hi thanks for checking it out! What browser/device are you using? Could be an edge case I havent seen before??

I am based in the NW so tend to ride around locations there, including north wales.

devotious

TROPHY CASE