Dev turning marketer via evolutionary psychology | My MCPs replaced 7 Google & Meta dashboards so I can focus on tracking user journeys back to ads @cavemanaiq
@thsottiaux To plan and discuss about everything in life I do claude
To go to war in a legacy backend codebase I do codex
Claude I would share a beer at a bar
Codex I would share a cigarette in the trenches
Tribalism is innate to human nature and this field is no different
@drugshipping I do fast 18 hours a day and drink copious amounts of coffee. Still anecdotal, but the love handles I got from age 25 were lost in 2 weeks at age 35 when I went low carb. Excess fat sent out of a liver to it's neighbouring area when it cannot handle fructose and glucose breakdown
I have some feelings on this
Are you familiar with the research from noakes, koutnik and d' Agostino?
For workouts lasting an hour or less, they say carbs are often unnecessary. Even during longer sessions, as little as 10 grams of carbohydrate per hour may be enough.
https://t.co/Ihd1Y3HM3t
@Ironmute Also consider walking does not tax the body as cardio. It's considered part of non exercise activity thermogenesis and my anecdotal evidence is it does not increase my appetite at all if any
@Ironmute For my 62kg frame I have calculated 23kcal per 1000 steps. You need to consider speed and subtract resting metabolic rate for the time needed to take these steps
@mattpocockuk@AidenAllred2 I'm also getting this randomly in some sessions while always run medium thinking. Sometimes though can get it even at 18-20% context
@tirupathipodugu As long as you can constantly track where each agent harness writes during active sessions of after, e.g codex has independent background thread even when inactive.
Removing stale or superseded memories is another headache.
How Claude Code and Codex share one project on one machine, step by step.
- Shared state lives in git
- Reviewed facts and handoffs in the repo
- Claims mark which handoff and which worktree a session is using
@weswinder I hear you.
Here's what I run on one machine for Claude and Codex on the same repo.
Give it to your agent as a step guide and try to replicate:
https://t.co/qEEniVLCt9
How Claude Code and Codex share one project on one machine, step by step.
- Shared state lives in git
- Reviewed facts and handoffs in the repo
- Claims mark which handoff and which worktree a session is using
Limits
- Claude sessions message each other directly
- A Claude session can queue a message into a Codex chat with codex queue; proven in Codex Desktop, untested in a terminal
- Codex has no way to message Claude
- A session that loads no handoff holds no claim
Memory between sessions
- Claude and Codex keep separate native memory, never merged
- At startup a hook flags what changed in either one
- The agent copies only verified, lasting facts into the repo's shared memory, and Git carries them to the next session