Christ follower | Engineer | Automator I build apps, agents & automations with Codex, Hermes and years of experience. The agents take the night shift.
U.S.A.
- Tweets 13,712
- Following 2,604
- Followers 3,549
- Likes 33,174
Pinned Tweet
My toolbox has gotten weirdly small lately: Claude Code CLI, Codex CLI, and Hermes Agent.
Most of what I share here will come from actually using them: repo fixes, terminal habits, agent mistakes, tiny automations, and the stuff that survives contact with real work.
18
5
109
4,620
"Automation" = removing manual steps
"Agent" = autonomous decision loop
"Pipeline" = sequential task chain
"Workflow" = orchestrated process with conditions
Automation and Agent are not the same thing.
Pipeline and Workflow are not the same thing.
"Agentic" means nothing specific.
The word you pick shapes what you build.
1
16
First thing to get right, before any agent touches your repo:
A clear boundary on what it will not change.
Without that, a helpful automation will expand its own scope and you won't notice until the diff is already wrong.
22
Less than a month ago Anthropic was the laughing stock and OpenAI looked unstoppable. Every timeline take was about who had already won.
Now the roles have completely reversed. Same companies, same people, one release cycle in between, and the entire narrative flipped direction.
This AI cycle moves way too fast for confident verdicts. If your strategy depends on a ranking that holds for a quarter, you are building on something that expires in weeks.
1
1
29
Every new model launches great, so how long until the company quietly nerfs it?
I'd say about two weeks.
46
jsnode retweeted
When the cute little fuzzy fb mascot goes rogue.
Deleted Muse after seeing this post on Threads about how it told some Facebook Marketplace sellers the guy’s address and they showed up at his door
Dangerous and creepy
This would have been 1000x worse if the person was a woman
1
2
97
8 tools in my agent stack:
1. Codex
2. Hermes
3. Claude Code
4. Cursor
5. plugin.json
6. AGENT_RECEIPT.md
7. MCP configs
8. a cold replay test
Which one would you pull out first?
4
8
102
The demo is the cheapest part of any agent you build.
The expensive part shows up three weeks later, when a scheduled job drifts and nobody owns the prompt.
I still build custom ones. I just budget for the maintenance now instead of pretending it's free.
1
1
4
57
How I actually structure an agent workflow in 2025:
- Codex: code changes
- Hermes: devotional content pipeline
- plugin.json: shared safety config
4
6
85
I almost shipped an agent pipeline that touched files it had no business touching. Stopped it.
Rebuilt the permission layer. Then rebuilt it again.
The safety boundary has to stay explicit.
2
4
53
I still like coding, but I don’t feel the need to write every line myself.
I’d rather spend more time figuring out how the app should work and whether we actually need everything we’re asking AI to build.
I was one of those nerds.
You've missed the way I'm adapting to AI, which is by moving *up* the stack rather than down. My job is design and specification now, not coding.
I was a hand-coder for nearly 50 years. I find I miss it surprisingly little. I guess I was a designer after all.
4
6
97
A model can look smarter when the test setup is doing a lot of the work for it.
Tony found his Tetris setup was preparing the best options for both models. Without that help, Jev struggled.
I don’t mind the extra help. I just want demos to show what the model actually figured out and what was already done for it.
Ok I made a mistake.
The game harness was doing a lot of heavy lifting for both models by preparing optimal options for Jev/Haiku to pick from, given a game state.
If I change the harness to provide only game rules and game state, and only allow Jev to decide the control buttons (left/right/rotate/drop), it pretty much becomes useless.
2
3
92
Ethan Mollick had Claude make an educational recursion video with scenes drawn in React and SVG, plus music and sound effects synthesized in Python.
The source code gives the next revision somewhere precise to go.
A weak scene can be changed without regenerating the whole piece, and the implementation becomes part of the handoff.
How do you explain recursion? This one is pretty fun.
I had Claude Opus 5.5 make: "A video explaining recursion, where every explanation about recursion has a radically different video style, make this self-referential & clever & fast moving."
Nine genre shifts, one prompt...
4
89
amirmushichge turned a demo for building walkable Unreal Engine spaces from room photos into a public Codex skill.
The repository carries the sequence, prerequisites, and checks with the result, so another builder can run it and find where the workflow breaks. Reusable instructions make a technical demo easier to inspect and improve.
github.com/amirmushichge/unr…
3
55
Generating several complete websites before choosing one is a good use of cheap design generation. It gives you real alternatives instead of a long chain of tweaks to the first draft.
The assembly still needs care. If the homepage, about page, and services page come from different directions, typography, spacing, navigation, and calls to action need one final pass as a system.
Huge hack if you're rebuilding your website:
Use Claude Design, but don't ask it for one site. Ask for five.
That's how I built my current site in about 20 minutes of generation time:
-Told Claude Design: "build me 5 full different websites. Same branding, same colors, use my design system, totally different layouts."
-Took the homepage from design 1, the about page from design 3, the services page from design 4
-Pushed the mockup to Claude Code to wire in podcast episodes and an email capture connected to my ESP
-One-click deployed it
It runs on Astro instead of WordPress, which is lighter and more AI-friendly.
I find myself using Claude Design more and more and really feel like it's one of the most underrated Claude products.
1
82
