Ben Holmes

14.3K posts

Ben Holmes banner
Ben Holmes

Ben Holmes

@BHolmesDev

The Whiteboard Guy @warpdotdev

Ordering more markers Katılım Eylül 2018
966 Takip Edilen44.3K Takipçiler
Sabitlenmiş Tweet
Ben Holmes
Ben Holmes@BHolmesDev·
Switching from Claude Code to Codex? I made a guide! It covers: • How to migrate your setup • Differences in the Claude Code and Codex CLIs • Prompting tips from my experience using GPT 5.5 to get real work done. It's more different from Opus than you might think
English
4
9
203
21.7K
Ben Holmes retweetledi
Warp
Warp@warpdotdev·
The past 48 hours of Warp open source have been busy. A few strong community PRs are in review now, covering terminal search, SSH history, worktrees, logs, and cloud agent UI. 🧵
English
1
4
37
2.8K
Ben Holmes
Ben Holmes@BHolmesDev·
Here's the quickest way to migrate your Claude Code setup to the Codex CLI, with backwards compatibility:
English
7
6
80
6.5K
TheZero
TheZero@TheZero_yf·
@BHolmesDev what if I want to use gpt-5.5 in Claude code harness? Any suggestions?
English
1
0
0
87
Ben Holmes
Ben Holmes@BHolmesDev·
You should use Codex differently than how you use Claude Code. I've found success with no plans and more involvement as an engineer. Here's a 1 min rundown of my process:
English
14
8
272
22.7K
Ben Holmes
Ben Holmes@BHolmesDev·
@LLMpsycho Yep. Also tend to ask Codex for multiple options whenever I’m even a little unsure. Want to build a habit of having Codex build all 3 options to feel out what’s best too, instead of making a judgment at the plan level
English
0
0
0
189
Bessi
Bessi@LLMpsycho·
@BHolmesDev Codex works better with engineer involvement because prod bugs rarely follow the neat plan.
English
1
0
4
274
Ben Holmes
Ben Holmes@BHolmesDev·
@yourkaisensei Closer to architecture / approach. I will review at the end of a pass and leave comments from @warpdotdev’s code review panel, but won’t edit code myself
English
0
0
0
288
kai
kai@yourkaisensei·
@BHolmesDev Curious where you draw the line on “more involvement” here. Are you mostly steering architecture/approach, or staying close enough to edit the diff as it goes?
English
1
0
0
369
Adam Weston 🤓 :blue-check:
Maybe the @warpdotdev ssh wrapper should be off by default. I don’t need IT reaching out about failed attempts to connect to channels. Love the idea, just think it should be opt in.
English
1
0
1
571
Tom Hosiawa
Tom Hosiawa@thosiawa·
I'm really liking it and have a few feedback items One thing I realized, I'm enjoying @warpdotdev's approach to filing issues and interacting with their oz agent. Would love to see other products use/adopt their oz agent approach @zachlloydtweets eg: github.com/warpdotdev/war…
Tom Hosiawa tweet mediaTom Hosiawa tweet media
Pedro Duarte@peduarte

dictation in the new @raycast is really good - custom instructions for how you want it to be formatted - use context from active app to improve accuracy - custom vocabulary for those tricky words - custom styles for diff processing on diff apps (ie: slack, twitter, email) - dictation history! raycast.com/new

English
2
0
3
1.2K
Tom Hosiawa
Tom Hosiawa@thosiawa·
A feedback forum feels so 2000s now lol
English
1
0
1
66
Ben Holmes
Ben Holmes@BHolmesDev·
@theo I like staying in Warp to have a code review panel, file viewer, and LSP support to go-to definition sometimes. Also getting addicted to Pi’s /tree to jump around points in conversation history
English
0
0
2
543
Ben Holmes
Ben Holmes@BHolmesDev·
@caviterginsoy @TheRealAdamG The Q&A is quite nice! But I find myself going between planning, implementation, discussion, etc very fluidly and forgetting to say what “mode” we’re in. I like just letting it flow. Would be cool for Codex to make Q&A a tool so I don’t need planning to activate it
English
1
0
0
1.3K
Cavit Erginsoy
Cavit Erginsoy@caviterginsoy·
@BHolmesDev @TheRealAdamG You’re missing out. I use it specifically because of the questions it asks that often surface inflection points I hadn’t thought of yet
English
2
0
3
1.4K
Ben Holmes
Ben Holmes@BHolmesDev·
I never use planning mode in Codex. GPT 5.5 loves to research, so I just have a conversation and reach a pseudo-plan in chat. Then, I let it implement, maybe with a /fork beforehand to keep that plan as a revisit-able point. Probably the biggest switch coming from Claude Code
English
55
36
703
134.4K
Ben Holmes retweetledi
Warp
Warp@warpdotdev·
Intro to Warp - terminal basics, Claude Code setup, and cloud handoff with Oz x.com/i/broadcasts/1…
English
0
2
32
2.1K
Ben Holmes
Ben Holmes@BHolmesDev·
So I can use /resume later to go back to the point we first made the plan in the conversation. To be fair, something like /tree in Pi to roll back to the plan is much nicer :)
English
0
0
2
1.4K
Ben Holmes
Ben Holmes@BHolmesDev·
@petradonka This community reply skill has made it so much easier to engage with everyone. Before, it was impossible give everyone the help and attention they deserve. Now it's <30 min out of my day 🙌
English
0
0
3
270
Ben Holmes
Ben Holmes@BHolmesDev·
I shared my full experience switching from Claude Code to Codex here. Really liking it so far youtu.be/Q9p_XtmkCqw ❤️
YouTube video
YouTube
English
1
2
16
6.4K
Ben Holmes retweetledi
Notion Developers
Notion Developers@NotionDevs·
Install ntn, the Notion CLI. It brings the entire Notion API to your terminal, plus everything you need to build and deploy Workers. Built for humans and coding agents alike. Install with: curl -fsSL ntn.dev | bash
English
121
287
3.3K
1.3M