This post was written inside a Claude Code session and posted directly to feld.com as a draft. Not copy-pasted. Not emailed to myself. I just typed /blog-feld in iterm2 and it showed up on my blog.

Setting this up took about ten minutes.

I asked Claude to figure out how to connect to feld.com (hosted on WordPress.com) for direct posting. It researched three approaches: the WordPress.com REST API, the official WordPress MCP connector, and the WordPress plugin MCP Adapter. The WordPress MCP connector is read-only (so, useless for posting). The MCP Adapter only works on self-hosted WordPress (not WordPress.com). That left the REST API with OAuth.

Claude wrote a command called /blog-feld that handles the workflow: look at whatever I’ve been discussing in the current conversation, assemble it into a post, show me a summary, interactively edit with me, and then push it to feld.com as a draft.

It never publishes directly — I still review everything in the WordPress editor before hitting publish.

For authentication, WordPress.com requires OAuth. Normally, my experience setting this up is tedious. In this case, Claude just told me what to do step by step.

– I registered an app at developer.wordpress.com (Client ID + Secret)
– Claude set up the authorization code flow.
– I visited a URL, clicked “Approve,” and the browser redirected to localhost with an authorization code in the URL.
– The page itself didn’t load, but the code was sitting right there in the address bar.
– I screenshotted the page and pasted it into iterm2, and Claude exchanged it for an access token.

Done.

To verify it worked, Claude pulled my last three posts from the API. “Tech I’m Obsessed With,” “Blurry Transitions,” and “Interview With Guy Kawasaki.”

This is a small thing, but it’s the kind of small thing that changes behavior. Every day as I work with Claude Code, I think of multiple things like this. Instead of waiting for someone else to implement it or paying for a third-party service, I just create it in Claude Code and make it a permanent part of my environment.

I’ve been writing more inside Claude Code sessions anyway — working through ideas, editing, and iterating. The friction was always the last step: copy the text, open WordPress, paste it in, format it, fix the formatting that broke. Now that step is gone.

Thinking-in-conversation and writing-for-the-blog are the same thing.

I love getting emails from Ben Casnocha. Short, sweet, and to the point. Today’s was “what tech are you obsessed with now? Saw your blog post…” I wrote a response and then realized it was a good answer to my tease from my previous blog post (Blurry Transitions) about what I was exploring. The only thing I removed was my ad hominem comments on various tech companies, since that’s not that interesting to me. And, I fixed some … typos.

Here are a few hints: IntensityMagic and an image of my computer screen (the one above).

I decided I really wanted to understand how AI coding works. I’ve been deeply involved in a few shifts in the past (Agile software development, user-generated content (RSS), email everything (SMTP), … and, if you go back far enough, Feld Technologies was all about shifting from minicomputer business systems to PC-based network database systems). In all cases, I had to “do stuff” to understand it and form a viewpoint, given all the BS and marketing in tech.

I wanted to see if I could create a zero-employee company, aside from the CEO and CTO. Daniel (Feld) is the CEO. I’m the very part-time CTO. I’ve created a thing called CompanyOS, which is IntensityMagic’s AI-powered business operations system. It’s designed around the premise: “Run 100% of a company’s business operations through Claude Code. Two people, multiple Claude agents, zero employee overhead.”

At the core, I’ve gone extremely deep on Claude Code and everything around it.

– I think “vibe coding” is nonsense – it’s just prototype development and a different flavor of no-code software, which is useful but not compelling for scaled applications.

– There are $x billions of VC who have funded what are effectively wrappers on AI and/or point solutions that can be made obsolete overnight. 

– Most companies that try to integrate “AI coding” into what they are doing are struggling because they haven’t figured out the tooling, which is not just “turn on Github Copilot” or “use Cursor.”

It’s much easier to experiment deeply with “no employees” and “no legacy stuff,” so that’s what I’m doing. I’m viewing it as a video game, and I’m on level 19. It’s awesomely fun.

Turning 60 in December marked an important moment for me. A key section from that blog post was:

“I’ve definitely shifted into a new mode over the past year. I’m still on a bunch of boards for Foundry and deeply involved in several companies. But I’m much less focused on the broader technology industry, uninterested in many of the things that are going on, and tired+bored of the arc the narrative about technology and society has taken.”

Amy and I spent the last six weeks in New Zealand and Australia for my 60th birthday trip. I went into hibernation as part of that, stopped doing anything public-facing, and flipped to default no. I also stopped blogging, engaging with social media, and reading the news.

It gave me a lot of time to think and reflect. One thing that I realized was that I’ve never had a hard break or a clean transition from one thing to another. I have multiple threads of this, but if I just choose a professional one, here’s an example.

– I started my first company while in college.
– I started making angel investments while working for the company that acquired my first company.
– I became a VC while I was still founding companies and making angel investments.
– I co-founded Techstars and Foundry while still managing the legacy Mobius funds.
– I started writing books as a VC.

I did a similar exercise on technologies that interested me and generated long investment arcs (which we used to call themes at Foundry). There was usually a trigger point that created a new theme, where I became obsessed with a new technology of some sort and went very deep into it as a user and investor. These overlapped and fed off each other multiple times.

Basically, I’ve never had a “clean break” or a hard transition from what I was doing to what I did next.

I’m enjoying another one of these blurry transitions. I’ve found the new technological thing I’m obsessed with. While I’ve played with this new thing over the past year, I spent a lot of time with it over the last two months. And my interest (and competence and understanding) is accelerating.

I also realized that I missed writing. I know that I learn by reading and writing. I don’t learn by listening and talking (or at least not very much). I have to actually write things down. And, my new obsession involves a lot of writing…

Historically, I’ve gotten a lot of feedback on ideas by writing publicly. It’s also more helpful to me, as it has generated a ton of randomness on many dimensions. And, if you’ve read Give First: The Power of Mentorship, you know that many of the successful things I’ve been involved in came from this randomness.

So, I’ll be writing publicly more. I’ve consciously decided that is not part of hibernating.

• #chai
• #guy kawasaki

When I was 17, I knew of four people at Apple Computer: Steve Jobs, Steve Wozniak, Al Eisenstat, and Guy Kawasaki. I loved my Apple ][ (not a +, 48k, with an Integer Card, two floppy disks). By this point, I was spending a lot of time on my high school buddy Kent Ellington’s TI PC (pre-release – his dad was the production manager), but my Applie ][, now with a Z-80 card, sat in the corner of our family room and consumed a lot of my time.

Of the four, I’ve met all but Steve Jobs in person. Al Eisenstat was the first, on a trip to Cupertino with my parents, where I was supposed to meet Steve Jobs, but Al greeted me and spent a meaningful 30 minutes with me instead. Woz was next and we ended up investing (via Mobius) in one of Woz’s companies (called … Woz – it was ahead of its time).

I’ve long admired Guy and we have lots of second-degree-of-separation friends. One of them, Buzz Bruggerman, came up to me after a Give First: The Power of Mentorship talk in Seattle this summer and asked if I knew Guy and had ever been on his podcast. I said, “Nope, but I just listened to the one with Ben Gilbert that Guy did.”

In typical Buzz fashion, I had an email connecting me to Guy within a few minutes, and we quickly set up a time to do a podcast. I did it sitting outside at Rancho Valencia on a sunny day, was in a great mood, and at the very end of the podcast grind for the book promotion.

The podcast is now up at Building What Lasts: Brad Feld on Trust, Mentorship, and Long-Term Thinking.

It was special. It starts off fast. We learn about Guy’s early dating history with Al Eistenstat’s daughter. We talk about Heidi Roizen and Atherton. And then Guy is the very first person to make the link between the 18 items in the Techstars Mentor Manifesto, Chai, the important number 18, and entrepreneurial Tzedakah. All within the first ten minutes.

Enjoy!

And Guy – that was a delight.